Mailman 3 February 2007 - Mailman-coders

[ mailman-Bugs-1658920 ] charset proble,
by SourceForge.net Feb. 13, 2007

Feb. 13, 2007

Bugs item #1658920, was opened at 2007-02-13 13:06 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=1658920&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: configuring/installing Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Private: No Submitted By: dudeua (dudeua) Assigned to: Nobody/Anonymous (nobody) Summary: charset proble, Initial Comment: Hello, I need help. I have mailman 2.1.9 .... if I receive mail in charset, different that koi8, than mailman in admins area shows this mail in "quoted-printable" charset ... But after approving this email, via web-interface email shows with correct charset. How to fix charset? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1658920&group_…

1 0

[ mailman-Feature Requests-1657458 ] feature request: batch deletion of subscription requests
by SourceForge.net Feb. 12, 2007

Feb. 12, 2007

Feature Requests item #1657458, was opened at 2007-02-11 18:55 Message generated for change (Comment added) made by tarheelcoxn You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1657458&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 Private: No Submitted By: Cristobal M. Palmer (tarheelcoxn) Assigned to: Nobody/Anonymous (nobody) Summary: feature request: batch deletion of subscription requests Initial Comment: please add a tick box for "delete all pending subscription requests marked /defer/" to the admindb page. It's great that I can scan a page and delete all pending messages that are spam, but several lists I deal with are getting a lot of spam in the form of subscription requests, and making those lists invisible is not an option and wouldn't help at this point. ---------------------------------------------------------------------- >Comment By: Cristobal M. Palmer (tarheelcoxn) Date: 2007-02-12 05:57 Message: Logged In: YES user_id=1297390 Originator: YES The latter (a single box that discards all) would be fine by me, but perhaps somebody with better UI sense than myself should make that call. I would say that regardless of which is the case, it should be *very* clear what exactly is getting discarded. ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2007-02-12 05:28 Message: Logged In: YES user_id=1123998 Originator: NO Re: the comment: Are the bodies of subscription requests visible in recent Mailman? No, they are not. Re: the original request. Do you specifically want a second tick box, or would a single box to "Discard all messages and requests marked _Defer_" be just as good? I can see advantages to separating the discard functions, but OTOH, I see advantages to keeping the page simpler with a single box. ---------------------------------------------------------------------- Comment By: Stephen J. Turnbull (yaseppochi) Date: 2007-02-12 04:57 Message: Logged In: YES user_id=88738 Originator: NO Are the bodies of subscription requests visible in recent Mailman (I'm currently using 2.1.5)? If not, it would be helpful to make them so. My lists don't get so much spam to the subscription address, but it's difficult to determine when somebody has a peculiar address and when it's autogenerated by a spammer sometimes. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1657458&group_…

1 0

[ mailman-Feature Requests-1657458 ] feature request: batch deletion of subscription requests
by SourceForge.net Feb. 12, 2007

Feb. 12, 2007

Feature Requests item #1657458, was opened at 2007-02-11 10:55 Message generated for change (Comment added) made by msapiro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1657458&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 Private: No Submitted By: Cristobal M. Palmer (tarheelcoxn) Assigned to: Nobody/Anonymous (nobody) Summary: feature request: batch deletion of subscription requests Initial Comment: please add a tick box for "delete all pending subscription requests marked /defer/" to the admindb page. It's great that I can scan a page and delete all pending messages that are spam, but several lists I deal with are getting a lot of spam in the form of subscription requests, and making those lists invisible is not an option and wouldn't help at this point. ---------------------------------------------------------------------- >Comment By: Mark Sapiro (msapiro) Date: 2007-02-11 21:28 Message: Logged In: YES user_id=1123998 Originator: NO Re: the comment: Are the bodies of subscription requests visible in recent Mailman? No, they are not. Re: the original request. Do you specifically want a second tick box, or would a single box to "Discard all messages and requests marked _Defer_" be just as good? I can see advantages to separating the discard functions, but OTOH, I see advantages to keeping the page simpler with a single box. ---------------------------------------------------------------------- Comment By: Stephen J. Turnbull (yaseppochi) Date: 2007-02-11 20:57 Message: Logged In: YES user_id=88738 Originator: NO Are the bodies of subscription requests visible in recent Mailman (I'm currently using 2.1.5)? If not, it would be helpful to make them so. My lists don't get so much spam to the subscription address, but it's difficult to determine when somebody has a peculiar address and when it's autogenerated by a spammer sometimes. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1657458&group_…

