3 ms·
at the least you can be sending multipart/alternative to include both a text/plain and html body, so you don't have the horrible situation of people getting htm
by shabble 14y ago
at the least you can be sending multipart/alternative to include both a text/plain and html body, so you don't have the horrible situation of people getting html source dumped at them. Most webmail clients these days support 'rich content' to a reasonable degree, but a lot of people still have old desktop clients that'll just give up and throw it all at them.
That said, maintaining 2 templates or deciding exactly how to handle the formatting of the text version can be a hassle. I'm curious how others have handled this problem.
- tomwalsham 14y agoSending HTML-only email is still a large spam flag, even at major ISPs, independent of the concerns about client compatibility. At PostageApp our solution to the problem is a templating engine where you can write your HTML/CSS separately and we inline it at run time to ensure client compatibility. We then provide a separate Plaintext tab with an 'import from html' function which does most of the work for you for managing dual formats.