-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
utf8-encoded mails do not work properly #4
Comments
Go-MailHog doesn't currently have support for RFC2047 It should be relatively simple to add - I'll have a look as soon as I have time! |
Should be supported in v0.05 |
Tanks for the quick fix. |
Would have expected it to work but I'll have another look, could you give an example if you have one? |
I copied the plain-text part of the source of a mail. Again I removed sensitive information (also in the screenshot), but it should work and you get the idea.
|
Thanks @dpeuscher - I think that's covered in RFC2045, RFC2047 refers to the message headers. It should be fairly straightforward, I'll have a look when I get a chance! |
Will be fixed with #9 |
When trying to send utf8-mails the =?utf8-Prefix is not interpreted and the whole mail looks broken in the web interface (see screenshot)
The text was updated successfully, but these errors were encountered: