Mailman 3 July 2005 - Mailman-coders

[ mailman-Bugs-1233670 ] Breaking expired locks logs a traceback
by SourceForge.net July 6, 2005

July 6, 2005

Bugs item #1233670, was opened at 2005-07-06 14:31 Message generated for change (Comment added) made by fehwalker You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1233670&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: Bryan Fullerton (fehwalker) Assigned to: Nobody/Anonymous (nobody) Summary: Breaking expired locks logs a traceback Initial Comment: This looks like a bug to me, though perhaps there's some reason a traceback is needed each time an expired lock is broken? Jun 29 23:51:18 2005 (4405) bryans-list.lock lifetime has expired, breaking Jun 29 23:51:18 2005 (4405) File "/usr/local/mailman/bin/qrunner", line 270, in ? Jun 29 23:51:18 2005 (4405) main() Jun 29 23:51:18 2005 (4405) File "/usr/local/mailman/bin/qrunner", line 230, in main Jun 29 23:51:18 2005 (4405) qrunner.run() Jun 29 23:51:18 2005 (4405) File "/usr/local/mailman/Mailman/Queue/Runner.py", line 70, in run Jun 29 23:51:18 2005 (4405) filecnt = self._oneloop() Jun 29 23:51:18 2005 (4405) File "/usr/local/mailman/Mailman/Queue/Runner.py", line 111, in _oneloop Jun 29 23:51:18 2005 (4405) self._onefile(msg, msgdata) Jun 29 23:51:18 2005 (4405) File "/usr/local/mailman/Mailman/Queue/Runner.py", line 167, in _onefile Jun 29 23:51:18 2005 (4405) keepqueued = self._dispose(mlist, msg, msgdata) Jun 29 23:51:18 2005 (4405) File "/usr/local/mailman/Mailman/Queue/VirginRunner.py", line 38, in _dispose Jun 29 23:51:18 2005 (4405) return IncomingRunner._dispose(self, mlist, msg, msgdata) Jun 29 23:51:18 2005 (4405) File "/usr/local/mailman/Mailman/Queue/IncomingRunner.py", line 115, in _dispose Jun 29 23:51:18 2005 (4405) mlist.Lock(timeout=mm_cfg.LIST_LOCK_TIMEOUT) Jun 29 23:51:18 2005 (4405) File "/usr/local/mailman/Mailman/MailList.py", line 160, in Lock Jun 29 23:51:18 2005 (4405) self.__lock.lock(timeout) Jun 29 23:51:18 2005 (4405) File "/usr/local/mailman/Mailman/LockFile.py", line 306, in lock Jun 29 23:51:18 2005 (4405) important=True) Jun 29 23:51:18 2005 (4405) File "/usr/local/mailman/Mailman/LockFile.py", line 416, in __writelog Jun 29 23:51:18 2005 (4405) traceback.print_stack(file=logf) Thanks, Bryan ---------------------------------------------------------------------- >Comment By: Bryan Fullerton (fehwalker) Date: 2005-07-06 14:33 Message: Logged In: YES user_id=660772 Oh, I'm running 2.1.6. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1233670&group_…

1 0

[ mailman-Bugs-1233670 ] Breaking expired locks logs a traceback
by SourceForge.net July 6, 2005

July 6, 2005