1 0

[ mailman-Feature Requests-1657458 ] feature request: batch deletion of subscription requests
by SourceForge.net Feb. 12, 2007

Feb. 12, 2007

Feature Requests item #1657458, was opened at 2007-02-12 03:55 Message generated for change (Comment added) made by yaseppochi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1657458&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 Private: No Submitted By: Cristobal M. Palmer (tarheelcoxn) Assigned to: Nobody/Anonymous (nobody) Summary: feature request: batch deletion of subscription requests Initial Comment: please add a tick box for "delete all pending subscription requests marked /defer/" to the admindb page. It's great that I can scan a page and delete all pending messages that are spam, but several lists I deal with are getting a lot of spam in the form of subscription requests, and making those lists invisible is not an option and wouldn't help at this point. ---------------------------------------------------------------------- Comment By: Stephen J. Turnbull (yaseppochi) Date: 2007-02-12 13:57 Message: Logged In: YES user_id=88738 Originator: NO Are the bodies of subscription requests visible in recent Mailman (I'm currently using 2.1.5)? If not, it would be helpful to make them so. My lists don't get so much spam to the subscription address, but it's difficult to determine when somebody has a peculiar address and when it's autogenerated by a spammer sometimes. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1657458&group_…

1 0

[ mailman-Feature Requests-1657458 ] feature request: batch deletion of subscription requests
by SourceForge.net Feb. 11, 2007

Feb. 11, 2007

Feature Requests item #1657458, was opened at 2007-02-11 18:55 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=1657458&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 Private: No Submitted By: Cristobal M. Palmer (tarheelcoxn) Assigned to: Nobody/Anonymous (nobody) Summary: feature request: batch deletion of subscription requests Initial Comment: please add a tick box for "delete all pending subscription requests marked /defer/" to the admindb page. It's great that I can scan a page and delete all pending messages that are spam, but several lists I deal with are getting a lot of spam in the form of subscription requests, and making those lists invisible is not an option and wouldn't help at this point. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1657458&group_…

1 0

[ mailman-Bugs-1656289 ] Unable to process the "in" folder: out of memory
by SourceForge.net Feb. 10, 2007

Feb. 10, 2007

