EmailMessage and send_email do not handle ugettext_lazy translated addresses correctly

[Mike Edmunds]

Most (all?) of the core email backends seem to have issues with lazy strings used as addresses: to, cc, etc.:

>>> from django.utils.translation import ugettext_lazy as _
>>> from django.core.mail import send_mail
>>> send_mail('Subject', 'Content', _('from@example.com'), [_('to@example.com')])
... TypeError: sequence item 0: expected str instance, __proxy__ found

(#7574 fixed this for subject and content, but not the address fields.)

Patch coming shortly.

[Mike Edmunds]

Test case and fix: ​https://github.com/medmunds/django/tree/ticket_24416
Pull request: ​https://github.com/django/django/pull/4211

[Tim Graham]

I'm curious what the use case is for having translatable email addresses?

[Mike Edmunds]

A reasonable use case is for the human-readable name -- you'd like the language on that to match the (lazy-translated) language of the email content:

"Customer Service <support@example.com>"
"Servicio Al Cliente <support@example.com>"

It's not inconceivable that the address-part might change, too:

"Translation team <L11n-en@example.com>"
"Les traducteurs <L11n-fr@example.com>"

[Tim Graham <timograham@…>]

In 5993b52:

Fixed #24416 -- Added support for lazy email addresses.