Bugs item #1233670, was opened at 2005-07-06 14:31 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=1233670&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: Bryan Fullerton (fehwalker) Assigned to: Nobody/Anonymous (nobody) Summary: Breaking expired locks logs a traceback Initial Comment: This looks like a bug to me, though perhaps there's some reason a traceback is needed each time an expired lock is broken? Jun 29 23:51:18 2005 (4405) bryans-list.lock lifetime has expired, breaking Jun 29 23:51:18 2005 (4405) File "/usr/local/mailman/bin/qrunner", line 270, in ? Jun 29 23:51:18 2005 (4405) main() Jun 29 23:51:18 2005 (4405) File "/usr/local/mailman/bin/qrunner", line 230, in main Jun 29 23:51:18 2005 (4405) qrunner.run() Jun 29 23:51:18 2005 (4405) File "/usr/local/mailman/Mailman/Queue/Runner.py", line 70, in run Jun 29 23:51:18 2005 (4405) filecnt = self._oneloop() Jun 29 23:51:18 2005 (4405) File "/usr/local/mailman/Mailman/Queue/Runner.py", line 111, in _oneloop Jun 29 23:51:18 2005 (4405) self._onefile(msg, msgdata) Jun 29 23:51:18 2005 (4405) File "/usr/local/mailman/Mailman/Queue/Runner.py", line 167, in _onefile Jun 29 23:51:18 2005 (4405) keepqueued = self._dispose(mlist, msg, msgdata) Jun 29 23:51:18 2005 (4405) File "/usr/local/mailman/Mailman/Queue/VirginRunner.py", line 38, in _dispose Jun 29 23:51:18 2005 (4405) return IncomingRunner._dispose(self, mlist, msg, msgdata) Jun 29 23:51:18 2005 (4405) File "/usr/local/mailman/Mailman/Queue/IncomingRunner.py", line 115, in _dispose Jun 29 23:51:18 2005 (4405) mlist.Lock(timeout=mm_cfg.LIST_LOCK_TIMEOUT) Jun 29 23:51:18 2005 (4405) File "/usr/local/mailman/Mailman/MailList.py", line 160, in Lock Jun 29 23:51:18 2005 (4405) self.__lock.lock(timeout) Jun 29 23:51:18 2005 (4405) File "/usr/local/mailman/Mailman/LockFile.py", line 306, in lock Jun 29 23:51:18 2005 (4405) important=True) Jun 29 23:51:18 2005 (4405) File "/usr/local/mailman/Mailman/LockFile.py", line 416, in __writelog Jun 29 23:51:18 2005 (4405) traceback.print_stack(file=logf) Thanks, Bryan ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1233670&group_…

1 0

[ mailman-Feature Requests-1231974 ] Don't do spam processing for owner emails
by SourceForge.net July 5, 2005

July 5, 2005

Feature Requests item #1231974, was opened at 2005-07-04 01:58 Message generated for change (Settings changed) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1231974&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: None >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Daniel O'Connor (danielo) Assigned to: Nobody/Anonymous (nobody) Summary: Don't do spam processing for owner emails Initial Comment: I have had to add the following to mm_cfg.py - # Don't spam detect on owner messages or we'll get a loop OWNER_PIPELINE = [ # 'SpamDetect', 'Replybot', 'OwnerRecips', 'ToOutgoing', ] The problem is that when I get spam to the list it gets passed (partially) to me as the owner and gets marked as spam, re-sent to me, etc.. I don't think it makes sense to look for spam to owner email by default - if the owner wants spam protection they can install a spam filter. It is much more difficult to alter a site wide filter to not process -owner emails. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2005-07-05 23:29 Message: Logged In: YES user_id=67709 Hi, I've fixed SpamDetect.py not to process -owner messages if it is internally crafted (having X-List-Administrivia header). I believe most of the list owners need this in the pipeline because you get a lot of spam on -owner address these days. Please get the latest version of SpamDetect.py from CVS (Release_2_1-maint branch). ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1231974&group_…

1 0

[ mailman-Feature Requests-1231974 ] Don't do spam processing for owner emails
by SourceForge.net July 5, 2005

July 5, 2005

Feature Requests item #1231974, was opened at 2005-07-04 01:58 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1231974&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: None Status: Open Resolution: None Priority: 5 Submitted By: Daniel O'Connor (danielo) Assigned to: Nobody/Anonymous (nobody) Summary: Don't do spam processing for owner emails Initial Comment: I have had to add the following to mm_cfg.py - # Don't spam detect on owner messages or we'll get a loop OWNER_PIPELINE = [ # 'SpamDetect', 'Replybot', 'OwnerRecips', 'ToOutgoing', ] The problem is that when I get spam to the list it gets passed (partially) to me as the owner and gets marked as spam, re-sent to me, etc.. I don't think it makes sense to look for spam to owner email by default - if the owner wants spam protection they can install a spam filter. It is much more difficult to alter a site wide filter to not process -owner emails. ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2005-07-05 23:29 Message: Logged In: YES user_id=67709 Hi, I've fixed SpamDetect.py not to process -owner messages if it is internally crafted (having X-List-Administrivia header). I believe most of the list owners need this in the pipeline because you get a lot of spam on -owner address these days. Please get the latest version of SpamDetect.py from CVS (Release_2_1-maint branch). ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1231974&group_…

1 0

[ mailman-Bugs-1232349 ] admin moderate post page bugs
by SourceForge.net July 4, 2005

July 4, 2005

