4teamwork/ftw.contentpage — pull request #164 by Tschanzt (2014-04-15 15:27:37+00:00)
Title: encode sender with utf-8

@maethu This encodes the sender with utf-8.
I do this because the Header class if given a unicode string tries to encode it in ascii first and only then encodes it with our given charset. Since ascii is treated like no encoding, we have problems with chars that have special meanings in the reply-to header(i.e. comma which is use is used for spliting addresses).

We now solve this problem by making the sender a bytestring because this way the Header class treats the charset we give it as encoding of the given string and always encodes it with this encoding. When this happens, the caracters loose their special meaning and get treated as normal chars which is what we want.