>As I understand messages are sent as multi-part in the following cases:
>
>* MIME encoding is used and a message is in HTML or Rich Text (as supported
>by some email clients) format
>* MIME encoding is used and a message has an attachment
Actually, the issue is strictly with MIME encoding. If there is MIME
encoding, a trailer added to the end of the E-mail won't normally be
visible; if there is no MIME encoding, it will be.
The MIME encoding is usually used if there is an attachment, and is always
used if there is an HTML version of the E-mail sent along with the text
version.
>Messages sent with UUEncode go through just fine (headers/trailers get
>appended)
FYI, there's a "rare" form of uuencoding that is done with MIME segments
("x-url-encoding", I believe). But that's rare, because if a mail client
knows MIME, there's really no reason to uuencode within the MIME segments.
>The problem is that most email clients default to MIME encoding and
>HTML/Rich Text.
And for that we can give a big thanks to Microsoft, who thinks it's great
to triple bandwidth and storage space for 100% of their users, in exchange
for letting 10% of their users actually use HTML features within
E-mail. I'd say about 90% of text+HTML E-mail is wasted (IE no HTML
features used, such as bolding, underlining, etc.).
-Scott
---
Declude: Anti-virus, Anti-spam and Anti-hijacking solutions for
IMail. http://www.declude.com
---
[This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)]
Please visit http://www.ipswitch.com/support/mailing-lists.html
to be removed from this list.
An Archive of this list is available at:
http://www.mail-archive.com/imail_forum%40list.ipswitch.com/
