[SAC] [OSGeo] #2597: Dangerous emails leaking into grass-web mailing list: mailman blocking fails

[OSGeo]

#2597: Dangerous emails leaking into grass-web mailing list: mailman blocking
fails
---------------------------+------------------------
 Reporter:  neteler        |       Owner:  sac@…
     Type:  task           |      Status:  new
 Priority:  critical       |   Milestone:  Unplanned
Component:  Systems Admin  |  Resolution:
 Keywords:  mailman        |
---------------------------+------------------------

Comment (by neteler):

 Since this is urgent, I have made the following change (edited
 `KNOWN_SPAMMERS`) in

 /usr/lib/mailman/Mailman/Defaults.py:

 {{{
 #####
 # Spam avoidance defaults
 #####

 # This variable contains a list of 2-tuple of the format (header, regex)
 which
 # the Mailman/Handlers/SpamDetect.py module uses to match against the
 current
 # message.  If the regex matches the given header in the current message,
 then
 # it is flagged as spam.  header is case-insensitive and should not
 include
 # the trailing colon.  regex is always matched with re.IGNORECASE.
 #
 # Note that the more searching done, the slower the whole process gets.
 Spam
 # detection is run against all messages coming to either the list, or the
 # -owners address, unless the message is explicitly approved.
 #KNOWN_SPAMMERS = []

 # MN 2021, see https://mail.python.org/pipermail/mailman-
 users/2010-August/070027.html
 KNOWN_SPAMMERS = [
                   ('from', 'noreply at microsoftteams\.uservoice\.com'),
                  ]
 }}}

 Now monitoring the mailman logs in

 {{{
 tail -f /var/log/mailman/post
 }}}

 and the list archive as well here: https://lists.osgeo.org/pipermail
 /grass-web/2021-May/date.html

 Hopefully we won't have bad side-effects!

-- 
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/2597#comment:1>
OSGeo <https://osgeo.org/>
OSGeo committee and general foundation issue tracker.