> *mime_alternative_prefs: text/plain text/richtext text/html
>
> which says, given a a multiplart alternative, preferentially pick
> the text/plain first, then text/richtext, then text/html. This
> violates the RFC of course, but is also rather user friendly.
In what way does this violate th
After applying Earl's "case insensitivity" patch, I find the subject
threading of our Mercury/32 archives to be greatly enhanced. Nearly all
our "repeat subject" threads have been separated now.
Few questions:
1. Is it possible (using a resource) to get rid of the text that says
"possible follow
Given an archived message which contains a To: header with multiple
destinations ala:
To: [EMAIL PROTECTED], [EMAIL PROTECTED], "Bubb" <[EMAIL PROTECTED]>
How, via a resource or variable, can I get the entire contents of
the To: header? I seem to be able to get most every other field,
just n
> In other words, which part you choose to display is purely a local matter.
> There's nothing anywhere that says that the ability to display the "most
> faithful" version requires you to display it.
I would second this kind of capability. In our case, we would
always prefer to display plain t
