On Sat, Mar 19, 2005 at 09:59:46AM -0800, Mark Sapiro wrote:
> Sylvain Beucler wrote:
> >
> >I'm a Savane (gna.org/p/savane) developer, and we noticed that when we
> >send mail with newlines in the \r\n format, Mailman converts them to
> >\n\n.
> >
> >I would like to get your point on what we shoul
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
On 3/19/2005 9:59, "Mark Sapiro" <[EMAIL PROTECTED]> wrote:
> Sylvain Beucler wrote:
>>
>> I'm a Savane (gna.org/p/savane) developer, and we noticed that when we
>> send mail with newlines in the \r\n format, Mailman converts them to
>> \n\n.
>>
>> I would like to get your point on what we shoul
Mathieu Roy wrote:
>Mark Sapiro <[EMAIL PROTECTED]> tapota :
>>
>> How does Savane inject its messages into the internet mail transport
>> system? If it is sending via SMTP, then it MUST send line terminators
>> as (or \r\n).
>
>I do not remember the specifics exactly but Sylvain wrote previousl
Sylvain Beucler wrote:
>
>I'm a Savane (gna.org/p/savane) developer, and we noticed that when we
>send mail with newlines in the \r\n format, Mailman converts them to
>\n\n.
>
>I would like to get your point on what we should do to fix the
>problem. I had a look at RFC 822; the EOL (end of line) de
Hi,
I'm a Savane (gna.org/p/savane) developer, and we noticed that when we
send mail with newlines in the \r\n format, Mailman converts them to
\n\n.
I would like to get your point on what we should do to fix the
problem. I had a look at RFC 822; the EOL (end of line) description is
not very clea
