You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The text and html body parts should always be sent using quoted-printable encoding. This way, even old 7bit-only smtp server won't have any problems in accepting and relaying the mail. Other possible 7bit-compatible encodings like base64 obfuscate too much of the content for debugging purposes.
The subject line and the name parts in the from: and to: header fields should similarly be encoded using quoted printable, enabling the use of utf-8 characters there as well.
Short description of the issue
Umlauts (non-ascii characters) used in the body or subject of messages sent using WireMail appear mangled.
Expected behavior
Umlauts should display as entered.
Actual behavior
Umlauts display as two characters with their raw ascii representation.
Optional: Screenshots/Links that demonstrate the issue
See forum discussion
Optional: Suggestion for a possible fix
The text and html body parts should always be sent using quoted-printable encoding. This way, even old 7bit-only smtp server won't have any problems in accepting and relaying the mail. Other possible 7bit-compatible encodings like base64 obfuscate too much of the content for debugging purposes.
The subject line and the name parts in the from: and to: header fields should similarly be encoded using quoted printable, enabling the use of utf-8 characters there as well.
Pull request submitted as processwire/processwire/pull/17
Steps to reproduce the issue
See the examples in the forum discussion
Setup/Environment
The text was updated successfully, but these errors were encountered: