[issue35805] email package folds msg-id identifiers using RFC2047 encoded words where it must not

Olivier Dony added the comment: Somehow the message identifiers in the code sample got messed up in previous comment, here's the actual code, for what it's worth ;-) https://gist.github.com/odony/0323eab303dad2077c1277076ecc3733 -- ___ Python

[issue35805] email package folds msg-id identifiers using RFC2047 encoded words where it must not

Olivier Dony added the comment: Further, under Python 3.8 the issue is not fully solved, as other identification headers are still being folded in a non-RFC-conformant manner (see OP for RFC references). This was indicated on the original PR by the author:

[issue35805] email package folds msg-id identifiers using RFC2047 encoded words where it must not

Olivier Dony added the comment: With regard to msg349895, is there any chance this fix could be considered for backport? I imagine you could view it as a new feature, but it seems to be the only official fix we have for the fact that Python 3 generates invalid SMTP messages. And that's not

[issue35805] email package folds msg-id identifiers using RFC2047 encoded words where it must not

Abhilash Raj added the comment: Closing this since it has been fixed in Python 3.8. -- resolution: -> fixed stage: needs patch -> resolved status: open -> closed versions: -Python 3.7 ___ Python tracker

[issue35805] email package folds msg-id identifiers using RFC2047 encoded words where it must not

Abhilash Raj added the comment: I am slightly confused if this should be backported to bugfix branches since this is technically a new feature, the ability to parse Message-ID field. I would love to see what David and Barry think about this? --

[issue35805] email package folds msg-id identifiers using RFC2047 encoded words where it must not

Barry A. Warsaw added the comment: New changeset 46d88a113142b26c01c95c93846a89318ba87ffc by Barry Warsaw (Abhilash Raj) in branch 'master': bpo-35805: Add parser for Message-ID email header. (GH-13397) https://github.com/python/cpython/commit/46d88a113142b26c01c95c93846a89318ba87ffc

[issue35805] email package folds msg-id identifiers using RFC2047 encoded words where it must not

Abhilash Raj added the comment: I have made the requested changes on PR. David, can you please review again? -- ___ Python tracker ___

[issue35805] email package folds msg-id identifiers using RFC2047 encoded words where it must not

Abhilash Raj added the comment: I have created https://github.com/python/cpython/pull/13397 for this. For now, it only parses Message-ID header. I do plan to add support for other Identification headers soon, perhaps in a 2nd PR. -- nosy: +maxking stage: patch review -> needs

[issue35805] email package folds msg-id identifiers using RFC2047 encoded words where it must not

Change by Abhilash Raj : -- keywords: +patch pull_requests: +13307 stage: needs patch -> patch review ___ Python tracker ___ ___

[issue35805] email package folds msg-id identifiers using RFC2047 encoded words where it must not

R. David Murray added the comment: Yes, the correct solution would be to write an actual parser for headers containing message ids. All the pieces needed to do this already exist in _header_value_parser, it "just" needs a function that glues them together in the right order, and then apply

[issue35805] email package folds msg-id identifiers using RFC2047 encoded words where it must not

New submission from Martijn Pieters : When encountering identifier headers such as Message-ID containing a msg-id token longer than 77 characters (including the <...> angle brackets), the email package folds that header using RFC 2047 encoded words, e.g. Message-ID: