[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 22:57:15 -0400 |
>I agree with Ralph: ripple the error back up (with returns,
>not longjmps :-) and don't even open the editor. In this
>case, it looks like that might not be too difficult:
>fmt_scan() currently doesn't return anything useful. Fix
>that, and have its callers check the return value.
So it turns out there's actually standards work in this space!
http://tools.ietf.org/html/draft-ietf-appsawg-malformed-mail-06
I think I'm going to digest this and think about things some more.
--Ken
- Re: [Nmh-workers] Weird behavior with non-ascii code in headers, (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, 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