From noreply at sourceforge.net Mon Aug 4 09:59:33 2008 From: noreply at sourceforge.net (SourceForge.net) Date: Mon, 04 Aug 2008 07:59:33 +0000 Subject: [ mailman-Bugs-2037414 ] Subscriber "disappears" after subscription Message-ID: Bugs item #2037414, was opened at 2008-08-04 00:59 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=2037414&group_id=103 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: (un)subscribing Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Private: No Submitted By: Massimo Lanfranconi (mlanfranconi) Assigned to: Nobody/Anonymous (nobody) Summary: Subscriber "disappears" after subscription Initial Comment: Mailman 2.1.11 Python 2.4.4 OS Solaris 2.11 Hi, I have been able to reproduce this bug consistently by running the replicate_bug script: replicate _bug is the following: #!/bin/sh /usr/local/mailman/bin/rmlist testlist1 /usr/local/mailman/bin/rmlist testlist2 /usr/local/mailman/bin/rmlist testlist3 /usr/local/mailman/bin/rmlist testlist4 /usr/local/mailman/bin/rmlist testlist5 /usr/local/mailman/bin/rmlist testlist6 /usr/local/mailman/bin/newlist -q -e url.domain.com testlist1 list-admin at domain.com testpwd /usr/local/mailman/bin/newlist -q -e url.domain.com testlist2 list-admin at domain.com testpwd /usr/local/mailman/bin/newlist -q -e url.domain.com testlist3 list-admin at domain.com testpwd /usr/local/mailman/bin/newlist -q -e url.domain.com testlist4 list-admin at domain.com testpwd /usr/local/mailman/bin/newlist -q -e url.domain.com testlist5 list-admin at domain.com testpwd /usr/local/mailman/bin/newlist -q -e url.domain.com testlist6 list-admin at domain.com testpwd echo "foo at bar.com" | /usr/local/mailman/bin/add_members -r - testlist1 echo "foo at bar.com" | /usr/local/mailman/bin/add_members -r - testlist2 echo "foo at bar.com" | /usr/local/mailman/bin/add_members -r - testlist3 echo "foo at bar.com" | /usr/local/mailman/bin/add_members -r - testlist4 echo "foo at bar.com" | /usr/local/mailman/bin/add_members -r - testlist5 echo "foo at bar.com" | /usr/local/mailman/bin/add_members -r - testlist6 echo "boo at foo.com" | /usr/local/mailman/bin/add_members -r - testlist1 echo "boo at foo.com" | /usr/local/mailman/bin/add_members -r - testlist2 echo "boo at foo.com" | /usr/local/mailman/bin/add_members -r - testlist3 echo "boo at foo.com" | /usr/local/mailman/bin/add_members -r - testlist4 echo "boo at foo.com" | /usr/local/mailman/bin/add_members -r - testlist5 echo "boo at foo.com" | /usr/local/mailman/bin/add_members -r - testlist6 After a short wait the following output is received: Subscribed: foo at bar.com Subscribed: foo at bar.com Subscribed: foo at bar.com Subscribed: foo at bar.com Subscribed: foo at bar.com Subscribed: foo at bar.com Subscribed: boo at foo.com Subscribed: boo at foo.com Subscribed: boo at foo.com Subscribed: boo at foo.com Subscribed: boo at foo.com Subscribed: boo at foo.com foo at bar.com receives 6 confirmation emails, as boo at foo.com does. So far so good. At this point testlist1-6 each should contain 2 subscribers: foo at bar.com and boo at foo.com BUT /usr/local/mailman/bin/list_members testlist1 /usr/local/mailman/bin/list_members testlist2 /usr/local/mailman/bin/list_members testlist3 /usr/local/mailman/bin/list_members testlist4 /usr/local/mailman/bin/list_members testlist5 /usr/local/mailman/bin/list_members testlist6 invariably produce some random combination in which one or more of the subscribers are missing: for example: boo at foo.com foo at bar.com foo at bar.com boo at foo.com foo at bar.com foo at bar.com foo at bar.com boo at foo.com foo at bar.com in which three instances of boo at foo.com are missing... No Errors in any Mailman log. Thanks in advance for your help. Please let me know if you need additional details. Regards, Max ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=2037414&group_id=103 From noreply at sourceforge.net Tue Aug 5 21:55:32 2008 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 05 Aug 2008 19:55:32 +0000 Subject: [ mailman-Bugs-2039241 ] teach firefox that different lists may have different passwo Message-ID: Bugs item #2039241, was opened at 2008-08-06 05:55 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=2039241&group_id=103 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Web/CGI Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Robert Collins (rbcollins) Assigned to: Nobody/Anonymous (nobody) Summary: teach firefox that different lists may have different passwo Initial Comment: given two lists on a mailman instance, foo and bar, each with a list passsword the same as the name. login to one, save the password in firefox, go to the other's admindb and it will fail - wrong password. login and ask firefox to remember it and it resets the password saved for the list foo. This is annoying :) I suspect you are using the same field and form names - while I don't know what the heuristic ff uses for html auth field detection, its certainly assuming its the *same* password. One hack that might be elegant and work would be a hidden field called username set to the list name :) Another would be just changing things to ff thinks its a different password and stores it differently. I'd *really* love a fix that can be backported to 2.1.8 which our list servers are running. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=2039241&group_id=103 From noreply at sourceforge.net Wed Aug 6 00:08:56 2008 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 05 Aug 2008 22:08:56 +0000 Subject: [ mailman-Bugs-2039241 ] teach firefox that different lists may have different passwo Message-ID: Bugs item #2039241, was opened at 2008-08-05 12:55 Message generated for change (Comment added) made by msapiro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=2039241&group_id=103 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Web/CGI Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Robert Collins (rbcollins) Assigned to: Nobody/Anonymous (nobody) Summary: teach firefox that different lists may have different passwo Initial Comment: given two lists on a mailman instance, foo and bar, each with a list passsword the same as the name. login to one, save the password in firefox, go to the other's admindb and it will fail - wrong password. login and ask firefox to remember it and it resets the password saved for the list foo. This is annoying :) I suspect you are using the same field and form names - while I don't know what the heuristic ff uses for html auth field detection, its certainly assuming its the *same* password. One hack that might be elegant and work would be a hidden field called username set to the list name :) Another would be just changing things to ff thinks its a different password and stores it differently. I'd *really* love a fix that can be backported to 2.1.8 which our list servers are running. ---------------------------------------------------------------------- >Comment By: Mark Sapiro (msapiro) Date: 2008-08-05 15:08 Message: Logged In: YES user_id=1123998 Originator: NO The template for the pages is admlogin.html. See for ways to make an edited version of this template. The string %(listname)s will be replaced with the list name. You could implement your first suggestion by changing the line to Changing the name "adminpw" to something list specific as in your second suggestion would require several code changes to identify the password. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=2039241&group_id=103 From noreply at sourceforge.net Wed Aug 6 02:08:34 2008 From: noreply at sourceforge.net (SourceForge.net) Date: Wed, 06 Aug 2008 00:08:34 +0000 Subject: [ mailman-Bugs-2037414 ] Subscriber "disappears" after subscription Message-ID: Bugs item #2037414, was opened at 2008-08-04 00:59 Message generated for change (Comment added) made by msapiro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=2037414&group_id=103 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: (un)subscribing Group: 2.1 (stable) Status: Open >Resolution: Accepted Priority: 5 Private: No Submitted By: Massimo Lanfranconi (mlanfranconi) >Assigned to: Mark Sapiro (msapiro) Summary: Subscriber "disappears" after subscription Initial Comment: Mailman 2.1.11 Python 2.4.4 OS Solaris 2.11 Hi, I have been able to reproduce this bug consistently by running the replicate_bug script: replicate _bug is the following: #!/bin/sh /usr/local/mailman/bin/rmlist testlist1 /usr/local/mailman/bin/rmlist testlist2 /usr/local/mailman/bin/rmlist testlist3 /usr/local/mailman/bin/rmlist testlist4 /usr/local/mailman/bin/rmlist testlist5 /usr/local/mailman/bin/rmlist testlist6 /usr/local/mailman/bin/newlist -q -e url.domain.com testlist1 list-admin at domain.com testpwd /usr/local/mailman/bin/newlist -q -e url.domain.com testlist2 list-admin at domain.com testpwd /usr/local/mailman/bin/newlist -q -e url.domain.com testlist3 list-admin at domain.com testpwd /usr/local/mailman/bin/newlist -q -e url.domain.com testlist4 list-admin at domain.com testpwd /usr/local/mailman/bin/newlist -q -e url.domain.com testlist5 list-admin at domain.com testpwd /usr/local/mailman/bin/newlist -q -e url.domain.com testlist6 list-admin at domain.com testpwd echo "foo at bar.com" | /usr/local/mailman/bin/add_members -r - testlist1 echo "foo at bar.com" | /usr/local/mailman/bin/add_members -r - testlist2 echo "foo at bar.com" | /usr/local/mailman/bin/add_members -r - testlist3 echo "foo at bar.com" | /usr/local/mailman/bin/add_members -r - testlist4 echo "foo at bar.com" | /usr/local/mailman/bin/add_members -r - testlist5 echo "foo at bar.com" | /usr/local/mailman/bin/add_members -r - testlist6 echo "boo at foo.com" | /usr/local/mailman/bin/add_members -r - testlist1 echo "boo at foo.com" | /usr/local/mailman/bin/add_members -r - testlist2 echo "boo at foo.com" | /usr/local/mailman/bin/add_members -r - testlist3 echo "boo at foo.com" | /usr/local/mailman/bin/add_members -r - testlist4 echo "boo at foo.com" | /usr/local/mailman/bin/add_members -r - testlist5 echo "boo at foo.com" | /usr/local/mailman/bin/add_members -r - testlist6 After a short wait the following output is received: Subscribed: foo at bar.com Subscribed: foo at bar.com Subscribed: foo at bar.com Subscribed: foo at bar.com Subscribed: foo at bar.com Subscribed: foo at bar.com Subscribed: boo at foo.com Subscribed: boo at foo.com Subscribed: boo at foo.com Subscribed: boo at foo.com Subscribed: boo at foo.com Subscribed: boo at foo.com foo at bar.com receives 6 confirmation emails, as boo at foo.com does. So far so good. At this point testlist1-6 each should contain 2 subscribers: foo at bar.com and boo at foo.com BUT /usr/local/mailman/bin/list_members testlist1 /usr/local/mailman/bin/list_members testlist2 /usr/local/mailman/bin/list_members testlist3 /usr/local/mailman/bin/list_members testlist4 /usr/local/mailman/bin/list_members testlist5 /usr/local/mailman/bin/list_members testlist6 invariably produce some random combination in which one or more of the subscribers are missing: for example: boo at foo.com foo at bar.com foo at bar.com boo at foo.com foo at bar.com foo at bar.com foo at bar.com boo at foo.com foo at bar.com in which three instances of boo at foo.com are missing... No Errors in any Mailman log. Thanks in advance for your help. Please let me know if you need additional details. Regards, Max ---------------------------------------------------------------------- >Comment By: Mark Sapiro (msapiro) Date: 2008-08-05 17:08 Message: Logged In: YES user_id=1123998 Originator: NO Thanks for the script. It was helpful in finding the problem. The analysis of the cause of the problem and potential fix is at . ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=2037414&group_id=103 From noreply at sourceforge.net Thu Aug 7 21:12:21 2008 From: noreply at sourceforge.net (SourceForge.net) Date: Thu, 07 Aug 2008 19:12:21 +0000 Subject: [ mailman-Patches-943827 ] true virtual hosting patch for 2.1 Message-ID: Patches item #943827, was opened at 2004-04-28 12:57 Message generated for change (Comment added) made by selsky You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=943827&group_id=103 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: list administration Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Private: No Submitted By: The Anarcat (anarcat) Assigned to: Nobody/Anonymous (nobody) Summary: true virtual hosting patch for 2.1 Initial Comment: [copy of the mail sent to -developpers@] We developped a reliable solution for running lists with the same name on different domains on the same Mailman installation. I implemented that on top of the Mailman 2.1.1-5.1 Debian stable package. All that is needed is to patch 2 files (bin/newlist, Mailman/MailList.py) in the mailman install, and here is the patch: http://bugs.koumbit.net/file_download.php?file_id=3&type=bug There's only one caveat right now: Mailman/Cgi/create.py might need to get patched too, but I haven't got around looking at it yet, and it "just works", for now. I don't know what's the current status of virtual hosting support on Mailman, but this patch is a simple hack that should bring joy in the homes of all Mailman admins around the world. :) I got my inspiration and part of the code from: http://mithrandr.moria.org/blog/139.html All it does is to add the domain to the internal_name() of a list. The real_name is kept as is, and the getListAddress() does the Right Thing. This makes Mailman generate aliases like: list-example.com: "|/var/lib/mailman/mail/mailman post list-example.com" Care will have to be taken on the MTA side to map those list-example.com to list at example.com. We are using alternc.org to manage our server, so we are using LDAP, so everything went pretty smoothly. :) But I guess it will require some magic on the Postfix side or something... Cheers, A. PS: for those wanting to see more, you can come to our Wiki: http://koumbit.net/wiki/VirtualMailman You'll probably have a little trouble finding your way if you don't read french though. :) Babelfish might help, haven't tried. ---------------------------------------------------------------------- Comment By: Matt Selsky (selsky) Date: 2008-08-07 15:12 Message: Logged In: YES user_id=324866 Originator: NO Is this forward compatible with Mailman 3? ---------------------------------------------------------------------- Comment By: The Anarcat (anarcat) Date: 2008-04-16 13:26 Message: Logged In: YES user_id=246797 Originator: YES The patch is online in our wiki: http://wiki.koumbit.net/VirtualMailman Note that the v3 of mailman now supports this out of the box, although it's in alpha, as far as I understand. ---------------------------------------------------------------------- Comment By: Graham Leggett (minfrin) Date: 2008-04-16 13:09 Message: Logged In: YES user_id=129704 Originator: NO The site http://nix.lauft.net/mailman/ is now down - does anyone have a copy of the mailman-vh-2.1.7.patch anywhere? ---------------------------------------------------------------------- Comment By: Paul Hampson (tbble) Date: 2007-03-01 17:57 Message: Logged In: YES user_id=87909 Originator: NO Grab mailman-vh-2.1.7.patch from http://nix.lauft.net/mailman/, it applies fine to 2.1.9. ---------------------------------------------------------------------- Comment By: GILLIG (fgillig) Date: 2007-03-01 06:18 Message: Logged In: YES user_id=1463624 Originator: NO I search this patch for mailman 2.1.9 ... (fc5). Anyone can help ? ---------------------------------------------------------------------- Comment By: Pedro Algarvio (s0undt3ch) Date: 2006-10-12 21:05 Message: Logged In: YES user_id=927681 +1 for this patch ---------------------------------------------------------------------- Comment By: Paul Hampson (tbble) Date: 2006-04-22 07:48 Message: Logged In: YES user_id=87909 Crud, wrapping... The changes are all on one line. ---------------------------------------------------------------------- Comment By: Paul Hampson (tbble) Date: 2006-04-22 07:47 Message: Logged In: YES user_id=87909 minfrin, create it as listname-domain or try this patch: diff -urNad mailman-2.1.5/Mailman/Cgi/create.py /tmp/dpep.bPHYjm/mailman-2.1.5/Mailman/Cgi/create.py --- mailman-2.1.5/Mailman/Cgi/create.py 2006-04-22 20:58:10.324872941 +1000 +++ /tmp/dpep.bPHYjm/mailman-2.1.5/Mailman/Cgi/create.py 2006-04-22 21:13:31.596133649 +1000 @@ -184,7 +184,7 @@ oldmask = os.umask(002) try: try: - mlist.Create(listname, owner, pw, langs, emailhost) + mlist.Create("%s@%s" % (listname,hostname), owner, pw, langs, emailhost) finally: os.umask(oldmask) except Errors.EmailAddressError, s: Which will add the '@domain' to the listname before passing it to mlist.Create, which the patch changes to deal with '@' the way we want. ---------------------------------------------------------------------- Comment By: Graham Leggett (minfrin) Date: 2006-03-17 15:39 Message: Logged In: YES user_id=129704 I tried the patch at http://al.blog.free.fr/mailman/mailman-vh-2.1.5.patch and it applied cleanly to mailman as provided by RHEL4. I tried to create a list called "list at domain1.com", but this failed with the error "Error: List name must not include "@"". Does this patch have any sort of instructions anywhere? ---------------------------------------------------------------------- Comment By: Arnaud Lavrard (arnaudlavrard) Date: 2005-07-20 09:52 Message: Logged In: YES user_id=1315788 I ported the patch to mailman 2.1.5 : http://al.blog.free.fr/mailman/mailman-vh-2.1.5.patch ---------------------------------------------------------------------- Comment By: The Anarcat (anarcat) Date: 2005-03-16 15:40 Message: Logged In: YES user_id=246797 I have ported the patch to 2.1.4, no news on 2.1.5 yet. I have also put the patch in a seperate CVS server. Fetch all the goods there: http://cvs.koumbit.net/cgi-bin/cvsweb/koumbit-maint/patches/mailman-true-virtual-2.1.1.patch http://cvs.koumbit.net/cgi-bin/cvsweb/koumbit-maint/patches/mailman-true-virtual-2.1.4.patch I've also updated the 2.1.1 patch to fix the list-id, so I delete the attachment, fetch the patch straight from our CVS for the latest fixes. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=943827&group_id=103 From noreply at sourceforge.net Sat Aug 23 02:40:49 2008 From: noreply at sourceforge.net (SourceForge.net) Date: Sat, 23 Aug 2008 00:40:49 +0000 Subject: [ mailman-Bugs-2068642 ] 2.1.11.rc2 crash Message-ID: Bugs item #2068642, was opened at 2008-08-22 19:40 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=2068642&group_id=103 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Pipermail Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Private: No Submitted By: measl (measl) Assigned to: Nobody/Anonymous (nobody) Summary: 2.1.11.rc2 crash Initial Comment: While I know this *looks* like an error caused by having no space... [root at lists /usr/home/crippen/mailman/bin]# df -h Filesystem Size Used Avail Capacity Mounted on /dev/idad0s1a 14G 6.9G 5.6G 55% / devfs 1.0K 1.0K 0B 100% /dev [root at lists /var/log/mailman]# cat error Aug 22 01:00:00 lists newsyslog[66511]: logfile turned over Aug 22 09:54:05 2008 (72778) No such list "ccm-l

