[Mailman-Developers] EOL handling in Mailman

[Barry Warsaw]

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

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 307 bytes
Desc: This is a digitally signed message part
Url : http://mail.python.org/pipermail/mailman-developers/attachments/20050319/8e2b6231/attachment.pgp