#25986: RFC 6532 support for e-mail
-------------------------------------+-------------------------------------
Reporter: sergei-maertens | Owner: sergei-
| maertens
Type: Bug | Status: assigned
Component: Core (Mail) | Version: 1.9
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by sergei-maertens):
* has_patch: 0 => 1
Comment:
As I was implementing this, some extra information:
* The RFC 6532 is a red herring. The actual issue was that the unicode
characters were not properly [https://en.wikipedia.org/wiki/MIME#Encoded-
Word MIME word-encoded]. To support said RFC, an extra mail-server plugin
must be enabled, so I went the safe way for Django where that's not
needed.
* There are major differences between Python 2 and 3. This is the case in:
* the FakeSMTPServer in the testcases, where the `mailfrom` variable
might not be MIME-word-encoded all the way.
* the usage of `Header(<string>, <encoding)`, where the `str`
representation calls the `encode` method on Python 2 and on Python 3 it
simply returns the initial `<string>` that was passed in.
**Potential issue**:
Because of the difference in `str` representation, that has been altered
to always call the `encode` method. This causes simple ascii local parts
to look garbled, for instance: `t...@example.com` becomes
`=?utf-8?q?to?=@example.com`. When django users test the e-mail messages
generated by Django, they may have failing tests because they're not
expecting the encoded version. I have not personally confirmed this yet
though.
--
Ticket URL: <https://code.djangoproject.com/ticket/25986#comment:7>
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/073.581853bea91f5f043dadad96cd5f5a47%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
