Re: Posible bug on MIME.Message parsing complex boundary mails (2nd level) with surrogated breaks or spaces

"Stephen R. van den Berg" <[email protected]> Fri, 27 Oct 2017 15:53:31 +0200

Newsgroups	gmane.comp.lang.pike.user
Message-ID	<[email protected]>

destopa wrote:
>You can use meld or similar tool to see visually that they differ minimally
>and the mime construction in original.eml seems to be also valid.

>modified.eml <http://pike.1058338.n5.nabble.com/file/t339041/modified.eml>   
>original.eml <http://pike.1058338.n5.nabble.com/file/t339041/original.eml>  

A cursory reading of the MIME RFCs and a quick glance at the provided files seems
to suggest that the newline(s) following separator and before the next header
are indeed optional.

If noone objects (and please object on the mailinglist, not in LysKOM), I'll
commit a patch to 8.1 which fixes this, which can then subsequently
be copied to 8.0.
-- 
Stephen.