Hi,
I have updated the KNOWN_SPAMMERS array in the mm_cfg.py and then bounced the Qrunner. I am using Mailman 2.1.15 with postfix.
My known_spammer declaration is:
KNOWN_SPAMMERS =[('from', 'hellocatboots.*’)]
Is there something I am missing on blocking the subscription requests now? These are all coming in via email.
Thanks, Bryan
Bryan Teague | Senior Web Administrator | University Web Services | ITS | Maher Hall, Room 198 5998 Alcalá Park | San Diego, CA 92110-2492 | P: (619) 260-7842 | C: (619) 321-7288 bryant@sandiego.edu<mailto:bryant@sandiego.edu>
On 01/14/2016 09:45 AM, Bryan Teague wrote:
KNOWN_SPAMMERS is an old setting. The list's Privacy options... -> Spam filters -> header_filter_rules is much more powerful and flexible.
Is there something I am missing on blocking the subscription requests now? These are all coming in via email.
What makes you think they are all coming by email? All the ones I see come via the web, but in any case, neither KNOWN_SPAMMERS nor header_filter_rules is applied to mail to the listname-{join|subscribe|request} addresses. They only apply to mail to the list and to listname-owner.
You need to use the ban_list to stop these. See this post <https://mail.python.org/pipermail/mailman-users/2016-January/080303.html> and the posts and threads linked from that.
Do not be misled by the fact that that post refers to "the newly implemented, not yet released GLOBAL_BAN_LIST". Each list has it's own Privacy options... -> Subscription rules -> ban_list and there is a withlist script at <https://www.msapiro.net/scripts/add_banned.py> (mirrored at <http://fog.ccsf.edu/~msapiro/scripts/add_banned.py>) which can add the regexp to the ban_list for all lists.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Hi Mark,
Thank you very much. You were right, I was looking at the wrong log file. As soon as I identified the proper log file, I confirmed the subscriptions through the web page.
Using the with list and the add_banned.py as explained in your email and the other links was what finally solved it for me.
Each list has it's own Privacy options... -> Subscription rules -> ban_list and there is a withlist script at <https://www.msapiro.net/scripts/add_banned.py> (mirrored at <http://fog.ccsf.edu/~msapiro/scripts/add_banned.py>) which can add the regexp to the ban_list for all lists.
Thanks, Bryan
Bryan Teague | Senior Web Administrator | University Web Services | ITS | Maher Hall, Room 198 5998 Alcalá Park | San Diego, CA 92110-2492 | P: (619) 260-7842 | C: (619) 321-7288 bryant@sandiego.edu<mailto:bryant@sandiego.edu>
On Jan 14, 2016, at 10:25 AM, Mark Sapiro <mark@msapiro.net<mailto:mark@msapiro.net>> wrote:
On 01/14/2016 09:45 AM, Bryan Teague wrote: Hi,
I have updated the KNOWN_SPAMMERS array in the mm_cfg.py and then bounced the Qrunner. I am using Mailman 2.1.15 with postfix.
My known_spammer declaration is:
KNOWN_SPAMMERS =[('from', 'hellocatboots.*’)]
KNOWN_SPAMMERS is an old setting. The list's Privacy options... -> Spam filters -> header_filter_rules is much more powerful and flexible.
Is there something I am missing on blocking the subscription requests now? These are all coming in via email.
What makes you think they are all coming by email? All the ones I see come via the web, but in any case, neither KNOWN_SPAMMERS nor header_filter_rules is applied to mail to the listname-{join|subscribe|request} addresses. They only apply to mail to the list and to listname-owner.
You need to use the ban_list to stop these. See this post <https://mail.python.org/pipermail/mailman-users/2016-January/080303.html> and the posts and threads linked from that.
Do not be misled by the fact that that post refers to "the newly implemented, not yet released GLOBAL_BAN_LIST". Each list has it's own Privacy options... -> Subscription rules -> ban_list and there is a withlist script at <https://www.msapiro.net/scripts/add_banned.py> (mirrored at <http://fog.ccsf.edu/~msapiro/scripts/add_banned.py>) which can add the regexp to the ban_list for all lists.
-- Mark Sapiro <mark@msapiro.net<mailto:mark@msapiro.net>> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Mailman-Users mailing list Mailman-Users@python.org<mailto:Mailman-Users@python.org> https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/bryant%40sandiego.edu
On 01/14/2016 09:45 AM, Bryan Teague wrote:
KNOWN_SPAMMERS is an old setting. The list's Privacy options... -> Spam filters -> header_filter_rules is much more powerful and flexible.
Is there something I am missing on blocking the subscription requests now? These are all coming in via email.
What makes you think they are all coming by email? All the ones I see come via the web, but in any case, neither KNOWN_SPAMMERS nor header_filter_rules is applied to mail to the listname-{join|subscribe|request} addresses. They only apply to mail to the list and to listname-owner.
You need to use the ban_list to stop these. See this post <https://mail.python.org/pipermail/mailman-users/2016-January/080303.html> and the posts and threads linked from that.
Do not be misled by the fact that that post refers to "the newly implemented, not yet released GLOBAL_BAN_LIST". Each list has it's own Privacy options... -> Subscription rules -> ban_list and there is a withlist script at <https://www.msapiro.net/scripts/add_banned.py> (mirrored at <http://fog.ccsf.edu/~msapiro/scripts/add_banned.py>) which can add the regexp to the ban_list for all lists.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Hi Mark,
Thank you very much. You were right, I was looking at the wrong log file. As soon as I identified the proper log file, I confirmed the subscriptions through the web page.
Using the with list and the add_banned.py as explained in your email and the other links was what finally solved it for me.
Each list has it's own Privacy options... -> Subscription rules -> ban_list and there is a withlist script at <https://www.msapiro.net/scripts/add_banned.py> (mirrored at <http://fog.ccsf.edu/~msapiro/scripts/add_banned.py>) which can add the regexp to the ban_list for all lists.
Thanks, Bryan
Bryan Teague | Senior Web Administrator | University Web Services | ITS | Maher Hall, Room 198 5998 Alcalá Park | San Diego, CA 92110-2492 | P: (619) 260-7842 | C: (619) 321-7288 bryant@sandiego.edu<mailto:bryant@sandiego.edu>
On Jan 14, 2016, at 10:25 AM, Mark Sapiro <mark@msapiro.net<mailto:mark@msapiro.net>> wrote:
On 01/14/2016 09:45 AM, Bryan Teague wrote: Hi,
I have updated the KNOWN_SPAMMERS array in the mm_cfg.py and then bounced the Qrunner. I am using Mailman 2.1.15 with postfix.
My known_spammer declaration is:
KNOWN_SPAMMERS =[('from', 'hellocatboots.*’)]
KNOWN_SPAMMERS is an old setting. The list's Privacy options... -> Spam filters -> header_filter_rules is much more powerful and flexible.
Is there something I am missing on blocking the subscription requests now? These are all coming in via email.
What makes you think they are all coming by email? All the ones I see come via the web, but in any case, neither KNOWN_SPAMMERS nor header_filter_rules is applied to mail to the listname-{join|subscribe|request} addresses. They only apply to mail to the list and to listname-owner.
You need to use the ban_list to stop these. See this post <https://mail.python.org/pipermail/mailman-users/2016-January/080303.html> and the posts and threads linked from that.
Do not be misled by the fact that that post refers to "the newly implemented, not yet released GLOBAL_BAN_LIST". Each list has it's own Privacy options... -> Subscription rules -> ban_list and there is a withlist script at <https://www.msapiro.net/scripts/add_banned.py> (mirrored at <http://fog.ccsf.edu/~msapiro/scripts/add_banned.py>) which can add the regexp to the ban_list for all lists.
-- Mark Sapiro <mark@msapiro.net<mailto:mark@msapiro.net>> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Mailman-Users mailing list Mailman-Users@python.org<mailto:Mailman-Users@python.org> https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/bryant%40sandiego.edu
participants (2)
-
Bryan Teague -
Mark Sapiro