1. Emails containing MIME boundaries with parentheses will now be properly handled.
Previously, emails with parentheses in the MIME boundaries, such as a boundary like:
Content-Type: multipart/mixed; boundary="nqp=nb64=()BDXjw0yWx"
would cause the JangoSMTP parser to throw an error. This is now fixed.
2. Emails containing unrecognized Content-Transfer-Encoding types will now default to "7bit".
Previously, if an email message contained an unrecognized or misspelled encoding type, like:
Content-Transfer-Encoding: 7 bit
would cause the JangoSMTP parser to throw an error. This is now fixed.
3. Emails containing foreign characters encoded as ISO-8859-1 will be properly handled.
Previously, an email containing certain foreign characters would have those characters replaced with ? marks or garbled when passed through the relay. For example, a Subject like:
Subject: Confirmation d'Inscription à la Liste de Diffusion - Liste TEST ML
would not have its foreign characters preserved. This is now fixed.