": Aug 22 17:56:06 2008 (60050) Uncaught runner exception: [Errno 28] No space left on device Aug 22 17:56:06 2008 (60050) Traceback (most recent call last): File "/usr/home/crippen/mailman/Mailman/Queue/Runner.py", line 120, in _oneloop self._onefile(msg, msgdata) File "/usr/home/crippen/mailman/Mailman/Queue/Runner.py", line 191, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/home/crippen/mailman/Mailman/Queue/OutgoingRunner.py", line 130, in _dispose self.__retryq.enqueue(msg, msgdata) File "/usr/home/crippen/mailman/Mailman/Queue/Switchboard.py", line 138, in enqueue fp.write(msgsave) IOError: [Errno 28] No space left on device Aug 22 17:56:07 2008 (60050) Uncaught runner exception: [Errno 28] No space left on device Aug 22 17:56:07 2008 (60050) Traceback (most recent call last): File "/usr/home/crippen/mailman/Mailman/Queue/Runner.py", line 136, in _oneloop new_filebase = self._shunt.enqueue(msg, msgdata) File "/usr/home/crippen/mailman/Mailman/Queue/Switchboard.py", line 138, in enqueue fp.write(msgsave) IOError: [Errno 28] No space left on device Aug 22 17:56:07 2008 (60050) SHUNTING FAILED, preserving original entry: 1219445382.26142+9c9610d3ebaeef247239107563d4dc48eb1ca558 Aug 22 18:01:07 2008 (60050) Uncaught runner exception: [Errno 6] Device not configured Aug 22 18:01:07 2008 (60050) Traceback (most recent call last): File "/usr/home/crippen/mailman/Mailman/Queue/Runner.py", line 120, in _oneloop self._onefile(msg, msgdata) File "/usr/home/crippen/mailman/Mailman/Queue/Runner.py", line 191, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/home/crippen/mailman/Mailman/Queue/OutgoingRunner.py", line 74, in _dispose self._func(mlist, msg, msgdata) File "/usr/home/crippen/mailman/Mailman/Handlers/SMTPDirect.py", line 160, in process deliveryfunc(mlist, msg, msgdata, envsender, refused, conn) File "/usr/home/crippen/mailman/Mailman/Handlers/SMTPDirect.py", line 392, in bulkdeliver syslog('smtp-failure', 'Low level smtp error: %s, msgid: %s', e, msgid) File "/usr/home/crippen/mailman/Mailman/Logging/Syslog.py", line 43, in write self.write_ex(kind, msg, args, kws) File "/usr/home/crippen/mailman/Mailman/Logging/Syslog.py", line 62, in write_ex logf.write(msg + '\n') File "/usr/home/crippen/mailman/Mailman/Logging/StampedLogger.py", line 73, in write Logger.write(self, "%s %s" % (prefix, msg)) File "/usr/home/crippen/mailman/Mailman/Logging/Logger.py", line 94, in write _logexc(self, msg) File "/usr/home/crippen/mailman/Mailman/Logging/Utils.py", line 22, in _logexc sys.__stderr__.write('Logging error: %s\n' % logger) IOError: [Errno 6] Device not configured Aug 22 18:01:08 2008 (60050) SHUNTING: 1219445385.9258931+e43b5a83d97d6d0d8ab87a585adda24feec4785f Aug 22 18:57:19 2008 (60049) Uncaught runner exception: [Errno 28] No space left on device Aug 22 18:57:19 2008 (60049) Traceback (most recent call last): File "/usr/home/crippen/mailman/Mailman/Queue/Runner.py", line 120, in _oneloop self._onefile(msg, msgdata) File "/usr/home/crippen/mailman/Mailman/Queue/Runner.py", line 191, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/home/crippen/mailman/Mailman/Queue/VirginRunner.py", line 38, in _dispose return IncomingRunner._dispose(self, mlist, msg, msgdata) File "/usr/home/crippen/mailman/Mailman/Queue/IncomingRunner.py", line 130, in _dispose more = self._dopipeline(mlist, msg, msgdata, pipeline) File "/usr/home/crippen/mailman/Mailman/Queue/IncomingRunner.py", line 153, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File "/usr/home/crippen/mailman/Mailman/Handlers/ToOutgoing.py", line 55, in process outq.enqueue(msg, msgdata, listname=mlist.internal_name()) File "/usr/home/crippen/mailman/Mailman/Queue/Switchboard.py", line 138, in enqueue fp.write(msgsave) admin(81551): ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=2068642&group_id=103 From noreply at sourceforge.net Sat Aug 23 03:21:46 2008 From: noreply at sourceforge.net (SourceForge.net) Date: Sat, 23 Aug 2008 01:21:46 +0000 Subject: [ mailman-Bugs-2068642 ] 2.1.11.rc2 crash Message-ID: Bugs item #2068642, was opened at 2008-08-22 17:40 Message generated for change (Comment added) made by msapiro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=2068642&group_id=103 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Pipermail Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Private: No Submitted By: measl (measl) Assigned to: Nobody/Anonymous (nobody) Summary: 2.1.11.rc2 crash Initial Comment: While I know this *looks* like an error caused by having no space... [root at lists /usr/home/crippen/mailman/bin]# df -h Filesystem Size Used Avail Capacity Mounted on /dev/idad0s1a 14G 6.9G 5.6G 55% / devfs 1.0K 1.0K 0B 100% /dev [root at lists /var/log/mailman]# cat error Aug 22 01:00:00 lists newsyslog[66511]: logfile turned over Aug 22 09:54:05 2008 (72778) No such list "ccm-l

