[Mailman-Users] Re: customized From handling?
Rich Morin writes: > [the blinux admins] would probably be more inclined to update > within version 2.1.x (and tweak the config a bit) than to move to > version 3. That's fine with us. We are proud of Mailman 2, it's just that a decade ago we could clearly see it was reaching the end of the line for major feature development. IMO, everybody should definitely update to the most recent version of Mailman 2 which is available from Launchpad via the bzr VCS (you can also download a tar.gz or maybe a .zip) as well as many distros' package repositories (if not the very most recent, something much better than 2.1.12 or 2.1.15). There have been *many* improvements since then, including the DMARC mitigations mentioned elsewhere in this thread that may help address this problem, but also a number of security issues that affect third parties (a few cross-site scripting vulnerabilities, for example) have been addressed. Staying up to date on Internet-facing software is just plain good citizenship. > Where can I find the right place to post a feature request for > Mailman 2.1.x? Here.[1] The answer will be "No" ;-) *but* that will be followed with (a) various suggestions for workarounds in the stock Mailman from developers and other users and (b) help with creating specific patches for sites to maintain for themselves. (a) is why I suggest here rather than mailman-developers -- other users are a great resource! We aren't opposed to folks developing Mailman 2 further, patch by patch. We're strict about devoting project resources to Mailman 3. Footnotes: [1] If it applies to Mailman 3 as well, an RFE on the tracker at https://gitlab.com/mailman would be appreciated, though. -- Mailman-Users mailing list -- mailman-users@python.org To unsubscribe send an email to mailman-users-le...@python.org https://mail.python.org/mailman3/lists/mailman-users.python.org/ Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/ https://mail.python.org/archives/list/mailman-users@python.org/
[Mailman-Users] messages being labeled as spam in the subject line?
Adam Morris writes: > I have seen on some mailman lists where messages sent to a list when > received by others have the word spam in the subject. Mailman does not do this, unless the list admin sets the subject tag to something containing "spam". > Is this a mailman setting that can be changed No. Mailman does have optional (quite primitive) spam filtering built in, all it does if it catches something spammy is hold it or discard it, depending on settings. Stock Mailman will not edit the message just because it's spammy. This filtering is off by default IIRC, because we recommend using it only as a last resort. Filtering should be done in the MTA, which has access to much more effective filtering options. > or is it a setting either with the mailman hosting provider? This should be the responsibility of the final recipient, not the Mailman host. Unfortunately the Mailman host MTA cannot automatically tell the difference between a mailing list post and other local mail. Worse, it may not be able to communicate this to a filter. If it turns out to be the Mailman host, the MTA needs to be reconfigured. In the simplest case, the MTA just gets a list of list addresses and sends mail for them to Mailman after doing its standard processing including spam filtering. In this case, you need to do a lot of reconfiguring and I can't get into it here. In most cases, every action taken by the MTA can be configured conditional on the address. It is a very bad idea to disable spam-checking for a mailing list. What needs to be done is to configure the spam-checker to *not* alter the Subject, but only for Mailman posts. Of course they could disable marking the Subject with "spam" for all mail, but that would surely get very strong pushback from the host admin. On the other hand, if you're sure enough that something is spam to edit the Subject, you really shouldn't be distributing it to a mailing list at all. This is going to be specific to the MTA and to the spam checker. -- Mailman-Users mailing list -- mailman-users@python.org To unsubscribe send an email to mailman-users-le...@python.org https://mail.python.org/mailman3/lists/mailman-users.python.org/ Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/ https://mail.python.org/archives/list/mailman-users@python.org/
[Mailman-Users] Re: messages being labeled as spam in the subject line?
I believe this is from random members replying to messages that were tagged as spam by the users' ISP/Mail software (eg false positives and/or broken spam filter settings). At Sun, 7 Nov 2021 15:23:05 +1100 Adam Morris wrote: > > I have seen on some mailman lists where messages sent to a list when > received by others have the word spam in the subject. > Is this a mailman setting that can be changed or is it a setting either > with the mailman hosting provider? > Thanks in advance. > -- Robert Heller -- Cell: 413-658-7953 GV: 978-633-5364 Deepwoods Software-- Custom Software Services http://www.deepsoft.com/ -- Linux Administration Services hel...@deepsoft.com -- Webhosting Services -- Mailman-Users mailing list -- mailman-users@python.org To unsubscribe send an email to mailman-users-le...@python.org https://mail.python.org/mailman3/lists/mailman-users.python.org/ Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/ https://mail.python.org/archives/list/mailman-users@python.org/
[Mailman-Users] Re: messages being labeled as spam in the subject line?
On 11/6/21 9:23 PM, Adam Morris wrote: I have seen on some mailman lists where messages sent to a list when received by others have the word spam in the subject. Is this a mailman setting that can be changed or is it a setting either with the mailman hosting provider? Both Steve and Robert have given relevant replies, but to summarize: It's not Mailman. The two possibilities that come to mind are: - The incoming MTA on the Mailman host has tagged the message as spam but delivered it to Mailman anyway. - A user is replying to a message that her MTA tagged as spam without removing the spam tag from the subject. For the second case, I'm sometimes guilty of this myself. My MTA (via MailScanner) tags subjects with {spam} or {disarmed} and I sometimes reply to such messages without removing the tag. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list -- mailman-users@python.org To unsubscribe send an email to mailman-users-le...@python.org https://mail.python.org/mailman3/lists/mailman-users.python.org/ Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/ https://mail.python.org/archives/list/mailman-users@python.org/