It's just the other way around.
There are too many assumptions on '\n' line endings in the code.
Inserting '\r\n' breaks things..
The problem is that quite a lot of the assumptions in code that is, for
me, until now, quite unreadable.
Ilja
Aaron Stone wrote:
So we need to add the \r's at the time of message insertion?
I'm not surprised, and I've been thinking that we'd have to do that, because
it seems clear that there are deep assumptions of \r\n line endings
throughout. It's not ideal, since we really should be keeping things in the
same format as they came in over the wire, but the level of breakage lately
has been too much :-\
Aaron
Ilja Booij <[EMAIL PROTECTED]> said:
Ilja Booij wrote:
BTW, I haven't been able to use OutLook yet to test the message
problems, as our only Windows machine here is in use at the moment.
I've taken a look at the OutLook problem using OutLook Express. The
cause of the problem was the fact that a message inserted via lmtp has
\r\n as line ending. When using imap, \r is added to this, resulting in
line endings of \r\r\n
This apparantly confuses OutLook
changing to the code to not insert \r\n, but to insert \n instead. This
was made easier by the change in message insertion code I made. :)
Though relying on storing \n and not \r\n is not the Right Thing to do,
it seems to be the easiest fix.
Ilja
_______________________________________________
Dbmail-dev mailing list
Dbmail-dev@dbmail.org
http://twister.fastxs.net/mailman/listinfo/dbmail-dev