Bugs item #1656289, was opened at 2007-02-09 13:14 Message generated for change (Comment added) made by zhenxjell You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1656289&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: mail delivery Group: 2.1 (stable) >Status: Closed Resolution: None Priority: 5 Private: No Submitted By: Paul Laudanski (zhenxjell) Assigned to: Nobody/Anonymous (nobody) Summary: Unable to process the "in" folder: out of memory Initial Comment: The files in mailman/qfiles/in are not being processed. Rather the following errors are displaying in the error log file. Its the same error over and over in version 2.1.9. Does this error effect the processing of the "in" folder? Currently 161 files are in there. The retry and out folders are empty. Feb 08 11:13:03 2007 (16016) Uncaught runner exception: out of memory Feb 08 11:13:06 2007 (16016) Traceback (most recent call last): File "/usr/local/mailman/Mailman/Queue/Runner.py", line 112, in _oneloop self._onefile(msg, msgdata) File "/usr/local/mailman/Mailman/Queue/Runner.py", line 170, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/local/mailman/Mailman/Queue/IncomingRunner.py", line 130, in _dispose more = self._dopipeline(mlist, msg, msgdata, pipeline) File "/usr/local/mailman/Mailman/Queue/IncomingRunner.py", line 153, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File "/usr/local/mailman/Mailman/Handlers/SpamDetect.py", line 111, in process g.flatten(p) File "/usr/local/mailman/pythonlib/email/Generator.py", line 101, in flatten self._write(msg) File "/usr/local/mailman/pythonlib/email/Generator.py", line 129, in _write self._dispatch(msg) File "/usr/local/mailman/pythonlib/email/Generator.py", line 155, in _dispatch meth(msg) File "/usr/local/mailman/pythonlib/email/Generator.py", line 258, in _handle_multipart print >> self._fp, '\n--' + boundary + '--', MemoryError: out of memory Feb 08 11:13:07 2007 qrunner(16016): Traceback (most recent call last): Feb 08 11:13:07 2007 qrunner(16016): File "/usr/local/mailman/bin/qrunner", line 278, in ? Feb 08 11:13:07 2007 qrunner(16016): main() Feb 08 11:13:07 2007 qrunner(16016): File "/usr/local/mailman/bin/qrunner", line 238, in main Feb 08 11:13:07 2007 qrunner(16016): qrunner.run() Feb 08 11:13:07 2007 qrunner(16016): File "/usr/local/mailman/Mailman/Queue/Runner.py", line 71, in run Feb 08 11:13:07 2007 qrunner(16016): filecnt = self._oneloop() Feb 08 11:13:07 2007 qrunner(16016): File "/usr/local/mailman/Mailman/Queue/Runner.py", line 124, in _oneloop Feb 08 11:13:07 2007 qrunner(16016): new_filebase = self._shunt.enqueue(msg, msgdata) Feb 08 11:13:08 2007 qrunner(16016): File "/usr/local/mailman/Mailman/Queue/Switchboard.py", line 106, in enqueue Feb 08 11:13:08 2007 qrunner(16016): msgsave = cPickle.dumps(_msg, protocol) Feb 08 11:13:08 2007 qrunner(16016): MemoryError : out of memory ---------------------------------------------------------------------- >Comment By: Paul Laudanski (zhenxjell) Date: 2007-02-09 19:19 Message: Logged In: YES user_id=1329578 Originator: YES Bingo, that did the trick. There was a file immensely large, that once removed and restarted, mailman worked. ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2007-02-09 14:52 Message: Logged In: YES user_id=1123998 Originator: NO This is not a Mailman bug per se. IncomingRunner is processing a message. It calls the process() function in the SpamDetect handler which encounters the MemoryError exception which occurs when some Python process tries to allocate more memory and is denied by the OS. Normally, the offending message queue entry would be shunted and processing would continue with the next message, but the attempt to shunt the message also hits the MemoryError. I suggest first trying 'bin/mailmanctl restart' if you haven't done so in case there is a memory leak somewhere in Python. If that doesn't fix it, I think the first file in qfiles/in is probably very large and contains a very large message which is causing the problem. Try 'bin/mailmanctl stop', then move that file aside and do 'bin/mailmanctl start' and see if that resolves the issue. If it does, you may be able to examine the file with bin/dumpdb or bin/show_qfiles. If you need further help, please follow up on mailman-users(a)python.org. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1656289&group_…

1 0

[ mailman-Bugs-1656289 ] Unable to process the "in" folder: out of memory
by SourceForge.net Feb. 9, 2007

Feb. 9, 2007

