➜

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 sreepriya
Recipients Duke.Dougal, Illirgway, barry, lpolzer, r.david.murray, richard, sreepriya, vstinner
Date 2014-03-17.21:17:35
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1395091055.42.0.634956920747.issue19662@psf.upfronthosting.co.za>
In-reply-to
Content 
Hi David, 

I would like to work on this bug. Can you give some more insights about the main issue? As far as I understood, the smtp server is now decoding the incoming bytes as UTF-8. Why do you say that it is not the right way? Can you give some idea about the right convention?  Also, you mention about a solution with a switch statement having default case as utf8. What are the other cases? And you also mention that smtpd should be emitting binary and unicode should be handled by the email package. 
But is it possible to make that change now as other functions depending on this might be affected?
History
Date User Action Args
2014-03-17 21:17:35sreepriyasetrecipients: + sreepriya, barry, richard, vstinner, r.david.murray, lpolzer, Illirgway, Duke.Dougal
2014-03-17 21:17:35sreepriyasetmessageid: <1395091055.42.0.634956920747.issue19662@psf.upfronthosting.co.za>
2014-03-17 21:17:35sreepriyalinkissue19662 messages
2014-03-17 21:17:35sreepriyacreate