On 2013-10-08, at 00:51, "Shawn K. Quinn" <[email protected]> wrote:
> On Mon, Oct 7, 2013, at 07:39 PM, Sandy Harris wrote: >> On Mon, Oct 7, 2013 at 5:56 PM, Travis Biehn <[email protected]> wrote: >>> This isn't the mailing lists job; it is your clients job. >>> If you don't want to see HTML email then use a client that can't / won't >>> interpret it. >> >> It is the sender's job. No-one should be sending such stuff >> to a public list since it serves no useful purpose. If your >> client won't send clean ASCII-only email, then switch to >> a client that will. >> >> If senders do not do that, there are four options: flame >> them to a crisp (off-list, please!), let every reader handle >> it, remove the HTML at the server, or set the server to >> drop such messages entirely. I'd prefer the last, with >> an appropriate bounce message, > > I think the third option is a reasonable compromise. I have reluctantly > began to tolerate some HTML mail since I am doing some marketing > research and consulting. But on a list like this, I agree, cute pink > bunny backgrounds, funny fonts, and a number of other silly things that > HTML mail allows don't belong. For that matter I can't think of one good > reason to allow HTML mail. I can think of plenty of bad reasons > though... It is the user/client's responsibility. Otherwise, you are susceptible to tracking pixels. Which I include in most of my emails these days. I say as I send from my work machine, with a client that is entirely vulnerable to the things I argue are terrible. -- ~j
signature.asc
Description: Message signed with OpenPGP using GPGMail
