Re: Legal values for a message-id, and references header

2016-11-25 Thread Kevin J. McCarthy
On Tue, Nov 22, 2016 at 03:38:57PM +0100, Vincent Lefevre wrote: > On 2016-11-22 20:43:12 +1100, Cameron Simpson wrote: > > On 22Nov2016 03:27, vincent lefevre wrote: > > > That's clearly illegal. MIME has been designed so that the main > > > features should still work with software that doesn't s

Re: Legal values for a message-id, and references header

2016-11-22 Thread Vincent Lefevre
On 2016-11-22 20:43:12 +1100, Cameron Simpson wrote: > On 22Nov2016 03:27, vincent lefevre wrote: > > That's clearly illegal. MIME has been designed so that the main > > features should still work with software that doesn't support MIME > > (said otherwise, software that only needs to work with ad

Re: Legal values for a message-id, and references header

2016-11-22 Thread Arnt Gulbrandsen
Cameron Simpson writes: Regarding non-ASCII, we decode to bytes. Valid message-ids only contain ASCII anyway. Actually message-ids can contain more than just ASCII, see RFC 6530 and friends. But never 2047. (And even 6530-cognisant senders do well to keep message-id to just ASCII.) My sugg

Re: Legal values for a message-id, and references header

2016-11-22 Thread Cameron Simpson
On 22Nov2016 03:27, vincent lefevre wrote: On 2016-11-20 18:51:25 +1100, Cameron Simpson wrote: On 19Nov2016 19:58, Kevin J. McCarthy wrote: > References: =?utf-8?Q?=3C201611170549=2EQ3WT?= >=?utf-8?Q?foMB=C3=83=C2=BEngguang=2Ewu=40i?= >=?utf-8?Q?ntel=2Ecom=3E=20=3C1479410?= =?utf-8?Q

Re: Legal values for a message-id, and references header

2016-11-21 Thread Vincent Lefevre
On 2016-11-20 18:51:25 +1100, Cameron Simpson wrote: > On 19Nov2016 19:58, Kevin J. McCarthy wrote: > > On Sun, Nov 20, 2016 at 10:08:13AM +1100, Cameron Simpson wrote: > > > On 19Nov2016 13:13, Kevin J. McCarthy wrote: > > > > Should mutt be rfc-2047 encoding/decoding the references > > > > head

Re: Legal values for a message-id, and references header

2016-11-19 Thread Cameron Simpson
On 19Nov2016 19:58, Kevin J. McCarthy wrote: On Sun, Nov 20, 2016 at 10:08:13AM +1100, Cameron Simpson wrote: On 19Nov2016 13:13, Kevin J. McCarthy wrote: > Should mutt be rfc-2047 encoding/decoding the references > header? No. RFC2047 tokens need to be whitespace delimited from the surroundi

Re: Legal values for a message-id, and references header

2016-11-19 Thread Kevin J. McCarthy
On Sun, Nov 20, 2016 at 10:08:13AM +1100, Cameron Simpson wrote: > On 19Nov2016 13:13, Kevin J. McCarthy wrote: > > Should mutt be rfc-2047 encoding/decoding the references > > header? > > No. RFC2047 tokens need to be whitespace delimited from the surrounding > text. No whitespace is permitted

Re: Legal values for a message-id, and references header

2016-11-19 Thread Cameron Simpson
On 19Nov2016 13:13, Kevin J. McCarthy wrote: On #mutt, andrey_utkin_ reported getting a bounce trying to reply to a linux-kernel mailing list email. When he replied, vger.kernel.org bounced it because of raw utf-8 in a header. He posted a gist at

Legal values for a message-id, and references header

2016-11-19 Thread Kevin J. McCarthy
On #mutt, andrey_utkin_ reported getting a bounce trying to reply to a linux-kernel mailing list email. When he replied, vger.kernel.org bounced it because of raw utf-8 in a header. He posted a gist at I don't know how long