Title: Gmail API method removes Content-Transfer-Encoding
Last modified: August 30, 2016

---

# Gmail API method removes Content-Transfer-Encoding

 *  [GermanKiwi](https://wordpress.org/support/users/germankiwi/)
 * (@germankiwi)
 * [10 years, 6 months ago](https://wordpress.org/support/topic/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!
 * [https://wordpress.org/plugins/postman-smtp/](https://wordpress.org/plugins/postman-smtp/)

Viewing 2 replies - 1 through 2 (of 2 total)

 *  Plugin Author [Jason Hendriks](https://wordpress.org/support/users/jasonhendriks/)
 * (@jasonhendriks)
 * [10 years, 6 months ago](https://wordpress.org/support/topic/gmail-api-method-removes-content-transfer-encoding/#post-6774510)
 * Hi. I’ve noticed this myself. AFAIK, it’s the Gmail API strips the quoted-printable.
   I always meant to dig into the API and see if there was a way to prevent that.
 *  Thread Starter [GermanKiwi](https://wordpress.org/support/users/germankiwi/)
 * (@germankiwi)
 * [10 years, 6 months ago](https://wordpress.org/support/topic/gmail-api-method-removes-content-transfer-encoding/#post-6774588)
 * Okay good to know. Certainly strange though! I’d have thought the API would just
   pass the email right on through without modifying any part of it. Well, if you
   are able to find a way around it, please let me know! I’ll have to switch to 
   the SMTP method in the meantime, as I don’t want to have forced line-wraps in
   my emails.

Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘Gmail API method removes Content-Transfer-Encoding’ is closed to new 
replies.

 * ![](https://s.w.org/plugins/geopattern-icon/postman-smtp_7c7b78.svg)
 * [Postman SMTP Mailer/Email Log](https://wordpress.org/plugins/postman-smtp/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/postman-smtp/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/postman-smtp/)
 * [Active Topics](https://wordpress.org/support/plugin/postman-smtp/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/postman-smtp/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/postman-smtp/reviews/)

 * 2 replies
 * 2 participants
 * Last reply from: [GermanKiwi](https://wordpress.org/support/users/germankiwi/)
 * Last activity: [10 years, 6 months ago](https://wordpress.org/support/topic/gmail-api-method-removes-content-transfer-encoding/#post-6774588)
 * Status: not resolved