#25986: RFC 6532 support for e-mail
---------------------------------+------------------------------------
Reporter: sergei-maertens | Owner: nobody
Type: Bug | Status: new
Component: Core (Mail) | Version: 1.9
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
---------------------------------+------------------------------------
Comment (by sergei-maertens):
The upstream ticket has been closed, with the following comment:
> formataddr is part of the legacy interface and has no knowledge of the
current policy. So it doesn't support RFC 6532. For > that you need to
use the new API: just assign your address to the appropriate field, or
create a headerregistry.Address object.
>
> I'm in the process of rewriting the docs to make all of this clear, but,
well, I'm slow...
Looks like this will have to be solved on Django's end after all. I'm not
too familiar with the e-mail library yet, but I could look into it when I
get some more spare time.
--
Ticket URL: <https://code.djangoproject.com/ticket/25986#comment:3>
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.0ca8891275bb7ebdf2939cf55cbb485c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
