4 messages in net.sourceforge.lists.courier-usersRE: [courier-users] what trouble in m...
FromSent OnAttachments
Yan shiqiangDec 22, 2000 9:22 pm 
Chris MeadorsDec 23, 2000 8:15 am 
Juha SaarinenDec 23, 2000 1:01 pm 
Juha SaarinenDec 25, 2000 12:34 pm 
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:RE: [courier-users] what trouble in mail server?Actions...
From:Juha Saarinen (ju@saarinen.org)
Date:Dec 25, 2000 12:34:42 pm
List:net.sourceforge.lists.courier-users

%-> Actually I'm pretty sure Hotmail, Yahoo, and even AOL get it right.

Don't know about AOL, but Hotmail and Yahoo don't get it right:

Dec 18 14:57:21 vimfuego courieresmtpd:
error,relay=::ffff:209.185.241.138,from=<@hotmail.com>: 550-The headers in this message contain 8-bit text, which violates RFC 2047. Dec 18 14:57:21 vimfuego courieresmtpd:
error,relay=::ffff:209.185.241.138,from=<@hotmail.com>: 550-Sorry, I cannot accept any mail without the required MIME headers. Dec 18 14:57:21 vimfuego courieresmtpd:
error,relay=::ffff:209.185.241.138,from=<@hotmail.com>: 550 See <URL:ftp://ftp.isi.edu/in-notes/rfc2047.txt> for more information. Dec 18 14:59:35 vimfuego courieresmtpd:
error,relay=::ffff:209.185.241.137,from=<@hotmail.com>: 550-This message has 8-bit contents, but does not have the necessary MIME Dec 18 14:59:35 vimfuego courieresmtpd:
error,relay=::ffff:209.185.241.137,from=<@hotmail.com>: 550-headers. Sorry, this mail server does not accept mail without the Dec 18 14:59:35 vimfuego courieresmtpd:
error,relay=::ffff:209.185.241.137,from=<@hotmail.com>: 550-required MIME headers. See <URL:ftp://ftp.isi.edu/in-notes/rfc2045.txt> Dec 18 14:59:35 vimfuego courieresmtpd:
error,relay=::ffff:209.185.241.137,from=<@hotmail.com>: 550 for more information.

Dec 10 12:11:23 vimfuego courieresmtpd:
error,relay=::ffff:216.136.130.40,from=<@yahoo.com>: 550-This message has 8-bit contents, but does not have the necessary MIME Dec 10 12:11:23 vimfuego courieresmtpd:
error,relay=::ffff:216.136.130.40,from=<@yahoo.com>: 550-headers. Sorry, this mail server does not accept mail without the Dec 10 12:11:23 vimfuego courieresmtpd:
error,relay=::ffff:216.136.130.40,from=<@yahoo.com>: 550-required MIME headers. See <URL:ftp://ftp.isi.edu/in-notes/rfc2045.txt> Dec 10 12:11:23 vimfuego courieresmtpd:
error,relay=::ffff:216.136.130.40,from=<@yahoo.com>: 550 for more information. Dec 10 12:21:04 vimfuego courieresmtpd:
error,relay=::ffff:216.136.130.40,from=<@yahoo.com>: 550-This message has 8-bit contents, but does not have the necessary MIME Dec 10 12:21:04 vimfuego courieresmtpd:
error,relay=::ffff:216.136.130.40,from=<@yahoo.com>: 550-headers. Sorry, this mail server does not accept mail without the Dec 10 12:21:04 vimfuego courieresmtpd:
error,relay=::ffff:216.136.130.40,from=<@yahoo.com>: 550-required MIME headers. See <URL:ftp://ftp.isi.edu/in-notes/rfc2045.txt> Dec 10 12:21:04 vimfuego courieresmtpd:
error,relay=::ffff:216.136.130.40,from=<@yahoo.com>: 550 for more information.

%-> I would tend to agree with you. But if you look in this list's archives %-> you'll see some pretty good arguments for keeping it as it is now. And %-> watching the 550 MIME bounces, I don't think I'm missing much. %-> So even if %-> it became configurable, I'd keep it on.

Yes... in an ideal world, you'd strip out non-MIME'd and HTML email, hoping to
educate the world, but it's kind of hard to make the world listen... ;-)

This is mainly an issue for Courier installations with users outside the US. I'd
like to pick up on the non-MIME'd stuff, and tag a "Please change your MTA to append the
correct MIME headers" with some How-To URLs to the messages.

%-> > Be conservative in what you do, %-> > be liberal in what you accept from others. %-> %-> That's pretty good (maybe you should wrap your text at <80 columns. :)

Vintage Postel.... and I thought Outlook 2000 wrapped at 76 cols? Hmmmmm...
seems if you pick the Encode Messages Using MIME Base64 the line wrapping box is greyed out.
You have to set it to UUENCODE instead. It can't be that stupid, surely? Arrgh.

-- Juha