HTML email sent to lists migrated from Mailman 2.1
Hello all,
I have some lists migrated from 2.1 that are stripping the HTML parts (perhaps all attachments?) from messages despite the options to do so not being enabled and lynx not even being installed. I'm trying to get a new list to behave the same way so I can figure out what's going on without spamming a production list, but have been unsuccessful: despite setting nearly all the list options the same as the old lists, new lists pass HTML portions and attachments just fine.
I've verified the settings using mailing list objects directly with
mailman withlist on the command line and the only differences are things
that I can't imagine would be related like admin_notify_mchanges,
advertised, and archive_policy. Are there are really old options that can't
be accessed via mailing list objects obtained with withlist on the
command line?
Thanks, --nate
On 4/15/19 8:21 AM, Nate Coraor wrote:
I have some lists migrated from 2.1 that are stripping the HTML parts (perhaps all attachments?) from messages despite the options to do so not being enabled and lynx not even being installed. I'm trying to get a new list to behave the same way so I can figure out what's going on without spamming a production list, but have been unsuccessful: despite setting nearly all the list options the same as the old lists, new lists pass HTML portions and attachments just fine.
I've verified the settings using mailing list objects directly with
mailman withliston the command line and the only differences are things that I can't imagine would be related like admin_notify_mchanges, advertised, and archive_policy. Are there are really old options that can't be accessed via mailing list objects obtained withwithliston the command line?
No, there aren't "hidden settings"
The relevant settings are
filter_content filter_extensions filter_types pass_extensions pass_types collapse_alternatives convert_html_to_plaintext
These are exactly analogous to the MM 2.1 settings
filter_content filter_filename_extensions filter_mime_types pass_mime_types pass_filename_extensions pass_mime_types collapse_alternatives convert_html_to_plaintext
and should behave the same way.
Note that filter_extensions, filter_types, pass_extensions and pass_types are not exposed in Postorius, but can be seen and set via withlist.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Nate Coraor writes:
I have some lists migrated from 2.1 that are stripping the HTML parts (perhaps all attachments?) from messages despite the options to do so not being enabled and lynx not even being installed.
Did the host change? How about MTA and malmail checkers? Is it possible that something else is doing the stripping?
Lynx is not used in stripping. Do you have the HTML-to-text conversion option on? If so I can imagine that lack of Lynx would fall back to stripping (but that would be a bug, of course, and we'd want to fix it).
Is there anything in the logs?
It would help if you attached full configurations from a Mailman 2 list and the Mailman 3 list it migrated to. Obfuscate names and IP addresses as appropriate.
I'm trying to get a new list to behave the same way so I can figure out what's going on without spamming a production list, but have been unsuccessful: despite setting nearly all the list options the same as the old lists, new lists pass HTML portions and attachments just fine.
How about spamming the "mailman" (ie, administrator's) list? I think Mailman 3 still has that?
Since your hypothesis is that it has something to do with the conversion, one route would be to create a test list in a Mailman 2.1 installation and migrate it. Also, it should be possible to copy an existing production configuration, change the name of the config object, and use withlist to fix up the internal names. But that would have to be done very carefully.
Are there are really old options that can't be accessed via mailing list objects obtained with
withliston the command line?
I don't think so. There's no reason to hide them, and they wouldn't be recognized by Mailman 3 anyway.
-- Associate Professor Division of Policy and Planning Science http://turnbull.sk.tsukuba.ac.jp/ Faculty of Systems and Information Email: turnbull@sk.tsukuba.ac.jp University of Tsukuba Tel: 029-853-5175 Tennodai 1-1-1, Tsukuba 305-8573 JAPAN
On 4/15/19 8:03 PM, Stephen J. Turnbull wrote:
Lynx is not used in stripping. Do you have the HTML-to-text conversion option on? If so I can imagine that lack of Lynx would fall back to stripping (but that would be a bug, of course, and we'd want to fix it).
If convert_html_to_plaintext is True and html_to_plain_text_command fails for any of several reasons including the command not existing, the HTML part is left in the message.
How about spamming the "mailman" (ie, administrator's) list? I think Mailman 3 still has that?
Nope.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (3)
-
Mark Sapiro -
Nate Coraor -
Stephen J. Turnbull