[SAC] [OSGeo] #2152: Mailman: mass "Bounce action notification" ongoing

OSGeo trac_osgeo at osgeo.org
Mon Apr 16 13:21:45 PDT 2018


#2152: Mailman: mass "Bounce action notification" ongoing
---------------------------+---------------------------------------
 Reporter:  neteler        |       Owner:  sac@…
     Type:  task           |      Status:  new
 Priority:  blocker        |   Milestone:  Sysadmin Contract 2018-I
Component:  Systems Admin  |  Resolution:
 Keywords:                 |
---------------------------+---------------------------------------

Comment (by neteler):

 Replying to [comment:3 neteler]:
 > Found a script to enable delivery for all members or all those in a
 given domain or those named members whose delivery is disabled by bounce:
 >
 > (Source: https://mail.python.org/pipermail/mailman-
 users/2011-August/072096.html)
 >
 > https://fog.ccsf.edu/~msapiro/scripts/
 >
 >  --> reset_bounce.py
 >
 > Please check if I can use it or not.

 Installed as:
 /usr/lib/mailman/bin/reset_bounce.py

 Seems to work:


 {{{
 # test run with myself:
 withlist -r reset_bounce grass-user --user=neteler at osgeo.org --verbose
 Importing reset_bounce...
 Running reset_bounce.reset_bounce()...
 Loading list grass-user (unlocked)
 List grass-user: Reset 1 bouncing members.
 Finalizing
 }}}

 Looks good. Now reset of all bounced members of the grass-user list:

 {{{
 withlist -r reset_bounce grass-user  --verbose
 Importing reset_bounce...
 Running reset_bounce.reset_bounce()...
 Loading list grass-user (unlocked)
 List grass-user: Reset 341 bouncing members.
 Finalizing
 }}}

 Kudos to M. Sapiro (https://fog.ccsf.edu/~msapiro/scripts/)!

 Question: how to avoid that this happens again?

-- 
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/2152#comment:5>
OSGeo <http://www.osgeo.org/>
OSGeo committee and general foundation issue tracker.


More information about the Sac mailing list