Mailman 3 November 2002 - Mailman-Developers

[ mailman-Bugs-563336 ] Unexpected MMBadUserError with MM-2.0.11
by noreply＠sourceforge.net 27 Nov '02

27 Nov '02

Bugs item #563336, was opened at 2002-06-01 12:48 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=563336&group_i… Category: (un)subscribing Group: 2.0.x Status: Open Resolution: None >Priority: 1 Submitted By: Federico Sevilla III (jijo) Assigned to: Nobody/Anonymous (nobody) Summary: Unexpected MMBadUserError with MM-2.0.11 Initial Comment: Just upgraded to Mailman 2.0.11. The upgrade itself worked fine, and basic tests after the upgrade seem to have worked okay, and mail has been getting delivered. However I got an email (as administrator) about an unexpected Mailman error. I have yet to get a complaint from our users so I do not know exactly what caused the problem. All I can deduce from the logs is that at around the same time, someone was subscribing/unsubscribing via email. The error message I got by email was: -----[ START ]----- An unexpected Mailman error has occurred in MailCommandHandler.ParseMailCommands(). Here is the traceback: Traceback (most recent call last): File "/usr/lib/mailman/Mailman/MailCommandHandler.py", line 223, in ParseMailCommands self.__dispatch[cmd](args, line, msg) File "/usr/lib/mailman/Mailman/MailCommandHandler.py", line 364, in ProcessSetCmd self.ConfirmUserPassword(sender, args[2]) File "/usr/lib/mailman/Mailman/SecurityManager.py", line 144, in ConfirmUserPassword raise Errors.MMBadUserError MMBadUserError -----[ END ]----- Some more miscellaneous information: - system is Debian GNU/Linux - mailman package is mailman-2.0.11-1 - python package is python-2.1.3-3 If anyone has tips as to where to dig for more information on the cause of this unexpected error, please do let me know and I will be more than happy to supply the missing details. It would also help calm my nerves if I knew whether this was fatal or not. :) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=563336&group_i…

1 0

[ mailman-Bugs-611185 ] rmlist doesn't delete lock files
by noreply＠sourceforge.net 27 Nov '02

27 Nov '02

Bugs item #611185, was opened at 2002-09-18 13:23 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=611185&group_i… Category: command line scripts Group: 2.0.x Status: Open Resolution: None >Priority: 1 Submitted By: Linda Julien (leira) Assigned to: Nobody/Anonymous (nobody) Summary: rmlist doesn't delete lock files Initial Comment: I'm using 2.0.13. The rmlist script doesn't delete lock files associated with the list (if any exist). Removing a list and creating a new one with the same name can have unexpected results. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=611185&group_i…

1 0

[ mailman-Bugs-612784 ] feature-request : Use of Spamassassintag
by noreply＠sourceforge.net 27 Nov '02

27 Nov '02

Bugs item #612784, was opened at 2002-09-22 06:20 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=612784&group_i… Category: mail delivery Group: 2.0.x Status: Open Resolution: None >Priority: 1 Submitted By: Alexandre Dulaunoy (adulau) Assigned to: Nobody/Anonymous (nobody) Summary: feature-request : Use of Spamassassintag Initial Comment: Mail::SpamAssassin is adding a tag when He suspects to be a spam. Do you plan to add a test on it and not forward mail into the mailing if the tag is present ? It's also useful when the list is moderated. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=612784&group_i…

1 0

[ mailman-Bugs-610265 ] Bad date field causes archiver to crash
by noreply＠sourceforge.net 27 Nov '02

27 Nov '02

Bugs item #610265, was opened at 2002-09-16 19:31 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=610265&group_i… Category: command line scripts Group: 2.0.x Status: Open Resolution: None >Priority: 1 Submitted By: Tim Potter (tpot) Assigned to: Nobody/Anonymous (nobody) Summary: Bad date field causes archiver to crash Initial Comment: The following date header causes the archiver to crash with an exception. Date: Fri, 1 Jan 1904 10:52:29 +1000 Traceback (innermost last): File "/var/mailman/bin/arch", line 129, in ? main() File "/var/mailman/bin/arch", line 119, in main archiver.close() File "/var/mailman/Mailman/Archiver/pipermail.py", line 306, in close self.write_TOC() File "/var/mailman/Mailman/Archiver/HyperArch.py", line 897, in write_TOC self.sortarchives() File "/var/mailman/Mailman/Archiver/HyperArch.py", line 835, in sortarchives self.archives.sort(sf) File "/var/mailman/Mailman/Archiver/HyperArch.py", line 826, in sf al=s.volNameToDate(a) File "/var/mailman/Mailman/Archiver/HyperArch.py", line 821, in volNameToDate return time.mktime((year,month,1,0,0,0,0,1,-1)) OverflowError: mktime argument out of range [whoops - the line numbers are out by one because I added some debugging] [tpot@dp:~]$ rpm -qa | grep mailman mailman-2.0.11-1 Regards, Tim. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=610265&group_i…

