Last modified: 2014-11-15 12:04:01 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T70992, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 68992 - Spam filter rules on the Wiki Loves Monuments Mailing list not working
Spam filter rules on the Wiki Loves Monuments Mailing list not working
Status: RESOLVED WORKSFORME
Product: Wikimedia
Classification: Unclassified
Mailing lists (Other open bugs)
wmf-deployment
All All
: Low minor (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-08-01 08:00 UTC by Cristian Consonni
Modified: 2014-11-15 12:04 UTC (History)
8 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Cristian Consonni 2014-08-01 08:00:02 UTC
Hi all,

Togheter with Effeietsanders I am administering the wikilovesmonuments-l mailing list[0].
This list is receiveing huge amounts of spam messages (quick stat: we are talking about 20 messages per hour).

We have tried to implement some spam filter rules following this[1] (a page which I have edited myself) but basically we were unable to get any effect of sorts.

Here's the two spam filtering rules I have created:
* Rule 1: X-Spam-Score: [+]{2,99}
* Rule 2: X-Spam-Score: [*]{2,99}

I have added both rules with "+" and "*" to be sure, and I have specified the numbers (more or equal than 2 and less or equal than 99) because in my first try the rule with just {2,} (i.e. "more or equal than 2") was not working.

The fact is that the solution didn't work out in the end (we were still holding in our moderation queue lots and lots of messages with an high spam score) and so we are changing the default policy for the list about non-member messages from "Hold" to "Reject" (see [2])

This was quite frustrating, but we were unable to fix the problem is
some other way. I am sharing this to make sure I wasn't making some
sort of stupid mistake in the rules.

This other bug report is related[3].

Thank you.

Cristian

[0] https://lists.wikimedia.org/mailman/listinfo/wikilovesmonuments
[1] https://wikitech.wikimedia.org/wiki/Mailing_lists#Fighting_spam_in_mailman
[2] http://lists.wikimedia.org/pipermail/wikilovesmonuments/2014-July/007319.html
[3] https://bugzilla.wikimedia.org/show_bug.cgi?id=56525
Comment 1 Seb35 2014-08-01 08:54:37 UTC
I have no experience with the spam level and Mailman, so I let someone else answer on this point.

For the Reject vs Discard mentionned in your original wikitech email, following [1], Reject rejects the message and warn the sender his/her message was rejected, and Discard rejects the message without any warning send to the sender. The latter is better for spam issues (because of the [[backscatter]] problem, i.e. someone whose address was spoofed by a spammer will get warnings when his/her address is rejected on some mailing lists, even if s/he is not the original sender to the mailing list), but it can be an issue for legitimate users (do not know their message was rejected). At the least, you can add some warning on the info page to say only members can send emails.

[1] http://staff.imsa.edu/~ckolar/mailman/mailman-administration-v2.html (search "discard")
Comment 2 Andre Klapper 2014-08-16 11:07:57 UTC
It's not clear to me if there is a request in this report for some technical change to fix or work around some well-defined (and described) problem.
And how this is different from what's requested in bug 56525.

Could you please clarify?
Comment 3 Andre Klapper 2014-09-18 13:27:49 UTC
Please answer comment 2.
Comment 4 John F. Lewis 2014-10-16 21:09:43 UTC
Poke for the above. It should technically work with a discard.
Comment 5 Andre Klapper 2014-11-15 12:04:01 UTC
Unfortunately closing this report as no further information has been provided.

Cristian: Please feel free to reopen this report if you can provide the information asked for and if this still happens. Thanks!

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links