[issue28463] Email long headers parsing/serialization

2021-11-26 Thread Irit Katriel
Change by Irit Katriel : -- type: -> behavior versions: +Python 3.10, Python 3.11, Python 3.9 -Python 3.4, Python 3.5 ___ Python tracker ___ __

[issue28463] Email long headers parsing/serialization

2016-10-18 Thread R. David Murray
R. David Murray added the comment: It is a bug, but it is not a bug that the message-id body gets put on a second line. The old (compat32) folder introduces an extra space while folding, which then gets preserved when the re-parsing is done. The new folder (policy=default) folds correctly (p

[issue28463] Email long headers parsing/serialization

2016-10-18 Thread Константин Волков
Константин Волков added the comment: But message ID have its own syntax https://www.ietf.org/rfc/rfc2822.txt: 3.6.4. Identification fields message-id = "Message-ID:" msg-id CRLF msg-id = [CFWS] "<" id-left "@" id-right ">" [CFWS] 3.2.3. Folding white space and comment

[issue28463] Email long headers parsing/serialization

2016-10-18 Thread Mariusz Masztalerczuk
Mariusz Masztalerczuk added the comment: I think that it is not bug. It is just rfc ;) Due to https://www.ietf.org/rfc/rfc2822.txt, A message consists of header fields, optionally followed by a message body. Lines in a message MUST be a maximum of 998 characters excluding the CRLF, but

[issue28463] Email long headers parsing/serialization

2016-10-17 Thread R. David Murray
R. David Murray added the comment: Ah, interesting case. Both the old folder/parser and the new folder/parser fail, in slightly different ways. I'll have to add this test case to the tests as I finish rewriting the folder. Thanks for the report. -- _

[issue28463] Email long headers parsing/serialization

2016-10-17 Thread Константин Волков
Константин Волков added the comment: Something with inserting long strings here. Its duplicating for some reason. Adding example as attachment. -- Added file: http://bugs.python.org/file45124/test.py ___ Python tracker

[issue28463] Email long headers parsing/serialization

2016-10-17 Thread Константин Волков
Константин Волков added the comment: Something with copy paste. x = '<147672320775.19544.6718708004153358...@mkren-spb.root.devdomain.local>' -- ___ Python tracker ___ __

[issue28463] Email long headers parsing/serialization

2016-10-17 Thread Константин Волков
New submission from Константин Волков: There is strange thing with long headers serialized, they have \n prefix. Example fails on Python3.4/3.5: from email.message import Message from email import message_from_bytes x = '<147672320775.19544.6718708004153358...@mkren-spb.root.devdomain.local>'