": Aug 22 17:56:06 2008 (60050) Uncaught runner exception: [Errno 28] No space left on device Aug 22 17:56:06 2008 (60050) Traceback (most recent call last): File "/usr/home/crippen/mailman/Mailman/Queue/Runner.py", line 120, in _oneloop self._onefile(msg, msgdata) File "/usr/home/crippen/mailman/Mailman/Queue/Runner.py", line 191, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/home/crippen/mailman/Mailman/Queue/OutgoingRunner.py", line 130, in _dispose self.__retryq.enqueue(msg, msgdata) File "/usr/home/crippen/mailman/Mailman/Queue/Switchboard.py", line 138, in enqueue fp.write(msgsave) IOError: [Errno 28] No space left on device Aug 22 17:56:07 2008 (60050) Uncaught runner exception: [Errno 28] No space left on device Aug 22 17:56:07 2008 (60050) Traceback (most recent call last): File "/usr/home/crippen/mailman/Mailman/Queue/Runner.py", line 136, in _oneloop new_filebase = self._shunt.enqueue(msg, msgdata) File "/usr/home/crippen/mailman/Mailman/Queue/Switchboard.py", line 138, in enqueue fp.write(msgsave) IOError: [Errno 28] No space left on device Aug 22 17:56:07 2008 (60050) SHUNTING FAILED, preserving original entry: 1219445382.26142+9c9610d3ebaeef247239107563d4dc48eb1ca558 Aug 22 18:01:07 2008 (60050) Uncaught runner exception: [Errno 6] Device not configured Aug 22 18:01:07 2008 (60050) Traceback (most recent call last): File "/usr/home/crippen/mailman/Mailman/Queue/Runner.py", line 120, in _oneloop self._onefile(msg, msgdata) File "/usr/home/crippen/mailman/Mailman/Queue/Runner.py", line 191, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/home/crippen/mailman/Mailman/Queue/OutgoingRunner.py", line 74, in _dispose self._func(mlist, msg, msgdata) File "/usr/home/crippen/mailman/Mailman/Handlers/SMTPDirect.py", line 160, in process deliveryfunc(mlist, msg, msgdata, envsender, refused, conn) File "/usr/home/crippen/mailman/Mailman/Handlers/SMTPDirect.py", line 392, in bulkdeliver syslog('smtp-failure', 'Low level smtp error: %s, msgid: %s', e, msgid) File "/usr/home/crippen/mailman/Mailman/Logging/Syslog.py", line 43, in write self.write_ex(kind, msg, args, kws) File "/usr/home/crippen/mailman/Mailman/Logging/Syslog.py", line 62, in write_ex logf.write(msg + '\n') File "/usr/home/crippen/mailman/Mailman/Logging/StampedLogger.py", line 73, in write Logger.write(self, "%s %s" % (prefix, msg)) File "/usr/home/crippen/mailman/Mailman/Logging/Logger.py", line 94, in write _logexc(self, msg) File "/usr/home/crippen/mailman/Mailman/Logging/Utils.py", line 22, in _logexc sys.__stderr__.write('Logging error: %s\n' % logger) IOError: [Errno 6] Device not configured Aug 22 18:01:08 2008 (60050) SHUNTING: 1219445385.9258931+e43b5a83d97d6d0d8ab87a585adda24feec4785f Aug 22 18:57:19 2008 (60049) Uncaught runner exception: [Errno 28] No space left on device Aug 22 18:57:19 2008 (60049) Traceback (most recent call last): File "/usr/home/crippen/mailman/Mailman/Queue/Runner.py", line 120, in _oneloop self._onefile(msg, msgdata) File "/usr/home/crippen/mailman/Mailman/Queue/Runner.py", line 191, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/home/crippen/mailman/Mailman/Queue/VirginRunner.py", line 38, in _dispose return IncomingRunner._dispose(self, mlist, msg, msgdata) File "/usr/home/crippen/mailman/Mailman/Queue/IncomingRunner.py", line 130, in _dispose more = self._dopipeline(mlist, msg, msgdata, pipeline) File "/usr/home/crippen/mailman/Mailman/Queue/IncomingRunner.py", line 153, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File "/usr/home/crippen/mailman/Mailman/Handlers/ToOutgoing.py", line 55, in process outq.enqueue(msg, msgdata, listname=mlist.internal_name()) File "/usr/home/crippen/mailman/Mailman/Queue/Switchboard.py", line 138, in enqueue fp.write(msgsave) admin(81551): ---------------------------------------------------------------------- >Comment By: Mark Sapiro (msapiro) Date: 2008-08-22 18:21 Message: Logged In: YES user_id=1123998 Originator: NO df notwithstanding, how is this a Mailman issue? Is it possible you're running into a user quota? In most of the above tracebacks, Mailman has successfully opened a tempfile to build a queue entry, and is denied by the OS with "[Errno 28] No space left on device". There's not much Mailman can do about that. In the case of the logging error, Mailman is attempting to write to the smtp-failure log and hits an IOError exception (possibly error 28) and tries to fall back to the original stderr which is probably the console that started Mailman and is long since detached from the process and gets the "[Errno 6] Device not configured" and logs that exception to the error log. The OS is not letting Mailman write to some files (but apparently the error log is OK). Mailman can't do anything about that. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=2068642&group_id=103 From noreply at sourceforge.net Mon Aug 25 23:58:30 2008 From: noreply at sourceforge.net (SourceForge.net) Date: Mon, 25 Aug 2008 21:58:30 +0000 Subject: [ mailman-Bugs-2074453 ] allow message display to wrap (simple HTML provided) Message-ID: Bugs item #2074453, was opened at 2008-08-25 14:58 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=2074453&group_id=103 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Private: No Submitted By: S Page (skierpage) Assigned to: Nobody/Anonymous (nobody) Summary: allow message display to wrap (simple HTML provided) Initial Comment: I browse the archives of many mailing lists created by Mailman. I love its ASCII preformatted display, but many messages to mailing lists are not word-wrapped and so each paragraph appears as a few unreadably long lines. For example, http://lists.freedesktop.org/archives/xorg/2008-August/038178.html, and resize your browser window wider and narrower. Modern browsers support the CSS "white-space" property to display long lines wrapped to fit the window, see http://archivist.incutio.com/viewlist/css-discuss/55677 I modified the 
 tag in that Mailman message to use this CSS style and it now displays fine (in Firefox 3.1a2 and MSIE7 on Windows XP), see http://www.skierpage.com/moz_bugs/pre_wrap_test.html , resize your browser window wider and narrower, and view its source.

