➜

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 hwgdb Smith
Recipients barry, dorosch, hwgdb Smith, r.david.murray
Date 2020-02-27.15:31:58
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1582817518.24.0.138996786246.issue39771@roundup.psfhosted.org>
In-reply-to
Content 
Using utf-8 doesn't display correctly on my mail client.
So i thought it might work using GBK, and I try to change the Content-Disposition filename using GBK.
And just now, I print the legacy Api MIMEMultipart.as_string(), I found it using utf-8 too. The difference is 
legacy api:  filename="=?utf-8?b?6LaFZeS/nTMwMDBQLmNzdg==?="   
EmailMessage: filename*=utf-8''.%2F%E8%B6%85e%E4%BF%9D3000P.csv

So it is not the encoding cause the display error. But I still don't know why? Base64?
History
Date User Action Args
2020-02-27 15:31:58hwgdb Smithsetrecipients: + hwgdb Smith, barry, r.david.murray, dorosch
2020-02-27 15:31:58hwgdb Smithsetmessageid: <1582817518.24.0.138996786246.issue39771@roundup.psfhosted.org>
2020-02-27 15:31:58hwgdb Smithlinkissue39771 messages
2020-02-27 15:31:58hwgdb Smithcreate