[Top][All Lists]

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

Re: [Nmh-workers] Weird behavior with non-ascii code in headers

From: David Levine
Subject: Re: [Nmh-workers] Weird behavior with non-ascii code in headers
Date: Sun, 30 Jun 2013 20:55:42 -0400

> >My concern is that something like boss=?utf8?Q?=2cX=excluded,
> >where X is a invalid UTF byte, will get converted to
> >boss=?utf8?Q?=2c?=excluded, which is a legal encoding of
> >boss,excluded.  If you can guarantee that kind of thing won't
> >ever happen in an nmh draft, great.
> I guess I don't really see why someone would do:
> From: boss=?utf8?Q?=2cX=excluded

It doesn't matter how or why it got that way.  Valdis received
an encoded header with an invalid character, period.

> But if you're concerned about what I have to call a non-problem,
> there's an easy solution.  Simply don't do %(decode) on address
> headers in the replcomps (we don't do this now).  That ensures that
> there's not a problem.

I was just starting to feel better about this :-)  Fine with me,
if it's documented.


reply via email to

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