Bugs item #1656289, was opened at 2007-02-09 10:14 Message generated for change (Comment added) made by msapiro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1656289&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: mail delivery Group: 2.1 (stable) >Status: Pending Resolution: None Priority: 5 Private: No Submitted By: Paul Laudanski (zhenxjell) Assigned to: Nobody/Anonymous (nobody) Summary: Unable to process the "in" folder: out of memory Initial Comment: The files in mailman/qfiles/in are not being processed. Rather the following errors are displaying in the error log file. Its the same error over and over in version 2.1.9. Does this error effect the processing of the "in" folder? Currently 161 files are in there. The retry and out folders are empty. Feb 08 11:13:03 2007 (16016) Uncaught runner exception: out of memory Feb 08 11:13:06 2007 (16016) Traceback (most recent call last): File "/usr/local/mailman/Mailman/Queue/Runner.py", line 112, in _oneloop self._onefile(msg, msgdata) File "/usr/local/mailman/Mailman/Queue/Runner.py", line 170, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/local/mailman/Mailman/Queue/IncomingRunner.py", line 130, in _dispose more = self._dopipeline(mlist, msg, msgdata, pipeline) File "/usr/local/mailman/Mailman/Queue/IncomingRunner.py", line 153, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File "/usr/local/mailman/Mailman/Handlers/SpamDetect.py", line 111, in process g.flatten(p) File "/usr/local/mailman/pythonlib/email/Generator.py", line 101, in flatten self._write(msg) File "/usr/local/mailman/pythonlib/email/Generator.py", line 129, in _write self._dispatch(msg) File "/usr/local/mailman/pythonlib/email/Generator.py", line 155, in _dispatch meth(msg) File "/usr/local/mailman/pythonlib/email/Generator.py", line 258, in _handle_multipart print >> self._fp, '\n--' + boundary + '--', MemoryError: out of memory Feb 08 11:13:07 2007 qrunner(16016): Traceback (most recent call last): Feb 08 11:13:07 2007 qrunner(16016): File "/usr/local/mailman/bin/qrunner", line 278, in ? Feb 08 11:13:07 2007 qrunner(16016): main() Feb 08 11:13:07 2007 qrunner(16016): File "/usr/local/mailman/bin/qrunner", line 238, in main Feb 08 11:13:07 2007 qrunner(16016): qrunner.run() Feb 08 11:13:07 2007 qrunner(16016): File "/usr/local/mailman/Mailman/Queue/Runner.py", line 71, in run Feb 08 11:13:07 2007 qrunner(16016): filecnt = self._oneloop() Feb 08 11:13:07 2007 qrunner(16016): File "/usr/local/mailman/Mailman/Queue/Runner.py", line 124, in _oneloop Feb 08 11:13:07 2007 qrunner(16016): new_filebase = self._shunt.enqueue(msg, msgdata) Feb 08 11:13:08 2007 qrunner(16016): File "/usr/local/mailman/Mailman/Queue/Switchboard.py", line 106, in enqueue Feb 08 11:13:08 2007 qrunner(16016): msgsave = cPickle.dumps(_msg, protocol) Feb 08 11:13:08 2007 qrunner(16016): MemoryError : out of memory ---------------------------------------------------------------------- >Comment By: Mark Sapiro (msapiro) Date: 2007-02-09 11:52 Message: Logged In: YES user_id=1123998 Originator: NO This is not a Mailman bug per se. IncomingRunner is processing a message. It calls the process() function in the SpamDetect handler which encounters the MemoryError exception which occurs when some Python process tries to allocate more memory and is denied by the OS. Normally, the offending message queue entry would be shunted and processing would continue with the next message, but the attempt to shunt the message also hits the MemoryError. I suggest first trying 'bin/mailmanctl restart' if you haven't done so in case there is a memory leak somewhere in Python. If that doesn't fix it, I think the first file in qfiles/in is probably very large and contains a very large message which is causing the problem. Try 'bin/mailmanctl stop', then move that file aside and do 'bin/mailmanctl start' and see if that resolves the issue. If it does, you may be able to examine the file with bin/dumpdb or bin/show_qfiles. If you need further help, please follow up on mailman-users(a)python.org. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1656289&group_…

1 0

[ mailman-Bugs-1656289 ] Unable to process the "in" folder: out of memory
by SourceForge.net Feb. 9, 2007

Feb. 9, 2007

