After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 786486 - release-team mailing list is broken
release-team mailing list is broken
Status: RESOLVED FIXED
Product: sysadmin
Classification: Infrastructure
Component: Mailman
unspecified
Other Linux
: Immediate critical
: ---
Assigned To: André Klapper
GNOME Sysadmins
Depends on:
Blocks:
 
 
Reported: 2017-08-18 20:19 UTC by Michael Catanzaro
Modified: 2017-08-18 20:56 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Michael Catanzaro 2017-08-18 20:19:17 UTC
The mailing list release-team@gnome.org is broken. No mails have reached the list since June 5.

We didn't realize until now because we usually CC other lists that we are subscribed to on most things, but now we are noticing because freeze break requests are not making it through.
Comment 1 André Klapper 2017-08-18 20:56:35 UTC
* I went to https://mail.gnome.org/mailman/admin/release-team/privacy/spam
* "Spam Filter Rule 1" was set to "Discard". 
* For reasons we do not know, it included the line "^X-Spam-Score" which
  is included in every damn email.
* That combination killed us, I think.
* I removed that line, and also set the entire rule to "Hold" instead of
  "Discard" to be on the safe side. If things work in the nearer future
  we could switch back, depending on the spam load which has been high.
* Then I tried to send a first test message to the list.
  Its headers included:
   X-Spam-Flag: NO
   X-Spam-Score: -2.351
   X-Spam-Level: 
* My first message ended up in moderation as 
  "The message headers matched a filter rule".
* I canceled that first message.
* Then to be sure, I also deleted the "Spam Filter Rule 2":
   Hold if applies:   ^X-Spam-Level:[^+]*[+]{1,}
* Then I sent a second test email.
* That second one got through.
For the records, there are no other generic "Spam Filter Rules" but there is a long list of specific ones regarding subjects (example: "subject: .*\sBDSM\s.*") due to all the recent spam. However they are and have been all on "Hold", not on "Discard".

So I'd think the problem is solved for the time being.