3 messages in net.sourceforge.lists.courier-users[courier-users] RE: Way to reject cor...
FromSent OnAttachments
Joe LaffeyOct 21, 2003 7:51 pm 
Julian MehnleOct 22, 2003 2:08 am 
Thomas SmithOct 22, 2003 11:03 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:[courier-users] RE: Way to reject corrupt messages?Actions...
From:Julian Mehnle (lis@mehnle.net)
Date:Oct 22, 2003 2:08:40 am
List:net.sourceforge.lists.courier-users

Joe Laffey <jo@laffeycomputer.com> wrote:

On Tue, 21 Oct 2003, Sam Varshavchik wrote:

Only Microsoft can fix this.

So mail servers MUST accept messages with this format? (only headers and no blank lines)

I can work around this by writing a script to search and destroy these messages. ISPs *can* choose and configure servers. They, sadly, *cannot* dictate which client people use. Every time I speak with a client I recommend against using Outlook (especially oon the PC, for security reasons). But none of them pay any attention.

Evil as as MS is, and crappy as Outlook is, it seems to me like we as admins must do everything to support it.

No, why should admins have to do everything to support broken client software?
Maybe clients will *now* pay attention to your recommendation, if only due to
the fact that Outlook chokes at all just because of broken messages. I'm using
Outlook (not Express) since its early days myself, and I think it's a decent
(although not optimal) mail client and PIM, but I'm very well aware of its
weaknesses, and I tend to switch to Kmail in the foreseeable future.

Of course there is a way to reject the "broken" messages: Write a courierfilter
that checks the messages and rejects broken ones right in the SMTP dialog.