"UTF8 text" in email migration API
22 views
Skip to first unread message
Chaskiel Grundman
Oct 2, 2012, 10:43:16 AM10/2/12
to google-app...@googlegroups.com
The python client for the email migration api still uses the deprecated
base64 encoding method and does not work with oauth2, so I am planning
on writing a custom client.
The documentation says:
To migrate mail messages into a hosted Gmail account, issue multipart
What if the message contains 8 bit characters in a non-utf8 character set?
e.g.
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
Am I supposed to recode the message as utf8? Encode the body/affected message parts with base64 or quoted-printable (so that the HTTP body is ASCII/utf8 even if the email message is not)?
I have done some tests, and it appears the migration service currently accepts 8bit iso8859-1 messages, and Gmail displays them the same as 8bit iso8859-1 messages delivered by smtp.
The documentation says:
To migrate mail messages into a hosted Gmail account, issue multipart
POST
requests, [...] the second part contains the complete
RFC 822 message as UTF-8 text.What if the message contains 8 bit characters in a non-utf8 character set?
e.g.
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
Am I supposed to recode the message as utf8? Encode the body/affected message parts with base64 or quoted-printable (so that the HTTP body is ASCII/utf8 even if the email message is not)?
I have done some tests, and it appears the migration service currently accepts 8bit iso8859-1 messages, and Gmail displays them the same as 8bit iso8859-1 messages delivered by smtp.
Reply all
Reply to author
Forward
0 new messages