[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Nmh-workers] Weird behavior with non-ascii code in headers
From: |
Ken Hornstein |
Subject: |
Re: [Nmh-workers] Weird behavior with non-ascii code in headers |
Date: |
Wed, 26 Jun 2013 23:41:24 -0400 |
>> Sure, that would have been bad. But if instead the invalid character
>> had been replaced by a ?, everything would have worked fine.
>
>That doesn't remove the possibility, it just makes it very,
>very unlikely. If we're going to change something, we might
>as well do it right. And, we wouldn't have to advise users
>to not use "?" in aliases.
Um, wait ... I'm confused. How would it have _not_ completely removed
the problem? In Valdis's case, the full header would be (after replacing
the "bad" character with a ?):
To: Mr Foo ? Bar <address@hidden>
The email address would still be fully qualified, and aliases would never
be checked. Am I missing something?
--Ken
- Re: [Nmh-workers] Smart enough to use nmh, (continued)
Re: [Nmh-workers] Weird behavior with non-ascii code in headers, David Levine, 2013/06/26
Re: [Nmh-workers] Weird behavior with non-ascii code in headers, David Levine, 2013/06/26
- Re: [Nmh-workers] Weird behavior with non-ascii code in headers,
Ken Hornstein <=
Re: [Nmh-workers] Weird behavior with non-ascii code in headers, David Levine, 2013/06/26
Re: [Nmh-workers] Weird behavior with non-ascii code in headers, David Levine, 2013/06/27
Re: [Nmh-workers] Weird behavior with non-ascii code in headers, David Levine, 2013/06/27
Re: [Nmh-workers] Weird behavior with non-ascii code in headers, David Levine, 2013/06/27
Re: [Nmh-workers] Weird behavior with non-ascii code in headers, David Levine, 2013/06/28