It is significant that the rfc says, "the body is simply a sequence of
characters", rather than a sequence of lines. This could be interpreted
to mean that the body has no line length.
Exactly. I'd never write software that spit out huge lines myself, but I'm having a really hard time explaining to lots of our clients why it's their email software that's broken and not our problem.
They simply don't care -- it works with everyone else's system, and they can justify why it should work because a) the RFCs are contradictory, and b) their message works fine with Postfix, with Exim, with Sendmail, and with MS Exchange. NO ONE else imposes this limit. Heck, SquirrelMail on our *own* system triggered this error yesterday when someone tried to send an odd PDF file as an attachment. (Merak on Windows also triggered it.)
Given that the RFCs are vague, and that EVERY server we've tested (except Courier) supports insanely long line lengths (we tested with 1,000,000 byte-long lines), it looks incredibly bad for us and Courier that it doesn't work on our system. There's a lot of RFC-enforcing that I'm willing to argue for, but this one is just too far out there.
Given this, what can we do?
best, Jeff
-------------------------------------------------------
This SF.Net email is sponsored by Sleepycat Software
Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver higher performing products faster, at low TCO.
http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3
_______________________________________________
courier-users mailing list
[EMAIL PROTECTED]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
