Mark Sapiro wrote: > >My guess (I haven't actually looked at the raw decoded message) is that >the decoded plain text has *nix <LF> only line endings as opposed to ><CR><LF> endings. This would not violate RFC 2821 as the data on the >wire is the base64 encoded data, not the original text.
I have now looked, and in today's two base64 encoded posts in the "export list subscribers list" thread, the decoded message body does have text with only <LF> as a line ending. So, >I think the issue may be that your MUA doesn't recognize a single <LF> >in the decoded text as a line break. I don't know if there is a standard that says your MUA 'should' recognize a single <LF> in the decoded text as a line break, but of five MUA's I just tried, four - Ultrafunk Popcorn 1.76, Mozilla Thunderbird 2.0.0.4, MS Outlook Express 6 and Mutt 1.4.2.1i - all rendered <LF> in the decoded text as a line break. The fifth - Qualcomm Eudora 5.2 (very old) - didn't decode the base64 encoded text at all, it just displayed the raw base64 encoded data. -- Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan ------------------------------------------------------ Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
