If the selected EMAIL_CHARSET does not support the encoding for some of
the message characters the user get a hard to understand error:

Edit Error: 'latin-1' codec can't encode character u'\u20ac' in position
57: ordinal not in range(256)

For my need the attached quick-fix solves this Problem, but maybe a more
secure Handling is possible.


In addition I noticed that the msgXXX.tmp files for the failed messages
are not deleted and stay around forever. The code has a rollback()
function but I can't find any place where its called.

see also issue2550540 for another email encoding issue. It may be the
same underlying issue.