1 0

[ mailman-Bugs-608524 ] QRUNNER is fucking the machine perform..
by noreply＠sourceforge.net 27 Nov '02

27 Nov '02

Bugs item #608524, was opened at 2002-09-12 13:49 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=608524&group_i… Category: mail delivery Group: 2.0.x Status: Open Resolution: None >Priority: 1 Submitted By: Jozeph Brasil (jozeph) Assigned to: Nobody/Anonymous (nobody) Summary: QRUNNER is fucking the machine perform.. Initial Comment: Hello Everybody, I'm with a big problem... :( I'm running mailman-2.0.13-1U70_1cl under python-2.1-14cl with gcc-2.95.3-20U70_1cl in an IBM NETFINITY 300 PIII 500 XEXON with 64MiB. When qrunner starts the proccess my machine stay totally SLOWLY... Look the qrunner proccess: mailman 12365 95.7 51.2 32340 30092 tty1 R 15:27 4:37 python -S cron/qrunner How you can see... look at the CPU / MEM usage... I need to wait more less 30 minutes to qrunner stop the proccess and... In qfiles directory have only 10 or 15 messages in delivery... Anyone have idea what's up? How fix that? PS: I disable my mailman at moment... :( ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=608524&group_i…

1 0

[ mailman-Bugs-634274 ] Some digest seems to have a wrong
by noreply＠sourceforge.net 27 Nov '02

27 Nov '02

Bugs item #634274, was opened at 2002-11-06 01:34 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=634274&group_i… Category: mail delivery Group: 2.0.x Status: Open Resolution: None >Priority: 1 Submitted By: divine rites (divinerites) Assigned to: Nobody/Anonymous (nobody) Summary: Some digest seems to have a wrong Initial Comment: Some Zope digests looks ugly with Evolution. Some digests on some lists are concerned. Not predictable. Digest should look like all normal ones (like for all digests who works fine in evolution) This link give the whole explanation for the digest problem from the evolution point of view. It seems that the mail has some wrong type. http://bugzilla.ximian.com/show_bug.cgi?id=33282 I don't know what Mailman version it is but i guess zope lists use a brand new mailman ;-)) ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-11-07 15:44 Message: Logged In: YES user_id=12800 Actually the Zope lists use Mailman 2.0. I've tested this for MM2.1 plaintext (RFC 1153) digest and can't verify it, so I suspct it's no longer a bug. If it's happening in MM2.0 I can't see it in the code, but I doubt it will get fixed in that branch. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=634274&group_i…

1 0

[ mailman-Bugs-631200 ] qrunner in loop, keeps eating memory
by noreply＠sourceforge.net 27 Nov '02

27 Nov '02

Bugs item #631200, was opened at 2002-10-30 14:28 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=631200&group_i… Category: command line scripts Group: 2.0.x Status: Open Resolution: None >Priority: 1 Submitted By: Andreas Hasenack (pandora) Assigned to: Nobody/Anonymous (nobody) Summary: qrunner in loop, keeps eating memory Initial Comment: mailman-2.0.13 python-2.2.1 Every now and then qrunner goes nuts and starts eating up all available memory on the system. I'm attaching a .msg and .db file which seems to reproduce the problem at all times, and also a log trace which showed up in the error log when I pressed CTRL-C. This last log shows where qrunner was looping, and it's in pickle.loads (log below). Oct 30 16:06:47 2002 qrunner(25698): Traceback (most recent call last): Oct 30 16:06:47 2002 qrunner(25698): File "/usr/lib/mailman/Mailman/Archiver/Archiver.py", line 222, in ArchiveMail Oct 30 16:06:47 2002 qrunner(25698): h.close() Oct 30 16:06:47 2002 qrunner(25698): File "/usr/lib/mailman/Mailman/Archiver/pipermail.py", line 304, in close Oct 30 16:06:47 2002 qrunner(25698): self.update_dirty_archives() Oct 30 16:06:47 2002 qrunner(25698): File "/usr/lib/mailman/Mailman/Archiver/HyperArch.py", line 935, in update_dirty _archives Oct 30 16:06:47 2002 qrunner(25698): self.__super_update_dirty_archives() Oct 30 16:06:47 2002 qrunner(25698): File "/usr/lib/mailman/Mailman/Archiver/pipermail.py", line 513, in update_dirty _archives Oct 30 16:06:47 2002 qrunner(25698): self.update_archive(i) Oct 30 16:06:47 2002 qrunner(25698): File "/usr/lib/mailman/Mailman/Archiver/HyperArch.py", line 938, in update_archi ve Oct 30 16:06:47 2002 qrunner(25698): self.__super_update_archive(archive) Oct 30 16:06:47 2002 qrunner(25698): File "/usr/lib/mailman/Mailman/Archiver/pipermail.py", line 420, in update_archi ve Oct 30 16:06:47 2002 qrunner(25698): self._update_simple_index(hdr, archive, arcdir) Oct 30 16:06:47 2002 qrunner(25698): File "/usr/lib/mailman/Mailman/Archiver/pipermail.py", line 437, in _update_simp le_index Oct 30 16:06:47 2002 qrunner(25698): article = self.database.getArticle(self.archive, msgid) Oct 30 16:06:47 2002 qrunner(25698): File "/usr/lib/mailman/Mailman/Archiver/HyperDatabase.py", line 281, in getArtic le Oct 30 16:06:47 2002 qrunner(25698): article = self.__cache[msgid] = pickle.loads(buf) Oct 30 16:06:47 2002 qrunner(25698): File "<string>", line 0, in ? Oct 30 16:06:47 2002 qrunner(25698): KeyboardInterrupt Oct 30 16:06:47 2002 (25698) CORRUPT ARCHIVE FOR LIST: commits I don't know if the CORRUPT ARCHIVE message is due to me pressing CTRL-C or if there is actually something wrong with it. Any help would be greatly appreciated. Thanks. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=631200&group_i…

