Gmail API method removes Content-Transfer-Encoding
-
Hi, I just noticed the following strange behaviour:
If I set your plugin to use SMTP as the transport type, configured to route through Gmail’s server, then a plain-text email generated by one of my other plugins will have these standard fields in the header:
Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline
But if I change your plugin to use Gmail API as the transport type, then the exact same plain-text email generated by the other plugin, will only have this field in the header, and not the other two:
Content-Type: text/plain; charset="UTF-8"
As a result, the text in the 2nd email (using Gmail API) is wrapped in my mail client – ie. the text doesn’t go more than about 70 or so characters wide before a line break.
However, the text in the 1st email (using SMTP) is not wrapped at all, and extends the full width of the screen in my email program, as it should.
Do you know if your plugin is doing this, or if the Gmail API is to blame?
Cheers!
- The topic ‘Gmail API method removes Content-Transfer-Encoding’ is closed to new replies.