On Tue, 07 Dec 2010 12:03:38 CST, Earl Hood said:
On Tue, Dec 7, 2010 at 11:10 AM, Jon Steinhart <jon(_at_)fourwinds(_dot_)com> 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 headers (which is what nmh has been doing in the past).
pgp4fjWLY5bGf.pgp
Description: PGP signature
_______________________________________________ Nmh-workers mailing list Nmh-workers(_at_)nongnu(_dot_)org http://lists.nongnu.org/mailman/listinfo/nmh-workers
Previous by Date: | Re: [Nmh-workers] Understanding nmh (aka. What's the goal) [ reallynon-ASCII message bodies ], David Levine |
---|---|
Next by Date: | Re: [Nmh-workers] Understanding nmh (aka. What's the goal) [ reallynon-ASCII message bodies ], Jon Steinhart |
Previous by Thread: | Re: [Nmh-workers] Understanding nmh (aka. What's the goal) [ really non-ASCII message bodies ], Earl Hood |
Next by Thread: | Re: [Nmh-workers] Understanding nmh (aka. What's the goal), Valdis . Kletnieks |
Indexes: | [Date] [Thread] [Top] [All Lists] |