1 0

[ mailman-Bugs-631447 ] error during subscription process
by noreply＠sourceforge.net 27 Nov '02

27 Nov '02

Bugs item #631447, was opened at 2002-10-31 04:18 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=631447&group_i… Category: (un)subscribing Group: 2.0.x Status: Open Resolution: None >Priority: 1 Submitted By: Carlo Meme' (cmeme) Assigned to: Nobody/Anonymous (nobody) Summary: error during subscription process Initial Comment: One user trying to subscribe got the following email message: Bug in Mailman version 2.0.13 We're sorry, we hit a bug! The information in the log are: admin(8347): [----- Mailman Version: 2.0.13 -----] admin(8347): [----- Traceback ------] admin(8347): Traceback (innermost last): admin(8347): File "/var/mailman/scripts/driver", line 96, in run_main admin(8347): main() admin(8347): File "/var/mailman/Mailman/Cgi/subscribe.py", line 76, in main admin(8347): process_form(mlist, doc) admin(8347): File "/var/mailman/Mailman/Cgi/subscribe.py", line 104, in process_form admin(8347): if form.has_key("UserOptions") or \ admin(8347): File "/var/mailman/Mailman/pythonlib/cgi.py", line 564, in has_key admin(8347): raise TypeError, "not indexable" admin(8347): TypeError: not indexable admin(8347): [----- Python Information -----] admin(8347): sys.version = 1.5.2 (#1, Jul 5 2001, 03:02:19) [GCC 2.96 20000731 (Red Hat Linux 7.1 2 admin(8347): sys.executable = /usr/bin/python admin(8347): sys.prefix = /usr admin(8347): sys.exec_prefix= /usr admin(8347): sys.path = /usr admin(8347): sys.platform = linux-i386 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=631447&group_i…

1 0

[ mailman-Bugs-631186 ] Postfix msg.type
by noreply＠sourceforge.net 27 Nov '02

27 Nov '02

Bugs item #631186, was opened at 2002-10-30 14:02 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=631186&group_i… Category: bounce detection Group: 2.0.x Status: Open Resolution: None >Priority: 1 Submitted By: Gregory Karpinsky, TIV.NET Inc. (tivnet) Assigned to: Nobody/Anonymous (nobody) Summary: Postfix msg.type Initial Comment: In Postfix.py, I replaced 'multipart/mixed' with 'multipart/report' -- and now the bouncing works for me. I have: postfix-20011210_1 mailman-2.0.13 gregory at tiv.net ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=631186&group_i…

1 0

[ mailman-Bugs-634026 ] Spurious option text on subscription GUI
by noreply＠sourceforge.net 27 Nov '02

27 Nov '02

Bugs item #634026, was opened at 2002-11-05 15:25 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=634026&group_i… Category: Web/CGI Group: 2.0.x Status: Open Resolution: None >Priority: 1 Submitted By: John A. Martin (jamux) Assigned to: Nobody/Anonymous (nobody) Summary: Spurious option text on subscription GUI Initial Comment: Mailman version 2.0.13 Nondigest option: nondigestable = 1 Subscription Page with option text without radio button confuses subscriber. Would you like to receive list mail batched in a daily digest? No Yes ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=634026&group_i…

1 0