<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#ffffff">
<blockquote style="border: 0px none;"
cite="mid:4DC7C4A7.3000505@evnetwork.it" type="cite">
<table style="padding-top: 5px;" class="__pbConvTable">
<tbody>
<tr>
<td valign="top"><img
src="cid:part1.04030206.00000003@ade.pt"
photoaddress="davide@evnetwork.it" photoname="Davide
Mirtillo" name="compose-unknown-contact.jpg"
height="29px" width="29px"></td>
<td style="padding-left: 5px;" valign="top"><a
moz-do-not-send="true" href="mailto:davide@evnetwork.it"
style="color: rgb(0, 136, 204) ! important;
text-decoration: none ! important;">Davide Mirtillo</a><br>
<font color="#888888">May 9, 2011 6:40 AM</font></td>
</tr>
</tbody>
</table>
<div style="color: rgb(136, 136, 136); margin-left: 40px;"
__pbrmquotes="true" class="__pbConvBody"><br>
<div><!----><br>
There are loads of reasons why HTML messages are not good for
mailing<br>
lists. See [0] for some examples. </div>
</div>
</blockquote>
by the way, that page is from, like 2003. It talks about Compuserve
4. Netscape Communicator. (is that even still available?) Regarding
the scary language about html emails and attachments potentially
carrying viruses, Trojans & worm -- nowadays it's at least just
as likely, if not more likely, that you'll end up getting some
malware on your computer just by simply visiting a web site. As for
the risk involved in attachments, would you counsel everyone to
never end or open attachments, then? If you would not warn against
attachments, then why warn against html?<br>
<br>
As for the issues with bandwidth and message size ... hey, read your
mail via webmail and simply don't download to your computer, if your
bandwidth is metered. As for message size, hell, my keyboard has a
Delete key, how about yours?<br>
<br>
Anyhow. Really. I was one of the loudest plain text email
evangelists. In 2000 :-) <br>
Ten years in the world of online communications is like a century in
other modes of human interaction.<br>
I have never looked back. I have saved countless precious hours in
my lifespan by NOT having to use equal signs and dashes and create
phony boxes and other ways of making a long plain text email
bearable to read. Throw in a little bolding or a larger text size
and that sure sets off a section subhead nicely. Sorry, but I will
never see this as being a problem.<br>
<br>
<blockquote style="border: 0px none;"
cite="mid:4DC7C4A7.3000505@evnetwork.it" type="cite">
<div style="color: rgb(136, 136, 136); margin-left: 40px;"
__pbrmquotes="true" class="__pbConvBody">
<div>There's also an rfc about messaging<br>
which i think would be pretty interesting for some of the
members of<br>
this mailing list [1].<br>
</div>
</div>
</blockquote>
<br>
Um. That's from 1995. Even the Wikipedia page on that RFC mentions
that these community rules change in practice, are "in flux". And
the page doesn't even mention formatted email (i don't think, just
scanned quickly).<br>
<blockquote style="border: 0px none;"
cite="mid:4DC7C4A7.3000505@evnetwork.it" type="cite">
<div style="color: rgb(136, 136, 136); margin-left: 40px;"
__pbrmquotes="true" class="__pbConvBody">
<div><br>
Simply saying "omg it's 2011, get an html e-mail
client!1!!!!!" is not<br>
an answer, because it's not a logic argument, and i could just
reply on<br>
the same line: "omg it's 2011, learn to configure your e-mail
client<br>
properly!".<br>
</div>
</div>
</blockquote>
<br>
My only point in my earlier message was, again, this is a losing
battle. I also think it would be much nicer of folks *requested*
plain text emails rather than instruct or demand folks to learn how
to send them.<br>
<br>
omg, it's not 1995 anymore, Either get an html capable email client
or just delete everything that's not plain-text ... :-)<br>
<br>
kazar<br>
</body>
</html>