Although I recommend against HTML email, I've been getting a *lot* of pressure from clients for HTML email. So I bite the bullet, get them to at least agree to an opt-out to plain text (or preferably an opt-in for html).
Back when I did consulting (well, I'm technically a consultant now, but it's a long-term relationship, not like the stuff I used to do, which I hated), I found that a lot of times the customer would think they knew what they wanted, but they often didn't have enough information to have made that decision.
Often, you have to educate them, and help them determine what it is that they really should be asking for, and setting the appropriate expectations for what it is that you're going to be doing for them.
If someone insists that they really want HTML e-mail, I would try to get them to step back for a second, and determine what it is that they're trying to achieve. Sometimes, what they're trying to do really does require HTML e-mail. Most of the time, however, they can just do it in plain text, and include a URL to 'View the HTML version of this message'.
Sometimes, you just need to explain the differences in the protocols, the issues with linking in images in HTML e-mail (it's either bulky, or a privacy issue), the general pain in the ass that is HTML, and how getting people desensitized to opening HTML e-mail can result in security issues.
In reply to OT: Re^4: embedding hyperlink using Mail::Sendmail
by jhourcle
in thread embedding hyperlink using Mail::Sendmail
by Anonymous Monk
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |