Warrl writes:

On Wed, 01 Mar 2000, Bob wrote:

...

On Tue, 29 Feb 2000, Warrl wrote:

...

...

My email client DOES handle HTML, but I set up a rule that spots HTML messages and transfers them directly to the trash without ever cluttering up the inbox.

Why do you do that, if you can read them? For one, I do have a few correspondents who send HTML routinely, and are interesting guys nevertheless :-). It's true that most of my correspondents avoid HTML.

...

If I read the headers correctly, we both use kmail 1.0.28. Mine does not handle the html but presents it as plain text. What do I set to change this?

I don't know, I just have a default install. Sometimes it renders HTML, sometimes it shows me the code. I haven't seen a pattern - but then I haven't looked for one.

Even if not strictly mandated by MIME standards, the normal way for the sender is to send a multipart/alternative structure, with a text/plain rendering of the message appearing first, and a text/html version appearing later. MIME strictly says that the alternative selected is the last appearing one for which the mail user agent has all the needed machinery to display. So parts within the alternative are usually ordered by increasing "complexity". It means that if you cannot display HTML (or ask your mail user agent to not do it), the text version should get displayed. Given the current state of affairs, I consider rude that someone widely broadcasts an HTML message without at least a text/plain rendering of it. Nowadays, in my opinion, it is excusable (and even commandable? :-) that one expects everybody else to be MIME-aware, but still premature to expect everybody to use a mail reader able to render HTML. P.S. - This is merely out of memory, please correct me if wrong. -- François Pinard http://www.iro.umontreal.ca/~pinard -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/