Issue Bug Rejected

#33633SwiftMailerAdapter doesn't handle Content-Transfer-Encoding correctly

Björn Steinbrink 02/02/12, 17:19 updated 04/13/13, 08:46

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.

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.