On Wed, Feb 13, 2002 at 02:22:07AM -0500, Aaron Haviland wrote:
...or he could just configure it properly :-)
It is configured properly, IMO. - Aside from the whole "email is TEXT goddamnit" argument (which I happen to agree with) have you seen some of the sludge that some of these mailreaders generate and label as HTML? - If the sender's email app is set up properly, even if it is sending an HTML version it should at least have the courtesy to include a plain text version as well. - I read my email through a web frontend ocasionally. I have it configured to only read the text portion of the message, because I'm usually using it from something other than my own machine, so I have no idea if it even has basic security precautions against HTML viruses/trojans/etc in place. - Going text -> HTML increases bandwidth needed (by 3 or 4 times with some of the "let's explicitly wrap everything in every tag we can think of" jobs I've seen - there's a reason the program to beautify FP output is called demoroniser), but rarely adds little additional content. Why waste bandwidth? -- Frank Sweetser fs at wpi.edu, fs at suave.net | $ x 16 Full-time WPI Network Tech, Part time Linux/Perl guy | I went to the eye doctor and found out I needed glasses for reading. So, I got some flip-up contact lenses. -- Stephen Wright