Mailman 3 January 2006 - Mailman-coders

[ mailman-Patches-1394949 ] held message expiration
by SourceForge.net 01 Jan '06

01 Jan '06

Patches item #1394949, was opened at 2006-01-01 15:29 Message generated for change (Comment added) made by alierak You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1394949&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: command line scripts Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Robby Griffin (alierak) Assigned to: Nobody/Anonymous (nobody) Summary: held message expiration Initial Comment: This patch against 2.1.4 includes an enhanced version of bin/discard and a trivial shell script that rejects held messages older than 10 days, to keep moderator queues relatively clean and to let users know when the moderator is asleep at the wheel. Note that bin/checkdbs in newer versions of Mailman can already discard held messages according to the max_days_to_hold per-list config parameter. Changes to bin/discard include: - support for --approve, --reject, and --comment= for rejection comments (compare to patch #992621). - sane error handling when a specified held message belongs to a nonexistent / invalid listname It's advisable to schedule the expire-heldmsgs cron job to happen before daily admin reminders, so that moderators don't see lists of messages that are gone by the time they visit the admin page. If anyone wants to do further work in this area, they should probably look into extending the expiration capability of 2.1.7 to support approval / rejection with optional comment of expired held posts. I would also suggest that deleting a list should cause its held messages to be expired immediately. ---------------------------------------------------------------------- >Comment By: Robby Griffin (alierak) Date: 2006-01-01 15:39 Message: Logged In: YES user_id=83996 The discard patch applies equally well to 2.1.7, for what it's worth. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1394949&group_…

1 0

[ mailman-Patches-1394949 ] held message expiration
by SourceForge.net 01 Jan '06

01 Jan '06

Patches item #1394949, was opened at 2006-01-01 15:29 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1394949&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: command line scripts Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Robby Griffin (alierak) Assigned to: Nobody/Anonymous (nobody) Summary: held message expiration Initial Comment: This patch against 2.1.4 includes an enhanced version of bin/discard and a trivial shell script that rejects held messages older than 10 days, to keep moderator queues relatively clean and to let users know when the moderator is asleep at the wheel. Note that bin/checkdbs in newer versions of Mailman can already discard held messages according to the max_days_to_hold per-list config parameter. Changes to bin/discard include: - support for --approve, --reject, and --comment= for rejection comments (compare to patch #992621). - sane error handling when a specified held message belongs to a nonexistent / invalid listname It's advisable to schedule the expire-heldmsgs cron job to happen before daily admin reminders, so that moderators don't see lists of messages that are gone by the time they visit the admin page. If anyone wants to do further work in this area, they should probably look into extending the expiration capability of 2.1.7 to support approval / rejection with optional comment of expired held posts. I would also suggest that deleting a list should cause its held messages to be expired immediately. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1394949&group_…

1 0

[ mailman-Bugs-1394914 ] Unable to set default header filter (new style)
by SourceForge.net 01 Jan '06

01 Jan '06

Bugs item #1394914, was opened at 2006-01-01 19:48 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1394914&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: security/privacy Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Magnus Danielson (magdan) Assigned to: Nobody/Anonymous (nobody) Summary: Unable to set default header filter (new style) Initial Comment: As I am working on setting up a multilist/multidomain setup using Mailman 2.1.6, I encountered the need that I wanted to be able to set the default header filter rules so that the lists I create will all have the same basic rule (since we concluded we want one as default). It proved to be a fairly small hack, so I thought I contribute it to you. diff MailList.py.orig MailList.py 342c342,343 < self.header_filter_rules = [] --- > self.header_filter_rules = \ > mm_cfg.DEFAULT_HEADER_FILTER_RULES diff Defaults.py.orig Defaults.py 908a909,918 > # New style SPAM Privacy header filtering > # Mailman can match the patterns of header content and decide upon different > # actions (Defer, Hold, Reject Discard and Accept). These properties is > # configured per list, and here can the list default be set. > # A list of rules where each entry contains the matching string, the action > # code and an empty flag (set False). > # Example (discard mails marked by SpamAssassin): > #DEFAULT_HEADER_FILTER_RULES = [('X-Spam-Status: Yes', DISCARD, False)] > DEFAULT_HEADER_FILTER_RULES = [] > OK, it certainly could be cleaned up in the aspect of comments/documentation, but it should be the trivia part for you guys. It has been tested to work. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1394914&group_…

1 0

[ mailman-Bugs-1394892 ] Unable to set default header filter (new style)
by SourceForge.net 01 Jan '06

01 Jan '06

Bugs item #1394892, was opened at 2006-01-01 19:01 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1394892&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: security/privacy Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Magnus Danielson (magdan) Assigned to: Nobody/Anonymous (nobody) Summary: Unable to set default header filter (new style) Initial Comment: As I am working on setting up a multilist/multidomain setup using Mailman 2.1.6, I encountered the need that I wanted to be able to set the default header filter rules so that the lists I create will all have the same basic rule (since we concluded we want one as default). It proved to be a fairly small hack, so I thought I contribute it to you. diff MailList.py.orig MailList.py 342c342,343 < self.header_filter_rules = [] --- > self.header_filter_rules = \ > mm_cfg.DEFAULT_HEADER_FILTER_RULES diff Defaults.py.orig Defaults.py 908a909,918 > # New style SPAM Privacy header filtering > # Mailman can match the patterns of header content and decide upon different > # actions (Defer, Hold, Reject Discard and Accept). These properties is > # configured per list, and here can the list default be set. > # A list of rules where each entry contains the matching string, the action > # code and an empty flag (set False). > # Example (discard mails marked by SpamAssassin): > #DEFAULT_HEADER_FILTER_RULES = [('X-Spam-Status: Yes', DISCARD, False)] > DEFAULT_HEADER_FILTER_RULES = [] > OK, it certainly could be cleaned up in the aspect of comments/documentation, but it should be the trivia part for you guys. It has been tested to work. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1394892&group_…

1 0

[ mailman-Bugs-1394696 ] "ValueError: day of year out of range" on Dec 31?
by SourceForge.net 01 Jan '06

01 Jan '06

Bugs item #1394696, was opened at 2006-01-01 06:44 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1394696&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: quinn comendant (quinncom) Assigned to: Nobody/Anonymous (nobody) Summary: "ValueError: day of year out of range" on Dec 31? Initial Comment: I haven't checked closely but I'm guessing the following error is because [root@one /var/mailman]# /etc/init.d/mailman stop Traceback (most recent call last): File "/var/mailman/bin/qrunner", line 270, in ? main() File "/var/mailman/bin/qrunner", line 230, in main qrunner.run() File "/var/mailman/Mailman/Queue/Runner.py", line 82, in run self._cleanup() File "/var/mailman/Mailman/Queue/BounceRunner.py", line 139, in _cleanup self._register_bounces() File "/var/mailman/Mailman/Queue/BounceRunner.py", line 129, in _register_bounces mlist.registerBounce(addr, msg, day=day) File "/var/mailman/Mailman/Bouncer.py", line 131, in registerBounce [root@one /var/mailman]# time.strftime('%d-%b-%Y', day + (0,)*6)) ValueError: day of year out of range [root@one /var/mailman]# date Sat Dec 31 23:39:23 CST 2005 [root@one /var/mailman]# bin/version Using Mailman version: 2.1.4 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1394696&group_…

1 0