Author maxking
Recipients Dain Dwarf, Windson Yang, barry, bortzmeyer, cnicodeme, jpic, kal.sze, maxking, msapiro, ned.deily, nicoe, r.david.murray, vstinner, xtreak
Date 2019-06-01.19:20:33
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1559416833.73.0.0656305198822.issue34155@roundup.psfhosted.org>
In-reply-to
Content
I don't know if we can make the API consistent between parseaddr and the parsing header value since they are completely different even right now. Like you already noticed there is no way to register defects and instead parseaddr returns ('', '') to denote the failure to parse.

About parsing malicious domain, my line of thinking was along the lines of presenting whatever is there to user of the API, without 'hiding' that information. It would be harder to figure out the exception if the domain is missing. 

Even though the domain is parsed in the `domain` value, the value itself is clearly invalid. Any attempt to ever use that Address() will definitely cause an error (perhaps, there should be a sanity check in SMTP.send_message for that?).
History
Date User Action Args
2019-06-01 19:20:33maxkingsetrecipients: + maxking, barry, vstinner, msapiro, ned.deily, r.david.murray, nicoe, kal.sze, Windson Yang, xtreak, cnicodeme, bortzmeyer, jpic, Dain Dwarf
2019-06-01 19:20:33maxkingsetmessageid: <1559416833.73.0.0656305198822.issue34155@roundup.psfhosted.org>
2019-06-01 19:20:33maxkinglinkissue34155 messages
2019-06-01 19:20:33maxkingcreate