[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Nmh-workers] Understanding nmh (aka. What's the goal) [ really non-

From: Valdis . Kletnieks
Subject: Re: [Nmh-workers] Understanding nmh (aka. What's the goal) [ really non-ASCII message bodies ]
Date: Tue, 07 Dec 2010 18:49:02 -0500

On Tue, 07 Dec 2010 12:03:38 CST, Earl Hood said:
> On Tue, Dec 7, 2010 at 11:10 AM, Jon Steinhart <address@hidden> wrote:
> > I understand that my attachment system does not handle non-ASCII message
> > bodies, but again, that's because non-ASCII message bodies are not "legal".
> Please cite an RFC that says non-ASCII bodies are not legal.
> With MIME, you have the Content-Transfer-Encoding field, which allows
> for 8bit.  And then, if you have a Content-Type type that supports
> charset parameter, you can "legally" have a body that is non-ASCII.

A MIME message that has a Mime-Version: and appropriate C-T-E: headers can
certainly be non-ASCII.  What's illegal is sending non-ASCII *without* such 
(which is what nmh has been doing in the past).

Attachment: pgpLpSaVkv5bj.pgp
Description: PGP signature

reply via email to

[Prev in Thread] Current Thread [Next in Thread]