Problem with <head> being modified when sending from GMail (breaks adaptive). #218
Unanswered
benmehlman
asked this question in
Help
Replies: 1 comment
-
I did some more work on this. It's simply the Content-Transfer-Encoding being quoted-printable that's messing things up.. the email is being wrapped to 80 columns with "=" escaping the newline.. which, seems to be ok because despite many lines being continued in that way, gmail has no problem decoding it and rendering the HTML with no visible breakage.. but: If create an email by hand.. in a text editor.. pasting the bootstrap-email output in the body.. adding the necessary RFC822 headers.. then send it with sendmail.. omitting any content-transfer-encoding.... IT WORKS. I suspect that the problem is the doctype header, not sure yet. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Thanks to the devs for this useful project! I'm having a small problem:
When I send a test email from the web-based editor, it works very well to a gmail recipient (myself) including adaptive behavior of my grid layout (displays 3 x 2 in browser, but 1 x 6 in mobile, which is what I want).
BUT when I copy the rendered HTML, and send the email from gmail, it works.. but adaptive is broken.
When I looked at the raw email, I could see first, that it was a multipart/mixed email, whereas the test email is a simple html email with no multipart. I could also see that elements of the had been removed and either moved to the body or missing. It was not the same as was rendered by bootstrap-email.
So the next thing I tried is to use Thunderbird connected to my gmail account (smtp.gmail.com) .. and this allows me to control the content type (Sending Format: Only HTML) and to easily paste HTML into the editor with "Insert HTML".. this results in a simple message body the same as the editor Test Email. Yet, the received html is still not the same as what I sent. It seems like gmail is messing with it on the way out...
Again, the problem occurs when I send FROM gmail (whether via their web client or their SMTP server). If I send from elsewhere TO gmail, it works correctly. Unfortunately my employer is a Google Apps user and it would cause a lot of problems if I had to send the email a different way.
Has anyone else experienced this?
Thanks
Ben
Beta Was this translation helpful? Give feedback.
All reactions