This *does not* affect copy and paste of long lines and does not involve processing or changing the text within the pre tag in any way.  It just makes many more messages readable!

The new pre tag is



Please consider making the change in a future Mailman release.  In appreciation of your consideration I donated $10 to GNU Mailman.

P.S.  In order to pass strict validation, adding a style means you have to specify the HTML 4.01 Transitional DOCTYPE.  I did in my modified file and passes 100%. According to validator.w3.org, the original DOCTYPE in Mailman's HTML output (  ) is invalid anyway.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=2074453&group_id=103

From noreply at sourceforge.net  Tue Aug 26 02:32:51 2008
From: noreply at sourceforge.net (SourceForge.net)
Date: Tue, 26 Aug 2008 00:32:51 +0000
Subject: [ mailman-Bugs-2074453 ] allow message display to wrap (simple HTML
	provided)
Message-ID: 

Bugs item #2074453, was opened at 2008-08-25 14:58
Message generated for change (Comment added) made by msapiro
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=2074453&group_id=103

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Web/CGI
Group: 2.1 (stable)
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: S Page (skierpage)
Assigned to: Nobody/Anonymous (nobody)
Summary: allow message display to wrap (simple HTML provided)

Initial Comment:
I browse the archives of many mailing lists created by Mailman.

I love its ASCII preformatted display, but many messages to mailing lists are not word-wrapped and so each paragraph appears as a few unreadably long lines.  For example, http://lists.freedesktop.org/archives/xorg/2008-August/038178.html, and resize your browser window wider and narrower.

