From noreply at sourceforge.net Tue Feb 1 18:02:40 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Feb 1 18:02:47 2005 Subject: [ mailman-Patches-871062 ] A MemberAdaptor for LDAP-based membership Message-ID: Patches item #871062, was opened at 2004-01-05 12:09 Message generated for change (Comment added) made by fubarobfusco You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=871062&group_id=103 Category: list administration Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: K. A. Krueger (fubarobfusco) Assigned to: Nobody/Anonymous (nobody) Summary: A MemberAdaptor for LDAP-based membership Initial Comment: This is a module, LDAPMemberships, which extends MemberAdaptor to support membership lists based on a search in an enterprise LDAP directory. With this module, you can make mailing lists which, rather than having a list of member addresses stored in the list, query your LDAP server for member addresses whenever necessary. For instance, if you wish to have a mailing list of all the Vice Presidents in your company, you can express this as an LDAP search: "(title=Vice President*)" and create a mailing list which performs this search and delivers mail to the resulting user accounts when a message is sent to it. This way, rather than manually adding new Vice Presidents to the mailing list, you can simply have Human Resources update the LDAP records, and the change will immediately take effect for the mailing list. Mailman lists with LDAP-based membership can still have moderators, list policies, and the other usual features of Mailman lists. There are a few missing features; notably: 1. There is no bounce processing. 2. There are no per-user preferences. 3. The Web interface still allows you to try setting user preferences, but if you do you will get a stack thrown at you. (Only the "readable" interface of MemberAdaptor is implemented.) 4. The LDAP settings of a list (e.g. LDAP server and search string) are only administrable by editing its "extend.py" file, not over the Web. 5. There is no digest mode. To use this module, you must have the "ldap" Python module installed (aka "python-ldap"). Then just put LDAPMemberships.py in the "Mailman" directory (~mailman/Mailman), create a new list, and write an "extend.py" file in the list directory like so: ##### from Mailman.LDAPMemberships import LDAPMemberships def extend(list): ldap = LDAPMemberships(list) ldap.ldapsearch = "(title=Vice President*)" # members search string ldap.ldapserver = "ldap.example.net" # your enterprise LDAP server ldap.ldapbasedn = "dc=Example dc=net" # your LDAP base DN ldap.ldapbinddn = '' # a bind DN which can read people's 'mail' field ldap.ldappasswd = '' # the password for the bind DN list._memberadaptor = ldap ##### This module has been tested at my site and is in production on a Mailman 2.1.2 installation. ---------------------------------------------------------------------- >Comment By: K. A. Krueger (fubarobfusco) Date: 2005-02-01 12:02 Message: Logged In: YES user_id=944208 I've just uploaded version 0.4 of LDAPMemberships.py. This includes the patch by the_olo to support multiple values in 'mail', and also fixes a bug reported by Mark Sapiro involving importing defaults from the wrong module. ---------------------------------------------------------------------- Comment By: martin whinnery (mawhin) Date: 2004-08-25 11:39 Message: Logged In: YES user_id=90418 I've hacked your work about to get it to handle lists based on group membership instead. You may find it worthwhile. http://webserver.offal.homelinux.org/LDAPMemberAdaptor/V3.0/LDAPMemberAdaptor/ This version's nasty, but you'll get the idea. Wanna roll it into yours? Mart ---------------------------------------------------------------------- Comment By: Aleksander Adamowski (the_olo) Date: 2004-04-05 09:47 Message: Logged In: YES user_id=244001 I suggest this patch to allow senders use any source address they might have set in LDAP (the 'mail' attribute can have multiple values!) --- LDAPMemberships.py.orig 2004-04-01 12:31:54.000000000 +0200 +++ LDAPMemberships.py 2004-04-05 15:40:03.000000000 +0200 @@ -115,7 +115,9 @@ # mail is unique mail = attrs['mail'][0].strip() self.__members.append(mail) - self.__member_map[mail] = mail + # mail can have multiple values + for secondarymail in attrs['mail']: + self.__member_map[secondarymail.strip()] = mail if attrs.has_key('mailalternateaddress'): malts = attrs['mailalternateaddress'] for malt in malts: ---------------------------------------------------------------------- Comment By: K. A. Krueger (fubarobfusco) Date: 2004-03-30 22:59 Message: Logged In: YES user_id=944208 Well, Mailman does a lot more than just keep track of who's subscribed -- for instance, restricted posters, list moderation, archiving. LDAPMemberships is not meant to be useful for Internet mailing lists with people signing up for them, but rather for institutional or enterprise lists. These have a lot of the same requirements (moderation etc.) as Internet lists, but don't need subscription/unsubscription -- since employees are usually required to be on them. My workplace is using this (well, actually a later version than the one I've uploaded here) as a replacement for an LDAP mailing-list feature in Netscape SuiteSpot now that we have migrated away from that system. We -also- use LDAP-based aliases (in Postfix, not Sendmail, actually) -- but for some things we need the moderation and other facilities that Mailman has. For instance, we have an announcements list that goes to all regular employees. A simple alias would allow anyone to send stuff to it, and certain senior scientists would love to send big PDFs to everyone. A Mailman list with LDAPMemberships can have sender restrictions so that only our IT Director and our mail systems admin can approve posts to it. Archiving is also quite useful for announcements lists. ---------------------------------------------------------------------- Comment By: Chris Drumgoole (cdrum) Date: 2004-03-30 22:38 Message: Logged In: YES user_id=429400 why use this when you can just use Sendmail's LDAP -> Alias functions? No need for a mailing list program like mailman.. right? ---------------------------------------------------------------------- Comment By: K. A. Krueger (fubarobfusco) Date: 2004-01-26 15:35 Message: Logged In: YES user_id=944208 Yet another new version (0.3) of LDAPMemberships.py. This one fixes some ambiguities with LDAP record handling, particularly for users with multiple "cn" values, and those who send mail as their "mailalternateaddress" field address rather than their "mail" field. If anyone is actually using this, please email me and let me know :) ---------------------------------------------------------------------- Comment By: K. A. Krueger (fubarobfusco) Date: 2004-01-20 11:53 Message: Logged In: YES user_id=944208 I've uploaded a new version (0.2) of LDAPMemberships.py. This one is some ungodly number of times faster, as it does not do redundant LDAP queries in a single load. ---------------------------------------------------------------------- Comment By: K. A. Krueger (fubarobfusco) Date: 2004-01-05 12:18 Message: Logged In: YES user_id=944208 Er. SF ate the indentation on my "extend.py" example in the patch description. All of the lines after "def extend(list):" are meant to be indented once. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=871062&group_id=103 From noreply at sourceforge.net Thu Feb 3 21:09:16 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Feb 3 21:09:19 2005 Subject: [ mailman-Bugs-1115695 ] __init__() got an unexpected keyword argument 'errors' Message-ID: Bugs item #1115695, was opened at 2005-02-03 21:09 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=1115695&group_id=103 Category: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: J?rn Tschersich (schneemensch) Assigned to: Nobody/Anonymous (nobody) Summary: __init__() got an unexpected keyword argument 'errors' Initial Comment: Hello! Out of the blue, Mailman stopped working and produced this bug message on some pages and as a reply to mails sent to a list: Traceback (most recent call last): File "/usr/local/mailman/scripts/driver", line 87, in run_main main() File "/usr/local/mailman/Mailman/Cgi/admin.py", line 175, in main change_options(mlist, category, subcat, cgidata, doc) File "/usr/local/mailman/Mailman/Cgi/admin.py", line 1337, in change_options whence='admin mass sub') File "/usr/local/mailman/Mailman/MailList.py", line 951, in ApprovedAddMember digest, text) File "/usr/local/mailman/Mailman/Deliverer.py", line 79, in SendSubscribeAck text, pluser) File "/usr/local/mailman/Mailman/Message.py", line 206, in __init__ errors='replace') TypeError: __init__() got an unexpected keyword argument 'errors' Python information: Variable Value sys.version 2.2.2 (#1, Apr 18 2003, 08:23:15) [GCC 3.3 20030226 (prerelease) (SuSE Linux)] sys.executable /usr/bin/python sys.prefix /usr sys.exec_prefix /usr sys.path /usr sys.platform linux2 The Mailman log "error" shows the same output, nothing in any of the syslogs. Can somebody help? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1115695&group_id=103 From noreply at sourceforge.net Thu Feb 3 21:48:23 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Feb 3 21:48:28 2005 Subject: [ mailman-Bugs-1115695 ] __init__() got an unexpected keyword argument 'errors' Message-ID: Bugs item #1115695, was opened at 2005-02-03 21:09 Message generated for change (Comment added) made by schneemensch You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1115695&group_id=103 Category: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: J?rn Tschersich (schneemensch) Assigned to: Nobody/Anonymous (nobody) Summary: __init__() got an unexpected keyword argument 'errors' Initial Comment: Hello! Out of the blue, Mailman stopped working and produced this bug message on some pages and as a reply to mails sent to a list: Traceback (most recent call last): File "/usr/local/mailman/scripts/driver", line 87, in run_main main() File "/usr/local/mailman/Mailman/Cgi/admin.py", line 175, in main change_options(mlist, category, subcat, cgidata, doc) File "/usr/local/mailman/Mailman/Cgi/admin.py", line 1337, in change_options whence='admin mass sub') File "/usr/local/mailman/Mailman/MailList.py", line 951, in ApprovedAddMember digest, text) File "/usr/local/mailman/Mailman/Deliverer.py", line 79, in SendSubscribeAck text, pluser) File "/usr/local/mailman/Mailman/Message.py", line 206, in __init__ errors='replace') TypeError: __init__() got an unexpected keyword argument 'errors' Python information: Variable Value sys.version 2.2.2 (#1, Apr 18 2003, 08:23:15) [GCC 3.3 20030226 (prerelease) (SuSE Linux)] sys.executable /usr/bin/python sys.prefix /usr sys.exec_prefix /usr sys.path /usr sys.platform linux2 The Mailman log "error" shows the same output, nothing in any of the syslogs. Can somebody help? ---------------------------------------------------------------------- >Comment By: J?rn Tschersich (schneemensch) Date: 2005-02-03 21:48 Message: Logged In: YES user_id=607911 Sorry to have bothered you ... reinstalling 2.1.1 from the SuSE 8.2 CD fixed it. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1115695&group_id=103 From noreply at sourceforge.net Thu Feb 3 21:50:39 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Feb 3 21:50:42 2005 Subject: [ mailman-Bugs-1115695 ] __init__() got an unexpected keyword argument 'errors' Message-ID: Bugs item #1115695, was opened at 2005-02-03 21:09 Message generated for change (Settings changed) made by schneemensch You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1115695&group_id=103 Category: Web/CGI Group: 2.1 (stable) >Status: Deleted Resolution: None Priority: 5 Submitted By: J?rn Tschersich (schneemensch) Assigned to: Nobody/Anonymous (nobody) Summary: __init__() got an unexpected keyword argument 'errors' Initial Comment: Hello! Out of the blue, Mailman stopped working and produced this bug message on some pages and as a reply to mails sent to a list: Traceback (most recent call last): File "/usr/local/mailman/scripts/driver", line 87, in run_main main() File "/usr/local/mailman/Mailman/Cgi/admin.py", line 175, in main change_options(mlist, category, subcat, cgidata, doc) File "/usr/local/mailman/Mailman/Cgi/admin.py", line 1337, in change_options whence='admin mass sub') File "/usr/local/mailman/Mailman/MailList.py", line 951, in ApprovedAddMember digest, text) File "/usr/local/mailman/Mailman/Deliverer.py", line 79, in SendSubscribeAck text, pluser) File "/usr/local/mailman/Mailman/Message.py", line 206, in __init__ errors='replace') TypeError: __init__() got an unexpected keyword argument 'errors' Python information: Variable Value sys.version 2.2.2 (#1, Apr 18 2003, 08:23:15) [GCC 3.3 20030226 (prerelease) (SuSE Linux)] sys.executable /usr/bin/python sys.prefix /usr sys.exec_prefix /usr sys.path /usr sys.platform linux2 The Mailman log "error" shows the same output, nothing in any of the syslogs. Can somebody help? ---------------------------------------------------------------------- Comment By: J?rn Tschersich (schneemensch) Date: 2005-02-03 21:48 Message: Logged In: YES user_id=607911 Sorry to have bothered you ... reinstalling 2.1.1 from the SuSE 8.2 CD fixed it. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1115695&group_id=103 From noreply at sourceforge.net Sat Feb 5 19:32:52 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Sat Feb 5 19:32:54 2005 Subject: [ mailman-Patches-1116952 ] Add Date header to digest messages Message-ID: Patches item #1116952, was opened at 2005-02-05 13:32 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=1116952&group_id=103 Category: mail delivery Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Jeffrey A. Groves (annorax) Assigned to: Nobody/Anonymous (nobody) Summary: Add Date header to digest messages Initial Comment: Digest messages do not have a Date header added to them. This patch provides the Date head with the time of day that the digest message is being created. Without this Date header, milters such as milter-date reject or mark as spam all digest messages. I have provided a diff file for Hander/ToDigest.py that remedies this issue. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1116952&group_id=103 From noreply at sourceforge.net Sat Feb 5 19:34:50 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Sat Feb 5 19:34:53 2005 Subject: [ mailman-Patches-1116952 ] Add Date header to digest messages in Mailman 2.1.5 Message-ID: Patches item #1116952, was opened at 2005-02-05 13:32 Message generated for change (Settings changed) made by annorax You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1116952&group_id=103 Category: mail delivery Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Jeffrey A. Groves (annorax) Assigned to: Nobody/Anonymous (nobody) >Summary: Add Date header to digest messages in Mailman 2.1.5 Initial Comment: Digest messages do not have a Date header added to them. This patch provides the Date head with the time of day that the digest message is being created. Without this Date header, milters such as milter-date reject or mark as spam all digest messages. I have provided a diff file for Hander/ToDigest.py that remedies this issue. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1116952&group_id=103 From noreply at sourceforge.net Sat Feb 5 19:39:00 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Sat Feb 5 19:39:03 2005 Subject: [ mailman-Patches-1116952 ] Add Date header to digest messages in Mailman 2.1.5 Message-ID: Patches item #1116952, was opened at 2005-02-05 13:32 Message generated for change (Comment added) made by annorax You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1116952&group_id=103 Category: mail delivery Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Jeffrey A. Groves (annorax) Assigned to: Nobody/Anonymous (nobody) Summary: Add Date header to digest messages in Mailman 2.1.5 Initial Comment: Digest messages do not have a Date header added to them. This patch provides the Date head with the time of day that the digest message is being created. Without this Date header, milters such as milter-date reject or mark as spam all digest messages. I have provided a diff file for Hander/ToDigest.py that remedies this issue. ---------------------------------------------------------------------- >Comment By: Jeffrey A. Groves (annorax) Date: 2005-02-05 13:39 Message: Logged In: YES user_id=537482 Please excuse the repeated misspelling of the word "Handlers". ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1116952&group_id=103 From noreply at sourceforge.net Mon Feb 7 02:28:01 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Feb 7 02:28:03 2005 Subject: [ mailman-Patches-1117618 ] Don't Cc list address when fully personalized and anonymous Message-ID: Patches item #1117618, was opened at 2005-02-06 17:28 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=1117618&group_id=103 Category: mail delivery Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Mark Sapiro (msapiro) Assigned to: Nobody/Anonymous (nobody) Summary: Don't Cc list address when fully personalized and anonymous Initial Comment: CookHeaders.py adds a Cc to the list posting address to enable replies to the list when the list is fully personalized and Reply-To has not been munged with the list posting address. This Cc should also be skipped when the list is anonymous as the posting address is already in From and Reply-To in this case. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1117618&group_id=103 From noreply at sourceforge.net Mon Feb 7 05:51:50 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Feb 7 05:51:52 2005 Subject: [ mailman-Patches-1117618 ] Don't Cc list address when fully personalized and anonymous Message-ID: Patches item #1117618, was opened at 2005-02-07 01:28 Message generated for change (Settings changed) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1117618&group_id=103 Category: mail delivery Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Mark Sapiro (msapiro) >Assigned to: Tokio Kikuchi (tkikuchi) Summary: Don't Cc list address when fully personalized and anonymous Initial Comment: CookHeaders.py adds a Cc to the list posting address to enable replies to the list when the list is fully personalized and Reply-To has not been munged with the list posting address. This Cc should also be skipped when the list is anonymous as the posting address is already in From and Reply-To in this case. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1117618&group_id=103 From noreply at sourceforge.net Mon Feb 7 14:09:42 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Feb 7 14:09:45 2005 Subject: [ mailman-Patches-1117853 ] Danish probe.txt Message-ID: Patches item #1117853, was opened at 2005-02-07 14:09 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=1117853&group_id=103 Category: internationalization Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Tom G. Christensen (tgc99) Assigned to: Nobody/Anonymous (nobody) Summary: Danish probe.txt Initial Comment: This is a danish translation of the probe.txt template ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1117853&group_id=103 From noreply at sourceforge.net Mon Feb 7 14:10:08 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Feb 7 14:10:13 2005 Subject: [ mailman-Patches-1117853 ] Danish probe.txt Message-ID: Patches item #1117853, was opened at 2005-02-07 14:09 Message generated for change (Settings changed) made by tgc99 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1117853&group_id=103 Category: internationalization Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Tom G. Christensen (tgc99) >Assigned to: Tokio Kikuchi (tkikuchi) Summary: Danish probe.txt Initial Comment: This is a danish translation of the probe.txt template ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1117853&group_id=103 From noreply at sourceforge.net Tue Feb 8 03:12:39 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Feb 8 03:12:42 2005 Subject: [ mailman-Patches-1117853 ] Danish probe.txt Message-ID: Patches item #1117853, was opened at 2005-02-07 13:09 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1117853&group_id=103 Category: internationalization Group: Mailman 2.1 >Status: Closed >Resolution: Accepted Priority: 5 Submitted By: Tom G. Christensen (tgc99) Assigned to: Tokio Kikuchi (tkikuchi) Summary: Danish probe.txt Initial Comment: This is a danish translation of the probe.txt template ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2005-02-08 02:12 Message: Logged In: YES user_id=67709 Thank you! ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1117853&group_id=103 From noreply at sourceforge.net Tue Feb 8 14:26:58 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Feb 8 14:27:02 2005 Subject: [ mailman-Bugs-1023942 ] No "Date:" line in digest header Message-ID: Bugs item #1023942, was opened at 2004-09-07 21:55 Message generated for change (Comment added) made by janschlosser You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1023942&group_id=103 Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Todd K. Watson (tkdubs) Assigned to: Nobody/Anonymous (nobody) Summary: No "Date:" line in digest header Initial Comment: I am running Mailman-2.1.5. Mailman fails to insert the "Date:" line in the header, which can cause problems for MTA's which do not inject a "Date:" line (such as qmail). Each individual message within the digest has a date line in its header, but the digest itself is missing the Date line. This causes mail readers like Thunderbird to label the message as being sent on Dec. 31, 1969. Most MTA's and MUA's inject a Date line, but I'm using Qmail as an MTA -- which doesn't inject one. It is the job of the MUA (Mailman in this case) to create the Date: line according to RFC-2822. This was fixed for non-digested messages delivered to lists in 2.1-beta-1 of Mailman according to the NEWS file, but has not yet been addressed for delivery of digests. ---------------------------------------------------------------------- Comment By: Jan Schlosser (janschlosser) Date: 2005-02-08 14:26 Message: Logged In: YES user_id=918851 This one is fixed by patch 1116952, although the patch file didn't work without manual rewriting to the ToDigest.py source file ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1023942&group_id=103 From noreply at sourceforge.net Thu Feb 10 20:37:01 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Feb 10 20:37:03 2005 Subject: [ mailman-Feature Requests-1120282 ] PASSWORD_REMINDERS_FROM Defaults.py Config Option Message-ID: Feature Requests item #1120282, was opened at 2005-02-10 12:37 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=1120282&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Matt (matt_ruzicka) Assigned to: Nobody/Anonymous (nobody) Summary: PASSWORD_REMINDERS_FROM Defaults.py Config Option Initial Comment: As a site that will be running a number of separate lists maintained and containing unrelated addresses it would be nice if there was if there was a config option that allowed an administrator to specify if the monthly password reminders came from the site owner (to retain current message reduction capacities) or the list owner (to allow bounces and responses from the reminders to go to the list owners themselves). Obviously this option would most defintiely end up causing people to get multiple messages from a single Mailman installation, but an administrator might see this as an acceptible trade off to ensure better communication between list members and list owners (as opposed to site owners who may not care to be bothered with messages from list members they are not aware of). My limited brain envisioned something like # This option determines what address the monthly # password reminders is sent from. It is strongly # recommended that you leave this set to site owner # so users subscribed to multiple lists will receive # only one message per month. # # examples are # %(siteowner)s@%(hostname)s - (recommended) # %(listowner)s@%(hostname)s # PASSWORD_REMINDERS_FROM = %(siteowner)s@%(hostname)s Also, not sure if this would actually be better suited for list specific list options so lists with a large number of cross over addresses could still benefit from the single address. Thanks for your time. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1120282&group_id=103 From noreply at sourceforge.net Fri Feb 11 01:39:51 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Feb 11 01:39:54 2005 Subject: [ mailman-Bugs-1120477 ] Traceback in private.py after security patch Message-ID: Bugs item #1120477, was opened at 2005-02-10 19:39 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=1120477&group_id=103 Category: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Roger H. Goun (rgoun) Assigned to: Nobody/Anonymous (nobody) Summary: Traceback in private.py after security patch Initial Comment: I applied the patch at http://www.list.org/CAN-2005-0202.txt to a Mailman 2.1.4 installation and restarted the Web server. The first time I tried to access the archives for a private list using an email address that's *not* subscribed to the list, I got the traceback below. I backed out the patch and restarted the Web server. I now get the correct "Authorization failed." message. Note that for the sake of paranoia I've obfuscated my email address, changed the names of private lists, and flipped a few bits in the cookie data and remote address below. -- Roger --------------- Bug in Mailman version 2.1.4 We're sorry, we hit a bug! If you would like to help us identify the problem, please email a copy of this page to the webmaster for this site with a description of what happened. Thanks! Traceback: Traceback (most recent call last): File "/usr/local/mailman/scripts/driver", line 87, in run_main main() File "/usr/local/mailman/Mailman/Cgi/private.py", line 124, in main password, username): File "/usr/local/mailman/Mailman/SecurityManager.py", line 220, in WebAuthenticate ok = self.CheckCookie(ac, user) File "/usr/local/mailman/Mailman/SecurityManager.py", line 300, in CheckCookie ok = self.__checkone(c, authcontext, user) File "/usr/local/mailman/Mailman/SecurityManager.py", line 310, in __checkone key, secret = self.AuthContextInfo(authcontext, user) File "/usr/local/mailman/Mailman/SecurityManager.py", line 105, in AuthContextInfo secret = self.getMemberPassword(user) File "/usr/local/mailman/Mailman/OldStyleMemberships.py", line 102, in getMemberPassword raise Errors.NotAMemberError, member NotAMemberError: roger-no@spam-bcah.com Python information: Variable Value sys.version 2.2.2 (#1, Jan 30 2003, 21:26:22) [GCC 2.96 20000731 (Red Hat Linux 7.3 2.96-112)] sys.executable /usr/bin/python2.2 sys.prefix /usr sys.exec_prefix /usr sys.path /usr sys.platform linux2 Environment variables: Variable Value PATH_INFO /dfnh-foo/ HTTP_ACCEPT text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 CONTENT_TYPE application/x-www-form-urlencoded HTTP_REFERER http://mail.democracyfornewhampshire.com/mailman/private/dfnh-foo/ SERVER_SOFTWARE Apache/1.3.27 (Unix) (Red-Hat/Linux) mod_python/2.7.8 Python/1.5.2 mod_ssl/2.8.12 OpenSSL/0.9.6b DAV/1.0.3 PHP/4.1.2 mod_perl/1.26 mod_throttle/3.1.2 PYTHONPATH /usr/local/mailman SCRIPT_FILENAME /usr/local/mailman/cgi-bin/private SERVER_ADMIN roger-no@spam-bcah.com SCRIPT_NAME /mailman/private SERVER_SIGNATURE Apache/1.3.27 Server at democracyfornewhampshire.com Port 80 REQUEST_METHOD POST HTTP_HOST mail.democracyfornewhampshire.com HTTP_KEEP_ALIVE 300 SERVER_PROTOCOL HTTP/1.1 QUERY_STRING REQUEST_URI /mailman/private/dfnh-foo/ CONTENT_LENGTH 63 HTTP_ACCEPT_CHARSET ISO-8859-1,utf-8;q=0.7,*;q=0.7 HTTP_USER_AGENT Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041111 Firefox/1.0 HTTP_CONNECTION keep-alive HTTP_COOKIE dfnh-board+user+roger-no--at--spam-bcah.com=280200000069caae0b42732800000063346130393963653330656239633862643737356337626437396561663334363862343563643536; dfnh-members+admin=280200000069dcee0b42732800000033353539613836343166396565376030323966663963313435646564633734303837666366666230 SERVER_NAME democracyfornewhampshire.com REMOTE_ADDR 24.35.177.35 REMOTE_PORT 38224 HTTP_ACCEPT_LANGUAGE en-us,en;q=0.5 PATH_TRANSLATED /home/roger/democracyfornewhampshire.com/html/dfnh-foo/ SERVER_PORT 80 GATEWAY_INTERFACE CGI/1.1 HTTP_ACCEPT_ENCODING gzip,deflate SERVER_ADDR 199.125.75.14 DOCUMENT_ROOT /home/roger/democracyfornewhampshire.com/html ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1120477&group_id=103 From noreply at sourceforge.net Fri Feb 11 02:33:50 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Feb 11 02:33:53 2005 Subject: [ mailman-Bugs-1120477 ] Traceback in private.py after security patch Message-ID: Bugs item #1120477, was opened at 2005-02-11 00:39 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1120477&group_id=103 Category: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Roger H. Goun (rgoun) Assigned to: Nobody/Anonymous (nobody) Summary: Traceback in private.py after security patch Initial Comment: I applied the patch at http://www.list.org/CAN-2005-0202.txt to a Mailman 2.1.4 installation and restarted the Web server. The first time I tried to access the archives for a private list using an email address that's *not* subscribed to the list, I got the traceback below. I backed out the patch and restarted the Web server. I now get the correct "Authorization failed." message. Note that for the sake of paranoia I've obfuscated my email address, changed the names of private lists, and flipped a few bits in the cookie data and remote address below. -- Roger --------------- Bug in Mailman version 2.1.4 We're sorry, we hit a bug! If you would like to help us identify the problem, please email a copy of this page to the webmaster for this site with a description of what happened. Thanks! Traceback: Traceback (most recent call last): File "/usr/local/mailman/scripts/driver", line 87, in run_main main() File "/usr/local/mailman/Mailman/Cgi/private.py", line 124, in main password, username): File "/usr/local/mailman/Mailman/SecurityManager.py", line 220, in WebAuthenticate ok = self.CheckCookie(ac, user) File "/usr/local/mailman/Mailman/SecurityManager.py", line 300, in CheckCookie ok = self.__checkone(c, authcontext, user) File "/usr/local/mailman/Mailman/SecurityManager.py", line 310, in __checkone key, secret = self.AuthContextInfo(authcontext, user) File "/usr/local/mailman/Mailman/SecurityManager.py", line 105, in AuthContextInfo secret = self.getMemberPassword(user) File "/usr/local/mailman/Mailman/OldStyleMemberships.py", line 102, in getMemberPassword raise Errors.NotAMemberError, member NotAMemberError: roger-no@spam-bcah.com Python information: Variable Value sys.version 2.2.2 (#1, Jan 30 2003, 21:26:22) [GCC 2.96 20000731 (Red Hat Linux 7.3 2.96-112)] sys.executable /usr/bin/python2.2 sys.prefix /usr sys.exec_prefix /usr sys.path /usr sys.platform linux2 Environment variables: Variable Value PATH_INFO /dfnh-foo/ HTTP_ACCEPT text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 CONTENT_TYPE application/x-www-form-urlencoded HTTP_REFERER http://mail.democracyfornewhampshire.com/mailman/private/dfnh-foo/ SERVER_SOFTWARE Apache/1.3.27 (Unix) (Red-Hat/Linux) mod_python/2.7.8 Python/1.5.2 mod_ssl/2.8.12 OpenSSL/0.9.6b DAV/1.0.3 PHP/4.1.2 mod_perl/1.26 mod_throttle/3.1.2 PYTHONPATH /usr/local/mailman SCRIPT_FILENAME /usr/local/mailman/cgi-bin/private SERVER_ADMIN roger-no@spam-bcah.com SCRIPT_NAME /mailman/private SERVER_SIGNATURE Apache/1.3.27 Server at democracyfornewhampshire.com Port 80 REQUEST_METHOD POST HTTP_HOST mail.democracyfornewhampshire.com HTTP_KEEP_ALIVE 300 SERVER_PROTOCOL HTTP/1.1 QUERY_STRING REQUEST_URI /mailman/private/dfnh-foo/ CONTENT_LENGTH 63 HTTP_ACCEPT_CHARSET ISO-8859-1,utf-8;q=0.7,*;q=0.7 HTTP_USER_AGENT Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041111 Firefox/1.0 HTTP_CONNECTION keep-alive HTTP_COOKIE dfnh-board+user+roger-no--at--spam-bcah.com=280200000069caae0b42732800000063346130393963653330656239633862643737356337626437396561663334363862343563643536; dfnh-members+admin=280200000069dcee0b42732800000033353539613836343166396565376030323966663963313435646564633734303837666366666230 SERVER_NAME democracyfornewhampshire.com REMOTE_ADDR 24.35.177.35 REMOTE_PORT 38224 HTTP_ACCEPT_LANGUAGE en-us,en;q=0.5 PATH_TRANSLATED /home/roger/democracyfornewhampshire.com/html/dfnh-foo/ SERVER_PORT 80 GATEWAY_INTERFACE CGI/1.1 HTTP_ACCEPT_ENCODING gzip,deflate SERVER_ADDR 199.125.75.14 DOCUMENT_ROOT /home/roger/democracyfornewhampshire.com/html ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2005-02-11 01:33 Message: Logged In: YES user_id=67709 The security patch should have nothing to do with the trace back. Will you please try again after deleting cookies of this site? (not disable but delete existing cookies) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1120477&group_id=103 From noreply at sourceforge.net Fri Feb 11 11:58:22 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Feb 11 11:58:25 2005 Subject: [ mailman-Feature Requests-1120700 ] ReturnMail from max_message_size, configure attachment? Message-ID: Feature Requests item #1120700, was opened at 2005-02-11 11: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=1120700&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Rickard Persson (ripop) Assigned to: Nobody/Anonymous (nobody) Summary: ReturnMail from max_message_size, configure attachment? Initial Comment: Hi I have a problem with "max_message_size", not the actual variable itself. My problem is with the message sent back to the admin of the list. This message has the original message included, and for me this is not a good solution. I sit on a slow connection and I guess you understand what happens :( I have lookt around but haven't found anything about it before in lists or documentations. So here comes the question: Is it possible to have a configuration option where the admin can chose if the complete original message should be attached to the message? Thus not needing to download the complete mail with the big atatchment? Tanks for all the hard work you have allready done Rickard Persson Sweden/Lappland/Lycksele ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1120700&group_id=103 From noreply at sourceforge.net Fri Feb 11 12:32:00 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Feb 11 12:32:04 2005 Subject: [ mailman-Bugs-1120477 ] Traceback in private.py after security patch Message-ID: Bugs item #1120477, was opened at 2005-02-10 19:39 Message generated for change (Comment added) made by rgoun You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1120477&group_id=103 Category: Web/CGI Group: 2.1 (stable) >Status: Closed >Resolution: Invalid Priority: 5 Submitted By: Roger H. Goun (rgoun) Assigned to: Nobody/Anonymous (nobody) Summary: Traceback in private.py after security patch Initial Comment: I applied the patch at http://www.list.org/CAN-2005-0202.txt to a Mailman 2.1.4 installation and restarted the Web server. The first time I tried to access the archives for a private list using an email address that's *not* subscribed to the list, I got the traceback below. I backed out the patch and restarted the Web server. I now get the correct "Authorization failed." message. Note that for the sake of paranoia I've obfuscated my email address, changed the names of private lists, and flipped a few bits in the cookie data and remote address below. -- Roger --------------- Bug in Mailman version 2.1.4 We're sorry, we hit a bug! If you would like to help us identify the problem, please email a copy of this page to the webmaster for this site with a description of what happened. Thanks! Traceback: Traceback (most recent call last): File "/usr/local/mailman/scripts/driver", line 87, in run_main main() File "/usr/local/mailman/Mailman/Cgi/private.py", line 124, in main password, username): File "/usr/local/mailman/Mailman/SecurityManager.py", line 220, in WebAuthenticate ok = self.CheckCookie(ac, user) File "/usr/local/mailman/Mailman/SecurityManager.py", line 300, in CheckCookie ok = self.__checkone(c, authcontext, user) File "/usr/local/mailman/Mailman/SecurityManager.py", line 310, in __checkone key, secret = self.AuthContextInfo(authcontext, user) File "/usr/local/mailman/Mailman/SecurityManager.py", line 105, in AuthContextInfo secret = self.getMemberPassword(user) File "/usr/local/mailman/Mailman/OldStyleMemberships.py", line 102, in getMemberPassword raise Errors.NotAMemberError, member NotAMemberError: roger-no@spam-bcah.com Python information: Variable Value sys.version 2.2.2 (#1, Jan 30 2003, 21:26:22) [GCC 2.96 20000731 (Red Hat Linux 7.3 2.96-112)] sys.executable /usr/bin/python2.2 sys.prefix /usr sys.exec_prefix /usr sys.path /usr sys.platform linux2 Environment variables: Variable Value PATH_INFO /dfnh-foo/ HTTP_ACCEPT text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 CONTENT_TYPE application/x-www-form-urlencoded HTTP_REFERER http://mail.democracyfornewhampshire.com/mailman/private/dfnh-foo/ SERVER_SOFTWARE Apache/1.3.27 (Unix) (Red-Hat/Linux) mod_python/2.7.8 Python/1.5.2 mod_ssl/2.8.12 OpenSSL/0.9.6b DAV/1.0.3 PHP/4.1.2 mod_perl/1.26 mod_throttle/3.1.2 PYTHONPATH /usr/local/mailman SCRIPT_FILENAME /usr/local/mailman/cgi-bin/private SERVER_ADMIN roger-no@spam-bcah.com SCRIPT_NAME /mailman/private SERVER_SIGNATURE Apache/1.3.27 Server at democracyfornewhampshire.com Port 80 REQUEST_METHOD POST HTTP_HOST mail.democracyfornewhampshire.com HTTP_KEEP_ALIVE 300 SERVER_PROTOCOL HTTP/1.1 QUERY_STRING REQUEST_URI /mailman/private/dfnh-foo/ CONTENT_LENGTH 63 HTTP_ACCEPT_CHARSET ISO-8859-1,utf-8;q=0.7,*;q=0.7 HTTP_USER_AGENT Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041111 Firefox/1.0 HTTP_CONNECTION keep-alive HTTP_COOKIE dfnh-board+user+roger-no--at--spam-bcah.com=280200000069caae0b42732800000063346130393963653330656239633862643737356337626437396561663334363862343563643536; dfnh-members+admin=280200000069dcee0b42732800000033353539613836343166396565376030323966663963313435646564633734303837666366666230 SERVER_NAME democracyfornewhampshire.com REMOTE_ADDR 24.35.177.35 REMOTE_PORT 38224 HTTP_ACCEPT_LANGUAGE en-us,en;q=0.5 PATH_TRANSLATED /home/roger/democracyfornewhampshire.com/html/dfnh-foo/ SERVER_PORT 80 GATEWAY_INTERFACE CGI/1.1 HTTP_ACCEPT_ENCODING gzip,deflate SERVER_ADDR 199.125.75.14 DOCUMENT_ROOT /home/roger/democracyfornewhampshire.com/html ---------------------------------------------------------------------- >Comment By: Roger H. Goun (rgoun) Date: 2005-02-11 06:32 Message: Logged In: YES user_id=3950 I deleted cookies and tried again. This time I got the "Authorization failed." message. Sorry for the false alarm. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2005-02-10 20:33 Message: Logged In: YES user_id=67709 The security patch should have nothing to do with the trace back. Will you please try again after deleting cookies of this site? (not disable but delete existing cookies) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1120477&group_id=103 From noreply at sourceforge.net Sat Feb 12 09:14:47 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Sat Feb 12 09:14:50 2005 Subject: [ mailman-Patches-1121257 ] adding html banners, user_id, list_id Message-ID: Patches item #1121257, was opened at 2005-02-12 08:14 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=1121257&group_id=103 Category: list administration Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: binworkers (binworkers) Assigned to: Nobody/Anonymous (nobody) Summary: adding html banners, user_id, list_id Initial Comment: Html header/footer patch. Add to mailman 2.1.5 functionality for add html and text banners to mime messages. Added new option for these to Non-Digest category on List admin panel. Adding list_id user_id and personalize it, so they may be included in text/html footers/headers. Added script for handle unsubscribe requests which contain user_id, list_id, password. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1121257&group_id=103 From noreply at sourceforge.net Sat Feb 12 09:34:05 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Sat Feb 12 09:34:08 2005 Subject: [ mailman-Patches-1121257 ] adding html banners, user_id, list_id Message-ID: Patches item #1121257, was opened at 2005-02-12 08:14 Message generated for change (Comment added) made by binworkers You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1121257&group_id=103 Category: list administration Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: binworkers (binworkers) >Assigned to: Barry A. Warsaw (bwarsaw) Summary: adding html banners, user_id, list_id Initial Comment: Html header/footer patch. Add to mailman 2.1.5 functionality for add html and text banners to mime messages. Added new option for these to Non-Digest category on List admin panel. Adding list_id user_id and personalize it, so they may be included in text/html footers/headers. Added script for handle unsubscribe requests which contain user_id, list_id, password. ---------------------------------------------------------------------- >Comment By: binworkers (binworkers) Date: 2005-02-12 08:34 Message: Logged In: YES user_id=1217687 authors: Main ideas and testing: adrian@tasdevil.com Implementation: binworkers@dcemail.com ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1121257&group_id=103 From noreply at sourceforge.net Mon Feb 14 04:14:42 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Feb 14 04:14:44 2005 Subject: [ mailman-Bugs-1122131 ] Can't configure Reply-To: to include Poster *and* List Message-ID: Bugs item #1122131, was opened at 2005-02-13 22: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=1122131&group_id=103 Category: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Seth Teller (seth_teller) Assigned to: Nobody/Anonymous (nobody) Summary: Can't configure Reply-To: to include Poster *and* List Initial Comment: Regarding Mailman 2.1.5, in use at MIT CSAIL. I administer a class, and a mailing list "help" to which students in the class can email problem reports. The reports go to the course staff. I would like Mailman to provide the default behavior that the staff's replies go to the list (so the rest of the staff sees them) *and* to the student (so that the student sees the solution!). Yet Mailman does not seem to be able to support this behavior. My choices are to set reply-to to Poster or to List. If I set to Poster, then the default Reply behavior excludes the List. If I set to List, then neither Reply or Reply-All includes the original Poster (i.e., the student). I submit that Mailman should support a third option: Reply-To: Poster *and* List. thanks, seth teller. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1122131&group_id=103 From noreply at sourceforge.net Mon Feb 14 23:16:05 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Feb 14 23:16:09 2005 Subject: [ mailman-Bugs-649112 ] " #" in mail address confuses mailman Message-ID: Bugs item #649112, was opened at 2002-12-05 19:59 Message generated for change (Comment added) made by effbot You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=649112&group_id=103 Category: Web/CGI Group: None Status: Open Resolution: None Priority: 5 Submitted By: Fredrik Lundh (effbot) Assigned to: Nobody/Anonymous (nobody) Summary: "#" in mail address confuses mailman Initial Comment: someone recently managed to subscribe himself to the python.org image-sig mailing list, using an add- ress looking a bit like this one: prefix#user@some.com unfortunately, the web interface doesn't escape the "#" character, so the web pages for this user cannot be accessed: http://mail.python.org/mailman/options/image- sig/prefix#user--at--some.com (the browser strips off the "#" and everything after it before sending the URL to mailman...). I'm not sure what version python.org is running, but I suspect that the Barry person might be able to figure that out. cheers /F ---------------------------------------------------------------------- >Comment By: Fredrik Lundh (effbot) Date: 2005-02-14 23:16 Message: Logged In: YES user_id=38376 (if this has been fixed, feel free to close this report) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=649112&group_id=103 From noreply at sourceforge.net Tue Feb 15 11:40:31 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Feb 15 11:40:36 2005 Subject: [ mailman-Patches-1123027 ] Danish translation update Message-ID: Patches item #1123027, was opened at 2005-02-15 11:40 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=1123027&group_id=103 Category: internationalization Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Tom G. Christensen (tgc99) Assigned to: Nobody/Anonymous (nobody) Summary: Danish translation update Initial Comment: Add missing translation Fix a fuzzy ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1123027&group_id=103 From noreply at sourceforge.net Tue Feb 15 11:41:04 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Feb 15 11:41:08 2005 Subject: [ mailman-Patches-1123027 ] Danish translation update Message-ID: Patches item #1123027, was opened at 2005-02-15 11:40 Message generated for change (Settings changed) made by tgc99 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1123027&group_id=103 Category: internationalization Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Tom G. Christensen (tgc99) >Assigned to: Tokio Kikuchi (tkikuchi) Summary: Danish translation update Initial Comment: Add missing translation Fix a fuzzy ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1123027&group_id=103 From noreply at sourceforge.net Tue Feb 15 13:23:11 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Feb 15 13:23:13 2005 Subject: [ mailman-Patches-1123027 ] Danish translation update Message-ID: Patches item #1123027, was opened at 2005-02-15 10:40 Message generated for change (Settings changed) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1123027&group_id=103 Category: internationalization Group: Mailman 2.1 >Status: Closed >Resolution: Accepted Priority: 5 Submitted By: Tom G. Christensen (tgc99) Assigned to: Tokio Kikuchi (tkikuchi) Summary: Danish translation update Initial Comment: Add missing translation Fix a fuzzy ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1123027&group_id=103 From noreply at sourceforge.net Tue Feb 15 13:27:10 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Feb 15 13:27:13 2005 Subject: [ mailman-Patches-1117618 ] Don't Cc list address when fully personalized and anonymous Message-ID: Patches item #1117618, was opened at 2005-02-07 01:28 Message generated for change (Settings changed) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1117618&group_id=103 Category: mail delivery Group: Mailman 2.1 >Status: Closed >Resolution: Accepted Priority: 5 Submitted By: Mark Sapiro (msapiro) Assigned to: Tokio Kikuchi (tkikuchi) Summary: Don't Cc list address when fully personalized and anonymous Initial Comment: CookHeaders.py adds a Cc to the list posting address to enable replies to the list when the list is fully personalized and Reply-To has not been munged with the list posting address. This Cc should also be skipped when the list is anonymous as the posting address is already in From and Reply-To in this case. ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2005-02-15 12:27 Message: Logged In: YES user_id=67709 Thank you! Fixed in CVS/2.1.6b3. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1117618&group_id=103 From noreply at sourceforge.net Tue Feb 15 13:29:44 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Feb 15 13:29:47 2005 Subject: [ mailman-Patches-1116952 ] Add Date header to digest messages in Mailman 2.1.5 Message-ID: Patches item #1116952, was opened at 2005-02-05 18:32 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1116952&group_id=103 Category: mail delivery Group: Mailman 2.1 >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Jeffrey A. Groves (annorax) Assigned to: Nobody/Anonymous (nobody) Summary: Add Date header to digest messages in Mailman 2.1.5 Initial Comment: Digest messages do not have a Date header added to them. This patch provides the Date head with the time of day that the digest message is being created. Without this Date header, milters such as milter-date reject or mark as spam all digest messages. I have provided a diff file for Hander/ToDigest.py that remedies this issue. ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2005-02-15 12:29 Message: Logged In: YES user_id=67709 Fixed in CVS. Thank you. ---------------------------------------------------------------------- Comment By: Jeffrey A. Groves (annorax) Date: 2005-02-05 18:39 Message: Logged In: YES user_id=537482 Please excuse the repeated misspelling of the word "Handlers". ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1116952&group_id=103 From noreply at sourceforge.net Tue Feb 15 13:35:14 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Feb 15 13:35:30 2005 Subject: [ mailman-Patches-1107169 ] Re-use member_moderation_notice for generic_nonmember_action Message-ID: Patches item #1107169, was opened at 2005-01-22 02:54 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1107169&group_id=103 Category: bounce processing Group: Mailman 2.1 >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Brad Knowles (shub) Assigned to: Nobody/Anonymous (nobody) Summary: Re-use member_moderation_notice for generic_nonmember_action Initial Comment: With Mailman 2.1.5, it's possible to create a fairly nicely worded rejection/moderation message in the member_moderation_notice field, and be able to maintain that via the web as opposed to a template file. However, there is no corresponding way to create a nice notice for people who are trying to post to the list but are not members. It is not uncommon to want to set the list so that no members are moderated by default (so that the member_moderation_notice does not apply), but to set the generic_nonmember_action to be Reject or Hold. Unfortunately, default standard text is hard-coded into Mailman/Handlers/Moderate.py for these instances. I'd be fine with a template file that I could modify, along the lines of postheld.txt -- at least that would allow me to put in URLs properly formatted with less-than and greater-than signs which don't get HTML-escaped when the text is saved. ;( Alternatively, a separate field should probably be created, probably something like generic_nonmember_notice, or somesuch. That way you could have two different notices for the two different cases, as appropriate. However, I don't grok Python, and I'm not a real programmer. So, I have hacked together a little patch that allows me to re-use the member_moderation_notice as a result of the setting of generic_nonmember_action. I hope you find this useful. ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2005-02-15 12:35 Message: Logged In: YES user_id=67709 Instead of re-use, we add a new text box for non-member rejection notice. Fixed in CVS/2.1.6b3. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1107169&group_id=103 From noreply at sourceforge.net Tue Feb 15 21:14:36 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Feb 15 21:14:38 2005 Subject: [ mailman-Patches-1123383 ] Daily Status Report script... Message-ID: Patches item #1123383, was opened at 2005-02-15 20:14 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=1123383&group_id=103 Category: list administration Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Brad Knowles (shub) Assigned to: Nobody/Anonymous (nobody) Summary: Daily Status Report script... Initial Comment: Folks, I quickly whacked together a Daily Status Report script for Mailman (using Bourne shell, not Python ;), and thought that other folks might be interested in seeing it. The basic concept is a program that gets fired off at 23:59 every night, and goes through a variety of log files looking for entries specific to that date, and indicating problems or certain types of activity that might be of interest to someone trying to administer the server. It also does an "ls -la" of /usr/local/mailman/qfiles/*, so that you can see what is in the queue at the time of the running of the script. My concept was that this daily report would get e-mailed to the admin, or posted to a "reports" mailing list, where they could be archived and kept for future reference. The script does not (yet) do any statistics calculations, although it should be relatively easy to hack together some basic stats using awk, sort, etc.... Anyway, I thought I'd share it and let folks take a look at it, and if anyone has any recommended improvements, we can incorporate those and share them back out with everyone. The code is written under a BSD-style license, so if you don't want to contribute any changes back to me, that's okay. Of course, I would prefer that you did, but I leave the choice up to you. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1123383&group_id=103 From noreply at sourceforge.net Tue Feb 15 21:26:16 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Feb 15 21:26:19 2005 Subject: [ mailman-Bugs-1123390 ] Bug in mailing list subscription request cancellation Message-ID: Bugs item #1123390, was opened at 2005-02-15 21:26 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=1123390&group_id=103 Category: None Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Sylvain BEUCLER (beuc) Assigned to: Nobody/Anonymous (nobody) Summary: Bug in mailing list subscription request cancellation Initial Comment: This was reported by a Savannah user (Darren.Hiebert@sstb.arc.army.mil - can he be added in Cc of this item?), for the lists.gnu.org install: Bug in Mailman version 2.1.5 We're sorry, we hit a bug! If you would like to help us identify the problem, please email a copy of this page to the webmaster for this site with a description of what happened. Thanks! Traceback: Traceback (most recent call last): File "/var/mailman/scripts/driver", line 87, in run_main main() File "/var/mailman/Mailman/Cgi/confirm.py", line 114, in main subscription_cancel(mlist, doc, cookie) File "/var/mailman/Mailman/Cgi/confirm.py", line 312, in subscription_cancel userdesc = mlist.pend_confirm(cookie)[1] File "/var/mailman/Mailman/Pending.py", line 141, in pend_confirm assert self.Locked() AssertionError Python information: Variable Value sys.version 2.3.3 (#1, May 7 2004, 10:31:40) [GCC 3.3.3 20040412 (Red Hat Linux 3.3.3-7)] sys.executable /usr/bin/python sys.prefix /usr sys.exec_prefix /usr sys.path /usr sys.platform linux2 Environment variables: Variable Value HTTP_COOKIE savannah-root+admin=28020000006999581242732800000036386335316237303736666537366461623438353837346561393533313164616161386164653439 SERVER_SOFTWARE Apache/2.0.51 (Fedora) SCRIPT_NAME /mailman/confirm SERVER_SIGNATURE REQUEST_METHOD POST HTTP_KEEP_ALIVE 300 SERVER_PROTOCOL HTTP/1.1 QUERY_STRING CONTENT_LENGTH 131 HTTP_ACCEPT_CHARSET ISO-8859-1,utf-8;q=0.7,*;q=0.7 HTTP_USER_AGENT Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0 HTTP_CONNECTION keep-alive HTTP_REFERER http://lists.gnu.org/mailman/confirm/bug-make/443c45564f830ea03dc4aa276c9da99f69ebd7e6 SERVER_NAME lists.gnu.org REMOTE_ADDR 82.230.99.124 PATH_TRANSLATED /var/www/html/lists.gnu.org/bug-make SERVER_PORT 80 SERVER_ADDR 199.232.76.165 DOCUMENT_ROOT /var/www/html/lists.gnu.org/ PYTHONPATH /var/mailman SCRIPT_FILENAME /var/mailman/cgi-bin/confirm SERVER_ADMIN gnu@gnu.org HTTP_HOST lists.gnu.org REQUEST_URI /mailman/confirm/bug-make HTTP_ACCEPT text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 GATEWAY_INTERFACE CGI/1.1 REMOTE_PORT 36922 HTTP_ACCEPT_LANGUAGE fr,en;q=0.5 CONTENT_TYPE application/x-www-form-urlencoded HTTP_ACCEPT_ENCODING gzip,deflate PATH_INFO /bug-make ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1123390&group_id=103 From noreply at sourceforge.net Tue Feb 15 21:28:57 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Feb 15 21:29:00 2005 Subject: [ mailman-Bugs-1123390 ] Bug in mailing list subscription request cancellation Message-ID: Bugs item #1123390, was opened at 2005-02-15 21:26 Message generated for change (Settings changed) made by beuc You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1123390&group_id=103 >Category: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Sylvain BEUCLER (beuc) Assigned to: Nobody/Anonymous (nobody) Summary: Bug in mailing list subscription request cancellation Initial Comment: This was reported by a Savannah user (Darren.Hiebert@sstb.arc.army.mil - can he be added in Cc of this item?), for the lists.gnu.org install: Bug in Mailman version 2.1.5 We're sorry, we hit a bug! If you would like to help us identify the problem, please email a copy of this page to the webmaster for this site with a description of what happened. Thanks! Traceback: Traceback (most recent call last): File "/var/mailman/scripts/driver", line 87, in run_main main() File "/var/mailman/Mailman/Cgi/confirm.py", line 114, in main subscription_cancel(mlist, doc, cookie) File "/var/mailman/Mailman/Cgi/confirm.py", line 312, in subscription_cancel userdesc = mlist.pend_confirm(cookie)[1] File "/var/mailman/Mailman/Pending.py", line 141, in pend_confirm assert self.Locked() AssertionError Python information: Variable Value sys.version 2.3.3 (#1, May 7 2004, 10:31:40) [GCC 3.3.3 20040412 (Red Hat Linux 3.3.3-7)] sys.executable /usr/bin/python sys.prefix /usr sys.exec_prefix /usr sys.path /usr sys.platform linux2 Environment variables: Variable Value HTTP_COOKIE savannah-root+admin=28020000006999581242732800000036386335316237303736666537366461623438353837346561393533313164616161386164653439 SERVER_SOFTWARE Apache/2.0.51 (Fedora) SCRIPT_NAME /mailman/confirm SERVER_SIGNATURE REQUEST_METHOD POST HTTP_KEEP_ALIVE 300 SERVER_PROTOCOL HTTP/1.1 QUERY_STRING CONTENT_LENGTH 131 HTTP_ACCEPT_CHARSET ISO-8859-1,utf-8;q=0.7,*;q=0.7 HTTP_USER_AGENT Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0 HTTP_CONNECTION keep-alive HTTP_REFERER http://lists.gnu.org/mailman/confirm/bug-make/443c45564f830ea03dc4aa276c9da99f69ebd7e6 SERVER_NAME lists.gnu.org REMOTE_ADDR 82.230.99.124 PATH_TRANSLATED /var/www/html/lists.gnu.org/bug-make SERVER_PORT 80 SERVER_ADDR 199.232.76.165 DOCUMENT_ROOT /var/www/html/lists.gnu.org/ PYTHONPATH /var/mailman SCRIPT_FILENAME /var/mailman/cgi-bin/confirm SERVER_ADMIN gnu@gnu.org HTTP_HOST lists.gnu.org REQUEST_URI /mailman/confirm/bug-make HTTP_ACCEPT text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 GATEWAY_INTERFACE CGI/1.1 REMOTE_PORT 36922 HTTP_ACCEPT_LANGUAGE fr,en;q=0.5 CONTENT_TYPE application/x-www-form-urlencoded HTTP_ACCEPT_ENCODING gzip,deflate PATH_INFO /bug-make ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1123390&group_id=103 From noreply at sourceforge.net Tue Feb 15 21:55:50 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Feb 15 21:55:53 2005 Subject: [ mailman-Bugs-1123390 ] Bug in mailing list subscription request cancellation Message-ID: Bugs item #1123390, was opened at 2005-02-15 14:26 Message generated for change (Comment added) made by dhiebert You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1123390&group_id=103 Category: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Sylvain BEUCLER (beuc) Assigned to: Nobody/Anonymous (nobody) Summary: Bug in mailing list subscription request cancellation Initial Comment: This was reported by a Savannah user (Darren.Hiebert@sstb.arc.army.mil - can he be added in Cc of this item?), for the lists.gnu.org install: Bug in Mailman version 2.1.5 We're sorry, we hit a bug! If you would like to help us identify the problem, please email a copy of this page to the webmaster for this site with a description of what happened. Thanks! Traceback: Traceback (most recent call last): File "/var/mailman/scripts/driver", line 87, in run_main main() File "/var/mailman/Mailman/Cgi/confirm.py", line 114, in main subscription_cancel(mlist, doc, cookie) File "/var/mailman/Mailman/Cgi/confirm.py", line 312, in subscription_cancel userdesc = mlist.pend_confirm(cookie)[1] File "/var/mailman/Mailman/Pending.py", line 141, in pend_confirm assert self.Locked() AssertionError Python information: Variable Value sys.version 2.3.3 (#1, May 7 2004, 10:31:40) [GCC 3.3.3 20040412 (Red Hat Linux 3.3.3-7)] sys.executable /usr/bin/python sys.prefix /usr sys.exec_prefix /usr sys.path /usr sys.platform linux2 Environment variables: Variable Value HTTP_COOKIE savannah-root+admin=28020000006999581242732800000036386335316237303736666537366461623438353837346561393533313164616161386164653439 SERVER_SOFTWARE Apache/2.0.51 (Fedora) SCRIPT_NAME /mailman/confirm SERVER_SIGNATURE REQUEST_METHOD POST HTTP_KEEP_ALIVE 300 SERVER_PROTOCOL HTTP/1.1 QUERY_STRING CONTENT_LENGTH 131 HTTP_ACCEPT_CHARSET ISO-8859-1,utf-8;q=0.7,*;q=0.7 HTTP_USER_AGENT Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0 HTTP_CONNECTION keep-alive HTTP_REFERER http://lists.gnu.org/mailman/confirm/bug-make/443c45564f830ea03dc4aa276c9da99f69ebd7e6 SERVER_NAME lists.gnu.org REMOTE_ADDR 82.230.99.124 PATH_TRANSLATED /var/www/html/lists.gnu.org/bug-make SERVER_PORT 80 SERVER_ADDR 199.232.76.165 DOCUMENT_ROOT /var/www/html/lists.gnu.org/ PYTHONPATH /var/mailman SCRIPT_FILENAME /var/mailman/cgi-bin/confirm SERVER_ADMIN gnu@gnu.org HTTP_HOST lists.gnu.org REQUEST_URI /mailman/confirm/bug-make HTTP_ACCEPT text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 GATEWAY_INTERFACE CGI/1.1 REMOTE_PORT 36922 HTTP_ACCEPT_LANGUAGE fr,en;q=0.5 CONTENT_TYPE application/x-www-form-urlencoded HTTP_ACCEPT_ENCODING gzip,deflate PATH_INFO /bug-make ---------------------------------------------------------------------- Comment By: Darren Hiebert (dhiebert) Date: 2005-02-15 14:55 Message: Logged In: YES user_id=38016 Can you PLEASE remove my email address from the text of this bug report. I purposely did not enter it on the form to avoid it appearing in the text of the report. I am desperate that it not be picked up by spam email harvesters. PLEASE remove it. Thank you. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1123390&group_id=103 From noreply at sourceforge.net Wed Feb 16 00:00:22 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Feb 16 00:00:25 2005 Subject: [ mailman-Bugs-1123540 ] can't login to list admin interface Message-ID: Bugs item #1123540, was opened at 2005-02-15 23:00 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=1123540&group_id=103 Category: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Iain Pople (iainpople) Assigned to: Nobody/Anonymous (nobody) Summary: can't login to list admin interface Initial Comment: As of a few days ago I can't login to the administrative interface for any of my lists. This is not browser related (I have tried with several browsers and have checked cookie settings). When i enter a password into the administrative login page the page just reloads. There is no error message displayed. Mailman version is 2.1.5 running on Debian, with Python 2.2.1 I have checked the log files and there are no relevant error messages. Apache shows a log of the POST request: x.x.x.x - - [16/Feb/2005:09:47:57 +1100] "POST /cgi-bin/mailman/admin/soccer-uni HTTP/1.1" 200 2281 I have found that if i manually enter a GET request I can login. e.g. http://host//cgi-bin/mailman/admin/soccer-uni?adminpw=mypassword However when I try and change any of the settings the page just reloads without the changes. So it looks to be like a problem with processing POST requests. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1123540&group_id=103 From noreply at sourceforge.net Wed Feb 16 00:14:49 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Feb 16 00:14:53 2005 Subject: [ mailman-Bugs-1123540 ] can't login to list admin interface Message-ID: Bugs item #1123540, was opened at 2005-02-15 23:00 Message generated for change (Comment added) made by iainpople You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1123540&group_id=103 Category: Web/CGI Group: 2.1 (stable) >Status: Closed Resolution: None Priority: 5 Submitted By: Iain Pople (iainpople) Assigned to: Nobody/Anonymous (nobody) Summary: can't login to list admin interface Initial Comment: As of a few days ago I can't login to the administrative interface for any of my lists. This is not browser related (I have tried with several browsers and have checked cookie settings). When i enter a password into the administrative login page the page just reloads. There is no error message displayed. Mailman version is 2.1.5 running on Debian, with Python 2.2.1 I have checked the log files and there are no relevant error messages. Apache shows a log of the POST request: x.x.x.x - - [16/Feb/2005:09:47:57 +1100] "POST /cgi-bin/mailman/admin/soccer-uni HTTP/1.1" 200 2281 I have found that if i manually enter a GET request I can login. e.g. http://host//cgi-bin/mailman/admin/soccer-uni?adminpw=mypassword However when I try and change any of the settings the page just reloads without the changes. So it looks to be like a problem with processing POST requests. ---------------------------------------------------------------------- >Comment By: Iain Pople (iainpople) Date: 2005-02-15 23:14 Message: Logged In: YES user_id=881670 Restarting apache resolved this issue. sorry :) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1123540&group_id=103 From noreply at sourceforge.net Wed Feb 16 09:15:01 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Feb 16 09:15:05 2005 Subject: [ mailman-Patches-1123383 ] Daily Status Report script... Message-ID: Patches item #1123383, was opened at 2005-02-15 21:14 Message generated for change (Comment added) made by tgc99 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1123383&group_id=103 Category: list administration Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Brad Knowles (shub) Assigned to: Nobody/Anonymous (nobody) Summary: Daily Status Report script... Initial Comment: Folks, I quickly whacked together a Daily Status Report script for Mailman (using Bourne shell, not Python ;), and thought that other folks might be interested in seeing it. The basic concept is a program that gets fired off at 23:59 every night, and goes through a variety of log files looking for entries specific to that date, and indicating problems or certain types of activity that might be of interest to someone trying to administer the server. It also does an "ls -la" of /usr/local/mailman/qfiles/*, so that you can see what is in the queue at the time of the running of the script. My concept was that this daily report would get e-mailed to the admin, or posted to a "reports" mailing list, where they could be archived and kept for future reference. The script does not (yet) do any statistics calculations, although it should be relatively easy to hack together some basic stats using awk, sort, etc.... Anyway, I thought I'd share it and let folks take a look at it, and if anyone has any recommended improvements, we can incorporate those and share them back out with everyone. The code is written under a BSD-style license, so if you don't want to contribute any changes back to me, that's okay. Of course, I would prefer that you did, but I leave the choice up to you. ---------------------------------------------------------------------- Comment By: Tom G. Christensen (tgc99) Date: 2005-02-16 09:15 Message: Logged In: YES user_id=1159458 The current UID grab command doesn't work on Solaris (2.6 & 8 tested). I'd recommend this instead: ps -o user -p $$|tail -1 This is tested and works on RH 6.2, RH 7.3, RHEL 2.1, RHEL3, FC3, FreeBSD 4.9, Solaris 2.6, 8. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1123383&group_id=103 From noreply at sourceforge.net Thu Feb 17 06:19:10 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Feb 17 06:19:12 2005 Subject: [ mailman-Patches-1124510 ] speed up update_pending in bin/update Message-ID: Patches item #1124510, was opened at 2005-02-17 13:19 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=1124510&group_id=103 Category: configure/install Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Pabs (pabs3) Assigned to: Nobody/Anonymous (nobody) Summary: speed up update_pending in bin/update Initial Comment: This patch changes the update script so that loading and saving the per-list pending.pck files is done once per list instead of once per pending request. This results in a significant speedup (seconds per list instead of minutes). ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1124510&group_id=103 From noreply at sourceforge.net Thu Feb 17 06:51:58 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Feb 17 06:52:01 2005 Subject: [ mailman-Patches-1124510 ] speed up update_pending in bin/update Message-ID: Patches item #1124510, was opened at 2005-02-17 13:19 Message generated for change (Comment added) made by pabs3 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1124510&group_id=103 Category: configure/install Group: Mailman 2.1 Status: Open Resolution: None >Priority: 7 Submitted By: Pabs (pabs3) Assigned to: Nobody/Anonymous (nobody) Summary: speed up update_pending in bin/update Initial Comment: This patch changes the update script so that loading and saving the per-list pending.pck files is done once per list instead of once per pending request. This results in a significant speedup (seconds per list instead of minutes). ---------------------------------------------------------------------- >Comment By: Pabs (pabs3) Date: 2005-02-17 13:51 Message: Logged In: YES user_id=35028 This is against 2.1.6b3 by the way. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1124510&group_id=103 From noreply at sourceforge.net Thu Feb 17 21:31:11 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Feb 17 21:31:14 2005 Subject: [ mailman-Bugs-1126206 ] Bounce processing tracebacks Message-ID: Bugs item #1126206, was opened at 2005-02-17 15: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=1126206&group_id=103 Category: bounce detection Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Bryan Fullerton (fehwalker) Assigned to: Nobody/Anonymous (nobody) Summary: Bounce processing tracebacks Initial Comment: Howdy, I was having some issues with bounces previously (some were being held in qfiles/bounces until the Mailman processes were restarted, then all of them would be sent to the list owner as uncaught bounces). I believed these were getting stuck because of the Mailman 2.1.5/python 2.4 "day of year out of range" issue, which I've seen logged and which I know is fixed in 2.1.6, but maybe something else was breaking and not being logged. On upgrade to 2.1.6b4, all of the bounce messages stuck in qfiles/bounce (1488 of them) were moved to qfiles/shunt and the following traceback logged in logs/error for each file: Feb 17 15:12:22 2005 (31261) SHUNTING: 1108670889.8425479+290d640542fcf19f6aef6711b3f9e60e2c419cb2 Feb 17 15:12:22 2005 (31261) Uncaught runner exception: 'str' object has no attribute 'get_sender' Feb 17 15:12:22 2005 (31261) Traceback (most recent call last): File "/usr/local/mailman/Mailman/Queue/Runner.py", line 111, in _oneloop self._onefile(msg, msgdata) File "/usr/local/mailman/Mailman/Queue/Runner.py", line 159, in _onefile sender = msg.get_sender() AttributeError: 'str' object has no attribute 'get_sender' Any idea what could cause this? Is this just an issue with 2.1.5 -> 2.1.6 bounces or qfiles in general? The 'make install' did take a while doing something to my qfiles at the end of the install process. Thanks, Bryan ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1126206&group_id=103 From noreply at sourceforge.net Sun Feb 20 14:01:11 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Sun Feb 20 14:01:14 2005 Subject: [ mailman-Bugs-1144784 ] 2.1.5 crash on date string? Message-ID: Bugs item #1144784, was opened at 2005-02-20 14: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=1144784&group_id=103 Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Auke Kok (sofar) Assigned to: Nobody/Anonymous (nobody) Summary: 2.1.5 crash on date string? Initial Comment: Just got a full error dump on the terminal that I re-started mailman on. Mailman has been repeatedly DYING unexpectedly in the few last days (We switched IP addresses and MX host), which is causing some problems: root@espresso ~ # 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 87, in run self._cleanup() File "/var/mailman/Mailman/Queue/OutgoingRunner.py", line 134, in _cleanup BounceMixin._cleanup(self) File "/var/mailman/Mailman/Queue/BounceRunner.py", line 132, in _cleanup self._register_bounces() File "/var/mailman/Mailman/Queue/BounceRunner.py", line 120, in _register_bounces mlist.registerBounce(addr, msg, day=day) File "/var/mailman/Mailman/Bouncer.py", line 131, in registerBounce time.strftime('%d-%b-%Y', day + (0,)*6)) ValueError: day of year out of range 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 87, in run self._cleanup() File "/var/mailman/Mailman/Queue/BounceRunner.py", line 220, in _cleanup BounceMixin._cleanup(self) File "/var/mailman/Mailman/Queue/BounceRunner.py", line 132, in _cleanup self._register_bounces() File "/var/mailman/Mailman/Queue/BounceRunner.py", line 120, in _register_bounces mlist.registerBounce(addr, msg, day=day) File "/var/mailman/Mailman/Bouncer.py", line 131, in registerBounce time.strftime('%d-%b-%Y', day + (0,)*6)) ValueError: day of year out of range ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1144784&group_id=103 From noreply at sourceforge.net Sun Feb 20 23:11:53 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Sun Feb 20 23:11:55 2005 Subject: [ mailman-Bugs-1051615 ] Tend to pending moderator requests error Message-ID: Bugs item #1051615, was opened at 2004-10-22 05:41 Message generated for change (Comment added) made by plasmadog You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1051615&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: curly (cunoodle2) Assigned to: Nobody/Anonymous (nobody) Summary: Tend to pending moderator requests error Initial Comment: I was logged in to manage my list and clicked on the link that said "Tend to pending moderator requests " and I got an error. Here it is... Bug in Mailman version 2.1.5 We're sorry, we hit a bug! If you would like to help us identify the problem, please email a copy of this page to the webmaster for this site with a description of what happened. Thanks! Traceback: Traceback (most recent call last): File "/usr/local/cpanel/3rdparty/mailman/scripts/driver", line 87, in run_main main() File "/usr/local/cpanel/3rdparty/mailman/Mailman/Cgi/admi ndb.py", line 246, in main print doc.Format() File "/usr/local/cpanel/3rdparty/mailman/Mailman/htmlfor mat.py", line 331, in Format output.append(Container.Format(self, indent)) File "/usr/local/cpanel/3rdparty/mailman/Mailman/htmlfor mat.py", line 264, in Format output.append(HTMLFormatObject(item, indent)) File "/usr/local/cpanel/3rdparty/mailman/Mailman/htmlfor mat.py", line 50, in HTMLFormatObject return item.Format(indent) File "/usr/local/cpanel/3rdparty/mailman/Mailman/htmlfor mat.py", line 417, in Format output = output + Container.Format(self, indent+2) File "/usr/local/cpanel/3rdparty/mailman/Mailman/htmlfor mat.py", line 264, in Format output.append(HTMLFormatObject(item, indent)) File "/usr/local/cpanel/3rdparty/mailman/Mailman/htmlfor mat.py", line 50, in HTMLFormatObject return item.Format(indent) File "/usr/local/cpanel/3rdparty/mailman/Mailman/htmlfor mat.py", line 200, in Format output = output + self.FormatRow(i, indent + 2) MemoryError ------------------------------------------------------ -------------------------- Python information: Variable Value sys.version 2.2.2 (#1, Jan 30 2003, 21:26:22) [GCC 2.96 20000731 (Red Hat Linux 7.3 2.96-112)] sys.executable /usr/bin/python2 sys.prefix /usr sys.exec_prefix /usr sys.path /usr sys.platform linux2 ------------------------------------------------------ -------------------------- Environment variables: Variable Value HTTP_COOKIE cpin_christianparents.com+admin=2802000000699cdd774 17328000000373338303438623638373364366135356262 32663961613331353935623932346338343832323465 SERVER_SOFTWARE Apache/1.3.31 (Unix) mod_auth_passthrough/1.8 mod_log_bytes/1.2 mod_bwlimited/1.4 PHP/4.3.9 FrontPage/5.0.2.2634a mod_ssl/2.8.20 OpenSSL/0.9.6b PYTHONPATH /usr/local/cpanel/3rdparty/mailman SCRIPT_FILENAME /usr/local/cpanel/3rdparty/mailman/c gi-bin/admindb SERVER_ADMIN webmaster@christianparents.com SCRIPT_NAME /mailman/admindb REQUEST_METHOD GET HTTP_HOST christianparents.com PATH_INFO /cpin_christianparents.com SERVER_PROTOCOL HTTP/1.1 QUERY_STRING REQUEST_URI /mailman/admindb/cpin_christianparents.c om HTTP_ACCEPT image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, application/x-shockwave-flash, application/vnd.ms-powerpoint, application/vnd.ms- excel, application/msword, */* HTTP_USER_AGENT Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; NetCaptor 7.5.2; (R1 1.5)) HTTP_CONNECTION Keep-Alive HTTP_REFERER http://christianparents.com/mailman/admin/cpin_christian parents.com/members SERVER_NAME www.christianparents.com REMOTE_ADDR 69.49.193.98 REMOTE_PORT 18495 HTTP_ACCEPT_LANGUAGE en-us PATH_TRANSLATED /home/chris/public_html/cpin_christi anparents.com SERVER_PORT 80 GATEWAY_INTERFACE CGI/1.1 HTTP_ACCEPT_ENCODING gzip, deflate SERVER_ADDR 205.243.144.12 DOCUMENT_ROOT /home/chris/public_html ---------------------------------------------------------------------- Comment By: Tony Peguero (plasmadog) Date: 2005-02-21 11:11 Message: Logged In: YES user_id=231995 I get this same error, also with v2.1.5 In my case, it appears that some messages with very large attachments were sent to the list. The messages were held for moderator approval, but now I can't do anything with them. I can neither approve them for sending, nor discard them. Any attempt to do anything with them, even view their details, is met by the same error. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1051615&group_id=103 From noreply at sourceforge.net Mon Feb 21 01:18:49 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Feb 21 01:18:53 2005 Subject: [ mailman-Bugs-1144784 ] 2.1.5 crash on date string? Message-ID: Bugs item #1144784, was opened at 2005-02-20 13:01 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1144784&group_id=103 Category: mail delivery Group: 2.1 (stable) >Status: Closed >Resolution: Duplicate Priority: 5 Submitted By: Auke Kok (sofar) Assigned to: Nobody/Anonymous (nobody) Summary: 2.1.5 crash on date string? Initial Comment: Just got a full error dump on the terminal that I re-started mailman on. Mailman has been repeatedly DYING unexpectedly in the few last days (We switched IP addresses and MX host), which is causing some problems: root@espresso ~ # 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 87, in run self._cleanup() File "/var/mailman/Mailman/Queue/OutgoingRunner.py", line 134, in _cleanup BounceMixin._cleanup(self) File "/var/mailman/Mailman/Queue/BounceRunner.py", line 132, in _cleanup self._register_bounces() File "/var/mailman/Mailman/Queue/BounceRunner.py", line 120, in _register_bounces mlist.registerBounce(addr, msg, day=day) File "/var/mailman/Mailman/Bouncer.py", line 131, in registerBounce time.strftime('%d-%b-%Y', day + (0,)*6)) ValueError: day of year out of range 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 87, in run self._cleanup() File "/var/mailman/Mailman/Queue/BounceRunner.py", line 220, in _cleanup BounceMixin._cleanup(self) File "/var/mailman/Mailman/Queue/BounceRunner.py", line 132, in _cleanup self._register_bounces() File "/var/mailman/Mailman/Queue/BounceRunner.py", line 120, in _register_bounces mlist.registerBounce(addr, msg, day=day) File "/var/mailman/Mailman/Bouncer.py", line 131, in registerBounce time.strftime('%d-%b-%Y', day + (0,)*6)) ValueError: day of year out of range ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2005-02-21 00:18 Message: Logged In: YES user_id=67709 Your new host installed latest Python 2.4. Mailman 2.1.6 (beta) is fixed for this bug. I recommend you to upgrade mailman to 2.1.6. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1144784&group_id=103 From noreply at sourceforge.net Mon Feb 21 01:25:19 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Feb 21 01:25:21 2005 Subject: [ mailman-Bugs-1126206 ] Bounce processing tracebacks Message-ID: Bugs item #1126206, was opened at 2005-02-17 20:31 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1126206&group_id=103 Category: bounce detection Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Bryan Fullerton (fehwalker) >Assigned to: Tokio Kikuchi (tkikuchi) Summary: Bounce processing tracebacks Initial Comment: Howdy, I was having some issues with bounces previously (some were being held in qfiles/bounces until the Mailman processes were restarted, then all of them would be sent to the list owner as uncaught bounces). I believed these were getting stuck because of the Mailman 2.1.5/python 2.4 "day of year out of range" issue, which I've seen logged and which I know is fixed in 2.1.6, but maybe something else was breaking and not being logged. On upgrade to 2.1.6b4, all of the bounce messages stuck in qfiles/bounce (1488 of them) were moved to qfiles/shunt and the following traceback logged in logs/error for each file: Feb 17 15:12:22 2005 (31261) SHUNTING: 1108670889.8425479+290d640542fcf19f6aef6711b3f9e60e2c419cb2 Feb 17 15:12:22 2005 (31261) Uncaught runner exception: 'str' object has no attribute 'get_sender' Feb 17 15:12:22 2005 (31261) Traceback (most recent call last): File "/usr/local/mailman/Mailman/Queue/Runner.py", line 111, in _oneloop self._onefile(msg, msgdata) File "/usr/local/mailman/Mailman/Queue/Runner.py", line 159, in _onefile sender = msg.get_sender() AttributeError: 'str' object has no attribute 'get_sender' Any idea what could cause this? Is this just an issue with 2.1.5 -> 2.1.6 bounces or qfiles in general? The 'make install' did take a while doing something to my qfiles at the end of the install process. Thanks, Bryan ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2005-02-21 00:25 Message: Logged In: YES user_id=67709 I guess this is one time error when you are upgrading from 2.1.5 to 2.1.6 under Python 2.4. If not, will you please upload or send me a sample bouncing message? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1126206&group_id=103 From noreply at sourceforge.net Mon Feb 21 01:27:27 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Feb 21 01:27:30 2005 Subject: [ mailman-Bugs-1123390 ] Bug in mailing list subscription request cancellation Message-ID: Bugs item #1123390, was opened at 2005-02-15 20:26 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1123390&group_id=103 Category: Web/CGI Group: 2.1 (stable) >Status: Closed >Resolution: Duplicate Priority: 5 Submitted By: Sylvain BEUCLER (beuc) Assigned to: Nobody/Anonymous (nobody) Summary: Bug in mailing list subscription request cancellation Initial Comment: This was reported by a Savannah user (Darren.Hiebert@sstb.arc.army.mil - can he be added in Cc of this item?), for the lists.gnu.org install: Bug in Mailman version 2.1.5 We're sorry, we hit a bug! If you would like to help us identify the problem, please email a copy of this page to the webmaster for this site with a description of what happened. Thanks! Traceback: Traceback (most recent call last): File "/var/mailman/scripts/driver", line 87, in run_main main() File "/var/mailman/Mailman/Cgi/confirm.py", line 114, in main subscription_cancel(mlist, doc, cookie) File "/var/mailman/Mailman/Cgi/confirm.py", line 312, in subscription_cancel userdesc = mlist.pend_confirm(cookie)[1] File "/var/mailman/Mailman/Pending.py", line 141, in pend_confirm assert self.Locked() AssertionError Python information: Variable Value sys.version 2.3.3 (#1, May 7 2004, 10:31:40) [GCC 3.3.3 20040412 (Red Hat Linux 3.3.3-7)] sys.executable /usr/bin/python sys.prefix /usr sys.exec_prefix /usr sys.path /usr sys.platform linux2 Environment variables: Variable Value HTTP_COOKIE savannah-root+admin=28020000006999581242732800000036386335316237303736666537366461623438353837346561393533313164616161386164653439 SERVER_SOFTWARE Apache/2.0.51 (Fedora) SCRIPT_NAME /mailman/confirm SERVER_SIGNATURE REQUEST_METHOD POST HTTP_KEEP_ALIVE 300 SERVER_PROTOCOL HTTP/1.1 QUERY_STRING CONTENT_LENGTH 131 HTTP_ACCEPT_CHARSET ISO-8859-1,utf-8;q=0.7,*;q=0.7 HTTP_USER_AGENT Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0 HTTP_CONNECTION keep-alive HTTP_REFERER http://lists.gnu.org/mailman/confirm/bug-make/443c45564f830ea03dc4aa276c9da99f69ebd7e6 SERVER_NAME lists.gnu.org REMOTE_ADDR 82.230.99.124 PATH_TRANSLATED /var/www/html/lists.gnu.org/bug-make SERVER_PORT 80 SERVER_ADDR 199.232.76.165 DOCUMENT_ROOT /var/www/html/lists.gnu.org/ PYTHONPATH /var/mailman SCRIPT_FILENAME /var/mailman/cgi-bin/confirm SERVER_ADMIN gnu@gnu.org HTTP_HOST lists.gnu.org REQUEST_URI /mailman/confirm/bug-make HTTP_ACCEPT text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 GATEWAY_INTERFACE CGI/1.1 REMOTE_PORT 36922 HTTP_ACCEPT_LANGUAGE fr,en;q=0.5 CONTENT_TYPE application/x-www-form-urlencoded HTTP_ACCEPT_ENCODING gzip,deflate PATH_INFO /bug-make ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2005-02-21 00:27 Message: Logged In: YES user_id=67709 This bug was fixed in 2.1.6 (beta). ---------------------------------------------------------------------- Comment By: Darren Hiebert (dhiebert) Date: 2005-02-15 20:55 Message: Logged In: YES user_id=38016 Can you PLEASE remove my email address from the text of this bug report. I purposely did not enter it on the form to avoid it appearing in the text of the report. I am desperate that it not be picked up by spam email harvesters. PLEASE remove it. Thank you. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1123390&group_id=103 From noreply at sourceforge.net Mon Feb 21 01:43:58 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Feb 21 01:44:00 2005 Subject: [ mailman-Bugs-1122131 ] Can't configure Reply-To: to include Poster *and* List Message-ID: Bugs item #1122131, was opened at 2005-02-14 03:14 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1122131&group_id=103 Category: Web/CGI Group: 2.1 (stable) >Status: Closed >Resolution: Wont Fix Priority: 5 Submitted By: Seth Teller (seth_teller) Assigned to: Nobody/Anonymous (nobody) Summary: Can't configure Reply-To: to include Poster *and* List Initial Comment: Regarding Mailman 2.1.5, in use at MIT CSAIL. I administer a class, and a mailing list "help" to which students in the class can email problem reports. The reports go to the course staff. I would like Mailman to provide the default behavior that the staff's replies go to the list (so the rest of the staff sees them) *and* to the student (so that the student sees the solution!). Yet Mailman does not seem to be able to support this behavior. My choices are to set reply-to to Poster or to List. If I set to Poster, then the default Reply behavior excludes the List. If I set to List, then neither Reply or Reply-All includes the original Poster (i.e., the student). I submit that Mailman should support a third option: Reply-To: Poster *and* List. thanks, seth teller. ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2005-02-21 00:43 Message: Logged In: YES user_id=67709 Read the FAQ entry: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq03.048.htp ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1122131&group_id=103 From noreply at sourceforge.net Mon Feb 21 01:51:01 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Feb 21 01:51:05 2005 Subject: [ mailman-Bugs-1111321 ] cron failures are sent to mailman list Message-ID: Bugs item #1111321, was opened at 2005-01-28 09:47 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1111321&group_id=103 Category: command line scripts Group: 2.1 (stable) >Status: Closed >Resolution: Invalid Priority: 5 Submitted By: Wim Heirman (wheirman) Assigned to: Nobody/Anonymous (nobody) Summary: cron failures are sent to mailman list Initial Comment: When a cronjob fails (e.g. nightly_gzip has a permission problem), the output is sent to mailman@localhost. However, mailman is by default a mailing list (at least it was on my older Debian system, I copied the /var/mailman/lists from there to a new Fedora Core 3 installation). Since root is not on the mailman list, I get "message awaits moderator approval" messages. Shouldn't the error go straight to root? For instance, with a MAILTO=root directive in /etc/cron.d/mailman ? ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2005-02-21 00:51 Message: Logged In: YES user_id=67709 You should change the mailman list privacy policy in admin/privacy/sender that anyone can post to this site list. ie. genric_nonmember_action to "accept." ---------------------------------------------------------------------- Comment By: Brad Knowles (shub) Date: 2005-01-28 10:28 Message: Logged In: YES user_id=18417 This sounds like an OS/distribution-specific issue. I get no such problems with Mailman on FreeBSD (for ntp.isc.org), nor with Mailman on Debian (for python.org). Feel free to try out your suggested change, and if it works, then recommend that to the people at Redhat for inclusion in future versions of their RPM. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1111321&group_id=103 From noreply at sourceforge.net Mon Feb 21 04:52:58 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Feb 21 04:53:00 2005 Subject: [ mailman-Bugs-1123390 ] Bug in mailing list subscription request cancellation Message-ID: Bugs item #1123390, was opened at 2005-02-15 14:26 Message generated for change (Comment added) made by dhiebert You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1123390&group_id=103 Category: Web/CGI Group: 2.1 (stable) Status: Closed Resolution: Duplicate Priority: 5 Submitted By: Sylvain BEUCLER (beuc) Assigned to: Nobody/Anonymous (nobody) Summary: Bug in mailing list subscription request cancellation Initial Comment: This was reported by a Savannah user (Darren.Hiebert@sstb.arc.army.mil - can he be added in Cc of this item?), for the lists.gnu.org install: Bug in Mailman version 2.1.5 We're sorry, we hit a bug! If you would like to help us identify the problem, please email a copy of this page to the webmaster for this site with a description of what happened. Thanks! Traceback: Traceback (most recent call last): File "/var/mailman/scripts/driver", line 87, in run_main main() File "/var/mailman/Mailman/Cgi/confirm.py", line 114, in main subscription_cancel(mlist, doc, cookie) File "/var/mailman/Mailman/Cgi/confirm.py", line 312, in subscription_cancel userdesc = mlist.pend_confirm(cookie)[1] File "/var/mailman/Mailman/Pending.py", line 141, in pend_confirm assert self.Locked() AssertionError Python information: Variable Value sys.version 2.3.3 (#1, May 7 2004, 10:31:40) [GCC 3.3.3 20040412 (Red Hat Linux 3.3.3-7)] sys.executable /usr/bin/python sys.prefix /usr sys.exec_prefix /usr sys.path /usr sys.platform linux2 Environment variables: Variable Value HTTP_COOKIE savannah-root+admin=28020000006999581242732800000036386335316237303736666537366461623438353837346561393533313164616161386164653439 SERVER_SOFTWARE Apache/2.0.51 (Fedora) SCRIPT_NAME /mailman/confirm SERVER_SIGNATURE REQUEST_METHOD POST HTTP_KEEP_ALIVE 300 SERVER_PROTOCOL HTTP/1.1 QUERY_STRING CONTENT_LENGTH 131 HTTP_ACCEPT_CHARSET ISO-8859-1,utf-8;q=0.7,*;q=0.7 HTTP_USER_AGENT Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0 HTTP_CONNECTION keep-alive HTTP_REFERER http://lists.gnu.org/mailman/confirm/bug-make/443c45564f830ea03dc4aa276c9da99f69ebd7e6 SERVER_NAME lists.gnu.org REMOTE_ADDR 82.230.99.124 PATH_TRANSLATED /var/www/html/lists.gnu.org/bug-make SERVER_PORT 80 SERVER_ADDR 199.232.76.165 DOCUMENT_ROOT /var/www/html/lists.gnu.org/ PYTHONPATH /var/mailman SCRIPT_FILENAME /var/mailman/cgi-bin/confirm SERVER_ADMIN gnu@gnu.org HTTP_HOST lists.gnu.org REQUEST_URI /mailman/confirm/bug-make HTTP_ACCEPT text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 GATEWAY_INTERFACE CGI/1.1 REMOTE_PORT 36922 HTTP_ACCEPT_LANGUAGE fr,en;q=0.5 CONTENT_TYPE application/x-www-form-urlencoded HTTP_ACCEPT_ENCODING gzip,deflate PATH_INFO /bug-make ---------------------------------------------------------------------- Comment By: Darren Hiebert (dhiebert) Date: 2005-02-20 21:52 Message: Logged In: YES user_id=38016 I wish to urgently request again that my email address be removed from the text of this bug report. I did not authorize it and it was done against my wishes. I do not want the email address included by the submitter at the top of the report (i.e. the Darren.Hiebert one) to be picked up by spam email harvesters. Please respect my wishes to remove it. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2005-02-20 18:27 Message: Logged In: YES user_id=67709 This bug was fixed in 2.1.6 (beta). ---------------------------------------------------------------------- Comment By: Darren Hiebert (dhiebert) Date: 2005-02-15 14:55 Message: Logged In: YES user_id=38016 Can you PLEASE remove my email address from the text of this bug report. I purposely did not enter it on the form to avoid it appearing in the text of the report. I am desperate that it not be picked up by spam email harvesters. PLEASE remove it. Thank you. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1123390&group_id=103 From noreply at sourceforge.net Mon Feb 21 04:55:54 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Feb 21 04:55:57 2005 Subject: [ mailman-Bugs-1123390 ] Bug in mailing list subscription request cancellation Message-ID: Bugs item #1123390, was opened at 2005-02-15 20:26 Message generated for change (Settings changed) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1123390&group_id=103 Category: Web/CGI Group: 2.1 (stable) >Status: Deleted Resolution: Duplicate Priority: 5 Submitted By: Sylvain BEUCLER (beuc) Assigned to: Nobody/Anonymous (nobody) Summary: Bug in mailing list subscription request cancellation Initial Comment: This was reported by a Savannah user (Darren.Hiebert@sstb.arc.army.mil - can he be added in Cc of this item?), for the lists.gnu.org install: Bug in Mailman version 2.1.5 We're sorry, we hit a bug! If you would like to help us identify the problem, please email a copy of this page to the webmaster for this site with a description of what happened. Thanks! Traceback: Traceback (most recent call last): File "/var/mailman/scripts/driver", line 87, in run_main main() File "/var/mailman/Mailman/Cgi/confirm.py", line 114, in main subscription_cancel(mlist, doc, cookie) File "/var/mailman/Mailman/Cgi/confirm.py", line 312, in subscription_cancel userdesc = mlist.pend_confirm(cookie)[1] File "/var/mailman/Mailman/Pending.py", line 141, in pend_confirm assert self.Locked() AssertionError Python information: Variable Value sys.version 2.3.3 (#1, May 7 2004, 10:31:40) [GCC 3.3.3 20040412 (Red Hat Linux 3.3.3-7)] sys.executable /usr/bin/python sys.prefix /usr sys.exec_prefix /usr sys.path /usr sys.platform linux2 Environment variables: Variable Value HTTP_COOKIE savannah-root+admin=28020000006999581242732800000036386335316237303736666537366461623438353837346561393533313164616161386164653439 SERVER_SOFTWARE Apache/2.0.51 (Fedora) SCRIPT_NAME /mailman/confirm SERVER_SIGNATURE REQUEST_METHOD POST HTTP_KEEP_ALIVE 300 SERVER_PROTOCOL HTTP/1.1 QUERY_STRING CONTENT_LENGTH 131 HTTP_ACCEPT_CHARSET ISO-8859-1,utf-8;q=0.7,*;q=0.7 HTTP_USER_AGENT Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0 HTTP_CONNECTION keep-alive HTTP_REFERER http://lists.gnu.org/mailman/confirm/bug-make/443c45564f830ea03dc4aa276c9da99f69ebd7e6 SERVER_NAME lists.gnu.org REMOTE_ADDR 82.230.99.124 PATH_TRANSLATED /var/www/html/lists.gnu.org/bug-make SERVER_PORT 80 SERVER_ADDR 199.232.76.165 DOCUMENT_ROOT /var/www/html/lists.gnu.org/ PYTHONPATH /var/mailman SCRIPT_FILENAME /var/mailman/cgi-bin/confirm SERVER_ADMIN gnu@gnu.org HTTP_HOST lists.gnu.org REQUEST_URI /mailman/confirm/bug-make HTTP_ACCEPT text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 GATEWAY_INTERFACE CGI/1.1 REMOTE_PORT 36922 HTTP_ACCEPT_LANGUAGE fr,en;q=0.5 CONTENT_TYPE application/x-www-form-urlencoded HTTP_ACCEPT_ENCODING gzip,deflate PATH_INFO /bug-make ---------------------------------------------------------------------- Comment By: Darren Hiebert (dhiebert) Date: 2005-02-21 03:52 Message: Logged In: YES user_id=38016 I wish to urgently request again that my email address be removed from the text of this bug report. I did not authorize it and it was done against my wishes. I do not want the email address included by the submitter at the top of the report (i.e. the Darren.Hiebert one) to be picked up by spam email harvesters. Please respect my wishes to remove it. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2005-02-21 00:27 Message: Logged In: YES user_id=67709 This bug was fixed in 2.1.6 (beta). ---------------------------------------------------------------------- Comment By: Darren Hiebert (dhiebert) Date: 2005-02-15 20:55 Message: Logged In: YES user_id=38016 Can you PLEASE remove my email address from the text of this bug report. I purposely did not enter it on the form to avoid it appearing in the text of the report. I am desperate that it not be picked up by spam email harvesters. PLEASE remove it. Thank you. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1123390&group_id=103 From noreply at sourceforge.net Tue Feb 22 01:49:47 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Feb 22 01:49:50 2005 Subject: [ mailman-Bugs-1145887 ] header_filter_rules/bounce_matching_headers updates error Message-ID: Bugs item #1145887, was opened at 2005-02-21 19:49 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=1145887&group_id=103 Category: Web/CGI Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Bryan Fullerton (fehwalker) Assigned to: Nobody/Anonymous (nobody) Summary: header_filter_rules/bounce_matching_headers updates error Initial Comment: When a list has a bunch of legacy header filters in bounce_matching_headers but nothing in header_filter_rules, updating bounce_matching_headers gives the error: Error: Header filter rules require a pattern. Incomplete filter rules will be ignored. (with Error in RED) This is confusing, because all the legacy filters are (at least in this case) valid. Is this intentional to try to push people into using header_filter_rules? If not, could it be made less Loud of a message? Thanks, Bryan ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1145887&group_id=103 From noreply at sourceforge.net Tue Feb 22 02:02:11 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Feb 22 02:02:15 2005 Subject: [ mailman-Bugs-1126206 ] Bounce processing tracebacks Message-ID: Bugs item #1126206, was opened at 2005-02-17 15:31 Message generated for change (Comment added) made by fehwalker You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1126206&group_id=103 Category: bounce detection Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Bryan Fullerton (fehwalker) Assigned to: Tokio Kikuchi (tkikuchi) Summary: Bounce processing tracebacks Initial Comment: Howdy, I was having some issues with bounces previously (some were being held in qfiles/bounces until the Mailman processes were restarted, then all of them would be sent to the list owner as uncaught bounces). I believed these were getting stuck because of the Mailman 2.1.5/python 2.4 "day of year out of range" issue, which I've seen logged and which I know is fixed in 2.1.6, but maybe something else was breaking and not being logged. On upgrade to 2.1.6b4, all of the bounce messages stuck in qfiles/bounce (1488 of them) were moved to qfiles/shunt and the following traceback logged in logs/error for each file: Feb 17 15:12:22 2005 (31261) SHUNTING: 1108670889.8425479+290d640542fcf19f6aef6711b3f9e60e2c419cb2 Feb 17 15:12:22 2005 (31261) Uncaught runner exception: 'str' object has no attribute 'get_sender' Feb 17 15:12:22 2005 (31261) Traceback (most recent call last): File "/usr/local/mailman/Mailman/Queue/Runner.py", line 111, in _oneloop self._onefile(msg, msgdata) File "/usr/local/mailman/Mailman/Queue/Runner.py", line 159, in _onefile sender = msg.get_sender() AttributeError: 'str' object has no attribute 'get_sender' Any idea what could cause this? Is this just an issue with 2.1.5 -> 2.1.6 bounces or qfiles in general? The 'make install' did take a while doing something to my qfiles at the end of the install process. Thanks, Bryan ---------------------------------------------------------------------- >Comment By: Bryan Fullerton (fehwalker) Date: 2005-02-21 20:02 Message: Logged In: YES user_id=660772 Emailed .pck files directly. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2005-02-20 19:25 Message: Logged In: YES user_id=67709 I guess this is one time error when you are upgrading from 2.1.5 to 2.1.6 under Python 2.4. If not, will you please upload or send me a sample bouncing message? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1126206&group_id=103 From noreply at sourceforge.net Tue Feb 22 05:09:27 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Feb 22 05:09:31 2005 Subject: [ mailman-Bugs-1126206 ] Bounce processing tracebacks Message-ID: Bugs item #1126206, was opened at 2005-02-17 20:31 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1126206&group_id=103 Category: bounce detection Group: 2.1 beta >Status: Closed >Resolution: Postponed Priority: 5 Submitted By: Bryan Fullerton (fehwalker) Assigned to: Tokio Kikuchi (tkikuchi) Summary: Bounce processing tracebacks Initial Comment: Howdy, I was having some issues with bounces previously (some were being held in qfiles/bounces until the Mailman processes were restarted, then all of them would be sent to the list owner as uncaught bounces). I believed these were getting stuck because of the Mailman 2.1.5/python 2.4 "day of year out of range" issue, which I've seen logged and which I know is fixed in 2.1.6, but maybe something else was breaking and not being logged. On upgrade to 2.1.6b4, all of the bounce messages stuck in qfiles/bounce (1488 of them) were moved to qfiles/shunt and the following traceback logged in logs/error for each file: Feb 17 15:12:22 2005 (31261) SHUNTING: 1108670889.8425479+290d640542fcf19f6aef6711b3f9e60e2c419cb2 Feb 17 15:12:22 2005 (31261) Uncaught runner exception: 'str' object has no attribute 'get_sender' Feb 17 15:12:22 2005 (31261) Traceback (most recent call last): File "/usr/local/mailman/Mailman/Queue/Runner.py", line 111, in _oneloop self._onefile(msg, msgdata) File "/usr/local/mailman/Mailman/Queue/Runner.py", line 159, in _onefile sender = msg.get_sender() AttributeError: 'str' object has no attribute 'get_sender' Any idea what could cause this? Is this just an issue with 2.1.5 -> 2.1.6 bounces or qfiles in general? The 'make install' did take a while doing something to my qfiles at the end of the install process. Thanks, Bryan ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2005-02-22 04:09 Message: Logged In: YES user_id=67709 Thank you for sending me the pck files. These files do create your error but I also tried to reproduce the situation without positive results. The error caused by mailman2.1.5/Python2.4 combination leaves unprocessed message in data directory and it is never processed again because BounceRunner exits with error and new BounceRuuner looks only for its PID marked pck file. You don't have to re-process these error bounce messages because they are stale after a few days (bounce score is incremented only once a day). And, you will get more bounce messages to process if the list is active. I've already done install and de-install 2.1.5/2.1.6b4 three times for tesing and think it's beyond the duty of an open source developer. I mark this entry as 'postponed' (until a few more similar reports emerge) and close this case. I do believe you lose nothing if you simply remove qfile/shunt/*. ---------------------------------------------------------------------- Comment By: Bryan Fullerton (fehwalker) Date: 2005-02-22 01:02 Message: Logged In: YES user_id=660772 Emailed .pck files directly. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2005-02-21 00:25 Message: Logged In: YES user_id=67709 I guess this is one time error when you are upgrading from 2.1.5 to 2.1.6 under Python 2.4. If not, will you please upload or send me a sample bouncing message? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1126206&group_id=103 From noreply at sourceforge.net Tue Feb 22 05:24:13 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Feb 22 05:24:17 2005 Subject: [ mailman-Bugs-1126206 ] Bounce processing tracebacks Message-ID: Bugs item #1126206, was opened at 2005-02-17 15:31 Message generated for change (Comment added) made by fehwalker You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1126206&group_id=103 Category: bounce detection Group: 2.1 beta Status: Closed Resolution: Postponed Priority: 5 Submitted By: Bryan Fullerton (fehwalker) Assigned to: Tokio Kikuchi (tkikuchi) Summary: Bounce processing tracebacks Initial Comment: Howdy, I was having some issues with bounces previously (some were being held in qfiles/bounces until the Mailman processes were restarted, then all of them would be sent to the list owner as uncaught bounces). I believed these were getting stuck because of the Mailman 2.1.5/python 2.4 "day of year out of range" issue, which I've seen logged and which I know is fixed in 2.1.6, but maybe something else was breaking and not being logged. On upgrade to 2.1.6b4, all of the bounce messages stuck in qfiles/bounce (1488 of them) were moved to qfiles/shunt and the following traceback logged in logs/error for each file: Feb 17 15:12:22 2005 (31261) SHUNTING: 1108670889.8425479+290d640542fcf19f6aef6711b3f9e60e2c419cb2 Feb 17 15:12:22 2005 (31261) Uncaught runner exception: 'str' object has no attribute 'get_sender' Feb 17 15:12:22 2005 (31261) Traceback (most recent call last): File "/usr/local/mailman/Mailman/Queue/Runner.py", line 111, in _oneloop self._onefile(msg, msgdata) File "/usr/local/mailman/Mailman/Queue/Runner.py", line 159, in _onefile sender = msg.get_sender() AttributeError: 'str' object has no attribute 'get_sender' Any idea what could cause this? Is this just an issue with 2.1.5 -> 2.1.6 bounces or qfiles in general? The 'make install' did take a while doing something to my qfiles at the end of the install process. Thanks, Bryan ---------------------------------------------------------------------- >Comment By: Bryan Fullerton (fehwalker) Date: 2005-02-21 23:24 Message: Logged In: YES user_id=660772 Ok, thanks for taking the time to look into it. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2005-02-21 23:09 Message: Logged In: YES user_id=67709 Thank you for sending me the pck files. These files do create your error but I also tried to reproduce the situation without positive results. The error caused by mailman2.1.5/Python2.4 combination leaves unprocessed message in data directory and it is never processed again because BounceRunner exits with error and new BounceRuuner looks only for its PID marked pck file. You don't have to re-process these error bounce messages because they are stale after a few days (bounce score is incremented only once a day). And, you will get more bounce messages to process if the list is active. I've already done install and de-install 2.1.5/2.1.6b4 three times for tesing and think it's beyond the duty of an open source developer. I mark this entry as 'postponed' (until a few more similar reports emerge) and close this case. I do believe you lose nothing if you simply remove qfile/shunt/*. ---------------------------------------------------------------------- Comment By: Bryan Fullerton (fehwalker) Date: 2005-02-21 20:02 Message: Logged In: YES user_id=660772 Emailed .pck files directly. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2005-02-20 19:25 Message: Logged In: YES user_id=67709 I guess this is one time error when you are upgrading from 2.1.5 to 2.1.6 under Python 2.4. If not, will you please upload or send me a sample bouncing message? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1126206&group_id=103 From noreply at sourceforge.net Tue Feb 22 16:22:19 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Feb 22 16:22:22 2005 Subject: [ mailman-Patches-1123383 ] Daily Status Report script... Message-ID: Patches item #1123383, was opened at 2005-02-15 15:14 Message generated for change (Comment added) made by adrianwi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1123383&group_id=103 Category: list administration Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Brad Knowles (shub) Assigned to: Nobody/Anonymous (nobody) Summary: Daily Status Report script... Initial Comment: Folks, I quickly whacked together a Daily Status Report script for Mailman (using Bourne shell, not Python ;), and thought that other folks might be interested in seeing it. The basic concept is a program that gets fired off at 23:59 every night, and goes through a variety of log files looking for entries specific to that date, and indicating problems or certain types of activity that might be of interest to someone trying to administer the server. It also does an "ls -la" of /usr/local/mailman/qfiles/*, so that you can see what is in the queue at the time of the running of the script. My concept was that this daily report would get e-mailed to the admin, or posted to a "reports" mailing list, where they could be archived and kept for future reference. The script does not (yet) do any statistics calculations, although it should be relatively easy to hack together some basic stats using awk, sort, etc.... Anyway, I thought I'd share it and let folks take a look at it, and if anyone has any recommended improvements, we can incorporate those and share them back out with everyone. The code is written under a BSD-style license, so if you don't want to contribute any changes back to me, that's okay. Of course, I would prefer that you did, but I leave the choice up to you. ---------------------------------------------------------------------- Comment By: adrianwi (adrianwi) Date: 2005-02-22 10:22 Message: Logged In: YES user_id=1175103 Use of variable named UID does work well with OS X (version 10.2.8). Apparently the variable UID is a constant already in use. When trying to the run the script without modification, I was receiving the following error message: UID: readonly variable This issue was resolved by changing the name of variable, UID, to something else, such as MMUID. Works fine with this change. As an aside (& for what it is worth), the UID grab command suggested by tgc99 on 2005-02-16 03:15 works on this system (OS X - version 10.2.8) ---------------------------------------------------------------------- Comment By: Tom G. Christensen (tgc99) Date: 2005-02-16 03:15 Message: Logged In: YES user_id=1159458 The current UID grab command doesn't work on Solaris (2.6 & 8 tested). I'd recommend this instead: ps -o user -p $$|tail -1 This is tested and works on RH 6.2, RH 7.3, RHEL 2.1, RHEL3, FC3, FreeBSD 4.9, Solaris 2.6, 8. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1123383&group_id=103 From noreply at sourceforge.net Tue Feb 22 21:10:31 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Feb 22 21:10:36 2005 Subject: [ mailman-Patches-1123383 ] Daily Status Report script... Message-ID: Patches item #1123383, was opened at 2005-02-15 20:14 Message generated for change (Comment added) made by shub You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1123383&group_id=103 Category: list administration Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Brad Knowles (shub) Assigned to: Nobody/Anonymous (nobody) Summary: Daily Status Report script... Initial Comment: Folks, I quickly whacked together a Daily Status Report script for Mailman (using Bourne shell, not Python ;), and thought that other folks might be interested in seeing it. The basic concept is a program that gets fired off at 23:59 every night, and goes through a variety of log files looking for entries specific to that date, and indicating problems or certain types of activity that might be of interest to someone trying to administer the server. It also does an "ls -la" of /usr/local/mailman/qfiles/*, so that you can see what is in the queue at the time of the running of the script. My concept was that this daily report would get e-mailed to the admin, or posted to a "reports" mailing list, where they could be archived and kept for future reference. The script does not (yet) do any statistics calculations, although it should be relatively easy to hack together some basic stats using awk, sort, etc.... Anyway, I thought I'd share it and let folks take a look at it, and if anyone has any recommended improvements, we can incorporate those and share them back out with everyone. The code is written under a BSD-style license, so if you don't want to contribute any changes back to me, that's okay. Of course, I would prefer that you did, but I leave the choice up to you. ---------------------------------------------------------------------- >Comment By: Brad Knowles (shub) Date: 2005-02-22 20:10 Message: Logged In: YES user_id=18417 The UID variable in the current code was already replaced by MYUID, because I got complaints on other platforms. But UID wasn't available to me as a useful constant, so I had to use something else to obtain the value. The recommended patch from tgc99 does work, and I will be uploading a new version of the code soon. ---------------------------------------------------------------------- Comment By: adrianwi (adrianwi) Date: 2005-02-22 15:22 Message: Logged In: YES user_id=1175103 Use of variable named UID does work well with OS X (version 10.2.8). Apparently the variable UID is a constant already in use. When trying to the run the script without modification, I was receiving the following error message: UID: readonly variable This issue was resolved by changing the name of variable, UID, to something else, such as MMUID. Works fine with this change. As an aside (& for what it is worth), the UID grab command suggested by tgc99 on 2005-02-16 03:15 works on this system (OS X - version 10.2.8) ---------------------------------------------------------------------- Comment By: Tom G. Christensen (tgc99) Date: 2005-02-16 08:15 Message: Logged In: YES user_id=1159458 The current UID grab command doesn't work on Solaris (2.6 & 8 tested). I'd recommend this instead: ps -o user -p $$|tail -1 This is tested and works on RH 6.2, RH 7.3, RHEL 2.1, RHEL3, FC3, FreeBSD 4.9, Solaris 2.6, 8. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1123383&group_id=103 From noreply at sourceforge.net Wed Feb 23 00:24:04 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Feb 23 00:24:08 2005 Subject: [ mailman-Bugs-1145887 ] header_filter_rules/bounce_matching_headers updates error Message-ID: Bugs item #1145887, was opened at 2005-02-21 19:49 Message generated for change (Comment added) made by fehwalker You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1145887&group_id=103 Category: Web/CGI Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Bryan Fullerton (fehwalker) Assigned to: Nobody/Anonymous (nobody) Summary: header_filter_rules/bounce_matching_headers updates error Initial Comment: When a list has a bunch of legacy header filters in bounce_matching_headers but nothing in header_filter_rules, updating bounce_matching_headers gives the error: Error: Header filter rules require a pattern. Incomplete filter rules will be ignored. (with Error in RED) This is confusing, because all the legacy filters are (at least in this case) valid. Is this intentional to try to push people into using header_filter_rules? If not, could it be made less Loud of a message? Thanks, Bryan ---------------------------------------------------------------------- >Comment By: Bryan Fullerton (fehwalker) Date: 2005-02-22 18:24 Message: Logged In: YES user_id=660772 D'oh, forgot - this is in 2.1.6b4, and was not the case in 2.1.5. Thanks, Bryan ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1145887&group_id=103 From noreply at sourceforge.net Wed Feb 23 01:08:54 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Feb 23 01:08:56 2005 Subject: [ mailman-Bugs-1145887 ] header_filter_rules/bounce_matching_headers updates error Message-ID: Bugs item #1145887, was opened at 2005-02-22 00:49 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1145887&group_id=103 Category: Web/CGI Group: 2.1 beta >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Bryan Fullerton (fehwalker) Assigned to: Nobody/Anonymous (nobody) Summary: header_filter_rules/bounce_matching_headers updates error Initial Comment: When a list has a bunch of legacy header filters in bounce_matching_headers but nothing in header_filter_rules, updating bounce_matching_headers gives the error: Error: Header filter rules require a pattern. Incomplete filter rules will be ignored. (with Error in RED) This is confusing, because all the legacy filters are (at least in this case) valid. Is this intentional to try to push people into using header_filter_rules? If not, could it be made less Loud of a message? Thanks, Bryan ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2005-02-23 00:08 Message: Logged In: YES user_id=67709 Thank you for the report. This bug was fixed in CVS. It should be more convenient if you move to the new filter though. ---------------------------------------------------------------------- Comment By: Bryan Fullerton (fehwalker) Date: 2005-02-22 23:24 Message: Logged In: YES user_id=660772 D'oh, forgot - this is in 2.1.6b4, and was not the case in 2.1.5. Thanks, Bryan ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1145887&group_id=103 From noreply at sourceforge.net Wed Feb 23 12:53:31 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Feb 23 12:53:34 2005 Subject: [ mailman-Patches-1149753 ] Optionally hide admin addresses Message-ID: Patches item #1149753, was opened at 2005-02-23 19: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=1149753&group_id=103 Category: Web UI Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: pabs (pabs3) Assigned to: Nobody/Anonymous (nobody) Summary: Optionally hide admin addresses Initial Comment: A dpatch to allow the admins to hide their email addresses from the web. Will need to be modified to apply to upstream mailman. See also: https://sf.net/tracker/?func=detail&aid=1020672&group_id=103&atid=300103 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1149753&group_id=103 From noreply at sourceforge.net Wed Feb 23 12:54:36 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Feb 23 12:54:39 2005 Subject: [ mailman-Patches-1020672 ] Prevent display of owner e-mail Message-ID: Patches item #1020672, was opened at 2004-09-02 03:22 Message generated for change (Comment added) made by pabs3 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1020672&group_id=103 Category: Web UI Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Joe Rhett (jrhett) Assigned to: Nobody/Anonymous (nobody) Summary: Prevent display of owner e-mail Initial Comment: Don't display the owner's e-mail address to the user. Instead display the listname-owner link. I'm surprised that this isn't a configuration option. A better patch would be to make a configuration option on a per-list basis and if() this. ---------------------------------------------------------------------- Comment By: pabs (pabs3) Date: 2005-02-23 19:54 Message: Logged In: YES user_id=35028 A per-list version of this patch is here: http://sf.net/tracker/?func=detail&aid=1149753&group_id=103&atid=300103 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1020672&group_id=103 From noreply at sourceforge.net Thu Feb 24 01:35:04 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Feb 24 01:35:09 2005 Subject: [ mailman-Bugs-1077587 ] Memory Leak in Bounce Runner Message-ID: Bugs item #1077587, was opened at 2004-12-02 09:02 Message generated for change (Comment added) made by prubin You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1077587&group_id=103 Category: bounce detection Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Paul Rubin (prubin) Assigned to: Nobody/Anonymous (nobody) Summary: Memory Leak in Bounce Runner Initial Comment: Something is going bady wrong with the BouceRunner It is leaking memory. After it runs for a short time it has consumed hundreds of megabytes of memory. I kill it with -9 and it restarts and is fine for another couple of hours. Sometimes it does not restart and I have to stop and restart the mailman service. This is running on a Linux box with Redhat 9 and postfix 2.1.1 and mailman 2.1.5 and python 2.2.2 Below you will se a PS from right before I killed the process and below that one from a few seconds later. If you will tell me what you need I would really like to get to the bottom of this, I am killing the process like 10 times per day. If it eats too much memory before I catch it then the entire system fails. [root@tbnonline ~]# ps -U mailman -o pid,%cpu,% mem,stime,time,vsz,args PID %CPU %MEM STIME TIME VSZ COMMAND 12949 0.0 0.0 08:05 00:00:00 7068 /usr/bin/python /var/mailman/bin/mailmanctl -s -q start 12950 0.1 0.3 08:05 00:00:02 11176 /usr/bin/python /var/mailman/bin/qrunner -- runner=ArchRunner:0:1 -s 12951 18.9 70.8 08:05 00:08:40 931312 /usr/bin/python /var/mailman/bin/qrunner -- runner=BounceRunner:0:1 -s 12952 0.0 0.0 08:05 00:00:00 7040 /usr/bin/python /var/mailman/bin/qrunner -- runner=CommandRunner:0:1 -s 12953 0.0 0.1 08:05 00:00:00 9256 /usr/bin/python /var/mailman/bin/qrunner -- runner=IncomingRunner:0:1 -s 12954 0.0 0.1 08:05 00:00:00 7080 /usr/bin/python /var/mailman/bin/qrunner -- runner=NewsRunner:0:1 -s 12955 2.5 0.6 08:05 00:01:11 14172 /usr/bin/python /var/mailman/bin/qrunner -- runner=OutgoingRunner:0:1 -s 12956 0.8 0.2 08:05 00:00:24 10628 /usr/bin/python /var/mailman/bin/qrunner -- runner=VirginRunner:0:1 -s 12957 0.1 0.2 08:05 00:00:04 13272 /usr/bin/python /var/mailman/bin/qrunner -- runner=RetryRunner:0:1 -s [root@tbnonline ~]# ps -U mailman -o pid,%cpu,% mem,stime,time,vsz,args PID %CPU %MEM STIME TIME VSZ COMMAND 12949 0.0 0.1 08:05 00:00:00 7072 /usr/bin/python /var/mailman/bin/mailmanctl -s -q start 12950 0.0 0.3 08:05 00:00:02 11176 /usr/bin/python /var/mailman/bin/qrunner -- runner=ArchRunner:0:1 -s 12952 0.0 0.0 08:05 00:00:00 7040 /usr/bin/python /var/mailman/bin/qrunner -- runner=CommandRunner:0:1 -s 12953 0.0 0.2 08:05 00:00:00 9256 /usr/bin/python /var/mailman/bin/qrunner -- runner=IncomingRunner:0:1 -s 12954 0.0 0.1 08:05 00:00:00 7080 /usr/bin/python /var/mailman/bin/qrunner -- runner=NewsRunner:0:1 -s 12955 3.0 0.9 08:05 00:01:43 13584 /usr/bin/python /var/mailman/bin/qrunner -- runner=OutgoingRunner:0:1 -s 12956 1.2 0.6 08:05 00:00:41 10848 /usr/bin/python /var/mailman/bin/qrunner -- runner=VirginRunner:0:1 -s 12957 0.1 0.6 08:05 00:00:06 13284 /usr/bin/python /var/mailman/bin/qrunner -- runner=RetryRunner:0:1 -s 14900 29.8 1.1 08:51 00:02:47 13764 /usr/bin/python /var/mailman/bin/qrunner -- runner=BounceRunner:0:1 -s ---------------------------------------------------------------------- >Comment By: Paul Rubin (prubin) Date: 2005-02-23 19:35 Message: Logged In: YES user_id=91557 Today we ran out of disk space, I have had to kill the bounce processor about 8 or nine times today... I found my diskspace problem: -rw-rw-rw- 1 mailman mailman 1.4G Feb 23 08:48 bounce-events-07208.pck -rw-rw-rw- 1 mailman mailman 931M Feb 23 09:50 bounce-events-08307.pck -rw-rw-rw- 1 mailman mailman 1.1G Feb 23 10:10 bounce-events-09037.pck -rw-rw-rw- 1 mailman mailman 1.4G Feb 23 10:29 bounce-events-10251.pck -rw-rw-rw- 1 mailman mailman 1.6G Feb 23 13:02 bounce-events-14874.pck -rw-rw-rw- 1 mailman mailman 1.4G Feb 23 14:17 bounce-events-17525.pck -rw-rw-rw- 1 mailman mailman 1.6G Feb 23 14:40 bounce-events-18973.pck -rw-rw-rw- 1 mailman mailman 1.6G Feb 23 15:02 bounce-events-19879.pck -rw-rw-rw- 1 mailman mailman 1.5G Feb 23 15:23 bounce-events-20584.pck And about 100 more file from other days. I have saved these file, and deleted the rest, does this or can these files tell you anything about what is going wrong? ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2004-12-16 20:29 Message: Logged In: YES user_id=67709 I suggest stop automatic processing of bounces by setting bounce_processing variable to 'No' at the admin/bounce page. Looks like your server is very busy and unsubscribing process due to the bounce score may interfering. You may also have to unsubscribe the problematic members manually. ---------------------------------------------------------------------- Comment By: Paul Rubin (prubin) Date: 2004-12-15 12:29 Message: Logged In: YES user_id=91557 I do not have a specific number of bounces per day. We send around 500,000 message per day with peak days around 1,000,000, we know that we have some bad addresses, but at any given time there should not be more than 5,000 bounce notices per day (full mailboxes are common) As far as I can tell only certain bounce notices cause the leak. We can go hours or days with memory being almost flat, then suddenly 200M vanishes in 2 or 3 minutes. Is there any way I could 'hack' the code to somehow grab the information about what bounce notice is causing the problem. Or to capture all bounce notices in some outof the way space that I could tar up an send to you for testing. If nothing else I could edit the aliases to copy all of the messages to a file and zip it down for you after a few days. Does any of this make any sense? ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2004-12-14 19:19 Message: Logged In: YES user_id=67709 My FreeBSD4.7/Solaris8 installations have no such problems. How many bounces you get on this system? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1077587&group_id=103 From noreply at sourceforge.net Thu Feb 24 02:22:33 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Feb 24 02:22:35 2005 Subject: [ mailman-Bugs-1077587 ] Memory Leak in Bounce Runner Message-ID: Bugs item #1077587, was opened at 2004-12-02 09:02 Message generated for change (Comment added) made by prubin You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1077587&group_id=103 Category: bounce detection Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Paul Rubin (prubin) Assigned to: Nobody/Anonymous (nobody) Summary: Memory Leak in Bounce Runner Initial Comment: Something is going bady wrong with the BouceRunner It is leaking memory. After it runs for a short time it has consumed hundreds of megabytes of memory. I kill it with -9 and it restarts and is fine for another couple of hours. Sometimes it does not restart and I have to stop and restart the mailman service. This is running on a Linux box with Redhat 9 and postfix 2.1.1 and mailman 2.1.5 and python 2.2.2 Below you will se a PS from right before I killed the process and below that one from a few seconds later. If you will tell me what you need I would really like to get to the bottom of this, I am killing the process like 10 times per day. If it eats too much memory before I catch it then the entire system fails. [root@tbnonline ~]# ps -U mailman -o pid,%cpu,% mem,stime,time,vsz,args PID %CPU %MEM STIME TIME VSZ COMMAND 12949 0.0 0.0 08:05 00:00:00 7068 /usr/bin/python /var/mailman/bin/mailmanctl -s -q start 12950 0.1 0.3 08:05 00:00:02 11176 /usr/bin/python /var/mailman/bin/qrunner -- runner=ArchRunner:0:1 -s 12951 18.9 70.8 08:05 00:08:40 931312 /usr/bin/python /var/mailman/bin/qrunner -- runner=BounceRunner:0:1 -s 12952 0.0 0.0 08:05 00:00:00 7040 /usr/bin/python /var/mailman/bin/qrunner -- runner=CommandRunner:0:1 -s 12953 0.0 0.1 08:05 00:00:00 9256 /usr/bin/python /var/mailman/bin/qrunner -- runner=IncomingRunner:0:1 -s 12954 0.0 0.1 08:05 00:00:00 7080 /usr/bin/python /var/mailman/bin/qrunner -- runner=NewsRunner:0:1 -s 12955 2.5 0.6 08:05 00:01:11 14172 /usr/bin/python /var/mailman/bin/qrunner -- runner=OutgoingRunner:0:1 -s 12956 0.8 0.2 08:05 00:00:24 10628 /usr/bin/python /var/mailman/bin/qrunner -- runner=VirginRunner:0:1 -s 12957 0.1 0.2 08:05 00:00:04 13272 /usr/bin/python /var/mailman/bin/qrunner -- runner=RetryRunner:0:1 -s [root@tbnonline ~]# ps -U mailman -o pid,%cpu,% mem,stime,time,vsz,args PID %CPU %MEM STIME TIME VSZ COMMAND 12949 0.0 0.1 08:05 00:00:00 7072 /usr/bin/python /var/mailman/bin/mailmanctl -s -q start 12950 0.0 0.3 08:05 00:00:02 11176 /usr/bin/python /var/mailman/bin/qrunner -- runner=ArchRunner:0:1 -s 12952 0.0 0.0 08:05 00:00:00 7040 /usr/bin/python /var/mailman/bin/qrunner -- runner=CommandRunner:0:1 -s 12953 0.0 0.2 08:05 00:00:00 9256 /usr/bin/python /var/mailman/bin/qrunner -- runner=IncomingRunner:0:1 -s 12954 0.0 0.1 08:05 00:00:00 7080 /usr/bin/python /var/mailman/bin/qrunner -- runner=NewsRunner:0:1 -s 12955 3.0 0.9 08:05 00:01:43 13584 /usr/bin/python /var/mailman/bin/qrunner -- runner=OutgoingRunner:0:1 -s 12956 1.2 0.6 08:05 00:00:41 10848 /usr/bin/python /var/mailman/bin/qrunner -- runner=VirginRunner:0:1 -s 12957 0.1 0.6 08:05 00:00:06 13284 /usr/bin/python /var/mailman/bin/qrunner -- runner=RetryRunner:0:1 -s 14900 29.8 1.1 08:51 00:02:47 13764 /usr/bin/python /var/mailman/bin/qrunner -- runner=BounceRunner:0:1 -s ---------------------------------------------------------------------- >Comment By: Paul Rubin (prubin) Date: 2005-02-23 20:22 Message: Logged In: YES user_id=91557 One additional piece, the bounce processor sits at a small amount of memory until the file with matching pid hits 1.5GB or so and then starts climbing fast. If I kill the bounce processor, the file is abandoned., If I stop the mailman service, the bounce processor keeps running and eating memory. If allowed to run unchecked, it will just eat all the memory in the system. I cannot kill the bounce process without another starting, even after stopping the mailman service. If I freshly re-boot the server and let mailman run for a few minutes, the the file grows, when I stop the service the file shrinks back to 0 bytes, but does not get deleted. I hope this helps. ---------------------------------------------------------------------- Comment By: Paul Rubin (prubin) Date: 2005-02-23 19:35 Message: Logged In: YES user_id=91557 Today we ran out of disk space, I have had to kill the bounce processor about 8 or nine times today... I found my diskspace problem: -rw-rw-rw- 1 mailman mailman 1.4G Feb 23 08:48 bounce-events-07208.pck -rw-rw-rw- 1 mailman mailman 931M Feb 23 09:50 bounce-events-08307.pck -rw-rw-rw- 1 mailman mailman 1.1G Feb 23 10:10 bounce-events-09037.pck -rw-rw-rw- 1 mailman mailman 1.4G Feb 23 10:29 bounce-events-10251.pck -rw-rw-rw- 1 mailman mailman 1.6G Feb 23 13:02 bounce-events-14874.pck -rw-rw-rw- 1 mailman mailman 1.4G Feb 23 14:17 bounce-events-17525.pck -rw-rw-rw- 1 mailman mailman 1.6G Feb 23 14:40 bounce-events-18973.pck -rw-rw-rw- 1 mailman mailman 1.6G Feb 23 15:02 bounce-events-19879.pck -rw-rw-rw- 1 mailman mailman 1.5G Feb 23 15:23 bounce-events-20584.pck And about 100 more file from other days. I have saved these file, and deleted the rest, does this or can these files tell you anything about what is going wrong? ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2004-12-16 20:29 Message: Logged In: YES user_id=67709 I suggest stop automatic processing of bounces by setting bounce_processing variable to 'No' at the admin/bounce page. Looks like your server is very busy and unsubscribing process due to the bounce score may interfering. You may also have to unsubscribe the problematic members manually. ---------------------------------------------------------------------- Comment By: Paul Rubin (prubin) Date: 2004-12-15 12:29 Message: Logged In: YES user_id=91557 I do not have a specific number of bounces per day. We send around 500,000 message per day with peak days around 1,000,000, we know that we have some bad addresses, but at any given time there should not be more than 5,000 bounce notices per day (full mailboxes are common) As far as I can tell only certain bounce notices cause the leak. We can go hours or days with memory being almost flat, then suddenly 200M vanishes in 2 or 3 minutes. Is there any way I could 'hack' the code to somehow grab the information about what bounce notice is causing the problem. Or to capture all bounce notices in some outof the way space that I could tar up an send to you for testing. If nothing else I could edit the aliases to copy all of the messages to a file and zip it down for you after a few days. Does any of this make any sense? ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2004-12-14 19:19 Message: Logged In: YES user_id=67709 My FreeBSD4.7/Solaris8 installations have no such problems. How many bounces you get on this system? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1077587&group_id=103 From noreply at sourceforge.net Thu Feb 24 02:46:21 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Feb 24 02:46:24 2005 Subject: [ mailman-Bugs-1077587 ] Memory Leak in Bounce Runner Message-ID: Bugs item #1077587, was opened at 2004-12-02 14:02 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1077587&group_id=103 Category: bounce detection Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Paul Rubin (prubin) Assigned to: Nobody/Anonymous (nobody) Summary: Memory Leak in Bounce Runner Initial Comment: Something is going bady wrong with the BouceRunner It is leaking memory. After it runs for a short time it has consumed hundreds of megabytes of memory. I kill it with -9 and it restarts and is fine for another couple of hours. Sometimes it does not restart and I have to stop and restart the mailman service. This is running on a Linux box with Redhat 9 and postfix 2.1.1 and mailman 2.1.5 and python 2.2.2 Below you will se a PS from right before I killed the process and below that one from a few seconds later. If you will tell me what you need I would really like to get to the bottom of this, I am killing the process like 10 times per day. If it eats too much memory before I catch it then the entire system fails. [root@tbnonline ~]# ps -U mailman -o pid,%cpu,% mem,stime,time,vsz,args PID %CPU %MEM STIME TIME VSZ COMMAND 12949 0.0 0.0 08:05 00:00:00 7068 /usr/bin/python /var/mailman/bin/mailmanctl -s -q start 12950 0.1 0.3 08:05 00:00:02 11176 /usr/bin/python /var/mailman/bin/qrunner -- runner=ArchRunner:0:1 -s 12951 18.9 70.8 08:05 00:08:40 931312 /usr/bin/python /var/mailman/bin/qrunner -- runner=BounceRunner:0:1 -s 12952 0.0 0.0 08:05 00:00:00 7040 /usr/bin/python /var/mailman/bin/qrunner -- runner=CommandRunner:0:1 -s 12953 0.0 0.1 08:05 00:00:00 9256 /usr/bin/python /var/mailman/bin/qrunner -- runner=IncomingRunner:0:1 -s 12954 0.0 0.1 08:05 00:00:00 7080 /usr/bin/python /var/mailman/bin/qrunner -- runner=NewsRunner:0:1 -s 12955 2.5 0.6 08:05 00:01:11 14172 /usr/bin/python /var/mailman/bin/qrunner -- runner=OutgoingRunner:0:1 -s 12956 0.8 0.2 08:05 00:00:24 10628 /usr/bin/python /var/mailman/bin/qrunner -- runner=VirginRunner:0:1 -s 12957 0.1 0.2 08:05 00:00:04 13272 /usr/bin/python /var/mailman/bin/qrunner -- runner=RetryRunner:0:1 -s [root@tbnonline ~]# ps -U mailman -o pid,%cpu,% mem,stime,time,vsz,args PID %CPU %MEM STIME TIME VSZ COMMAND 12949 0.0 0.1 08:05 00:00:00 7072 /usr/bin/python /var/mailman/bin/mailmanctl -s -q start 12950 0.0 0.3 08:05 00:00:02 11176 /usr/bin/python /var/mailman/bin/qrunner -- runner=ArchRunner:0:1 -s 12952 0.0 0.0 08:05 00:00:00 7040 /usr/bin/python /var/mailman/bin/qrunner -- runner=CommandRunner:0:1 -s 12953 0.0 0.2 08:05 00:00:00 9256 /usr/bin/python /var/mailman/bin/qrunner -- runner=IncomingRunner:0:1 -s 12954 0.0 0.1 08:05 00:00:00 7080 /usr/bin/python /var/mailman/bin/qrunner -- runner=NewsRunner:0:1 -s 12955 3.0 0.9 08:05 00:01:43 13584 /usr/bin/python /var/mailman/bin/qrunner -- runner=OutgoingRunner:0:1 -s 12956 1.2 0.6 08:05 00:00:41 10848 /usr/bin/python /var/mailman/bin/qrunner -- runner=VirginRunner:0:1 -s 12957 0.1 0.6 08:05 00:00:06 13284 /usr/bin/python /var/mailman/bin/qrunner -- runner=RetryRunner:0:1 -s 14900 29.8 1.1 08:51 00:02:47 13764 /usr/bin/python /var/mailman/bin/qrunner -- runner=BounceRunner:0:1 -s ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2005-02-24 01:46 Message: Logged In: YES user_id=67709 Your site has really big amount of bounces get. I'd suggest try one or two of these: 1. Set bounce_processing to "No" in admin->bounce page. 2. Set REGISTER_BOUNCES_EVERY = minutes(1) in mm_cfg.py and process bounces before they accumulate to Giga-Byte. 3. Rewrite your MTA's alias file as your-list-bounce: yourmail@your.dom.ain and process the counce manually. 4. Rewrite your MTA's alias file as your-list-bounce: /dev/null and forget about the bounces totally. ---------------------------------------------------------------------- Comment By: Paul Rubin (prubin) Date: 2005-02-24 01:22 Message: Logged In: YES user_id=91557 One additional piece, the bounce processor sits at a small amount of memory until the file with matching pid hits 1.5GB or so and then starts climbing fast. If I kill the bounce processor, the file is abandoned., If I stop the mailman service, the bounce processor keeps running and eating memory. If allowed to run unchecked, it will just eat all the memory in the system. I cannot kill the bounce process without another starting, even after stopping the mailman service. If I freshly re-boot the server and let mailman run for a few minutes, the the file grows, when I stop the service the file shrinks back to 0 bytes, but does not get deleted. I hope this helps. ---------------------------------------------------------------------- Comment By: Paul Rubin (prubin) Date: 2005-02-24 00:35 Message: Logged In: YES user_id=91557 Today we ran out of disk space, I have had to kill the bounce processor about 8 or nine times today... I found my diskspace problem: -rw-rw-rw- 1 mailman mailman 1.4G Feb 23 08:48 bounce-events-07208.pck -rw-rw-rw- 1 mailman mailman 931M Feb 23 09:50 bounce-events-08307.pck -rw-rw-rw- 1 mailman mailman 1.1G Feb 23 10:10 bounce-events-09037.pck -rw-rw-rw- 1 mailman mailman 1.4G Feb 23 10:29 bounce-events-10251.pck -rw-rw-rw- 1 mailman mailman 1.6G Feb 23 13:02 bounce-events-14874.pck -rw-rw-rw- 1 mailman mailman 1.4G Feb 23 14:17 bounce-events-17525.pck -rw-rw-rw- 1 mailman mailman 1.6G Feb 23 14:40 bounce-events-18973.pck -rw-rw-rw- 1 mailman mailman 1.6G Feb 23 15:02 bounce-events-19879.pck -rw-rw-rw- 1 mailman mailman 1.5G Feb 23 15:23 bounce-events-20584.pck And about 100 more file from other days. I have saved these file, and deleted the rest, does this or can these files tell you anything about what is going wrong? ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2004-12-17 01:29 Message: Logged In: YES user_id=67709 I suggest stop automatic processing of bounces by setting bounce_processing variable to 'No' at the admin/bounce page. Looks like your server is very busy and unsubscribing process due to the bounce score may interfering. You may also have to unsubscribe the problematic members manually. ---------------------------------------------------------------------- Comment By: Paul Rubin (prubin) Date: 2004-12-15 17:29 Message: Logged In: YES user_id=91557 I do not have a specific number of bounces per day. We send around 500,000 message per day with peak days around 1,000,000, we know that we have some bad addresses, but at any given time there should not be more than 5,000 bounce notices per day (full mailboxes are common) As far as I can tell only certain bounce notices cause the leak. We can go hours or days with memory being almost flat, then suddenly 200M vanishes in 2 or 3 minutes. Is there any way I could 'hack' the code to somehow grab the information about what bounce notice is causing the problem. Or to capture all bounce notices in some outof the way space that I could tar up an send to you for testing. If nothing else I could edit the aliases to copy all of the messages to a file and zip it down for you after a few days. Does any of this make any sense? ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2004-12-15 00:19 Message: Logged In: YES user_id=67709 My FreeBSD4.7/Solaris8 installations have no such problems. How many bounces you get on this system? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1077587&group_id=103 From noreply at sourceforge.net Thu Feb 24 13:42:39 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Feb 24 13:42:43 2005 Subject: [ mailman-Bugs-1077587 ] Memory Leak in Bounce Runner Message-ID: Bugs item #1077587, was opened at 2004-12-02 09:02 Message generated for change (Comment added) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1077587&group_id=103 Category: bounce detection Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Paul Rubin (prubin) Assigned to: Nobody/Anonymous (nobody) Summary: Memory Leak in Bounce Runner Initial Comment: Something is going bady wrong with the BouceRunner It is leaking memory. After it runs for a short time it has consumed hundreds of megabytes of memory. I kill it with -9 and it restarts and is fine for another couple of hours. Sometimes it does not restart and I have to stop and restart the mailman service. This is running on a Linux box with Redhat 9 and postfix 2.1.1 and mailman 2.1.5 and python 2.2.2 Below you will se a PS from right before I killed the process and below that one from a few seconds later. If you will tell me what you need I would really like to get to the bottom of this, I am killing the process like 10 times per day. If it eats too much memory before I catch it then the entire system fails. [root@tbnonline ~]# ps -U mailman -o pid,%cpu,% mem,stime,time,vsz,args PID %CPU %MEM STIME TIME VSZ COMMAND 12949 0.0 0.0 08:05 00:00:00 7068 /usr/bin/python /var/mailman/bin/mailmanctl -s -q start 12950 0.1 0.3 08:05 00:00:02 11176 /usr/bin/python /var/mailman/bin/qrunner -- runner=ArchRunner:0:1 -s 12951 18.9 70.8 08:05 00:08:40 931312 /usr/bin/python /var/mailman/bin/qrunner -- runner=BounceRunner:0:1 -s 12952 0.0 0.0 08:05 00:00:00 7040 /usr/bin/python /var/mailman/bin/qrunner -- runner=CommandRunner:0:1 -s 12953 0.0 0.1 08:05 00:00:00 9256 /usr/bin/python /var/mailman/bin/qrunner -- runner=IncomingRunner:0:1 -s 12954 0.0 0.1 08:05 00:00:00 7080 /usr/bin/python /var/mailman/bin/qrunner -- runner=NewsRunner:0:1 -s 12955 2.5 0.6 08:05 00:01:11 14172 /usr/bin/python /var/mailman/bin/qrunner -- runner=OutgoingRunner:0:1 -s 12956 0.8 0.2 08:05 00:00:24 10628 /usr/bin/python /var/mailman/bin/qrunner -- runner=VirginRunner:0:1 -s 12957 0.1 0.2 08:05 00:00:04 13272 /usr/bin/python /var/mailman/bin/qrunner -- runner=RetryRunner:0:1 -s [root@tbnonline ~]# ps -U mailman -o pid,%cpu,% mem,stime,time,vsz,args PID %CPU %MEM STIME TIME VSZ COMMAND 12949 0.0 0.1 08:05 00:00:00 7072 /usr/bin/python /var/mailman/bin/mailmanctl -s -q start 12950 0.0 0.3 08:05 00:00:02 11176 /usr/bin/python /var/mailman/bin/qrunner -- runner=ArchRunner:0:1 -s 12952 0.0 0.0 08:05 00:00:00 7040 /usr/bin/python /var/mailman/bin/qrunner -- runner=CommandRunner:0:1 -s 12953 0.0 0.2 08:05 00:00:00 9256 /usr/bin/python /var/mailman/bin/qrunner -- runner=IncomingRunner:0:1 -s 12954 0.0 0.1 08:05 00:00:00 7080 /usr/bin/python /var/mailman/bin/qrunner -- runner=NewsRunner:0:1 -s 12955 3.0 0.9 08:05 00:01:43 13584 /usr/bin/python /var/mailman/bin/qrunner -- runner=OutgoingRunner:0:1 -s 12956 1.2 0.6 08:05 00:00:41 10848 /usr/bin/python /var/mailman/bin/qrunner -- runner=VirginRunner:0:1 -s 12957 0.1 0.6 08:05 00:00:06 13284 /usr/bin/python /var/mailman/bin/qrunner -- runner=RetryRunner:0:1 -s 14900 29.8 1.1 08:51 00:02:47 13764 /usr/bin/python /var/mailman/bin/qrunner -- runner=BounceRunner:0:1 -s ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2005-02-24 07:42 Message: Logged In: YES user_id=12800 I have some ideas about fixing bounce runner. If I have time for 2.1.6 I'll try to attack it. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2005-02-23 20:46 Message: Logged In: YES user_id=67709 Your site has really big amount of bounces get. I'd suggest try one or two of these: 1. Set bounce_processing to "No" in admin->bounce page. 2. Set REGISTER_BOUNCES_EVERY = minutes(1) in mm_cfg.py and process bounces before they accumulate to Giga-Byte. 3. Rewrite your MTA's alias file as your-list-bounce: yourmail@your.dom.ain and process the counce manually. 4. Rewrite your MTA's alias file as your-list-bounce: /dev/null and forget about the bounces totally. ---------------------------------------------------------------------- Comment By: Paul Rubin (prubin) Date: 2005-02-23 20:22 Message: Logged In: YES user_id=91557 One additional piece, the bounce processor sits at a small amount of memory until the file with matching pid hits 1.5GB or so and then starts climbing fast. If I kill the bounce processor, the file is abandoned., If I stop the mailman service, the bounce processor keeps running and eating memory. If allowed to run unchecked, it will just eat all the memory in the system. I cannot kill the bounce process without another starting, even after stopping the mailman service. If I freshly re-boot the server and let mailman run for a few minutes, the the file grows, when I stop the service the file shrinks back to 0 bytes, but does not get deleted. I hope this helps. ---------------------------------------------------------------------- Comment By: Paul Rubin (prubin) Date: 2005-02-23 19:35 Message: Logged In: YES user_id=91557 Today we ran out of disk space, I have had to kill the bounce processor about 8 or nine times today... I found my diskspace problem: -rw-rw-rw- 1 mailman mailman 1.4G Feb 23 08:48 bounce-events-07208.pck -rw-rw-rw- 1 mailman mailman 931M Feb 23 09:50 bounce-events-08307.pck -rw-rw-rw- 1 mailman mailman 1.1G Feb 23 10:10 bounce-events-09037.pck -rw-rw-rw- 1 mailman mailman 1.4G Feb 23 10:29 bounce-events-10251.pck -rw-rw-rw- 1 mailman mailman 1.6G Feb 23 13:02 bounce-events-14874.pck -rw-rw-rw- 1 mailman mailman 1.4G Feb 23 14:17 bounce-events-17525.pck -rw-rw-rw- 1 mailman mailman 1.6G Feb 23 14:40 bounce-events-18973.pck -rw-rw-rw- 1 mailman mailman 1.6G Feb 23 15:02 bounce-events-19879.pck -rw-rw-rw- 1 mailman mailman 1.5G Feb 23 15:23 bounce-events-20584.pck And about 100 more file from other days. I have saved these file, and deleted the rest, does this or can these files tell you anything about what is going wrong? ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2004-12-16 20:29 Message: Logged In: YES user_id=67709 I suggest stop automatic processing of bounces by setting bounce_processing variable to 'No' at the admin/bounce page. Looks like your server is very busy and unsubscribing process due to the bounce score may interfering. You may also have to unsubscribe the problematic members manually. ---------------------------------------------------------------------- Comment By: Paul Rubin (prubin) Date: 2004-12-15 12:29 Message: Logged In: YES user_id=91557 I do not have a specific number of bounces per day. We send around 500,000 message per day with peak days around 1,000,000, we know that we have some bad addresses, but at any given time there should not be more than 5,000 bounce notices per day (full mailboxes are common) As far as I can tell only certain bounce notices cause the leak. We can go hours or days with memory being almost flat, then suddenly 200M vanishes in 2 or 3 minutes. Is there any way I could 'hack' the code to somehow grab the information about what bounce notice is causing the problem. Or to capture all bounce notices in some outof the way space that I could tar up an send to you for testing. If nothing else I could edit the aliases to copy all of the messages to a file and zip it down for you after a few days. Does any of this make any sense? ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2004-12-14 19:19 Message: Logged In: YES user_id=67709 My FreeBSD4.7/Solaris8 installations have no such problems. How many bounces you get on this system? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1077587&group_id=103 From noreply at sourceforge.net Thu Feb 24 16:08:36 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Feb 24 16:08:40 2005 Subject: [ mailman-Bugs-1077587 ] Memory Leak in Bounce Runner Message-ID: Bugs item #1077587, was opened at 2004-12-02 09:02 Message generated for change (Comment added) made by prubin You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1077587&group_id=103 Category: bounce detection Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Paul Rubin (prubin) Assigned to: Nobody/Anonymous (nobody) Summary: Memory Leak in Bounce Runner Initial Comment: Something is going bady wrong with the BouceRunner It is leaking memory. After it runs for a short time it has consumed hundreds of megabytes of memory. I kill it with -9 and it restarts and is fine for another couple of hours. Sometimes it does not restart and I have to stop and restart the mailman service. This is running on a Linux box with Redhat 9 and postfix 2.1.1 and mailman 2.1.5 and python 2.2.2 Below you will se a PS from right before I killed the process and below that one from a few seconds later. If you will tell me what you need I would really like to get to the bottom of this, I am killing the process like 10 times per day. If it eats too much memory before I catch it then the entire system fails. [root@tbnonline ~]# ps -U mailman -o pid,%cpu,% mem,stime,time,vsz,args PID %CPU %MEM STIME TIME VSZ COMMAND 12949 0.0 0.0 08:05 00:00:00 7068 /usr/bin/python /var/mailman/bin/mailmanctl -s -q start 12950 0.1 0.3 08:05 00:00:02 11176 /usr/bin/python /var/mailman/bin/qrunner -- runner=ArchRunner:0:1 -s 12951 18.9 70.8 08:05 00:08:40 931312 /usr/bin/python /var/mailman/bin/qrunner -- runner=BounceRunner:0:1 -s 12952 0.0 0.0 08:05 00:00:00 7040 /usr/bin/python /var/mailman/bin/qrunner -- runner=CommandRunner:0:1 -s 12953 0.0 0.1 08:05 00:00:00 9256 /usr/bin/python /var/mailman/bin/qrunner -- runner=IncomingRunner:0:1 -s 12954 0.0 0.1 08:05 00:00:00 7080 /usr/bin/python /var/mailman/bin/qrunner -- runner=NewsRunner:0:1 -s 12955 2.5 0.6 08:05 00:01:11 14172 /usr/bin/python /var/mailman/bin/qrunner -- runner=OutgoingRunner:0:1 -s 12956 0.8 0.2 08:05 00:00:24 10628 /usr/bin/python /var/mailman/bin/qrunner -- runner=VirginRunner:0:1 -s 12957 0.1 0.2 08:05 00:00:04 13272 /usr/bin/python /var/mailman/bin/qrunner -- runner=RetryRunner:0:1 -s [root@tbnonline ~]# ps -U mailman -o pid,%cpu,% mem,stime,time,vsz,args PID %CPU %MEM STIME TIME VSZ COMMAND 12949 0.0 0.1 08:05 00:00:00 7072 /usr/bin/python /var/mailman/bin/mailmanctl -s -q start 12950 0.0 0.3 08:05 00:00:02 11176 /usr/bin/python /var/mailman/bin/qrunner -- runner=ArchRunner:0:1 -s 12952 0.0 0.0 08:05 00:00:00 7040 /usr/bin/python /var/mailman/bin/qrunner -- runner=CommandRunner:0:1 -s 12953 0.0 0.2 08:05 00:00:00 9256 /usr/bin/python /var/mailman/bin/qrunner -- runner=IncomingRunner:0:1 -s 12954 0.0 0.1 08:05 00:00:00 7080 /usr/bin/python /var/mailman/bin/qrunner -- runner=NewsRunner:0:1 -s 12955 3.0 0.9 08:05 00:01:43 13584 /usr/bin/python /var/mailman/bin/qrunner -- runner=OutgoingRunner:0:1 -s 12956 1.2 0.6 08:05 00:00:41 10848 /usr/bin/python /var/mailman/bin/qrunner -- runner=VirginRunner:0:1 -s 12957 0.1 0.6 08:05 00:00:06 13284 /usr/bin/python /var/mailman/bin/qrunner -- runner=RetryRunner:0:1 -s 14900 29.8 1.1 08:51 00:02:47 13764 /usr/bin/python /var/mailman/bin/qrunner -- runner=BounceRunner:0:1 -s ---------------------------------------------------------------------- >Comment By: Paul Rubin (prubin) Date: 2005-02-24 10:08 Message: Logged In: YES user_id=91557 I will try the suggested settings... The bounce process currently builds up about 150MB per minute when started and takes about 2 minutes after being stoped for each minute run before it exits. This occures even when postfix is complete stopped. If the file gets over 300Meg than the exit time goes to 3 times, at 400Meg it will crash first with out of memory. Is is possible that there is some hangup that is causing bounce notices not to get pulled from postfix and the same ones just keep getting pulled over and over? ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2005-02-24 07:42 Message: Logged In: YES user_id=12800 I have some ideas about fixing bounce runner. If I have time for 2.1.6 I'll try to attack it. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2005-02-23 20:46 Message: Logged In: YES user_id=67709 Your site has really big amount of bounces get. I'd suggest try one or two of these: 1. Set bounce_processing to "No" in admin->bounce page. 2. Set REGISTER_BOUNCES_EVERY = minutes(1) in mm_cfg.py and process bounces before they accumulate to Giga-Byte. 3. Rewrite your MTA's alias file as your-list-bounce: yourmail@your.dom.ain and process the counce manually. 4. Rewrite your MTA's alias file as your-list-bounce: /dev/null and forget about the bounces totally. ---------------------------------------------------------------------- Comment By: Paul Rubin (prubin) Date: 2005-02-23 20:22 Message: Logged In: YES user_id=91557 One additional piece, the bounce processor sits at a small amount of memory until the file with matching pid hits 1.5GB or so and then starts climbing fast. If I kill the bounce processor, the file is abandoned., If I stop the mailman service, the bounce processor keeps running and eating memory. If allowed to run unchecked, it will just eat all the memory in the system. I cannot kill the bounce process without another starting, even after stopping the mailman service. If I freshly re-boot the server and let mailman run for a few minutes, the the file grows, when I stop the service the file shrinks back to 0 bytes, but does not get deleted. I hope this helps. ---------------------------------------------------------------------- Comment By: Paul Rubin (prubin) Date: 2005-02-23 19:35 Message: Logged In: YES user_id=91557 Today we ran out of disk space, I have had to kill the bounce processor about 8 or nine times today... I found my diskspace problem: -rw-rw-rw- 1 mailman mailman 1.4G Feb 23 08:48 bounce-events-07208.pck -rw-rw-rw- 1 mailman mailman 931M Feb 23 09:50 bounce-events-08307.pck -rw-rw-rw- 1 mailman mailman 1.1G Feb 23 10:10 bounce-events-09037.pck -rw-rw-rw- 1 mailman mailman 1.4G Feb 23 10:29 bounce-events-10251.pck -rw-rw-rw- 1 mailman mailman 1.6G Feb 23 13:02 bounce-events-14874.pck -rw-rw-rw- 1 mailman mailman 1.4G Feb 23 14:17 bounce-events-17525.pck -rw-rw-rw- 1 mailman mailman 1.6G Feb 23 14:40 bounce-events-18973.pck -rw-rw-rw- 1 mailman mailman 1.6G Feb 23 15:02 bounce-events-19879.pck -rw-rw-rw- 1 mailman mailman 1.5G Feb 23 15:23 bounce-events-20584.pck And about 100 more file from other days. I have saved these file, and deleted the rest, does this or can these files tell you anything about what is going wrong? ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2004-12-16 20:29 Message: Logged In: YES user_id=67709 I suggest stop automatic processing of bounces by setting bounce_processing variable to 'No' at the admin/bounce page. Looks like your server is very busy and unsubscribing process due to the bounce score may interfering. You may also have to unsubscribe the problematic members manually. ---------------------------------------------------------------------- Comment By: Paul Rubin (prubin) Date: 2004-12-15 12:29 Message: Logged In: YES user_id=91557 I do not have a specific number of bounces per day. We send around 500,000 message per day with peak days around 1,000,000, we know that we have some bad addresses, but at any given time there should not be more than 5,000 bounce notices per day (full mailboxes are common) As far as I can tell only certain bounce notices cause the leak. We can go hours or days with memory being almost flat, then suddenly 200M vanishes in 2 or 3 minutes. Is there any way I could 'hack' the code to somehow grab the information about what bounce notice is causing the problem. Or to capture all bounce notices in some outof the way space that I could tar up an send to you for testing. If nothing else I could edit the aliases to copy all of the messages to a file and zip it down for you after a few days. Does any of this make any sense? ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2004-12-14 19:19 Message: Logged In: YES user_id=67709 My FreeBSD4.7/Solaris8 installations have no such problems. How many bounces you get on this system? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1077587&group_id=103 From noreply at sourceforge.net Thu Feb 24 16:18:08 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Feb 24 16:18:11 2005 Subject: [ mailman-Bugs-1077587 ] Memory Leak in Bounce Runner Message-ID: Bugs item #1077587, was opened at 2004-12-02 09:02 Message generated for change (Comment added) made by prubin You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1077587&group_id=103 Category: bounce detection Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Paul Rubin (prubin) Assigned to: Nobody/Anonymous (nobody) Summary: Memory Leak in Bounce Runner Initial Comment: Something is going bady wrong with the BouceRunner It is leaking memory. After it runs for a short time it has consumed hundreds of megabytes of memory. I kill it with -9 and it restarts and is fine for another couple of hours. Sometimes it does not restart and I have to stop and restart the mailman service. This is running on a Linux box with Redhat 9 and postfix 2.1.1 and mailman 2.1.5 and python 2.2.2 Below you will se a PS from right before I killed the process and below that one from a few seconds later. If you will tell me what you need I would really like to get to the bottom of this, I am killing the process like 10 times per day. If it eats too much memory before I catch it then the entire system fails. [root@tbnonline ~]# ps -U mailman -o pid,%cpu,% mem,stime,time,vsz,args PID %CPU %MEM STIME TIME VSZ COMMAND 12949 0.0 0.0 08:05 00:00:00 7068 /usr/bin/python /var/mailman/bin/mailmanctl -s -q start 12950 0.1 0.3 08:05 00:00:02 11176 /usr/bin/python /var/mailman/bin/qrunner -- runner=ArchRunner:0:1 -s 12951 18.9 70.8 08:05 00:08:40 931312 /usr/bin/python /var/mailman/bin/qrunner -- runner=BounceRunner:0:1 -s 12952 0.0 0.0 08:05 00:00:00 7040 /usr/bin/python /var/mailman/bin/qrunner -- runner=CommandRunner:0:1 -s 12953 0.0 0.1 08:05 00:00:00 9256 /usr/bin/python /var/mailman/bin/qrunner -- runner=IncomingRunner:0:1 -s 12954 0.0 0.1 08:05 00:00:00 7080 /usr/bin/python /var/mailman/bin/qrunner -- runner=NewsRunner:0:1 -s 12955 2.5 0.6 08:05 00:01:11 14172 /usr/bin/python /var/mailman/bin/qrunner -- runner=OutgoingRunner:0:1 -s 12956 0.8 0.2 08:05 00:00:24 10628 /usr/bin/python /var/mailman/bin/qrunner -- runner=VirginRunner:0:1 -s 12957 0.1 0.2 08:05 00:00:04 13272 /usr/bin/python /var/mailman/bin/qrunner -- runner=RetryRunner:0:1 -s [root@tbnonline ~]# ps -U mailman -o pid,%cpu,% mem,stime,time,vsz,args PID %CPU %MEM STIME TIME VSZ COMMAND 12949 0.0 0.1 08:05 00:00:00 7072 /usr/bin/python /var/mailman/bin/mailmanctl -s -q start 12950 0.0 0.3 08:05 00:00:02 11176 /usr/bin/python /var/mailman/bin/qrunner -- runner=ArchRunner:0:1 -s 12952 0.0 0.0 08:05 00:00:00 7040 /usr/bin/python /var/mailman/bin/qrunner -- runner=CommandRunner:0:1 -s 12953 0.0 0.2 08:05 00:00:00 9256 /usr/bin/python /var/mailman/bin/qrunner -- runner=IncomingRunner:0:1 -s 12954 0.0 0.1 08:05 00:00:00 7080 /usr/bin/python /var/mailman/bin/qrunner -- runner=NewsRunner:0:1 -s 12955 3.0 0.9 08:05 00:01:43 13584 /usr/bin/python /var/mailman/bin/qrunner -- runner=OutgoingRunner:0:1 -s 12956 1.2 0.6 08:05 00:00:41 10848 /usr/bin/python /var/mailman/bin/qrunner -- runner=VirginRunner:0:1 -s 12957 0.1 0.6 08:05 00:00:06 13284 /usr/bin/python /var/mailman/bin/qrunner -- runner=RetryRunner:0:1 -s 14900 29.8 1.1 08:51 00:02:47 13764 /usr/bin/python /var/mailman/bin/qrunner -- runner=BounceRunner:0:1 -s ---------------------------------------------------------------------- >Comment By: Paul Rubin (prubin) Date: 2005-02-24 10:18 Message: Logged In: YES user_id=91557 ok, setting REGISTER_BOUNCES_EVERY = minutes(1) has the file hovering at between 120 and 10MB, but the process is using 300MB of RAM. Does this make any sense? What is the bounce processor doing that is consuming soo much memory relative to the file size? ---------------------------------------------------------------------- Comment By: Paul Rubin (prubin) Date: 2005-02-24 10:08 Message: Logged In: YES user_id=91557 I will try the suggested settings... The bounce process currently builds up about 150MB per minute when started and takes about 2 minutes after being stoped for each minute run before it exits. This occures even when postfix is complete stopped. If the file gets over 300Meg than the exit time goes to 3 times, at 400Meg it will crash first with out of memory. Is is possible that there is some hangup that is causing bounce notices not to get pulled from postfix and the same ones just keep getting pulled over and over? ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2005-02-24 07:42 Message: Logged In: YES user_id=12800 I have some ideas about fixing bounce runner. If I have time for 2.1.6 I'll try to attack it. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2005-02-23 20:46 Message: Logged In: YES user_id=67709 Your site has really big amount of bounces get. I'd suggest try one or two of these: 1. Set bounce_processing to "No" in admin->bounce page. 2. Set REGISTER_BOUNCES_EVERY = minutes(1) in mm_cfg.py and process bounces before they accumulate to Giga-Byte. 3. Rewrite your MTA's alias file as your-list-bounce: yourmail@your.dom.ain and process the counce manually. 4. Rewrite your MTA's alias file as your-list-bounce: /dev/null and forget about the bounces totally. ---------------------------------------------------------------------- Comment By: Paul Rubin (prubin) Date: 2005-02-23 20:22 Message: Logged In: YES user_id=91557 One additional piece, the bounce processor sits at a small amount of memory until the file with matching pid hits 1.5GB or so and then starts climbing fast. If I kill the bounce processor, the file is abandoned., If I stop the mailman service, the bounce processor keeps running and eating memory. If allowed to run unchecked, it will just eat all the memory in the system. I cannot kill the bounce process without another starting, even after stopping the mailman service. If I freshly re-boot the server and let mailman run for a few minutes, the the file grows, when I stop the service the file shrinks back to 0 bytes, but does not get deleted. I hope this helps. ---------------------------------------------------------------------- Comment By: Paul Rubin (prubin) Date: 2005-02-23 19:35 Message: Logged In: YES user_id=91557 Today we ran out of disk space, I have had to kill the bounce processor about 8 or nine times today... I found my diskspace problem: -rw-rw-rw- 1 mailman mailman 1.4G Feb 23 08:48 bounce-events-07208.pck -rw-rw-rw- 1 mailman mailman 931M Feb 23 09:50 bounce-events-08307.pck -rw-rw-rw- 1 mailman mailman 1.1G Feb 23 10:10 bounce-events-09037.pck -rw-rw-rw- 1 mailman mailman 1.4G Feb 23 10:29 bounce-events-10251.pck -rw-rw-rw- 1 mailman mailman 1.6G Feb 23 13:02 bounce-events-14874.pck -rw-rw-rw- 1 mailman mailman 1.4G Feb 23 14:17 bounce-events-17525.pck -rw-rw-rw- 1 mailman mailman 1.6G Feb 23 14:40 bounce-events-18973.pck -rw-rw-rw- 1 mailman mailman 1.6G Feb 23 15:02 bounce-events-19879.pck -rw-rw-rw- 1 mailman mailman 1.5G Feb 23 15:23 bounce-events-20584.pck And about 100 more file from other days. I have saved these file, and deleted the rest, does this or can these files tell you anything about what is going wrong? ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2004-12-16 20:29 Message: Logged In: YES user_id=67709 I suggest stop automatic processing of bounces by setting bounce_processing variable to 'No' at the admin/bounce page. Looks like your server is very busy and unsubscribing process due to the bounce score may interfering. You may also have to unsubscribe the problematic members manually. ---------------------------------------------------------------------- Comment By: Paul Rubin (prubin) Date: 2004-12-15 12:29 Message: Logged In: YES user_id=91557 I do not have a specific number of bounces per day. We send around 500,000 message per day with peak days around 1,000,000, we know that we have some bad addresses, but at any given time there should not be more than 5,000 bounce notices per day (full mailboxes are common) As far as I can tell only certain bounce notices cause the leak. We can go hours or days with memory being almost flat, then suddenly 200M vanishes in 2 or 3 minutes. Is there any way I could 'hack' the code to somehow grab the information about what bounce notice is causing the problem. Or to capture all bounce notices in some outof the way space that I could tar up an send to you for testing. If nothing else I could edit the aliases to copy all of the messages to a file and zip it down for you after a few days. Does any of this make any sense? ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2004-12-14 19:19 Message: Logged In: YES user_id=67709 My FreeBSD4.7/Solaris8 installations have no such problems. How many bounces you get on this system? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1077587&group_id=103 From noreply at sourceforge.net Thu Feb 24 16:18:48 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Feb 24 16:18:51 2005 Subject: [ mailman-Bugs-1077587 ] Memory Leak in Bounce Runner Message-ID: Bugs item #1077587, was opened at 2004-12-02 09:02 Message generated for change (Comment added) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1077587&group_id=103 Category: bounce detection Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Paul Rubin (prubin) Assigned to: Nobody/Anonymous (nobody) Summary: Memory Leak in Bounce Runner Initial Comment: Something is going bady wrong with the BouceRunner It is leaking memory. After it runs for a short time it has consumed hundreds of megabytes of memory. I kill it with -9 and it restarts and is fine for another couple of hours. Sometimes it does not restart and I have to stop and restart the mailman service. This is running on a Linux box with Redhat 9 and postfix 2.1.1 and mailman 2.1.5 and python 2.2.2 Below you will se a PS from right before I killed the process and below that one from a few seconds later. If you will tell me what you need I would really like to get to the bottom of this, I am killing the process like 10 times per day. If it eats too much memory before I catch it then the entire system fails. [root@tbnonline ~]# ps -U mailman -o pid,%cpu,% mem,stime,time,vsz,args PID %CPU %MEM STIME TIME VSZ COMMAND 12949 0.0 0.0 08:05 00:00:00 7068 /usr/bin/python /var/mailman/bin/mailmanctl -s -q start 12950 0.1 0.3 08:05 00:00:02 11176 /usr/bin/python /var/mailman/bin/qrunner -- runner=ArchRunner:0:1 -s 12951 18.9 70.8 08:05 00:08:40 931312 /usr/bin/python /var/mailman/bin/qrunner -- runner=BounceRunner:0:1 -s 12952 0.0 0.0 08:05 00:00:00 7040 /usr/bin/python /var/mailman/bin/qrunner -- runner=CommandRunner:0:1 -s 12953 0.0 0.1 08:05 00:00:00 9256 /usr/bin/python /var/mailman/bin/qrunner -- runner=IncomingRunner:0:1 -s 12954 0.0 0.1 08:05 00:00:00 7080 /usr/bin/python /var/mailman/bin/qrunner -- runner=NewsRunner:0:1 -s 12955 2.5 0.6 08:05 00:01:11 14172 /usr/bin/python /var/mailman/bin/qrunner -- runner=OutgoingRunner:0:1 -s 12956 0.8 0.2 08:05 00:00:24 10628 /usr/bin/python /var/mailman/bin/qrunner -- runner=VirginRunner:0:1 -s 12957 0.1 0.2 08:05 00:00:04 13272 /usr/bin/python /var/mailman/bin/qrunner -- runner=RetryRunner:0:1 -s [root@tbnonline ~]# ps -U mailman -o pid,%cpu,% mem,stime,time,vsz,args PID %CPU %MEM STIME TIME VSZ COMMAND 12949 0.0 0.1 08:05 00:00:00 7072 /usr/bin/python /var/mailman/bin/mailmanctl -s -q start 12950 0.0 0.3 08:05 00:00:02 11176 /usr/bin/python /var/mailman/bin/qrunner -- runner=ArchRunner:0:1 -s 12952 0.0 0.0 08:05 00:00:00 7040 /usr/bin/python /var/mailman/bin/qrunner -- runner=CommandRunner:0:1 -s 12953 0.0 0.2 08:05 00:00:00 9256 /usr/bin/python /var/mailman/bin/qrunner -- runner=IncomingRunner:0:1 -s 12954 0.0 0.1 08:05 00:00:00 7080 /usr/bin/python /var/mailman/bin/qrunner -- runner=NewsRunner:0:1 -s 12955 3.0 0.9 08:05 00:01:43 13584 /usr/bin/python /var/mailman/bin/qrunner -- runner=OutgoingRunner:0:1 -s 12956 1.2 0.6 08:05 00:00:41 10848 /usr/bin/python /var/mailman/bin/qrunner -- runner=VirginRunner:0:1 -s 12957 0.1 0.6 08:05 00:00:06 13284 /usr/bin/python /var/mailman/bin/qrunner -- runner=RetryRunner:0:1 -s 14900 29.8 1.1 08:51 00:02:47 13764 /usr/bin/python /var/mailman/bin/qrunner -- runner=BounceRunner:0:1 -s ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2005-02-24 10:18 Message: Logged In: YES user_id=12800 The problem really is that information is logged to a file and periodically that file is read and processed, however no limit is placed on the amount of the log file that's read during any one processing loop. The bounce runner wants to read as much as possible because it will sort bounces so it can be more efficient about locking lists for bounce info updates. But if too much of the file is read then of course you get the huge memory footprint. Probably some sort of limit on the number of records read from the file is the way to go. ---------------------------------------------------------------------- Comment By: Paul Rubin (prubin) Date: 2005-02-24 10:18 Message: Logged In: YES user_id=91557 ok, setting REGISTER_BOUNCES_EVERY = minutes(1) has the file hovering at between 120 and 10MB, but the process is using 300MB of RAM. Does this make any sense? What is the bounce processor doing that is consuming soo much memory relative to the file size? ---------------------------------------------------------------------- Comment By: Paul Rubin (prubin) Date: 2005-02-24 10:08 Message: Logged In: YES user_id=91557 I will try the suggested settings... The bounce process currently builds up about 150MB per minute when started and takes about 2 minutes after being stoped for each minute run before it exits. This occures even when postfix is complete stopped. If the file gets over 300Meg than the exit time goes to 3 times, at 400Meg it will crash first with out of memory. Is is possible that there is some hangup that is causing bounce notices not to get pulled from postfix and the same ones just keep getting pulled over and over? ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2005-02-24 07:42 Message: Logged In: YES user_id=12800 I have some ideas about fixing bounce runner. If I have time for 2.1.6 I'll try to attack it. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2005-02-23 20:46 Message: Logged In: YES user_id=67709 Your site has really big amount of bounces get. I'd suggest try one or two of these: 1. Set bounce_processing to "No" in admin->bounce page. 2. Set REGISTER_BOUNCES_EVERY = minutes(1) in mm_cfg.py and process bounces before they accumulate to Giga-Byte. 3. Rewrite your MTA's alias file as your-list-bounce: yourmail@your.dom.ain and process the counce manually. 4. Rewrite your MTA's alias file as your-list-bounce: /dev/null and forget about the bounces totally. ---------------------------------------------------------------------- Comment By: Paul Rubin (prubin) Date: 2005-02-23 20:22 Message: Logged In: YES user_id=91557 One additional piece, the bounce processor sits at a small amount of memory until the file with matching pid hits 1.5GB or so and then starts climbing fast. If I kill the bounce processor, the file is abandoned., If I stop the mailman service, the bounce processor keeps running and eating memory. If allowed to run unchecked, it will just eat all the memory in the system. I cannot kill the bounce process without another starting, even after stopping the mailman service. If I freshly re-boot the server and let mailman run for a few minutes, the the file grows, when I stop the service the file shrinks back to 0 bytes, but does not get deleted. I hope this helps. ---------------------------------------------------------------------- Comment By: Paul Rubin (prubin) Date: 2005-02-23 19:35 Message: Logged In: YES user_id=91557 Today we ran out of disk space, I have had to kill the bounce processor about 8 or nine times today... I found my diskspace problem: -rw-rw-rw- 1 mailman mailman 1.4G Feb 23 08:48 bounce-events-07208.pck -rw-rw-rw- 1 mailman mailman 931M Feb 23 09:50 bounce-events-08307.pck -rw-rw-rw- 1 mailman mailman 1.1G Feb 23 10:10 bounce-events-09037.pck -rw-rw-rw- 1 mailman mailman 1.4G Feb 23 10:29 bounce-events-10251.pck -rw-rw-rw- 1 mailman mailman 1.6G Feb 23 13:02 bounce-events-14874.pck -rw-rw-rw- 1 mailman mailman 1.4G Feb 23 14:17 bounce-events-17525.pck -rw-rw-rw- 1 mailman mailman 1.6G Feb 23 14:40 bounce-events-18973.pck -rw-rw-rw- 1 mailman mailman 1.6G Feb 23 15:02 bounce-events-19879.pck -rw-rw-rw- 1 mailman mailman 1.5G Feb 23 15:23 bounce-events-20584.pck And about 100 more file from other days. I have saved these file, and deleted the rest, does this or can these files tell you anything about what is going wrong? ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2004-12-16 20:29 Message: Logged In: YES user_id=67709 I suggest stop automatic processing of bounces by setting bounce_processing variable to 'No' at the admin/bounce page. Looks like your server is very busy and unsubscribing process due to the bounce score may interfering. You may also have to unsubscribe the problematic members manually. ---------------------------------------------------------------------- Comment By: Paul Rubin (prubin) Date: 2004-12-15 12:29 Message: Logged In: YES user_id=91557 I do not have a specific number of bounces per day. We send around 500,000 message per day with peak days around 1,000,000, we know that we have some bad addresses, but at any given time there should not be more than 5,000 bounce notices per day (full mailboxes are common) As far as I can tell only certain bounce notices cause the leak. We can go hours or days with memory being almost flat, then suddenly 200M vanishes in 2 or 3 minutes. Is there any way I could 'hack' the code to somehow grab the information about what bounce notice is causing the problem. Or to capture all bounce notices in some outof the way space that I could tar up an send to you for testing. If nothing else I could edit the aliases to copy all of the messages to a file and zip it down for you after a few days. Does any of this make any sense? ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2004-12-14 19:19 Message: Logged In: YES user_id=67709 My FreeBSD4.7/Solaris8 installations have no such problems. How many bounces you get on this system? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1077587&group_id=103 From noreply at sourceforge.net Fri Feb 25 00:13:11 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Feb 25 00:13:15 2005 Subject: [ mailman-Bugs-1151439 ] Mailman apparently converts \r\n to \n\n Message-ID: Bugs item #1151439, was opened at 2005-02-25 00:13 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=1151439&group_id=103 Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Sylvain BEUCLER (beuc) Assigned to: Nobody/Anonymous (nobody) Summary: Mailman apparently converts \r\n to \n\n Initial Comment: We are working with the Savane tracking system. It sends a message using Unix newlines \n, except that the core of the message, sent via a web form, uses CRLF \r\n. In this case, we receive correct personal notifications, but notifications sent to the list end up with CRLF converted to double Unix \n\n. I modified the Savane code and replaced all [^\r]\n by \r\n before to send the message. Same result: all \r\n converted to Unix \n, despite the fact there was not any Unix \n left. I then tried to do the opposite, replace all \r\n by \n. It worked as expected, no newlines duplicated. Again, in all cases, the personal notifications, not sent via a Mailman-managed mailing list, were ok. Apparently a mail system transparently converted CRLF to LF at a point. http://ietf.org/rfc/rfc0821.txt is not very clear but suggests that in SMTP the DATA section should use CRLF. So apparently Mailman does not have a good behavior and should convert CRLF to LF instead of LFLF. What do you think? Savane-related bug report: https://gna.org/bugs/?func=detailitem&item_id=1980 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1151439&group_id=103 From noreply at sourceforge.net Fri Feb 25 09:10:46 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Feb 25 09:10:48 2005 Subject: [ mailman-Patches-1124510 ] speed up update_pending in bin/update Message-ID: Patches item #1124510, was opened at 2005-02-17 05:19 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1124510&group_id=103 Category: configure/install Group: Mailman 2.1 Status: Open Resolution: None Priority: 7 Submitted By: pabs (pabs3) Assigned to: Nobody/Anonymous (nobody) Summary: speed up update_pending in bin/update Initial Comment: This patch changes the update script so that loading and saving the per-list pending.pck files is done once per list instead of once per pending request. This results in a significant speedup (seconds per list instead of minutes). ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2005-02-25 08:10 Message: Logged In: YES user_id=67709 Sorry, but I'm declined to integrate this patch because, 1. patch is lengthy 2. the work is only one time (pre 2.1.4 to 2.1.5) 3. better bin/discard the pending requests than update at all. Maybe, Barry have a different view. ---------------------------------------------------------------------- Comment By: pabs (pabs3) Date: 2005-02-17 05:51 Message: Logged In: YES user_id=35028 This is against 2.1.6b3 by the way. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1124510&group_id=103 From noreply at sourceforge.net Sat Feb 26 09:28:05 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Sat Feb 26 09:28:08 2005 Subject: [ mailman-Patches-1124510 ] speed up update_pending in bin/update Message-ID: Patches item #1124510, was opened at 2005-02-17 13:19 Message generated for change (Comment added) made by pabs3 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1124510&group_id=103 Category: configure/install Group: Mailman 2.1 Status: Open Resolution: None Priority: 7 Submitted By: pabs (pabs3) Assigned to: Nobody/Anonymous (nobody) Summary: speed up update_pending in bin/update Initial Comment: This patch changes the update script so that loading and saving the per-list pending.pck files is done once per list instead of once per pending request. This results in a significant speedup (seconds per list instead of minutes). ---------------------------------------------------------------------- >Comment By: pabs (pabs3) Date: 2005-02-26 16:28 Message: Logged In: YES user_id=35028 Thats a shame :( 1. Do you know of a way to access private functions of subclasses of MailList? I don't know enough python to do it :( 2. Yes, but it would be good if the downtime on this was minutes instead of hours. 3. And generate complaints when people accuse list admins of covering up their questions/discarding posts? What would it take to get this patch into shape for mailman 2.1.6/2.1.7? ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2005-02-25 16:10 Message: Logged In: YES user_id=67709 Sorry, but I'm declined to integrate this patch because, 1. patch is lengthy 2. the work is only one time (pre 2.1.4 to 2.1.5) 3. better bin/discard the pending requests than update at all. Maybe, Barry have a different view. ---------------------------------------------------------------------- Comment By: pabs (pabs3) Date: 2005-02-17 13:51 Message: Logged In: YES user_id=35028 This is against 2.1.6b3 by the way. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1124510&group_id=103 From noreply at sourceforge.net Sun Feb 27 09:36:11 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Sun Feb 27 09:36:15 2005 Subject: [ mailman-Bugs-1152800 ] Footer is Added in Plaintext to baes64 encoded mails Message-ID: Bugs item #1152800, was opened at 2005-02-27 08:36 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=1152800&group_id=103 Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: James (james_tis) Assigned to: Nobody/Anonymous (nobody) Summary: Footer is Added in Plaintext to baes64 encoded mails Initial Comment: When a user sends an email to the list with the following headers: Content-Type: text/plain Content-Transfer-Encoding: base64 The mailman software attaches the list footer to the body part of the message in plain text. When users receive the message, they see a string of garbage characters at the bottom, where their mail client software tried to base64 decode the plaintext footer. Mailman should instead check the Content-Transfer-Encoding header and either: (1) append the footer encoded in the appropriate encoding (2) change the Content-Type header to multipart/text and add the footer as a separate body part (3) do not add the footer ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1152800&group_id=103 From noreply at sourceforge.net Sun Feb 27 09:46:27 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Sun Feb 27 09:46:31 2005 Subject: [ mailman-Bugs-1152800 ] Footer is Added in Plaintext to baes64 encoded mails Message-ID: Bugs item #1152800, was opened at 2005-02-27 08:36 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1152800&group_id=103 Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: James (james_tis) Assigned to: Nobody/Anonymous (nobody) Summary: Footer is Added in Plaintext to baes64 encoded mails Initial Comment: When a user sends an email to the list with the following headers: Content-Type: text/plain Content-Transfer-Encoding: base64 The mailman software attaches the list footer to the body part of the message in plain text. When users receive the message, they see a string of garbage characters at the bottom, where their mail client software tried to base64 decode the plaintext footer. Mailman should instead check the Content-Transfer-Encoding header and either: (1) append the footer encoded in the appropriate encoding (2) change the Content-Type header to multipart/text and add the footer as a separate body part (3) do not add the footer ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2005-02-27 08:46 Message: Logged In: YES user_id=67709 What is the version of your mailman? I believe I fixed this in mailman-2.1.6(b4). The latest version should decode base64 before appending the footer (and re-encode appropriately according to the charset). ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1152800&group_id=103 From noreply at sourceforge.net Sun Feb 27 10:28:48 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Sun Feb 27 10:28:51 2005 Subject: [ mailman-Bugs-1152800 ] Footer is Added in Plaintext to baes64 encoded mails Message-ID: Bugs item #1152800, was opened at 2005-02-27 08:36 Message generated for change (Comment added) made by james_tis You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1152800&group_id=103 Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: James (james_tis) Assigned to: Nobody/Anonymous (nobody) Summary: Footer is Added in Plaintext to baes64 encoded mails Initial Comment: When a user sends an email to the list with the following headers: Content-Type: text/plain Content-Transfer-Encoding: base64 The mailman software attaches the list footer to the body part of the message in plain text. When users receive the message, they see a string of garbage characters at the bottom, where their mail client software tried to base64 decode the plaintext footer. Mailman should instead check the Content-Transfer-Encoding header and either: (1) append the footer encoded in the appropriate encoding (2) change the Content-Type header to multipart/text and add the footer as a separate body part (3) do not add the footer ---------------------------------------------------------------------- >Comment By: James (james_tis) Date: 2005-02-27 09:28 Message: Logged In: YES user_id=1228458 I'll try upgrading and see if that helps... ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2005-02-27 08:46 Message: Logged In: YES user_id=67709 What is the version of your mailman? I believe I fixed this in mailman-2.1.6(b4). The latest version should decode base64 before appending the footer (and re-encode appropriately according to the charset). ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1152800&group_id=103 From noreply at sourceforge.net Sun Feb 27 18:15:38 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Sun Feb 27 18:15:40 2005 Subject: [ mailman-Bugs-1152953 ] Cancelling a subscription confirmation throws assertion Message-ID: Bugs item #1152953, was opened at 2005-02-27 12:15 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=1152953&group_id=103 Category: (un)subscribing Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Geoff Mottram (gmottram) Assigned to: Nobody/Anonymous (nobody) Summary: Cancelling a subscription confirmation throws assertion Initial Comment: When you use the web interface to confirm a subscription and select the "Cancel my subscription request", Mailman throws an assertion. The problem can be fixed by replacing line 312 in Mailman/Cgi/confirm.py which currently reads: userdesc = mlist.pend_confirm(cookie)[1] With the following code: mlist.Lock() try: userdesc = mlist.pend_confirm(cookie)[1] finally: mlist.Unlock() More detailed information on this fix can be found here: http://www.minaret.biz/tips/mailman2.html Geoff Mottram ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1152953&group_id=103