Bugs item #1232349, was opened at 2005-07-04 11:23 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=1232349&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: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: JC Dill (jcdill) Assigned to: Nobody/Anonymous (nobody) Summary: admin moderate post page bugs Initial Comment: When reviewing posts held for moderation on the page at: http://$domain/mailman/admindb/$listname Defer Accept Reject Discard as well as a checkbox to "Clear this member's moderate flag" When the moderator clicks on the link to see the whole message, that page has choices for: Defer Approve Reject Discard and there is no entry/checkbox for "Clear this member's moderate flag". ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1232349&group_…

1 0

[ mailman-Feature Requests-1231974 ] Don't do spam processing for owner emails
by SourceForge.net July 4, 2005

July 4, 2005

Feature Requests item #1231974, was opened at 2005-07-04 01:58 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1231974&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: None Status: Open Resolution: None Priority: 5 Submitted By: Daniel O'Connor (danielo) Assigned to: Nobody/Anonymous (nobody) Summary: Don't do spam processing for owner emails Initial Comment: I have had to add the following to mm_cfg.py - # Don't spam detect on owner messages or we'll get a loop OWNER_PIPELINE = [ # 'SpamDetect', 'Replybot', 'OwnerRecips', 'ToOutgoing', ] The problem is that when I get spam to the list it gets passed (partially) to me as the owner and gets marked as spam, re-sent to me, etc.. I don't think it makes sense to look for spam to owner email by default - if the owner wants spam protection they can install a spam filter. It is much more difficult to alter a site wide filter to not process -owner emails. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1231974&group_…

1 0

[ mailman-Bugs-1020013 ] spam filters get removed when changing other privacy pages
by SourceForge.net July 1, 2005

July 1, 2005

Bugs item #1020013, was opened at 2004-08-31 21:10 Message generated for change (Comment added) made by ams001 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1020013&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: Web/CGI Group: 2.1 (stable) Status: Closed Resolution: None Priority: 5 Submitted By: John Dennis (johndennis) Assigned to: Nobody/Anonymous (nobody) Summary: spam filters get removed when changing other privacy pages Initial Comment: This was filed in the Red Hat bugzilla as: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=130479 Promoting to upstream Summary is: If you enter some header_filter_rules in the mailman admin pages (Privacy->Spam filters) and click "submit" they are added to the list configuration database. However, if you now go to one of the other Privacy pages and click "submit" and return to the Spam Filters page, you'll find that your header_filter_rules settings have been removed. This appears to be caused by the handleForm function in ~mailman/Mailman/Gui/Privacy.py not checking to see which subsection is being submitted before processing the data for and setting the mlist.header_filter_rules list configuration variable. Version-Release number of selected component (if applicable): mailman-2.1.5 How reproducible: Always Steps to Reproduce: 1. Create list. 2. Go to the Privacy->Spam filters page, add some header_filter_rules and hit submit. 3. Go to the Privacy->Sender filters page but don't hit submit 4. Go back to Spam filters and note that they're still present 5. Return to Sender filters and hit submit 6. Go back to Spam filters and note that they've been removed. Actual Results: All spam filters are removed. Expected Results: Spam filter settings should be retained. ---------------------------------------------------------------------- Comment By: Alex (ams001) Date: 2005-07-01 10:56 Message: Logged In: YES user_id=1156173 See 1230865 (http://sourceforge.net/tracker/index.php?func=detail&aid=1230865&group_id=1…) for updated patch against v2.1.6 (http://sourceforge.net/tracker/download.php?group_id=103&atid=100103&file_i…) ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2004-09-15 12:48 Message: Logged In: YES user_id=67709 Fixed in CVS Gui/Privacy.py Revision 2.15.2.4 ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2004-09-01 01:33 Message: Logged In: YES user_id=67709 a patch is uploaded (id 1020102) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1020013&group_…

1 0

[ mailman-Bugs-1230865 ] spam filters get removed when changing other privacy pages
by SourceForge.net July 1, 2005

July 1, 2005

Bugs item #1230865, was opened at 2005-07-01 10:51 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=1230865&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: Alex (ams001) Assigned to: Nobody/Anonymous (nobody) Summary: spam filters get removed when changing other privacy pages Initial Comment: Originally reported in 1020013 http://sourceforge.net/tracker/?group_id=103&atid=100103&func=detail&aid=10… This problem still very annoyingly ocurrs in the 2.1.6 release which appears not to include the patch submitted. I have updated the patch against 2.1.6 and included it below. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1230865&group_…

1 0