I have uncovered a problem, though. The problem lies with the message itself. Instead of following the headers with two new lines (courier seems to strip the CRs) it follows the headers with one new line (at the end of the last header) and then a line that has 3 tab characters followed by a newline.
So normal:
Subject: test\n \n <body>
This msg:
Subject: test\n \t\t\t\n <body>
This is obviously wrong. The message is a temp fail undeliverable warning from an SBC webhosting server: Connected to 216.173.237.164. Escape character is '^]'. 220 mail26a.sbc-webhosting.com SMTP RS ver 1.0.80vs
The problem is this: This message stops Outlook dead. Outlook cannot retrieve this message, and it cannot retrieve any messages after it. It requires admin intervention.
So the questions are: A) Who truly is to blame here? SBC's server for one, but which other program is viloating RFCs?
SBC is generating a garbage DSN. Outlook is broken because it chokes on it, and can't recover.
B) What can we do about it? Obviously this kind of thing is going to continue to happen. It has happened a number of times in the past. Outlook, although garbage, is the most popular email client. SBC is not going away any time soon. Can we either reject these bad messages at an SMTP level or fix them?
... and then people who just absolutely have a desire to receive broken mail from these servers, but use a mail client that can handle them, will complain about bouncing them.
------------------------------------------------------- This SF.net email is sponsored by: Etnus, makers of TotalView, The best thread debugger on the planet. Designed with thread debugging features you've never dreamed of, try TotalView 6 free at www.etnus.com. _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
