From: J. B. Moreno (planb@newsreaders.com)
Date: Mon Feb 02 2004 - 19:02:56 CST
On 2/2/04 6:43 PM, Russ Allbery at <rra@stanford.edu> wrote:
> J B Moreno <planb@newsreaders.com> writes:
>
>> It is also (A) a binary,
>
> What are you talking about? It was no more binary than this message is.
Your message
==
Content-Type: text/plain; charset=us-ascii
==
His message
==
Content-Type: multipart/mixed;
==
and then further down
==
Content-Disposition: inline;
filename*=ISO-8859-1'en-us'Re%3A%208.6
==
Looks like an included file to me. OK, so the content of the file was a
text message, and one that can be handled by the agent (if it does MIME),
but so what? My agent can display jpg's and gif's all by itself too,
possibly movies as well.
He forwarded a message as an attachment -- and an attachment is an
attachment, whether it's a rfc 822 message with a copy of the Lord of the
Rings body, or an MPG of the Lord of the Rings, it's still an attachment.
Good god, that's the whole point behind MIME -- to define a unified way to
handle them all the same at the base level.
-- J.B. Moreno