At 07:27 PM 12/29/99 -0800, Jeremy Blackman wrote:
>I don't know about demime, but one of the things that NORM does is examine
>multipart/alternative and look for text/plain. If it finds it, it uses
>just that. If the message itself is in HTML, it renders it a'la Lynx and
>uses that plaintext rendition instead.
As a new user, I can vouch for demime: it handles those "= 20" codes,
handles rich text tags like [bold], rejects non-text portions of MIME
messages, uses the libwww perl modules to approximate the HTML format
in plain text, etc. Even strips out uuencoded data which has been
pasted into a plain text section. Generally does a nice job!
The answer is NOT to attack the mail tool or the mail sender, which
I tried doing for years. Many people LIKE having all that fancy stuff
in their email, but even more don't have a clue that it could possibly
look different to the receiver than to the sender (like changing the
width of the compose message window thinking that will re-wrap the
lines, using spaces with variable pitch fonts, etc).
The answer is to clean stuff up on the way to the list. Bouncing just
reduces the number of people who can/will post, stripping lets both
educated and clueless post in the way they feel most comfortable
WITHOUT exposing the subscribers to all the formatting.
SRE
mailto:[EMAIL PROTECTED] | http://www.climber.org/eckert/
Info on peak climbing email lists mailto:[EMAIL PROTECTED]
"The only possible interpretation of any research whatever
in the `social sciences' is: some do, some don't."
-- Ernest Rutherford