Bugs item #1656289, was opened at 2007-02-09 13:14 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=1656289&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: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Private: No Submitted By: Paul Laudanski (zhenxjell) Assigned to: Nobody/Anonymous (nobody) Summary: Unable to process the "in" folder: out of memory Initial Comment: The files in mailman/qfiles/in are not being processed. Rather the following errors are displaying in the error log file. Its the same error over and over in version 2.1.9. Does this error effect the processing of the "in" folder? Currently 161 files are in there. The retry and out folders are empty. Feb 08 11:13:03 2007 (16016) Uncaught runner exception: out of memory Feb 08 11:13:06 2007 (16016) Traceback (most recent call last): File "/usr/local/mailman/Mailman/Queue/Runner.py", line 112, in _oneloop self._onefile(msg, msgdata) File "/usr/local/mailman/Mailman/Queue/Runner.py", line 170, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/local/mailman/Mailman/Queue/IncomingRunner.py", line 130, in _dispose more = self._dopipeline(mlist, msg, msgdata, pipeline) File "/usr/local/mailman/Mailman/Queue/IncomingRunner.py", line 153, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File "/usr/local/mailman/Mailman/Handlers/SpamDetect.py", line 111, in process g.flatten(p) File "/usr/local/mailman/pythonlib/email/Generator.py", line 101, in flatten self._write(msg) File "/usr/local/mailman/pythonlib/email/Generator.py", line 129, in _write self._dispatch(msg) File "/usr/local/mailman/pythonlib/email/Generator.py", line 155, in _dispatch meth(msg) File "/usr/local/mailman/pythonlib/email/Generator.py", line 258, in _handle_multipart print >> self._fp, '\n--' + boundary + '--', MemoryError: out of memory Feb 08 11:13:07 2007 qrunner(16016): Traceback (most recent call last): Feb 08 11:13:07 2007 qrunner(16016): File "/usr/local/mailman/bin/qrunner", line 278, in ? Feb 08 11:13:07 2007 qrunner(16016): main() Feb 08 11:13:07 2007 qrunner(16016): File "/usr/local/mailman/bin/qrunner", line 238, in main Feb 08 11:13:07 2007 qrunner(16016): qrunner.run() Feb 08 11:13:07 2007 qrunner(16016): File "/usr/local/mailman/Mailman/Queue/Runner.py", line 71, in run Feb 08 11:13:07 2007 qrunner(16016): filecnt = self._oneloop() Feb 08 11:13:07 2007 qrunner(16016): File "/usr/local/mailman/Mailman/Queue/Runner.py", line 124, in _oneloop Feb 08 11:13:07 2007 qrunner(16016): new_filebase = self._shunt.enqueue(msg, msgdata) Feb 08 11:13:08 2007 qrunner(16016): File "/usr/local/mailman/Mailman/Queue/Switchboard.py", line 106, in enqueue Feb 08 11:13:08 2007 qrunner(16016): msgsave = cPickle.dumps(_msg, protocol) Feb 08 11:13:08 2007 qrunner(16016): MemoryError : out of memory ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1656289&group_…

1 0

[ mailman-Feature Requests-1656269 ] code analysis, flaw detection
by SourceForge.net Feb. 9, 2007

Feb. 9, 2007

Feature Requests item #1656269, was opened at 2007-02-09 18:36 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=1656269&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 Private: No Submitted By: Markus Elfring (elfring) Assigned to: Nobody/Anonymous (nobody) Summary: code analysis, flaw detection Initial Comment: Would you like to use the approach "http://en.wikipedia.org/wiki/Static_code_analysis"? Would you like to integrate the tool "http://splint.org/" into your build process? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1656269&group_…

1 0

[ mailman-Patches-1656171 ] list_members moderation options
by SourceForge.net Feb. 9, 2007

Feb. 9, 2007

Patches item #1656171, was opened at 2007-02-09 15:43 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=1656171&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: list administration Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Private: No Submitted By: Anna (annalangley) Assigned to: Nobody/Anonymous (nobody) Summary: list_members moderation options Initial Comment: This patch modifies the list_members command so that in addition to the other options it can filter the addresses listed according to whether the addresses have the "Moderated" bit set (or not). ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1656171&group_…

1 0