Am 04.10.2014 23:44, schrieb Andrew Wood:
After doing some tests the problem appears to be a modification to the
Content-Type header
The incoming email and the one passed to BEmailMessage is in the form:
Content-Type: multipart/mixed;
boundary="_AA8B9F75-F456-45D0-96E8-99EF801DCBD4_"
but having passed through BEmailMessage and sent it ends up as:
Content-Type:
multipart/mixed;
=?iso-8859-15?q?boundary=3D?="_AA8B9F75-F456-45D0-96E8-99EF801DCBD4_
Why does it do this and is there a way to prevent it?
How do you fill the message? The default content type in the mail kit is iso-8859-15. Unless you specify a different one, this is the one being used.
Bye, Axel.
