Skip Menu |

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

Report information
The Basics
Id: 35031
Status: resolved
Priority: 0/
Queue: Mail-IMAPClient

People
Owner: Nobody in particular
Requestors: jik [...] kamens.brookline.ma.us
Cc:
AdminCc:

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



Subject: LF -> CRLF not done for messages uploaded from strings
It appears that the new Mail::IMAPClient doesn't correctly convert bare LF to CRLF when uploading a message from a string. Patch is attached.
Subject: Mail-IMAPClient-3.05-bare-newlines.patch
--- lib/Mail/IMAPClient.pm.orig 2008-02-20 03:01:31.000000000 -0500 +++ lib/Mail/IMAPClient.pm 2008-04-14 16:34:59.000000000 -0400 @@ -2306,6 +2306,8 @@ my $count = $self->Count($self->Count+1); + $text =~ s/\r?\n/\r\n/g; + my $command = "$count APPEND $folder " . ($flags ? "$flags " : "") . ($date ? "$date " : "") . "{" . length($text) . "}\r\n";
Subject: Re: [rt.cpan.org #35031] LF -> CRLF not done for messages uploaded from strings
Date: Mon, 14 Apr 2008 23:23:20 +0200
To: Jonathan Kamens via RT <bug-Mail-IMAPClient [...] rt.cpan.org>
From: NLnet webmaster <webmaster [...] nlnet.nl>
* Jonathan Kamens via RT (bug-Mail-IMAPClient@rt.cpan.org) [080414 20:43]: Show quoted text
> Mon Apr 14 16:43:41 2008: Request 35031 was acted upon. > Transaction: Ticket created by JIK > Queue: Mail-IMAPClient > Subject: LF -> CRLF not done for messages uploaded from strings > Broken in: 3.05 > Ticket <URL: http://rt.cpan.org/Ticket/Display.html?id=35031 > > > It appears that the new Mail::IMAPClient doesn't correctly convert bare > LF to CRLF when uploading a message from a string. Patch is attached.
Apparently not needed for many servers (there are many users of this module), but I have restored the original behavior. -- Regards, MarkOv ------------------------------------------------------------------------ Mark Overmeer MSc MARKOV Solutions Mark@Overmeer.net solutions@overmeer.net http://Mark.Overmeer.net http://solutions.overmeer.net
Was fixed in 3.06 (just released 3.07)