[FFML] A thought on the future of the FFML

[Paul Henkel]

>> While I would certainly prefer for the chosen requirements to be either
>> plain text or something easily convertible to/from plain text (and that
>> can be discussed separately, though I'm not going to do it right this
>> moment), that's not essential for the type of dual-interface
>> compatibility that was being proposed; having the requirements be the
>> same in both interfaces *is* essential.
>
>
> The standard for email continues to be plain text in many
> cases, does it not?  Sure, there are an increasing number
> of HTML-friendly email clients, but is it a large enough
> percent that we can safely abandon the text-only (and
> HTML-badly-enough-implemented-that-it-might-as-well-be
> text-only) readers?

There is a simple reason that speaks for plain text: It is vastly more 
secure for the receiving party (and the reason for ff.net's heavy 
restrictions). Best to protect the readers of the is to scrub everything 
html like right as it is now:

> -------------- next part --------------
> An HTML attachment was scrubbed...

A multi part mail can be handled by pretty much every client of today. I 
personally use a mail proxy to clean my mail of every html tag.

Paul