Marci Abraham O'Daffer wrote:

I am having a hard time understanding how mm handles HTML mail. I realize the digest pretty much trashes it, and the archive does not preserve it, but is there any way to make either of them behave so that the end user has a digest or an archive that is more readable?

If your goal is simply to have readable messages on your list, turn on content filtering and allow only multipart/mixed, multipart/alternative, message/rfc822 and text/plain in pass_mime_types. This will insure that only plain text reaches the list, the digest and the archives.

You can also experiment with turning on convert_html_to_plaintext and adding text/html to the above list, but there is a problem with HTML to plain text conversion if the HTML part is also encoded base64 or quoted-printable. Note that with this filtering, a multipart/alternative part with text/plain and text/html sub-parts will by design have the HTML part stripped in favor of the plain text part rather than converted.

If your goal is to actually deliver HTML formatted messages to the list, then you won't want the above. If the users select MIME format digests, then messages containing HTML might be more readable in the digest. I'm not sure of this as I've never tried it.

-- Mark Sapiro <msapiro@value.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan