I am not sure 76 or 78 characters but definitely less than 80 characters. To be confirm with the standard and the rest of the mail clients community. A final snarfed message prior sending to the smtp server should not have any line longer than 76 characters. Some SMTP server maybe able to handle lines longer than 76 characters but there is no guarantee. Especially when a message delivered from one MTA to another MTA. To avoid lines being chopped off, a good practice would be using quoted-printable encoding for content-type: text/____. This long line problem can be easily seen when composing the mail message using html compose with charset UTF-8 and 8bit content-transfer-encoding. I guess this should be a beta stopper.

I always thought this myself, but if this is the case, we've been broken for years on this one. I have sample multipart alternative emails sent by 4.x where the HTML part has line lengths of 300+ characters. I'll look into it. - rhp

Rich, I would suggest that we always use quoted-printable for charset=UTF-8 instead of 8 bit encoding. There is no data loss and guarantee lines no longer than 80 characters and better chance of not being chopped off.

Ok, code was there, but we had old prefs for forcing strict MIME conformance and we actually sent 8bit instead of Quoted Printable. We now send QP instead as the default. From my testing, looks like this problem is fixed. - rhp

changing qa assigned to pmock@netscape.com

Verified as fixed on win32, linux, and macos using the following builds: ftp://sweetlou/products/client/seamonkey/windows/32bit/x86/2000-01-12-11-M13/sea monkey32e.exe ftp://sweetlou/products/client/seamonkey/unix/linux_glibc/2.2/x86/2000-01-11-10- M13/netscape-i686-pc-linux-gnu.tar.gz ftp://sweetlou/products/client/seamonkey/macos/8.x/ppc/2000-01-12-08-M13/netscap e5-mac-M13.sea.bin I sent multipart/alternative messages from 5.0. I used 4.7 to view the messsage page source. The longest character string I saw was 72 characters. When I sent multipart/alternative messages from 5.0, the Content-Transfer-Encoding was sent as quoted-printable