Modern browsers support the CSS "white-space" property to display long lines wrapped to fit the window, see http://archivist.incutio.com/viewlist/css-discuss/55677

I modified the 
 tag in that Mailman message to use this CSS style and it now displays fine (in Firefox 3.1a2 and MSIE7 on Windows XP), see http://www.skierpage.com/moz_bugs/pre_wrap_test.html , resize your browser window wider and narrower, and view its source.

This *does not* affect copy and paste of long lines and does not involve processing or changing the text within the pre tag in any way.  It just makes many more messages readable!

The new pre tag is



Please consider making the change in a future Mailman release.  In appreciation of your consideration I donated $10 to GNU Mailman.

P.S.  In order to pass strict validation, adding a style means you have to specify the HTML 4.01 Transitional DOCTYPE.  I did in my modified file and passes 100%. According to validator.w3.org, the original DOCTYPE in Mailman's HTML output (  ) is invalid anyway.

----------------------------------------------------------------------

>Comment By: Mark Sapiro (msapiro)
Date: 2008-08-25 17:32

Message:
Logged In: YES 
user_id=1123998
Originator: NO

Thank you for the suggested style. It looks promising.

It is not clear to me whether you operate a Mailman site or are just a
member of lists, but a site can easily accomplish what you've done by
making site/language versions of the article.html template per
 with the following changes:

