#11212: Don't encode emails with base64/qp
---------------------------------------+------------------------------------
Reporter: phr | Owner: nobody
Status: new | Milestone:
Component: django.core.mail | Version: SVN
Resolution: | Keywords: send_mail
Stage: Accepted | Has_patch: 1
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 1 |
---------------------------------------+------------------------------------
Comment (by phr):
Replying to [comment:8 gisle]:
> I've included a patch that makes the tests pass, but as demonstrated by
the patch this make us start generating email with "`Content-Transfer-
Encoding: 8bit`" when passing in Unicode strings as subject or content. I
think that should be avoided, so I don't recommend this patch as is.
[[BR]]
The use of 8bit encoding is exactly the aim of this ticket, so the patch
does the right thing IMHO.
Except for a few legacy paths, SMTP is mostly 8bit today - and where not,
it's the MTA's role to downconvert to 7bit.
Many email clients are generating 8bit-encoded messages (Thunderbird,
Mutt, etc) and people routinely use 8bit email every day. Avoiding it
makes no longer any sense, and the current practice of using quoted-
printable does not work right for non-latin aplhabets.
Please note that other software already implemented my proposal - see e.g.
http://trac.edgewall.org/ticket/8252
--
Ticket URL: <http://code.djangoproject.com/ticket/11212#comment:10>
Django <http://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 post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
