Skip Menu |

Preferred bug tracker

Please visit the preferred bug tracker to report your issue.

This queue is for tickets about the Email-MIME CPAN distribution.

Report information
The Basics
Id: 62913
Status: resolved
Priority: 0/
Queue: Email-MIME

People
Owner: Nobody in particular
Requestors: russellj [...] strategicdata.com.au
Cc:
AdminCc:

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



Subject: Incorrect use of MIME-Q encoding on (some) headers
RFC2047 states that MIME-Q encoding MUST NOT appear in any portion of an 'addr-spec'. However all headers passed via the header_str attribute in the call to Email::MIME->create( ) get MIME-Q encoded [1]. This causes long addresses to have spaces inserted within them (before any folding takes place). A simple (failing) test case is attached to highlight this. Cheers, Russell. [1] I'm using Email::MIME::Kit to do the heave lifting of the email generation, which passes headers via the header_str attribute..
Subject: fold.t
#!/usr/bin/perl use warnings; use strict; use Test::More tests => 1; use Email::MIME; use Email::Simple; my $address = 'this-is-a-very-very-very-very-very-very-very-very-very-long-address@some.domain.name'; my $header = [ 'To' => $address ]; my $body = '...'; my $email = Email::MIME->create( header_str => $header, body => $body, ); like($email->as_string, qr/$address/,"Email::MIME - To: address is correct (no MIME-Q encoding)");
Is this still plaguing you? This problem was meant to be addressed some time ago. -- rjbs
Subject: Re: [rt.cpan.org #62913] Incorrect use of MIME-Q encoding on (some) headers
Date: Fri, 09 Aug 2013 11:38:18 +1000
To: bug-Email-MIME [...] rt.cpan.org
From: Russell Jenkins <russell.jenkins [...] strategicdata.com.au>
On 9/08/13 11:03 AM, Ricardo Signes via RT wrote: Show quoted text
> <URL: https://rt.cpan.org/Ticket/Display.html?id=62913 > > > Is this still plaguing you?
I'd forgotten all about it! Show quoted text
> This problem was meant to be addressed some time ago.
The test case I attached to the bug report passes on Email::MIME 1.911 and 1.922. Happy to consider it resolved. Cheers, Russell.
Thanks for the rapid response! I will try to learn from your example. -- rjbs