Change the doctype declaration to



and add the following style in the  section



Of course the browser specific parts of the style don't pass validation at
 but that's not unexpected. Note
however that the valid style



alone appears sufficient in Firefox 3.0.1, Opera 9.51 and Safari 3.1.2,
but not in Camino 1.6.3 or MSIE 7.0 and adding

  white-space: -moz-pre-wrap;

works in Camino.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=2074453&group_id=103

From noreply at sourceforge.net  Tue Aug 26 02:57:41 2008
From: noreply at sourceforge.net (SourceForge.net)
Date: Tue, 26 Aug 2008 00:57:41 +0000
Subject: [ mailman-Bugs-2074653 ] error encoding
Message-ID: 

Bugs item #2074653, was opened at 2008-08-26 08:57
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=2074653&group_id=103

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: 2.1 (stable)
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Liu Junmin (openread)
Assigned to: Nobody/Anonymous (nobody)
Summary: error encoding

Initial Comment:
At  /mailman-2.1.11rc2/templates/zh_CN/  have four file is gb2312 encoding, but correct encoding is UTF-8.The files is 
postack.txt
postauth.txt
postheld.txt
unsub.txt
This files can be using send wrong encoding message to user.


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=2074653&group_id=103

From noreply at sourceforge.net  Tue Aug 26 05:12:35 2008
From: noreply at sourceforge.net (SourceForge.net)
Date: Tue, 26 Aug 2008 03:12:35 +0000
Subject: [ mailman-Bugs-2074653 ] error encoding
Message-ID: 

