Skip Menu |

This queue is for tickets about the Mail-IMAPClient CPAN distribution.

Report information
The Basics
Id: 128913
Status: rejected
Priority: 0/
Queue: Mail-IMAPClient

People
Owner: Nobody in particular
Requestors: dailylama [...] gmail.com
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)



Subject: Fwd: Undeliverable: Mail::IMAPClient
Date: Fri, 22 Mar 2019 12:26:01 +0200
To: bug-Mail-IMAPClient [...] rt.cpan.org
From: Afanasiy Fet <dailylama [...] gmail.com>
have you checked if message_to_file is correctly saving messages to file which have attachment-files with utf8 filenames? I'm getting error from this: $obj->message_to_file("$temp", $msg) my $message = $temp->slurp; Email::MIME->new($message); Show quoted text
---------- Forwarded message --------- From: <postmaster@kernengroup.com> Date: Fri, Mar 22, 2019 at 8:55 AM Subject: Undeliverable: Mail::IMAPClient To: <dailylama@gmail.com> Your message to imap@kernengroup.com couldn't be delivered. imap wasn't found at kernengroup.com. dailylama Office 365 imap *Action Required* Recipient Unknown To address How to Fix It The address may be misspelled or may not exist. Try one or more of the following: - Send the message again following these steps: In Outlook, open this non-delivery report (NDR) and choose *Send Again* from the Report ribbon. In Outlook on the web, select this NDR, then select the link "*To send this message again, click here.*" Then delete and retype the entire recipient address. If prompted with an Auto-Complete List suggestion don't select it. After typing the complete address, click *Send*. - Contact the recipient (by phone, for example) to check that the address exists and is correct. - The recipient may have set up email forwarding to an incorrect address. Ask them to check that any forwarding they've set up is working correctly. - Clear the recipient Auto-Complete List in Outlook or Outlook on the web by following the steps in this article: Fix email delivery issues for error code 5.1.10 in Office 365 <https://go.microsoft.com/fwlink/?LinkId=532972>, and then send the message again. Retype the entire recipient address before selecting *Send*. If the problem continues, forward this message to your email admin. If you're an email admin, refer to the *More Info for Email Admins* section below. *Was this helpful? Send feedback to Microsoft <https://go.microsoft.com/fwlink/?LinkId=525921>.* ------------------------------ More Info for Email Admins *Status code: 550 5.1.10* This error occurs because the sender sent a message to an email address hosted by Office 365 but the address is incorrect or doesn't exist at the destination domain. The error is reported by the recipient domain's email server, but most often it must be fixed by the person who sent the message. If the steps in the *How to Fix It* section above don't fix the problem, and you're the email admin for the recipient, try one or more of the following: *The email address exists and is correct* - Confirm that the recipient address exists, is correct, and is accepting messages. *Synchronize your directories* - If you have a hybrid environment and are using directory synchronization make sure the recipient's email address is synced correctly in both Office 365 and in your on-premises directory. *Errant forwarding rule* - Check for forwarding rules that aren't behaving as expected. Forwarding can be set up by an admin via mail flow rules or mailbox forwarding address settings, or by the recipient via the Inbox Rules feature. *Recipient has a valid license* - Make sure the recipient has an Office 365 license assigned to them. The recipient's email admin can use the Office 365 admin center to assign a license (Users > Active Users > select the recipient > Assigned License > Edit). *Mail flow settings and MX records are not correct* - Misconfigured mail flow or MX record settings can cause this error. Check your Office 365 mail flow settings to make sure your domain and any mail flow connectors are set up correctly. Also, work with your domain registrar to make sure the MX records for your domain are configured correctly. For more information and additional tips to fix this issue, see Fix email delivery issues for error code 5.1.10 in Office 365 <https://go.microsoft.com/fwlink/?LinkId=532972>. Original Message Details Created Date: 3/22/2019 6:54:32 AM Sender Address: dailylama@gmail.com Recipient Address: imap@kernengroup.com Subject: Mail::IMAPClient Error Details Reported error: *550 5.1.10 RESOLVER.ADR.RecipientNotFound; Recipient imap@kernengroup.com <imap@kernengroup.com> not found by SMTP address lookup* DSN generated by: MWHPR1701MB1872.namprd17.prod.outlook.com Message Hops HOP TIME (UTC) FROM TO WITH RELAY TIME 1 3/22/2019 6:54:45 AM mail-lj1-f171.google.com SMTP 13 sec 2 3/22/2019 6:54:45 AM mail-lj1-f171.google.com xx1.develooper.com ESMTPS * 3 3/22/2019 6:55:13 AM xx1.develooper.com localhost SMTP 28 sec 4 3/22/2019 6:55:14 AM localhost localhost ESMTP 1 sec 5 3/22/2019 6:55:14 AM xx1.develooper.com mx3.develooper.com ESMTPS * 6 3/22/2019 6:55:15 AM mx3.develooper.com CO1NAM05FT045.mail.protection.outlook.com Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 1 sec 7 3/22/2019 6:55:15 AM CO1NAM05FT045.eop-nam05.prod.protection.outlook.com DM5PR17CA0057.outlook.office365.com Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) * 8 3/22/2019 6:55:16 AM DM5PR17CA0057.namprd17.prod.outlook.com MWHPR1701MB1872.namprd17.prod.outlook.com Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 1 sec Original Message Headers Received: from DM5PR17CA0057.namprd17.prod.outlook.com (2603:10b6:3:13f::19) by MWHPR1701MB1872.namprd17.prod.outlook.com (2603:10b6:301:1d::18) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1730.18; Fri, 22 Mar 2019 06:55:16 +0000 Received: from CO1NAM05FT045.eop-nam05.prod.protection.outlook.com (2a01:111:f400:7e50::203) by DM5PR17CA0057.outlook.office365.com (2603:10b6:3:13f::19) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1730.15 via Frontend Transport; Fri, 22 Mar 2019 06:55:15 +0000 Authentication-Results: spf=softfail (sender IP is 207.171.7.185) smtp.mailfrom=gmail.com; kernengroup.com; dkim=pass (signature was verified) header.d=gmail.com;kernengroup.com; dmarc=pass action=none header.from=gmail.com; Received-SPF: SoftFail (protection.outlook.com: domain of transitioning gmail.com discourages use of 207.171.7.185 as permitted sender) Received: from mx3.develooper.com (207.171.7.185) by CO1NAM05FT045.mail.protection.outlook.com (10.152.96.159) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1750.4 via Frontend Transport; Fri, 22 Mar 2019 06:55:15 +0000 Received: from xx1.develooper.com (xx1.dev [10.0.100.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx3.develooper.com (Postfix) with ESMTPS id 63FB646F for <imap@kernengroup.com>; Thu, 21 Mar 2019 23:55:14 -0700 (PDT) Received: from localhost (xx1.develooper.com [127.0.0.1]) by localhost (Postfix) with ESMTP id 5047E7CEEC for <imap@kernengroup.com>; Thu, 21 Mar 2019 23:55:14 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on mx3.develooper.com X-Spam-Status: No, score=-2.0 required=6.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.1 Received: from xx1.develooper.com (xx1.develooper.com [127.0.0.1]) by localhost (Postfix) with SMTP id 34B5C7CED0 for <imap@kernengroup.com>; Thu, 21 Mar 2019 23:55:13 -0700 (PDT) X-CPAN.org: This message routed through the cpan.org mail forwarding service. Please use PAUSE pause.perl.org to configure your delivery settings. Received: from mail-lj1-f171.google.com (mail-lj1-f171.google.com [209.85.208.171]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by xx1.develooper.com (Postfix) with ESMTPS id 527F37CF29 for <DJKERNEN@cpan.org>; Thu, 21 Mar 2019 23:54:45 -0700 (PDT) Received: by mail-lj1-f171.google.com with SMTP id j89so1120026ljb.1 for <DJKERNEN@cpan.org>; Thu, 21 Mar 2019 23:54:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:reply-to:from:date:message-id:subject:to; bh=jft1d6Rr+SEuQh1NWPDttvULCjvq29cl/3E9jK5w90U=; b=JPCxeZpwB7ib2A5wG20RnXam/zja0YXAT71QWHs97vmRdCtV72cWAFZKGJZ3SFCYkO 0aQiEUYozlKCDqnFZzmWYEC8vrA2moWzij38VbXqryQie8dpgwBPCRnacPOx+rIpvmSB nDcv1nVjimOAs8MGj0epIeh+rvIlkNWfIiGi41pIKe/KWpQRPJjO7MUnWuzardhZ96kg aIospjWljDcZ+3mRdxf9asz8fw7T5++SO5cmENWbBDsSTahOn4IyuX30o5faUITCrGQX 0IDaywmtsSYHB1tKJlZ3qOnjvAMGuJoln5oXRyG/oa9l8jA+PPknEqeBUZdOB6+tCheC 38iA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:reply-to:from:date:message-id :subject:to; bh=jft1d6Rr+SEuQh1NWPDttvULCjvq29cl/3E9jK5w90U=; b=gI1B7EH+Tlg7LKkpyssyFonk8YVWs9vgKOuOFMDCTcbw2Pwshq8CeJ54KMx3yFkk/R NnBCITrb/X1eQ3FP4SdkhuAorz43nMn5FbDD03RfADP617pKCc/1siCYw6Rqp0DbDqNF 5pBDqQL51onjLWtGasC/edn6UOuCZ8F7+yuZIuZ6QuY9WI8Wk+FnMWPosTSRd18TOJ9b drZL4U0vm6gJ3OdAyUmPYoq36fBV1RJzIHMyeyxpdPVDhS/nb7E3YyqEeJ1ZTrdyAIQ4 n24EkV2w8r/f/Dm5UXcT/3kZBiBTJHeHOcMT2Clnq8bbOnq47ANr1b7Tl8anzWoAt6xL tu+Q== X-Gm-Message-State: APjAAAVmjfiSWaJ+aEdhPcaZWd4iRvjKsxopI/EOxRJUYqF4MRMC72L3 b9CLz+LDDoo99C5WJgcym0IC058X/uUS/HKOjyr8/JJZnKI= X-Google-Smtp-Source: APXvYqw/POBFbIFyIf2JJTdl32ebSfKMMV7QwboCbspqT6RKlMzdqk2ppO3URlkL5Tgn18w61Y/N9yHZwE0nVDUd0d4= X-Received: by 2002:a2e:87d8:: with SMTP id v24mr2142580ljj.172.1553237683454; Thu, 21 Mar 2019 23:54:43 -0700 (PDT) MIME-Version: 1.0 Reply-To: dailylama@gmail.com From: Afanasiy Fet <dailylama@gmail.com> Date: Fri, 22 Mar 2019 08:54:32 +0200 Message-ID: <CADJk8Zekx18dzav6XDtXqVrnqMNSxVbRtGdOefBikJo7wO=2nA@mail.gmail.com> Subject: Mail::IMAPClient To: DJKERNEN@cpan.org Content-Type: text/plain; charset="UTF-8" X-PMX-Version: 5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2019.1.28.225115 X-PMX-Spam: Gauge=IIIIIIII, Probability=8%, Report=' HTML_00_01 0.05, HTML_00_10 0.05, BODYTEXTP_SIZE_3000_LESS 0, BODYTEXTP_SIZE_400_LESS 0, BODY_SIZE_1000_LESS 0, BODY_SIZE_100_199 0, BODY_SIZE_2000_LESS 0, BODY_SIZE_5000_LESS 0, BODY_SIZE_7000_LESS 0, CT_TEXT_PLAIN_UTF8_CAPS 0, DKIM_ALIGNS 0, DKIM_SIGNATURE 0, NO_CTA_URI_FOUND 0, NO_URI_FOUND 0, NO_URI_HTTPS 0, REPLYTO_SAMEAS_FROM 0, SMALL_BODY 0, SPF_PASS 0, WEBMAIL_SOURCE 0, __CT 0, __CT_TEXT_PLAIN 0, __DKIM_ALIGNS_1 0, __DKIM_ALIGNS_2 0, __DQ_NEG_HEUR 0, __DQ_NEG_IP 0, __FRAUD_WEBMAIL 0, __FRAUD_WEBMAIL_FROM 0, __FRAUD_WEBMAIL_REPLYTO 0, __FROM_GMAIL 0, __FUR_RDNS_GMAIL 0, __HAS_FROM 0, __HAS_MSGID 0, __HAS_REPLYTO 0, __HELO_GMAIL 0, __MIME_TEXT_ONLY 0, __MIME_TEXT_P 0, __MIME_TEXT_P1 0, __MIME_VERSION 0, __NO_HTML_TAG_RAW 0, __PHISH_SPEAR_STRUCTURE_1 0, __PHISH_SPEAR_SUBJ_SUBJECT 0, __RDNS_WEBMAIL 0, __REPLYTO_SAMEAS_FROM_ACC 0, __REPLYTO_SAMEAS_FROM_ADDY 0, __REPLYTO_SAMEAS_FROM_DOMAIN 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __TO_NO_NAME 0, __X_GOOGLE_DKIM_SIGNATURE 0, __YOUTUBE_RCVD 0, __zen.spamhaus.org_ERROR ' Return-Path: dailylama@gmail.com X-EOPAttributedMessage: 0 X-EOPTenantAttributedMessage: 11a05a03-8d9a-450d-86cd-8bac2174142d:0 X-Forefront-Antispam-Report: CIP:207.171.7.185;IPV:NLI;CTRY:US;EFV:NLI; X-MS-PublicTrafficType: Email X-MS-Office365-Filtering-Correlation-Id: 4991fc60-e905-4838-3484-08d6ae93566c X-Microsoft-Antispam: BCL:0;PCL:0;RULEID:(2390118)(7020095)(4652040)(5600127)(711020)(4605104)(4709054)(1401299)(8001031)(1421009)(1402095)(71702078);SRVR:MWHPR1701MB1872; X-MS-TrafficTypeDiagnostic: MWHPR1701MB1872:
---------- Forwarded message ---------- From: Afanasiy Fet <dailylama@gmail.com> To: DJKERNEN@cpan.org Cc: Bcc: Date: Fri, 22 Mar 2019 08:54:32 +0200 Subject: Mail::IMAPClient have you checked if message_to_file is correctly saving messages to file which have attachment-files with utf8 filenames?

