#26227: Unicode attachment filename displays incorrectly in some clients
-------------------------------------+-------------------------------------
Reporter: Sergey Gornostaev | Owner: nobody
Type: Bug | Status: new
Component: Core (Mail) | Version: 1.9
Severity: Normal | Resolution:
Keywords: email attachment, | Triage Stage:
filenames, i18n | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Simon Charette):
* status: closed => new
* resolution: needsinfo =>
Comment:
I managed to reproduce by sending an email to a @gmail.com address with an
attachment containing non-ASCII characters on master.
{{{#!python
msg = EmailMultiAlternatives('Subject', 'Body', '...@gmail.com', [
'...@gmail.com'])
msg.attach(u'Имя файла', BytesIO(b'hello word'), 'text/plain')
msg.send()
}}}
The issue seems to be that GMail ignores RFC2231 header parameters (e.g.
`filename*=`) and only accepts RFC2047 ones (`filename=?UTF...`).
The code changes suggested by Thomi include both parameters if the
attachment name is not ASCII encodable.
--
Ticket URL: <https://code.djangoproject.com/ticket/26227#comment:9>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/068.c3e50c6a56c432d71baaae6defad8eb2%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
