[Patch] ''Content-Transfer-Encoding'' header not allowed in the main mime container
|Reported by:||Thomas Moschny||Owned by:||Robert Corsaro|
|Cc:||Thomas Moschny||Trac Release:||0.11|
(At least the) ticket notification mails sent by the plugin contain in the main header the fields:
Content-Type: multipart/related; charset="utf-8"; boundary="..."
According to RFC 1521 (5. The Content-Transfer-Encoding Header Field) that is invalid (and may confuse certain email clients, hence the ticket):
"Certain Content-Transfer-Encoding values may only be used on certain Content-Types. In particular, it is expressly forbidden to use any encodings other than "7bit", "8bit", or "binary" with any Content- Type that recursively includes other Content-Type fields, notably the "multipart" and "message" Content-Types. All encodings that are desired for bodies of type multipart or message must be done at the innermost level, by encoding the actual body that needs to be encoded."
To fix the problem, the "Content-Transfer-Encoding:" field could simply be removed from the main header of the messages. This is valid and the standard value "7bit" will be assumed.
Change History (5)
comment:3 Changed 7 years ago by
|Cc:||Thomas Moschny added; anonymous removed|
|Summary:||''Content-Transfer-Encoding'' header not allowed in the main mime container → [Patch] ''Content-Transfer-Encoding'' header not allowed in the main mime container|