Bugs item #2074653, was opened at 2008-08-25 17:57
Message generated for change (Comment added) made by msapiro
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=2074653&group_id=103

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: 2.1 (stable)
>Status: Closed
>Resolution: Fixed
Priority: 5
Private: No
Submitted By: Liu Junmin (openread)
>Assigned to: Mark Sapiro (msapiro)
Summary: error encoding

Initial Comment:
At  /mailman-2.1.11rc2/templates/zh_CN/  have four file is gb2312 encoding, but correct encoding is UTF-8.The files is 
postack.txt
postauth.txt
postheld.txt
unsub.txt
This files can be using send wrong encoding message to user.


----------------------------------------------------------------------

>Comment By: Mark Sapiro (msapiro)
Date: 2008-08-25 20:12

Message:
Logged In: YES 
user_id=1123998
Originator: NO

Fixed in the Bazaar repository on Launchpad for the 2.1 and 2.2 branches.

Thank you for your help.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=2074653&group_id=103

From noreply at sourceforge.net  Thu Aug 28 22:37:43 2008
From: noreply at sourceforge.net (SourceForge.net)
Date: Thu, 28 Aug 2008 20:37:43 +0000
Subject: [ mailman-Bugs-2081096 ] Misleading text
Message-ID: 

Bugs item #2081096, was opened at 2008-08-28 13:37
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=2081096&group_id=103

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: (un)subscribing
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: m1ss1ontomars (m1ss1ontomars)
Assigned to: Nobody/Anonymous (nobody)
Summary: Misleading text

