[issue30701] Exception parsing certain invalid email address headers

2021-01-08 Thread Irit Katriel
Change by Irit Katriel : -- resolution: -> out of date stage: -> resolved status: pending -> closed ___ Python tracker ___ ___ Pyt

[issue30701] Exception parsing certain invalid email address headers

2020-12-02 Thread Irit Katriel
Irit Katriel added the comment: I don't see the error now, I think this has been fixed. -- nosy: +iritkatriel status: open -> pending ___ Python tracker ___ __

[issue30701] Exception parsing certain invalid email address headers

2019-09-12 Thread Tim Bell
Tim Bell added the comment: This appears to be the same issue as subsequently reported in #34155. -- ___ Python tracker ___ ___ Pyt

[issue30701] Exception parsing certain invalid email address headers

2018-09-22 Thread Karthikeyan Singaravelan
Change by Karthikeyan Singaravelan : -- nosy: +xtreak ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https:/

[issue30701] Exception parsing certain invalid email address headers

2017-08-07 Thread Nick Coghlan
Changes by Nick Coghlan : -- nosy: +ncoghlan ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pytho

[issue30701] Exception parsing certain invalid email address headers

2017-06-19 Thread Tim Bell
Tim Bell added the comment: I'm using the email package to ingest a firehose of spam; spammers aren't known for following norms or standards, so it's not surprising that I'm discovering lots of edge cases. I'll supply fixes for what I find where I can, time permitting. -- ___

[issue30701] Exception parsing certain invalid email address headers

2017-06-19 Thread R. David Murray
R. David Murray added the comment: Yep, you found an edge case I didn't write a test for. The defect should get added to the header object during parsing. (Those are supposed to get copied to the message object...) -- ___ Python tracker

[issue30701] Exception parsing certain invalid email address headers

2017-06-19 Thread Tim Bell
New submission from Tim Bell: According to RFC 5322, an email address like this isn't valid: u...@example.com (The display-name "u...@example.com" contains "@", which isn't in the set of atext characters used to form an atom.) How it's handled by the email package varies by policy: >>> impo