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 r.david.murray
Recipients barry, py.user, r.david.murray
Date 2014-11-10.14:50:45
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1415631046.02.0.625726872506.issue22833@psf.upfronthosting.co.za>
In-reply-to
Content
This is a duplicate of issue 6302.  Re-reading that issue (again), I'm not quite sure why we didn't fix it, but it may be too late to fix it now for backward compatibility reasons.

Since that issue strayed off into other topics, I'm going to leave this one open to consider whether or not we can/should fix this.  The new email API does avoid this problem, though.  Is there a reason you are choosing not to use the new API?
History
Date User Action Args
2014-11-10 14:50:46r.david.murraysetrecipients: + r.david.murray, barry, py.user
2014-11-10 14:50:46r.david.murraysetmessageid: <1415631046.02.0.625726872506.issue22833@psf.upfronthosting.co.za>
2014-11-10 14:50:46r.david.murraylinkissue22833 messages
2014-11-10 14:50:45r.david.murraycreate