Closed Bug 1297763 Opened 9 years ago Closed 9 years ago

email sent from an address in mailman "Sender filters" to be automatically discarded unexpectedly held for moderation

Categories

(Infrastructure & Operations :: Infrastructure: Mail, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: wsmwk, Unassigned)

References

Details

dev-apps-thunderbird is an unmoderated list, open to posting from non-subscribers. contact@c40foolprooflist.biz is in https://lists.mozilla.org/admin/dev-apps-thunderbird/privacy/sender "List of non-member addresses whose postings will be automatically discarded". But messages from this address are not being discarded. https://lists.mozilla.org/admindb/dev-apps-thunderbird?details=all shows the emails from this address which have been held for moderation. (note, this happened before I added ^.*@c40foolprooflist\.biz to the end of the sender discard list) So I am wondering why. And, whether https://lists.mozilla.org/admin/dev-apps-thunderbird/privacy/spam is taking precidence because the held messages do meet the criteria spam rule 4 and 5. It would be unfortunate if the spam rule takes precidence.
Summary: email sent from an address in Sender filters gets held for moderation → email sent from an address in Sender filters to be automatically discarded gets held for moderation
Still accumulating moderation requests for contact@c40foolprooflist.biz
Flags: needinfo?(limed)
See Also: → 1283374
Chris do you have any insight on how mailman does/should behave in this area? I haven't found anything that discusses precedence of privacy categories. Even http://www.list.org/mailman-admin/node20.html
Flags: needinfo?(bmo2010)
Summary: email sent from an address in Sender filters to be automatically discarded gets held for moderation → email sent from an address in mailman "Sender filters" to be automatically discarded unexpectedly held for moderation
(In reply to Wayne Mery (:wsmwk, NI for questions) from comment #2) > Chris do you have any insight on how mailman does/should behave in this area? Not really. I rarely create filters to auto-discard spam. The lists I moderate get so many different kinds of spam, I find creating filters for specific spam addresses not worth it. I just delete the notifications, and once a day, purge the moderation que. I do know that the filters in /privacy/sender/ don't apply to incoming newsgroup messages, which is why I usually use /privacy/spam/. I'll add contact@c40foolprooflist.biz to the /privacy/sender/ filters on the test mailing list, and see what happens.
Flags: needinfo?(bmo2010)
This is still happening. This morning I have Pending posts: From: admin@c40foolprooflist.biz on Fri Sep 16 20:18:39 2016 Subject: Welcome To The Team Cause: The message headers matched a filter rule
I can ask mailman about this, I am unsure if there is a precedence for that non-subscriber vs spam list. If this is becoming a problem I have no issues just blacklisting the c40foolprooflist.biz domain as well if it truly becomes an issue
Flags: needinfo?(limed)
It appears that spam checks do take precedence
I added admin@c40foolprooflist.biz to https://lists.mozilla.org/admin/test/?VARHELP=privacy/sender/discard_these_nonmembers a couple of days ago, and that seems to have worked on today's batch. Note that the latest ones us admin@ instead of contact@
Thanks for double checking all this for me. I can't believe one can't simply blacklist an address in mailman, and I don't find a bug report on it at https://bugs.launchpad.net/mailman (In reply to Ed Lim [:limed] from comment #5) > I can ask mailman about this, I am unsure if there is a precedence for that > non-subscriber vs spam list. If this is becoming a problem I have no issues > just blacklisting the c40foolprooflist.biz domain as well if it truly > becomes an issue I have no desire to deal with these addresses on a daily basis. So it would be great if were to blacklist the domain
https://bugs.launchpad.net/mailman/+bug/1625599/ states mailman's behavior is intentional and working as designed. Citing from the bug .... If you want to do membership tests (moderation and non-member tests) before header filter rules, you can configure that by putting the following in mm_cfg.py. GLOBAL_PIPELINE.remove('Moderate') GLOBAL_PIPELINE.insert(GLOBAL_PIPELINE.index('SpamDetect'), 'Moderate') You could also address this with a header_filter_rules rule of the form regexp: ^From:.*\WX@Y\.Z(\W|$) action: discard ahead of your other rules.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.