>The majority of email clients today however are HTML aware, and the
>percentage of people using such HTML-aware clients is only increasing. The
>reasons are simple - it is easier to read (typically), and more information
>can be conveyed effectively. Other lists that I'm subscribed to have made
>good use of this capability by its members being able to send out queries or
>replies, including screen shots (inline with the text and not a random
>attachment). Being able to understand what is going on by the messages in
>these environments is much more effective than any text only group I've been
>involved with.
While this may be true, try reading your e-mail remotely via ssh and elm.
Using a graphical client is a little tough. Having all that extra text
for HTML is a waste.
Most messages going to mail lists are short and sweet. If there is an image
to go along with it, it can just be MIME attached, no need for HTML.
>Trying to hold back the tide at this point in terms of HTML usage within
>email seems like an exercise in futility. Better to get more up to date
>clients that can handle what has for all practical purposes become a defacto
>standard in email.
It is actually easy to force no HTML e-mail. Some mail lists actually have
software that removes HTML e-mail. So if you post an HTML only e-mail,
the message comes out blank.
HTML e-mail is also a pain for digest people, especially if they pay for each
character that arrives. I've seen some lousy MicroCrap produced HTML e-mail
that took 100 lines to send a 5 line message.
MB
--
e-mail: [EMAIL PROTECTED] It is God's job to forgive bin Laden.
It is our job to set up the meeting.
U.S. Marine Corp.
Visit - URL: http://www.vidiot.com/ (Your link to Star Trek and UPN)
--
redhat-list mailing list
unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe
https://listman.redhat.com/mailman/listinfo/redhat-list
