From noreply at sourceforge.net Wed Aug 1 03:29:11 2007 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 31 Jul 2007 18:29:11 -0700 Subject: [ mailman-Patches-1765041 ] add_members: Support for invite & pre-generated passwords Message-ID: Patches item #1765041, was opened at 2007-08-01 03: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=1765041&group_id=103 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 Private: No Submitted By: Julian Mehnle (jmehnle) Assigned to: Nobody/Anonymous (nobody) Summary: add_members: Support for invite & pre-generated passwords Initial Comment: Here is a patch for the add_members command-line utility that adds support for inviting users and specifying pre-generated passwords. If you specify a "--invite-only" option, the users are invited instead of being subscribed right away. You can also specify pre-generated passwords as the last "word" (of non-whitespace characters) in address list files. For example: John Doe PaSsWoRd jane.doe at example.org pAsSwOrD user.with.autogen.password at example.net ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1765041&group_id=103 From noreply at sourceforge.net Fri Aug 3 21:15:27 2007 From: noreply at sourceforge.net (SourceForge.net) Date: Fri, 03 Aug 2007 12:15:27 -0700 Subject: [ mailman-Patches-1611855 ] Add invite option to add_members script Message-ID: Patches item #1611855, was opened at 2006-12-08 13:31 Message generated for change (Comment added) made by mylogon You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1611855&group_id=103 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 Private: No Submitted By: Abram Thielke (athielke) Assigned to: Mark Sapiro (msapiro) Summary: Add invite option to add_members script Initial Comment: This will add two options to the add_members script: --invite-msg-file=file -m file This will prepend the message in the file to the invite email that gets generated. --invite= -i Set to yes if you only want to invite the users to a list, instead of subscribing them. ---------------------------------------------------------------------- Comment By: mylogon (mylogon) Date: 2007-08-03 12:15 Message: Logged In: YES user_id=1042734 Originator: NO Now the pending.pck file is corrupt. Someone else filed a bug report: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=911648&group_id=103 AttributeError: 'module' object has no attribute 'UserDesc' Private: (?) No When adding members via InviteNewMember, and he/she receives the emails asking for confirmation, this is the message shown when clicking: Also happens when trying to post a message to the list. It seems the problem is UserDesc class is defined to be empty, which it should not be. Sample Invite from Web - pending.pck: (dp1 S'32cd3506286849a4a7f4fdef09cec7b1ed8188f3' p2 (S'S' (iMailman.UserDesc UserDesc p3 (dp4 S'language' p5 S'en' p6 sS'address' p7 S'me at mydomain' p8 sS'invitation' p9 S'listname' p10 sS'fullname' p11 V sS'password' p12 S'ozwetuut' p13 sS'digest' p14 I0 sbtp15 sS'evictions' p16 (dp17 g2 F1187031528.2229049 ssS'version' p18 Sample from script: (dp1 S'evictions' p2 (dp3 S'8341fdb4bb70336aa678196525e761559f96ecc9' p4 F1187031624.769033 ssg4 (S'S' (i__main__ UserDesc p5 (dp6 S'fullname' p7 S'' sS'invitation' p8 S'listname' p9 sS'digest' p10 I0 sS'address' p11 S'me at mydomain' p12 sbtp13 sS'version' p14 I2 s. It has been suggested that: (i__main__ UserDesc is the error. It was suggested to change: (from a similar error) http://mail.python.org/pipermail/mailman-users/2005-December/048056.html Add from Mailman.UserDesc import UserDesc Remove class UserDesc: pass and that seems to solve the problem. ---------------------------------------------------------------------- Comment By: mylogon (mylogon) Date: 2007-07-28 20:47 Message: Logged In: YES user_id=1042734 Originator: NO As a quick change to that section: try: if invite: if mlist.isMember(member): raise Errors.MMAlreadyAMember print >> tee, _('Already a member: %(member)s') else: mlist.InviteNewMember(userdesc, invite_msg) else: mlist.ApprovedAddMember(userdesc, ack, 0) This works - but still not for banned. ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2007-07-28 18:32 Message: Logged In: YES user_id=1123998 Originator: NO Actually, the patch looks quite good. There are some problems but they aren't problems with the patch. The problem with inviting someone who is already a member is because MailList.InviteNewMember() does not test for membership before inviting. The patch would catch Errors.MMAlreadyAMember just as is done for adding, but the exception isn't thrown. The web Mailman/Cgi/admin.py gets around this by doing the test itself before inviting, but I think the proper thing is for InviteNewMember() to do it. There is another problem in that InviteNewMember() can throw an Errors.MembershipIsBanned exception which is not caught, but this problem is in the base add_members, not the patch. ---------------------------------------------------------------------- Comment By: mylogon (mylogon) Date: 2007-07-27 01:15 Message: Logged In: YES user_id=1042734 Originator: NO It invites everyone - including people who are members for me. It totally ignores the except Errors.MMAlreadyAMember: ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1611855&group_id=103 From noreply at sourceforge.net Fri Aug 3 21:16:34 2007 From: noreply at sourceforge.net (SourceForge.net) Date: Fri, 03 Aug 2007 12:16:34 -0700 Subject: [ mailman-Patches-1611855 ] Add invite option to add_members script Message-ID: Patches item #1611855, was opened at 2006-12-08 13:31 Message generated for change (Comment added) made by mylogon You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1611855&group_id=103 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 Private: No Submitted By: Abram Thielke (athielke) Assigned to: Mark Sapiro (msapiro) Summary: Add invite option to add_members script Initial Comment: This will add two options to the add_members script: --invite-msg-file=file -m file This will prepend the message in the file to the invite email that gets generated. --invite= -i Set to yes if you only want to invite the users to a list, instead of subscribing them. ---------------------------------------------------------------------- Comment By: mylogon (mylogon) Date: 2007-08-03 12:16 Message: Logged In: YES user_id=1042734 Originator: NO But maybe someone else could also verify and report back... ---------------------------------------------------------------------- Comment By: mylogon (mylogon) Date: 2007-08-03 12:15 Message: Logged In: YES user_id=1042734 Originator: NO Now the pending.pck file is corrupt. Someone else filed a bug report: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=911648&group_id=103 AttributeError: 'module' object has no attribute 'UserDesc' Private: (?) No When adding members via InviteNewMember, and he/she receives the emails asking for confirmation, this is the message shown when clicking: Also happens when trying to post a message to the list. It seems the problem is UserDesc class is defined to be empty, which it should not be. Sample Invite from Web - pending.pck: (dp1 S'32cd3506286849a4a7f4fdef09cec7b1ed8188f3' p2 (S'S' (iMailman.UserDesc UserDesc p3 (dp4 S'language' p5 S'en' p6 sS'address' p7 S'me at mydomain' p8 sS'invitation' p9 S'listname' p10 sS'fullname' p11 V sS'password' p12 S'ozwetuut' p13 sS'digest' p14 I0 sbtp15 sS'evictions' p16 (dp17 g2 F1187031528.2229049 ssS'version' p18 Sample from script: (dp1 S'evictions' p2 (dp3 S'8341fdb4bb70336aa678196525e761559f96ecc9' p4 F1187031624.769033 ssg4 (S'S' (i__main__ UserDesc p5 (dp6 S'fullname' p7 S'' sS'invitation' p8 S'listname' p9 sS'digest' p10 I0 sS'address' p11 S'me at mydomain' p12 sbtp13 sS'version' p14 I2 s. It has been suggested that: (i__main__ UserDesc is the error. It was suggested to change: (from a similar error) http://mail.python.org/pipermail/mailman-users/2005-December/048056.html Add from Mailman.UserDesc import UserDesc Remove class UserDesc: pass and that seems to solve the problem. ---------------------------------------------------------------------- Comment By: mylogon (mylogon) Date: 2007-07-28 20:47 Message: Logged In: YES user_id=1042734 Originator: NO As a quick change to that section: try: if invite: if mlist.isMember(member): raise Errors.MMAlreadyAMember print >> tee, _('Already a member: %(member)s') else: mlist.InviteNewMember(userdesc, invite_msg) else: mlist.ApprovedAddMember(userdesc, ack, 0) This works - but still not for banned. ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2007-07-28 18:32 Message: Logged In: YES user_id=1123998 Originator: NO Actually, the patch looks quite good. There are some problems but they aren't problems with the patch. The problem with inviting someone who is already a member is because MailList.InviteNewMember() does not test for membership before inviting. The patch would catch Errors.MMAlreadyAMember just as is done for adding, but the exception isn't thrown. The web Mailman/Cgi/admin.py gets around this by doing the test itself before inviting, but I think the proper thing is for InviteNewMember() to do it. There is another problem in that InviteNewMember() can throw an Errors.MembershipIsBanned exception which is not caught, but this problem is in the base add_members, not the patch. ---------------------------------------------------------------------- Comment By: mylogon (mylogon) Date: 2007-07-27 01:15 Message: Logged In: YES user_id=1042734 Originator: NO It invites everyone - including people who are members for me. It totally ignores the except Errors.MMAlreadyAMember: ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1611855&group_id=103 From noreply at sourceforge.net Sat Aug 4 15:09:29 2007 From: noreply at sourceforge.net (SourceForge.net) Date: Sat, 04 Aug 2007 06:09:29 -0700 Subject: [ mailman-Feature Requests-1767626 ] one-shot custom notes for group invitation Message-ID: Feature Requests item #1767626, was opened at 2007-08-04 09:09 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=1767626&group_id=103 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: konsultor (konsultor) Assigned to: Nobody/Anonymous (nobody) Summary: one-shot custom notes for group invitation Initial Comment: In a way similar to the customized greeting for new subscribers (which is sent only after a subscription), it would be great to be able to add text to the initial invitation message, to explain what the list is about, the basis for the invitation ("met you at the conference"), etc. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1767626&group_id=103 From noreply at sourceforge.net Sat Aug 4 16:48:18 2007 From: noreply at sourceforge.net (SourceForge.net) Date: Sat, 04 Aug 2007 07:48:18 -0700 Subject: [ mailman-Feature Requests-1767626 ] one-shot custom notes for group invitation Message-ID: Feature Requests item #1767626, was opened at 2007-08-04 06:09 Message generated for change (Comment added) made by msapiro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1767626&group_id=103 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: konsultor (konsultor) Assigned to: Nobody/Anonymous (nobody) Summary: one-shot custom notes for group invitation Initial Comment: In a way similar to the customized greeting for new subscribers (which is sent only after a subscription), it would be great to be able to add text to the initial invitation message, to explain what the list is about, the basis for the invitation ("met you at the conference"), etc. ---------------------------------------------------------------------- >Comment By: Mark Sapiro (msapiro) Date: 2007-08-04 07:48 Message: Logged In: YES user_id=1123998 Originator: NO This feature already exists. On the Membership Management...Mass Subscription page, put your additional text in the second text box, the one below the box for addresses where it says "Below, enter additional text to be added to the top of your invitation or the subscription notification. Include at least one blank line at the end..." Or do you mean that you want to be able to customize the invitation email 'permanently' as you can the 'Welcome' message? While you can't do this via the web admin interface as you can with the welcome, you can make a list specific version of the invite.txt template as discussed at http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq04.048.htp If this is a request to add the ability to edit the invite.txt template via the web admin interface, please clarify that that is the case. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1767626&group_id=103 From noreply at sourceforge.net Fri Aug 17 13:53:36 2007 From: noreply at sourceforge.net (SourceForge.net) Date: Fri, 17 Aug 2007 04:53:36 -0700 Subject: [ mailman-Patches-1776178 ] Use inotify instead of polling in Runner.py Message-ID: Patches item #1776178, was opened at 2007-08-17 13:53 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=1776178&group_id=103 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: Mailman 2.2 / 3.0 Status: Open Resolution: None Priority: 5 Private: No Submitted By: Tomas Smetana (tsmetana) Assigned to: Nobody/Anonymous (nobody) Summary: Use inotify instead of polling in Runner.py Initial Comment: Hi, the Mailman wakes up 7 times per second which is somehow resource unfriendly. This is caused by qrunners that poll for new files in queue directory. The proposed patch replaces polling in Runner.py with inotify which enables CPU to idle when possible. The patch requires python-inotify (http://pyinotify.sourceforge.net) to be installed. --ts ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1776178&group_id=103 From noreply at sourceforge.net Fri Aug 17 14:16:46 2007 From: noreply at sourceforge.net (SourceForge.net) Date: Fri, 17 Aug 2007 05:16:46 -0700 Subject: [ mailman-Patches-1776178 ] Use inotify instead of polling in Runner.py Message-ID: Patches item #1776178, was opened at 2007-08-17 07:53 Message generated for change (Comment added) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1776178&group_id=103 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: Mailman 2.2 / 3.0 Status: Open Resolution: None Priority: 5 Private: No Submitted By: Tomas Smetana (tsmetana) Assigned to: Nobody/Anonymous (nobody) Summary: Use inotify instead of polling in Runner.py Initial Comment: Hi, the Mailman wakes up 7 times per second which is somehow resource unfriendly. This is caused by qrunners that poll for new files in queue directory. The proposed patch replaces polling in Runner.py with inotify which enables CPU to idle when possible. The patch requires python-inotify (http://pyinotify.sourceforge.net) to be installed. --ts ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2007-08-17 08:16 Message: Logged In: YES user_id=12800 Originator: NO IIUC, inotify is a Linux-only thing so this would have to be optional. I haven't looked at the patch, but I would target this for Mailman 3 instead of 2.2. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1776178&group_id=103 From noreply at sourceforge.net Fri Aug 17 14:36:34 2007 From: noreply at sourceforge.net (SourceForge.net) Date: Fri, 17 Aug 2007 05:36:34 -0700 Subject: [ mailman-Patches-1776178 ] Use inotify instead of polling in Runner.py Message-ID: Patches item #1776178, was opened at 2007-08-17 13:53 Message generated for change (Comment added) made by tsmetana You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1776178&group_id=103 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: Mailman 2.2 / 3.0 Status: Open Resolution: None Priority: 5 Private: No Submitted By: Tomas Smetana (tsmetana) Assigned to: Nobody/Anonymous (nobody) Summary: Use inotify instead of polling in Runner.py Initial Comment: Hi, the Mailman wakes up 7 times per second which is somehow resource unfriendly. This is caused by qrunners that poll for new files in queue directory. The proposed patch replaces polling in Runner.py with inotify which enables CPU to idle when possible. The patch requires python-inotify (http://pyinotify.sourceforge.net) to be installed. --ts ---------------------------------------------------------------------- >Comment By: Tomas Smetana (tsmetana) Date: 2007-08-17 14:36 Message: Logged In: YES user_id=1869522 Originator: YES Yes, you're right... I didn't realize that inotify is Linux specific. I will add a configure script option -- this should solve the Linux-only problem and make the python-inotify dependency optional. Also I will take a look at Mailman 3 and try to create a patch for it as well. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2007-08-17 14:16 Message: Logged In: YES user_id=12800 Originator: NO IIUC, inotify is a Linux-only thing so this would have to be optional. I haven't looked at the patch, but I would target this for Mailman 3 instead of 2.2. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1776178&group_id=103 From noreply at sourceforge.net Sun Aug 19 06:00:38 2007 From: noreply at sourceforge.net (SourceForge.net) Date: Sat, 18 Aug 2007 21:00:38 -0700 Subject: [ mailman-Feature Requests-403066 ] Auto Approval of subscriptions for certain domains Message-ID: Feature Requests item #403066, was opened at 2001-01-01 06:27 Message generated for change (Comment added) made by msapiro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=403066&group_id=103 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: Accepted Priority: 3 Private: No Submitted By: Mark Tearle (mtearle) Assigned to: Mark Sapiro (msapiro) Summary: Auto Approval of subscriptions for certain domains Initial Comment: A patch to enable automatic approval for certain domains, eg people in the example.com are automatically approved all others have to wait for the moderator ---------------------------------------------------------------------- >Comment By: Mark Sapiro (msapiro) Date: 2007-08-18 21:00 Message: Logged In: YES user_id=1123998 Originator: NO Reopened. Pending/closed was a mistake. ---------------------------------------------------------------------- Comment By: Jim Popovitch (jimpop) Date: 2006-07-31 15:13 Message: Logged In: YES user_id=3142 New feature request for this patch, seeking feedback. Most of my lists automatically moderate new subscribers, in addition some require admin approval for subsciption, except for domains listed in subscribe_auto_approval. A nice addition to this patch would be to not moderate subscribers whose domains are listed in subscribe_auto_approval. ---------------------------------------------------------------------- Comment By: SourceForge Robot (sf-robot) Date: 2006-03-25 19:21 Message: Logged In: YES user_id=1312539 This Tracker item was closed automatically by the system. It was previously set to a Pending status, and the original submitter did not respond within 14 days (the time period specified by the administrator of this Tracker). ---------------------------------------------------------------------- Comment By: Jim Popovitch (jimpop) Date: 2006-03-12 19:12 Message: Logged In: YES user_id=3142 I've successfully applied this against a v2.1.8 system and it works well. Thanks!! ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2006-03-11 10:36 Message: Logged In: YES user_id=1123998 The attached patch is against a 2.1.8a1 installed base (installed because it patches Defaults.py and not Defaults.py.in). It is a modification and extension of the original patch. It implements a new list attribute 'subscribe_auto_approval' which is a list of email addresses and regular expressions matching email addresses whose subscriptions are exempt from admin approval. It implements the original intent if one just uses regexps that match domains. This will go in Mailman 2.2, but it would be nice to get some feedback from people who are interested in this feature and are willing to try the patch. ---------------------------------------------------------------------- Comment By: Thomas Wouters (twouters) Date: 2003-03-11 05:31 Message: Logged In: YES user_id=34209 Is this still necessary with Mailman 2.1, which has more 'automatic' options (as well as 'memberadaptors') ? In any case, the patch is likely heavily out of date by now, I'm moving this to Feature Requests for now. Feel free to respond if you (still) have a need. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=403066&group_id=103 From noreply at sourceforge.net Tue Aug 21 10:00:21 2007 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 21 Aug 2007 01:00:21 -0700 Subject: [ mailman-Patches-1776178 ] Use inotify instead of polling in Runner.py Message-ID: Patches item #1776178, was opened at 2007-08-17 13:53 Message generated for change (Comment added) made by tsmetana You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1776178&group_id=103 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: Mailman 2.2 / 3.0 Status: Open Resolution: None Priority: 5 Private: No Submitted By: Tomas Smetana (tsmetana) Assigned to: Nobody/Anonymous (nobody) Summary: Use inotify instead of polling in Runner.py Initial Comment: Hi, the Mailman wakes up 7 times per second which is somehow resource unfriendly. This is caused by qrunners that poll for new files in queue directory. The proposed patch replaces polling in Runner.py with inotify which enables CPU to idle when possible. The patch requires python-inotify (http://pyinotify.sourceforge.net) to be installed. --ts ---------------------------------------------------------------------- >Comment By: Tomas Smetana (tsmetana) Date: 2007-08-21 10:00 Message: Logged In: YES user_id=1869522 Originator: YES File Added: mailman-inotify.patch ---------------------------------------------------------------------- Comment By: Tomas Smetana (tsmetana) Date: 2007-08-17 14:36 Message: Logged In: YES user_id=1869522 Originator: YES Yes, you're right... I didn't realize that inotify is Linux specific. I will add a configure script option -- this should solve the Linux-only problem and make the python-inotify dependency optional. Also I will take a look at Mailman 3 and try to create a patch for it as well. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2007-08-17 14:16 Message: Logged In: YES user_id=12800 Originator: NO IIUC, inotify is a Linux-only thing so this would have to be optional. I haven't looked at the patch, but I would target this for Mailman 3 instead of 2.2. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1776178&group_id=103 From noreply at sourceforge.net Tue Aug 21 10:04:16 2007 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 21 Aug 2007 01:04:16 -0700 Subject: [ mailman-Patches-1776178 ] Use inotify instead of polling in Runner.py Message-ID: Patches item #1776178, was opened at 2007-08-17 13:53 Message generated for change (Comment added) made by tsmetana You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1776178&group_id=103 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: Mailman 2.2 / 3.0 Status: Open Resolution: None Priority: 5 Private: No Submitted By: Tomas Smetana (tsmetana) Assigned to: Nobody/Anonymous (nobody) Summary: Use inotify instead of polling in Runner.py Initial Comment: Hi, the Mailman wakes up 7 times per second which is somehow resource unfriendly. This is caused by qrunners that poll for new files in queue directory. The proposed patch replaces polling in Runner.py with inotify which enables CPU to idle when possible. The patch requires python-inotify (http://pyinotify.sourceforge.net) to be installed. --ts ---------------------------------------------------------------------- >Comment By: Tomas Smetana (tsmetana) Date: 2007-08-21 10:04 Message: Logged In: YES user_id=1869522 Originator: YES I'm adding updated patch for Mailman 2.2 and a new patch for Mailman 3. I've moved the python-inotify parts in conditionals, so if inotify is not present in the system, everything should work as in the unpatched version. File Added: mailman3-inotify.patch ---------------------------------------------------------------------- Comment By: Tomas Smetana (tsmetana) Date: 2007-08-21 10:00 Message: Logged In: YES user_id=1869522 Originator: YES File Added: mailman-inotify.patch ---------------------------------------------------------------------- Comment By: Tomas Smetana (tsmetana) Date: 2007-08-17 14:36 Message: Logged In: YES user_id=1869522 Originator: YES Yes, you're right... I didn't realize that inotify is Linux specific. I will add a configure script option -- this should solve the Linux-only problem and make the python-inotify dependency optional. Also I will take a look at Mailman 3 and try to create a patch for it as well. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2007-08-17 14:16 Message: Logged In: YES user_id=12800 Originator: NO IIUC, inotify is a Linux-only thing so this would have to be optional. I haven't looked at the patch, but I would target this for Mailman 3 instead of 2.2. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1776178&group_id=103 From noreply at sourceforge.net Tue Aug 21 21:54:34 2007 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 21 Aug 2007 12:54:34 -0700 Subject: [ mailman-Bugs-1778960 ] Empty Bounces Message-ID: Bugs item #1778960, was opened at 2007-08-21 19:54 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=1778960&group_id=103 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: bounce detection Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Private: No Submitted By: Nick Lange (ninja_k) Assigned to: Nobody/Anonymous (nobody) Summary: Empty Bounces Initial Comment: I have a mailing list, X managed by Mailman 2.1.9 on FreeBSD 5.3 with Courier as our MTA. All the member addresses of X are valid. The owner address is also valid. We allow non-member postings as well. Every time we send an e-mail to the list, we get an e-mail with no subject, and no body from mailman-bounces. If I turn on Uncaught bounce notification, the message that is forwarded has no contents. The logs show: Aug 21 11:01:12 2007 (1493) bounce message w/no discernable addresses: None Aug 21 11:01:12 2007 (1493) forwarding unrecognized, message-id: n/a Aug 21 11:01:12 2007 (1493) bounce message w/no discernable addresses: None Aug 21 11:01:12 2007 (1493) forwarding unrecognized, message-id: n/a ... I'm not quite sure what is going on, but I am fairly certain that this is a bug. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1778960&group_id=103 From noreply at sourceforge.net Wed Aug 22 01:46:12 2007 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 21 Aug 2007 16:46:12 -0700 Subject: [ mailman-Bugs-1778960 ] Empty Bounces Message-ID: Bugs item #1778960, was opened at 2007-08-21 12:54 Message generated for change (Comment added) made by msapiro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1778960&group_id=103 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: bounce detection Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Private: No Submitted By: Nick Lange (ninja_k) Assigned to: Nobody/Anonymous (nobody) Summary: Empty Bounces Initial Comment: I have a mailing list, X managed by Mailman 2.1.9 on FreeBSD 5.3 with Courier as our MTA. All the member addresses of X are valid. The owner address is also valid. We allow non-member postings as well. Every time we send an e-mail to the list, we get an e-mail with no subject, and no body from mailman-bounces. If I turn on Uncaught bounce notification, the message that is forwarded has no contents. The logs show: Aug 21 11:01:12 2007 (1493) bounce message w/no discernable addresses: None Aug 21 11:01:12 2007 (1493) forwarding unrecognized, message-id: n/a Aug 21 11:01:12 2007 (1493) bounce message w/no discernable addresses: None Aug 21 11:01:12 2007 (1493) forwarding unrecognized, message-id: n/a ... I'm not quite sure what is going on, but I am fairly certain that this is a bug. ---------------------------------------------------------------------- >Comment By: Mark Sapiro (msapiro) Date: 2007-08-21 16:46 Message: Logged In: YES user_id=1123998 Originator: NO > ... I'm not quite sure what is going on, but I am fairly certain that this > is a bug. Maybe, but not necessarily. What do your Courier logs show? It is even possible that one of your list members has a misconfigured autoresponder of some kind. In any case, Mailman is receiving this empty bounce message, and something (presumably outside Mailman) is sending it. > If I turn on Uncaught bounce > notification, the message that is forwarded has no contents. What are the headers of this message, or are there no headers either? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1778960&group_id=103 From noreply at sourceforge.net Wed Aug 22 07:23:16 2007 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 21 Aug 2007 22:23:16 -0700 Subject: [ mailman-Bugs-1778960 ] Empty Bounces Message-ID: Bugs item #1778960, was opened at 2007-08-21 19:54 Message generated for change (Comment added) made by ninja_k You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1778960&group_id=103 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: bounce detection Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Private: No Submitted By: Nick Lange (ninja_k) Assigned to: Nobody/Anonymous (nobody) Summary: Empty Bounces Initial Comment: I have a mailing list, X managed by Mailman 2.1.9 on FreeBSD 5.3 with Courier as our MTA. All the member addresses of X are valid. The owner address is also valid. We allow non-member postings as well. Every time we send an e-mail to the list, we get an e-mail with no subject, and no body from mailman-bounces. If I turn on Uncaught bounce notification, the message that is forwarded has no contents. The logs show: Aug 21 11:01:12 2007 (1493) bounce message w/no discernable addresses: None Aug 21 11:01:12 2007 (1493) forwarding unrecognized, message-id: n/a Aug 21 11:01:12 2007 (1493) bounce message w/no discernable addresses: None Aug 21 11:01:12 2007 (1493) forwarding unrecognized, message-id: n/a ... I'm not quite sure what is going on, but I am fairly certain that this is a bug. ---------------------------------------------------------------------- >Comment By: Nick Lange (ninja_k) Date: 2007-08-22 05:23 Message: Logged In: YES user_id=411568 Originator: YES To answer your questions (apparently I can't quote your message, my apologies) 1. No auto responders are in use. I will attempt to sanitize and post up some courier logs for you tomorrow. 2. While I haven't gone as far as to capture individual messages in transit, the attached "messages" are completely empty, yes. With consideration to one, I'll try to enable some kind of tracing on the programs as they are executed when I get into work... ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2007-08-21 23:46 Message: Logged In: YES user_id=1123998 Originator: NO > ... I'm not quite sure what is going on, but I am fairly certain that this > is a bug. Maybe, but not necessarily. What do your Courier logs show? It is even possible that one of your list members has a misconfigured autoresponder of some kind. In any case, Mailman is receiving this empty bounce message, and something (presumably outside Mailman) is sending it. > If I turn on Uncaught bounce > notification, the message that is forwarded has no contents. What are the headers of this message, or are there no headers either? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1778960&group_id=103 From noreply at sourceforge.net Fri Aug 24 10:07:43 2007 From: noreply at sourceforge.net (SourceForge.net) Date: Fri, 24 Aug 2007 01:07:43 -0700 Subject: [ mailman-Patches-1776178 ] Use inotify instead of polling in Runner.py Message-ID: Patches item #1776178, was opened at 2007-08-17 13:53 Message generated for change (Comment added) made by tsmetana You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1776178&group_id=103 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: Mailman 2.2 / 3.0 >Status: Closed >Resolution: Invalid Priority: 5 Private: No Submitted By: Tomas Smetana (tsmetana) Assigned to: Nobody/Anonymous (nobody) Summary: Use inotify instead of polling in Runner.py Initial Comment: Hi, the Mailman wakes up 7 times per second which is somehow resource unfriendly. This is caused by qrunners that poll for new files in queue directory. The proposed patch replaces polling in Runner.py with inotify which enables CPU to idle when possible. The patch requires python-inotify (http://pyinotify.sourceforge.net) to be installed. --ts ---------------------------------------------------------------------- >Comment By: Tomas Smetana (tsmetana) Date: 2007-08-24 10:07 Message: Logged In: YES user_id=1869522 Originator: YES The patches will make Mailman working but unstoppable. It looks to be a python's problem with handling signals in threads. I'm closing this ticket until the issues got solved. ---------------------------------------------------------------------- Comment By: Tomas Smetana (tsmetana) Date: 2007-08-21 10:04 Message: Logged In: YES user_id=1869522 Originator: YES I'm adding updated patch for Mailman 2.2 and a new patch for Mailman 3. I've moved the python-inotify parts in conditionals, so if inotify is not present in the system, everything should work as in the unpatched version. File Added: mailman3-inotify.patch ---------------------------------------------------------------------- Comment By: Tomas Smetana (tsmetana) Date: 2007-08-21 10:00 Message: Logged In: YES user_id=1869522 Originator: YES File Added: mailman-inotify.patch ---------------------------------------------------------------------- Comment By: Tomas Smetana (tsmetana) Date: 2007-08-17 14:36 Message: Logged In: YES user_id=1869522 Originator: YES Yes, you're right... I didn't realize that inotify is Linux specific. I will add a configure script option -- this should solve the Linux-only problem and make the python-inotify dependency optional. Also I will take a look at Mailman 3 and try to create a patch for it as well. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2007-08-17 14:16 Message: Logged In: YES user_id=12800 Originator: NO IIUC, inotify is a Linux-only thing so this would have to be optional. I haven't looked at the patch, but I would target this for Mailman 3 instead of 2.2. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1776178&group_id=103 From noreply at sourceforge.net Tue Aug 28 22:55:57 2007 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 28 Aug 2007 13:55:57 -0700 Subject: [ mailman-Patches-1783633 ] allow add_member to offer confirmation Message-ID: Patches item #1783633, was opened at 2007-08-28 20:55 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=1783633&group_id=103 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 Private: No Submitted By: David Turner (novalis_dt) Assigned to: Nobody/Anonymous (nobody) Summary: allow add_member to offer confirmation Initial Comment: Adds a -c option to add_member to allow it to be used to subscribe members with confirmation. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1783633&group_id=103 From noreply at sourceforge.net Tue Aug 28 22:56:39 2007 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 28 Aug 2007 13:56:39 -0700 Subject: [ mailman-Patches-1783633 ] allow add_member to offer confirmation Message-ID: Patches item #1783633, was opened at 2007-08-28 20:55 Message generated for change (Comment added) made by novalis_dt You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1783633&group_id=103 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: Duplicate Priority: 5 Private: No Submitted By: David Turner (novalis_dt) Assigned to: Nobody/Anonymous (nobody) Summary: allow add_member to offer confirmation Initial Comment: Adds a -c option to add_member to allow it to be used to subscribe members with confirmation. ---------------------------------------------------------------------- >Comment By: David Turner (novalis_dt) Date: 2007-08-28 20:56 Message: Logged In: YES user_id=83137 Originator: YES Oops. This duplicates #1765041 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1783633&group_id=103 From noreply at sourceforge.net Tue Aug 28 22:57:06 2007 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 28 Aug 2007 13:57:06 -0700 Subject: [ mailman-Patches-1783633 ] allow add_member to offer confirmation Message-ID: Patches item #1783633, was opened at 2007-08-28 20:55 Message generated for change (Settings changed) made by novalis_dt You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1783633&group_id=103 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: Closed Resolution: Duplicate Priority: 5 Private: No Submitted By: David Turner (novalis_dt) Assigned to: Nobody/Anonymous (nobody) Summary: allow add_member to offer confirmation Initial Comment: Adds a -c option to add_member to allow it to be used to subscribe members with confirmation. ---------------------------------------------------------------------- Comment By: David Turner (novalis_dt) Date: 2007-08-28 20:56 Message: Logged In: YES user_id=83137 Originator: YES Oops. This duplicates #1765041 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1783633&group_id=103