Swiftmailer integration does not use charset definitions in all cases
The swiftmailer integration does not use the renderCharset and metaCharset in all cases.
This results in broken e-mail encoding in some cases.
The first case is in the formmail content element. Here no charset is set if metaCharset equals renderCharset.
The second case is a bug in swiftmailer itself. The charset of the message is not used if a new part is added.
I added a patch, that let it work in my cases.
Updated by Jigal van Hemert over 12 years ago
- Status changed from New to Needs Feedback
- Assignee set to Jigal van Hemert
- Complexity set to medium
Can you give the setup how to reproduce the problem?
The problem inside SwiftMailer itself has to be fixed by the author of SwiftMailer. The problem is already reported (quite some time ago):
At first sight, it looks like the problem for TYPO3 could be solved by explicitly setting the charset for each part which is added.