id summary reporter owner description type status priority component severity resolution keywords cc release 6171 [Patch] ''Content-Transfer-Encoding'' header not allowed in the main mime container Thomas Moschny Robert Corsaro "(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=""...""''[[br]] ''Content-Transfer-Encoding: base64'' According to RFC1521 (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. " defect closed normal AnnouncerPlugin normal fixed Thomas Moschny 0.11