Message body is not shown because it is too large.

The question was: Show quoted text
> have you checked if > > message_to_file > > is correctly saving messages to file which have > attachment-files with utf8 filenames?
I may be missing the point of the question here, but the content and/or number of attachments to a message has no bearing on the behavior of message_to_file. If you disagree, please provide some support to back up the disagreement. Thanks!
Subject: Re: [rt.cpan.org #128913] Fwd: Undeliverable: Mail::IMAPClient
Date: Sat, 23 Mar 2019 10:51:19 +0200
To: bug-Mail-IMAPClient [...] rt.cpan.org
From: Afanasiy Fet <dailylama [...] gmail.com>
I'm trying Email::MIME->new() on the file which was saved by message_to_file() An issue with utf8 filename is closed (perhaps bug fixed) here: https://github.com/rjbs/Email-MIME/issues/18 why I'm guessing only source of problem is message_to_file. Also I found that message_to_file(path) does not flush the Path::Tiny::tempfile, but does flush with filehandle as parameter. No documentation if is there is sorts of threading going on behind the scenes On Fri, Mar 22, 2019 at 7:45 PM Phil Pearl (Lobbes) via RT <bug-Mail-IMAPClient@rt.cpan.org> wrote: Show quoted text
> > <URL: https://rt.cpan.org/Ticket/Display.html?id=128913 > > > The question was: >
> > have you checked if > > > > message_to_file > > > > is correctly saving messages to file which have > > attachment-files with utf8 filenames?
> > I may be missing the point of the question here, but the content and/or number of attachments to a message has no bearing on the behavior of message_to_file. > > If you disagree, please provide some support to back up the disagreement. Thanks!