[issue41553] encoded-word abused for header line folding causes RFC 2047 violation

Mika Hawkins added the comment: Truly for the vault changes. I thought we had fixed the bug that was causing message-id to get encoded, yet perhaps it despite everything exists in 3.7? I don't recall when we fixed it (and I might be recollecting incorrectly!) With respect to X-"unstructured

[issue41553] encoded-word abused for header line folding causes RFC 2047 violation

R. David Murray added the comment: Yes for the registry changes. I thought we had fixed the bug that was causing message-id to get encoded, but maybe it still exists in 3.7? I don't remember when we fixed it (and I may be remembering wrong!) As for X- "unstructured headers" getting trashed

[issue41553] encoded-word abused for header line folding causes RFC 2047 violation

Change by Jeffrey Kintscher : -- nosy: +Jeffrey.Kintscher ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: htt

[issue41553] encoded-word abused for header line folding causes RFC 2047 violation

Erik Quaeghebeur added the comment: We also shouldn't forget Resent-Message-Id. So in the header registry , 'message-id': MessageIDHeader, should be replaced by 'message-id': U

[issue41553] encoded-word abused for header line folding causes RFC 2047 violation

Erik Quaeghebeur added the comment: Note that In-Reply-To can also contain multiple message ids: . It should be treated the same as References. When you say that a message_id parser exists, then that means it is not applied to the Message-Id

[issue41553] encoded-word abused for header line folding causes RFC 2047 violation

R. David Murray added the comment: It's not really an abuse. It is, however, buggy. It should be being applied *only* when the header contains unstructured text. Unfortunately I made the choice to treat any header that doesn't have a specific parser as unstructured, and that was a wrong c

[issue41553] encoded-word abused for header line folding causes RFC 2047 violation

New submission from Erik Quaeghebeur : Encoded-word is apparently used for header line folding sometimes. This appears to me as an abuse of this encoding technique. However, that is not the main issue: it also causes a violation of RFC 2074, as it also encodes message id's: https://tools.ietf.