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 terry.reedy
Recipients barry, jcea, kushal.das, msapiro, r.david.murray, terry.reedy
Date 2013-03-20.20:50:45
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1363812646.16.0.573441075227.issue5713@psf.upfronthosting.co.za>
In-reply-to
Content
Given that David is usually more conservative about calling things bugs than I am, knows more about this subject than me, and has explained that the change will make smptlib act more sanely in the face of external errors, I am reversing myself and agreeing with him.

The patch seems to tighten the test in a way relevant to the code change.

I see that there are several open smptlib issues.
Should we open one for 'update to rfc 5321'?
Does the absence of 'obsoleted by' (or similar) mean that it is still the latest?
History
Date User Action Args
2013-03-20 20:50:46terry.reedysetrecipients: + terry.reedy, barry, jcea, msapiro, r.david.murray, kushal.das
2013-03-20 20:50:46terry.reedysetmessageid: <1363812646.16.0.573441075227.issue5713@psf.upfronthosting.co.za>
2013-03-20 20:50:46terry.reedylinkissue5713 messages
2013-03-20 20:50:45terry.reedycreate