-
-
Notifications
You must be signed in to change notification settings - Fork 359
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is it possible to force UTF-8 encoding for Headers ? #493
Comments
Why do you need to enforce an encoding? Anything that handles UTF-8 will also handle iso-8859-1. It seems most people who ask me this THINK that it has to be UTF-8 but in reality it doesn't. |
2 reasons for this : 1/ We don't no exactly why, but for some mailing campaigns we obtain a higher spam score (VadeSecure) with iso encoding than with utf-8 2/ Some clients use an external Smtp relay service which seams not respect all rfc, it needs full utf-8 encoding for "From" header |
I'll look into making some changes which allow you to hard-code UTF-8. FWIW, here are the answers to your previous questions:
That specifies the encoding to use if MimeKit can't use us-ascii or iso-8859-1 (which it is using for max compatibility, but I suppose I could make it not try to use us-ascii or latin1)
Same as above. The |
…ser-specified charset Previously this could/would still use us-ascii and/or iso-8859-1 if the entire header could fit within one of those charsets. Fixes issue #493
Thank you for these changes, we'll test it as soon as possible. |
Describe the bug
It's not really a bug but rather a question.
Is it possible to force encoding for headers ?
Platform (please complete the following information):
To Reproduce
for MailboxAddress :
and for Subject :
Expected behavior
I understand that MimeKit uses the shortest solution, but I need to force headers' encoding (base64 utf-8)
The text was updated successfully, but these errors were encountered: