I think this has got to the point, where some package might not be RFC
compliant, but that is no reason to stick one's head in the sand when it
comes to compatibility.
If another MTA will work with your other chosen software, then what's to
stop you moving to it.
The discussion below about -dropcr is a smart way to allow the widest
compatibility between mail packages.
Perhaps in the interest of compatibility Xmail could support
a server.tab setting UseCRLFinMessages={0|1}
Obviously this would not apply to headers.
Rob :-)
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] Behalf Of Richard Mayhew
> Sent: Wednesday, July 30, 2003 6:18 PM
> To: [EMAIL PROTECTED]
> Subject: [xmail] More info on the <CR><LF> vs <LF> Saga on unix servers.
>
>
> The RFCs that define Internet mail apply only to messages
> in transit
> between hosts. They specify that lines of text should be
> terminated by
> the two-character sequence CR, LF. When a message is within a host
> system, the software that processes it may use any method
> it likes for
> terminating lines. The natural assumption is to use the
> host's normal
> convention. Most software on Unix-like systems uses a single LF
> character, which is the Unix standard.
>
> When a non-SMTP message is passed to Exim via its command line, LF
> termination is assumed. Any CR characters in the message,
> wherever they
> appear, are treated as data characters.
>
> Unfortunately, not all software writers take the same
> view. At least
> one MUA (dtmail) terminates each line with CR, LF, and the Cyrus
> message store behaves in the same way. There is also some
> UUCP software
> which does this. To support these callers, Exim has the
> -dropcr option,
> which causes it to discard a CR character if it
> immediately precedes an
> LF. Any other CR characters are treated as data. For example, a
> sequence such as CR, CR, LF is treated as one data CR,
> followed by the
> end of the line. The "drop_cr" configuration file option
> can be used to
> force -dropcr for all non-SMTP input.
>
> -
> To unsubscribe from this list: send the line "unsubscribe xmail" in
> the body of a message to [EMAIL PROTECTED]
> For general help: send the line "help" in the body of a message to
> [EMAIL PROTECTED]
>
>
-
To unsubscribe from this list: send the line "unsubscribe xmail" in
the body of a message to [EMAIL PROTECTED]
For general help: send the line "help" in the body of a message to
[EMAIL PROTECTED]