Ertugrul =?UTF-8?B?U8O2eWxlbWV6?= <es@ertes.de> wrote in
news:fvmn9v$krg$00$1@news.t-online.com:

> bz <bz+csm@ch100-5.chem.lsu.edu> wrote:
>
>> > MIME doesn't have an 'attachment' concept. A MIME message is made up
>> > of parts, none of which are 'main', 'primary' or 'attached'.
>>
>> I suggest you study the SMTP protocol such as RFC2821.
>> It starts with a 'MAIL FROM:', 'RCPT TO:' and then comes the 'DATA
>> <CRLF>'
>>
>> ALL of the message, including the 'header' that you see (except for
>> the most recent section) are part of the 'DATA' section of the
>> message.
>>
>> There are no separate 'attachments'. It is all part of the DATA.
>
> You're missing the context. We were talking about how the messages have
> to be formatted, not about how they are transferred.

You missed my point.

The contents of each message is text.
Plain ASCII text.
ALL 'attachments' end up as part of the 'DATA' portion of the message and
are transmitted as plain ASCII text.

If you want to communicate most reliably, you will stick to plain ASCII
text. If you want to communicate most economically, you will stick to
plain ASCII text. If you want to communicate most safely, you will stick
to plain ASCII text.

Any encoding, such as mime and HTML simply add hazards and complexity.
They add 'bling' but they most often prove to be an unnecessary and
unneeded conduit for infection and a reliable sign of spam.

That is not to say that they are not valuable for languages that can not
be represented in plain ASCII, but there is no reason for me to need to
send or receive such messages.





--
bz

please pardon my infinite ignorance, the set-of-things-I-do-not-know is an
infinite set.

bz+csm@ch100-5.chem.lsu.edu remove ch100-5 to avoid spam trap