Content filtering and HTML emails. Bug?
This may be a bug...
Mailman is converting html messages to plain text even when set not to convert. And it is not an MUA issue. We just verified this using web-based Gmail on both ends.
Background (from past discussions on this list):
Here is the question: http://mail.python.org/pipermail/mailman-users/2007-December/059517.html
Mark Sapiro's answer: http://mail.python.org/pipermail/mailman-users/2006-April/050753.html
We see different (incorrect?) behavior:
To reproduce:
- Turn content filtering on, but set plain text conversion to NO:
Should Mailman convert text/html parts to plain text: No
- Send html emails through the list using web-based gmail on each end.
Expected result:
Receive HTML when an HTML message is sent.
Actual result:
Plain text messages are received. HTML messages are converted to plain text by Mailman. I believe the next step shows it is not an MUA issue.
Next step:
Turn content filtering OFF. No need to make any other changes.
Send html emails through the list using web-based gmail on each end.
Expected result:
Receive HTML when an HTML message is sent.
Actual result:
It works correctly now. HTML messages are not converted to plain text by Mailman.
David <dave@fiteyes.com> wrote:
Is text/html in the pass_mime_types content filtering setting?
Is collapse_alternatives set to No?
I suspect that one or both of those is not the case, and setting them will solve your problem.
I further suspect that collapse_alternatives is the issue. Gmail creates a multi-part alternative message with a text/plain alternative containing Gmail's conversion of the HTML and a text/html alternative containing the HTML.
If collapse_alternatives is Yes, Mailman simply replaces the multipart/alternative part with the first (i.e.text/plain) alternative.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
David <dave@fiteyes.com> wrote:
The easy solution is to allow only plain text, but that's not going to work for you. See the FAQ at <http://wiki.list.org/x/84A9> for a more complete discussion.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
David <dave@fiteyes.com> wrote:
Is text/html in the pass_mime_types content filtering setting?
Is collapse_alternatives set to No?
I suspect that one or both of those is not the case, and setting them will solve your problem.
I further suspect that collapse_alternatives is the issue. Gmail creates a multi-part alternative message with a text/plain alternative containing Gmail's conversion of the HTML and a text/html alternative containing the HTML.
If collapse_alternatives is Yes, Mailman simply replaces the multipart/alternative part with the first (i.e.text/plain) alternative.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
David <dave@fiteyes.com> wrote:
The easy solution is to allow only plain text, but that's not going to work for you. See the FAQ at <http://wiki.list.org/x/84A9> for a more complete discussion.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (2)
-
David -
Mark Sapiro