This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author robertus
Recipients barry, r.david.murray, robertus
Date 2017-08-01.09:29:35
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1501579776.31.0.523441406707.issue31089@psf.upfronthosting.co.za>
In-reply-to
Content
RFC regarding this topic looks quite complicated to me, but I know that \r\n is used for line breaking in e-mail headers and \n is not. So in my opinion it shouldn't be treated the same like \n. The \r\n should be removed in parsed text, but \n should be preserved like any other character. So I don't think "universal newline mode" is correct approach to read raw e-mails.

I have tested policies in python3 - you have right - it works. But I cannot use it because of application incompatibility with python3.

I was hoping it will be easy to fix for some more experienced than me... If not - you can close issue and I will stay with present solution (removing \r\n).

Thanks for all your help!
History
Date User Action Args
2017-08-01 09:29:36robertussetrecipients: + robertus, barry, r.david.murray
2017-08-01 09:29:36robertussetmessageid: <1501579776.31.0.523441406707.issue31089@psf.upfronthosting.co.za>
2017-08-01 09:29:36robertuslinkissue31089 messages
2017-08-01 09:29:35robertuscreate