Actions
Bug #33633
closed
SwiftMailerAdapter doesn't handle Content-Transfer-Encoding correctly
Status:
Rejected
Priority:
Must have
Assignee:
-
Category:
-
Target version:
-
Start date:
2012-02-02
Due date:
% Done:
0%
Estimated time:
TYPO3 Version:
4.5
PHP Version:
Tags:
Complexity:
Is Regression:
Sprint Focus:
Description
If there's a Content-Transfer-Encoding header set in the incoming mail, the adapter class sets that header for the SwiftMailer message, but doesn't change the encoder of the message. Thus it always uses the default encoder (quoted printable), which causes messed up messages when the mail that gets handed into the adapter is encoded differently. Strictly, the bug is in SwiftMailer, because it allows messing with the Content-Transfer-Encoding header without observing it to change the encoder accordingly. But for the time being, I guess the adapter should learn to just special case that header and do the encoder update itself.
I'll submit a patch for review tomorrow.
Updated by 
Updated by 
Updated by
Actions