Initial Comment:
Mailman is used at UC Berkeley for mailing list management. Unfortunately, many students (not me, obviously) are being confused by what appears to be a standard introductory text:

"To post to this list, send your email to:"

At least two people thought that they should send their email address to the given address in order to join the mailing list, thus spamming everyone on the list.

I suggest that this be changed to:

"To post to this list, send the email to:"

Or basically anything other than what is currently standard.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=2081096&group_id=103

From noreply at sourceforge.net  Fri Aug 29 04:53:35 2008
From: noreply at sourceforge.net (SourceForge.net)
Date: Fri, 29 Aug 2008 02:53:35 +0000
Subject: [ mailman-Bugs-2081096 ] Misleading text
Message-ID: 

Bugs item #2081096, was opened at 2008-08-28 13:37
Message generated for change (Comment added) made by msapiro
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=2081096&group_id=103

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: (un)subscribing
Group: None
>Status: Closed
>Resolution: Fixed
Priority: 5
Private: No
Submitted By: m1ss1ontomars (m1ss1ontomars)
>Assigned to: Mark Sapiro (msapiro)
Summary: Misleading text

Initial Comment:
Mailman is used at UC Berkeley for mailing list management. Unfortunately, many students (not me, obviously) are being confused by what appears to be a standard introductory text:

"To post to this list, send your email to:"

At least two people thought that they should send their email address to the given address in order to join the mailing list, thus spamming everyone on the list.

I suggest that this be changed to:

"To post to this list, send the email to:"

Or basically anything other than what is currently standard.

----------------------------------------------------------------------

>Comment By: Mark Sapiro (msapiro)
Date: 2008-08-28 19:53

Message:
Logged In: YES 
user_id=1123998
Originator: NO

I assume you are talking about the text in the "welcome" email sent to new
members.

I will change this to "To post to this list, send your message to:" for
Mailman 2.2.

In the mean time, note that any list admin can change this text and
anything else in the welcome email for the list by going to the list admin
-> Edit the public HTML pages and text files link and editing the Welcome
email text file. In addition, the Mailman site admin can follow the
instructions at  and make a site wide version
of the subscribeack.txt template (the welcome message).

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=2081096&group_id=103

From noreply at sourceforge.net  Fri Aug 29 06:10:38 2008
From: noreply at sourceforge.net (SourceForge.net)
Date: Fri, 29 Aug 2008 04:10:38 +0000
Subject: [ mailman-Bugs-2081096 ] Misleading text
Message-ID: 

Bugs item #2081096, was opened at 2008-08-28 13:37
Message generated for change (Comment added) made by m1ss1ontomars
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=2081096&group_id=103

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: (un)subscribing
Group: None
Status: Closed
Resolution: Fixed
Priority: 5
Private: No
Submitted By: m1ss1ontomars (m1ss1ontomars)
Assigned to: Mark Sapiro (msapiro)
Summary: Misleading text

Initial Comment:
Mailman is used at UC Berkeley for mailing list management. Unfortunately, many students (not me, obviously) are being confused by what appears to be a standard introductory text:

"To post to this list, send your email to:"

At least two people thought that they should send their email address to the given address in order to join the mailing list, thus spamming everyone on the list.

I suggest that this be changed to:

"To post to this list, send the email to:"

Or basically anything other than what is currently standard.

----------------------------------------------------------------------

>Comment By: m1ss1ontomars (m1ss1ontomars)
Date: 2008-08-28 21:10

Message:
Logged In: YES 
user_id=1976087
Originator: YES

Yeah, thanks; that sums it up nicely. At any rate I tried to send an email
to whoever maintains Mailman; hopefully someone who can do something knows
how to fix it.

----------------------------------------------------------------------

Comment By: Mark Sapiro (msapiro)
Date: 2008-08-28 19:53

Message:
Logged In: YES 
user_id=1123998
Originator: NO

I assume you are talking about the text in the "welcome" email sent to new
members.

I will change this to "To post to this list, send your message to:" for
Mailman 2.2.

In the mean time, note that any list admin can change this text and
anything else in the welcome email for the list by going to the list admin
-> Edit the public HTML pages and text files link and editing the Welcome
email text file. In addition, the Mailman site admin can follow the
instructions at  and make a site wide version
of the subscribeack.txt template (the welcome message).

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=2081096&group_id=103