On Sat, 2005-03-19 at 19:27, John W. Baxter wrote: > Note that 2821 is talking about how messages are transmitted over the wire > as part of the SMTP transaction. An MTA will usually present the message to > mailboxes, scripts, etc in the native form expected on the platform (for > Unix, newline = ASCII linefeed). Mailman is very likely operating on that > expectation (in particular, Mailman is not one end of an SMTP conversation, > so the SMTP RFC doesn't apply).
Exactly. Mailman isn't going to convert line endings. The email package is the component that parses messages and generates the flattened text from the message objects. If anything was converting newlines it would be the email package. But the email package tries very hard to preserve whatever line endings it finds in the messages it parses. John is right that typically the MTA will present the message to mail programs using native line endings. The on-the-wire representation really has no bearing on the issue. -Barry
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Mailman-Developers mailing list [email protected] http://mail.python.org/mailman/listinfo/mailman-developers 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-developers/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
