I'm not sure this is a bug (yet), but: I'm using Netsacpe 4.7 for Linux and am having a lot of trouble with some mail recipients, because their mail client or MTA doesn't understand content-transfer-encoding=base64. I haven't been able to figure out exactly when this happens, but often, when sending plain text messages in NS4.7, the message is sent in base64. The effect is that some recipients only get gobbledygook. Please make sure that plain text messages are not sent using base64 encoding, or at least add an option/preference somewhere that allows me to force 8bit. This seems to happen especially when the message is sent as "Text and HTML"; the text part is in base64.

The only time we do Base64 encoding is when 10% of the message is detected as being non-printable, otherwise it will be quoted printable if the lines are over detected longer than 900 characters. I'll put this on my list and keep an eye on it. - rhp

I think with my latest checkins for defaulting to Quoted Printable, I've checked on this issue as well. The only time we should send BASE64 encoded data is the following: - we detect the mime type requires it (i.e. image/jpeg, etc...) - When it is of character set iso-2022-jp and its a web page - the document contains more than 10% unprintable characters Other than that, it should be Quoted Printable. Keep in mind, we should NOT send lines longer than 72 chars through SMTP servers or we are at the risk of truncation. - rhp

changing qa assigned to pmock@netscape.com

Verified as fixed on win32, macos, and linux using the following builds: win32 commercial seamonkey build 00051109-m16 installed on Dell P500, Win98 macos commercial seamonkey build 00051008-m16 installed on G3/400, MacOS 9.04 linux commercial seamonkey build 00051008-m16 installed on P200, RedHat 6.1