Mailman 3 December 2003 - Mailman-coders

[ mailman-Bugs-853235 ] IncomingRunner reached maximum restart limit of 10
by SourceForge.net 04 Dec '03

04 Dec '03

Bugs item #853235, was opened at 2003-12-03 03:52 Message generated for change (Comment added) made by emechler You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=853235&group_i… Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 7 Submitted By: Erick Mechler (emechler) Assigned to: Nobody/Anonymous (nobody) Summary: IncomingRunner reached maximum restart limit of 10 Initial Comment: I just upgraded to 2.1 from 2.0.13, and I'm getting these errors when trying to startup the qrunner from the startup script (this is from the $MAILMAN/logs/qrunner log file): Dec 03 03:40:43 2003 (91944) ArchRunner qrunner started. Dec 03 03:40:43 2003 (91950) VirginRunner qrunner started. Dec 03 03:40:43 2003 (91947) IncomingRunner qrunner started. Dec 03 03:40:43 2003 (91945) BounceRunner qrunner started. Dec 03 03:40:44 2003 (91949) OutgoingRunner qrunner started. Dec 03 03:40:44 2003 (91948) NewsRunner qrunner started. Dec 03 03:40:44 2003 (91946) CommandRunner qrunner started. Dec 03 03:40:44 2003 (91951) RetryRunner qrunner started. Dec 03 03:40:44 2003 (91943) Master qrunner detected subprocess exit (pid: 91947, sig: None, sts: 1, class: IncomingRunner, slice: 1/1) [restarting] Dec 03 03:40:44 2003 (91952) IncomingRunner qrunner started. Dec 03 03:40:44 2003 (91943) Master qrunner detected subprocess exit (pid: 91952, sig: None, sts: 1, class: IncomingRunner, slice: 1/1) [restarting] Dec 03 03:40:44 2003 (91953) IncomingRunner qrunner started. Dec 03 03:40:44 2003 (91943) Master qrunner detected subprocess exit (pid: 91953, sig: None, sts: 1, class: IncomingRunner, slice: 1/1) [restarting] Dec 03 03:40:45 2003 (91954) IncomingRunner qrunner started. Dec 03 03:40:45 2003 (91943) Master qrunner detected subprocess exit (pid: 91954, sig: None, sts: 1, class: IncomingRunner, slice: 1/1) [restarting] Dec 03 03:40:47 2003 (91955) IncomingRunner qrunner started. Dec 03 03:40:47 2003 (91943) Master qrunner detected subprocess exit (pid: 91955, sig: None, sts: 1, class: IncomingRunner, slice: 1/1) [restarting] Dec 03 03:40:47 2003 (91956) IncomingRunner qrunner started. Dec 03 03:40:47 2003 (91943) Master qrunner detected subprocess exit (pid: 91956, sig: None, sts: 1, class: IncomingRunner, slice: 1/1) [restarting] Dec 03 03:40:47 2003 (91957) IncomingRunner qrunner started. Dec 03 03:40:47 2003 (91943) Master qrunner detected subprocess exit (pid: 91957, sig: None, sts: 1, class: IncomingRunner, slice: 1/1) [restarting] Dec 03 03:40:48 2003 (91958) IncomingRunner qrunner started. Dec 03 03:40:48 2003 (91943) Master qrunner detected subprocess exit (pid: 91958, sig: None, sts: 1, class: IncomingRunner, slice: 1/1) [restarting] Dec 03 03:40:48 2003 (91959) IncomingRunner qrunner started. Dec 03 03:40:48 2003 (91943) Master qrunner detected subprocess exit (pid: 91959, sig: None, sts: 1, class: IncomingRunner, slice: 1/1) [restarting] Dec 03 03:40:49 2003 (91960) IncomingRunner qrunner started. Dec 03 03:40:49 2003 (91943) Master qrunner detected subprocess exit (pid: 91960, sig: None, sts: 1, class: IncomingRunner, slice: 1/1) [restarting] Dec 03 03:40:50 2003 (91961) IncomingRunner qrunner started. Dec 03 03:40:50 2003 (91943) Master qrunner detected subprocess exit (pid: 91961, sig: None, sts: 1, class: IncomingRunner, slice: 1/1) [restarting] Dec 03 03:40:50 2003 (91943) Qrunner IncomingRunner reached maximum restart limit of 10, not re starting. On the console, I'm getting these errors which might be more useful (just pasting 1 here, the other 9 are exactly the same) Traceback (most recent call last): File "/usr/local/mailman/bin/qrunner", line 270, in ? main() File "/usr/local/mailman/bin/qrunner", line 230, in main qrunner.run() File "/usr/local/mailman/Mailman/Queue/Runner.py", line 65, in run filecnt = self._oneloop() File "/usr/local/mailman/Mailman/Queue/Runner.py", line 93, in _oneloop msg, msgdata = self._switchboard.dequeue(filebase) File "/usr/local/mailman/Mailman/Queue/Switchboard.py", line 158, in dequeue data = self._ext_read(dbfile) File "/usr/local/mailman/Mailman/Queue/Switchboard.py", line 264, in _ext_read dict = marshal.load(fp) EOFError: EOF read where object expected I'm running this on FreeBSD 4.9-STABLE, mailman version 2.1.3, python 2.3.2 (both out of the ports tree). Any help you can send my way is much appreciated. Cheers - Erick emechler(a)techometer.net ---------------------------------------------------------------------- >Comment By: Erick Mechler (emechler) Date: 2003-12-04 01:04 Message: Logged In: YES user_id=922815 Please disregard this bug report. It appears that I had a bad .db file in $PREFIX/qfiles/in/ that was causing the marshal.load function to choke. Perhaps as a feature request, however, when you can't open a file you give some indication as to which one it is. Just a thought :) Thanks - Erick ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=853235&group_i…

1 0

[ mailman-Bugs-853235 ] IncomingRunner reached maximum restart limit of 10
by SourceForge.net 03 Dec '03

03 Dec '03

Bugs item #853235, was opened at 2003-12-03 03:52 Message generated for change (Settings changed) made by emechler You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=853235&group_i… Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None >Priority: 7 Submitted By: Erick Mechler (emechler) Assigned to: Nobody/Anonymous (nobody) Summary: IncomingRunner reached maximum restart limit of 10 Initial Comment: I just upgraded to 2.1 from 2.0.13, and I'm getting these errors when trying to startup the qrunner from the startup script (this is from the $MAILMAN/logs/qrunner log file): Dec 03 03:40:43 2003 (91944) ArchRunner qrunner started. Dec 03 03:40:43 2003 (91950) VirginRunner qrunner started. Dec 03 03:40:43 2003 (91947) IncomingRunner qrunner started. Dec 03 03:40:43 2003 (91945) BounceRunner qrunner started. Dec 03 03:40:44 2003 (91949) OutgoingRunner qrunner started. Dec 03 03:40:44 2003 (91948) NewsRunner qrunner started. Dec 03 03:40:44 2003 (91946) CommandRunner qrunner started. Dec 03 03:40:44 2003 (91951) RetryRunner qrunner started. Dec 03 03:40:44 2003 (91943) Master qrunner detected subprocess exit (pid: 91947, sig: None, sts: 1, class: IncomingRunner, slice: 1/1) [restarting] Dec 03 03:40:44 2003 (91952) IncomingRunner qrunner started. Dec 03 03:40:44 2003 (91943) Master qrunner detected subprocess exit (pid: 91952, sig: None, sts: 1, class: IncomingRunner, slice: 1/1) [restarting] Dec 03 03:40:44 2003 (91953) IncomingRunner qrunner started. Dec 03 03:40:44 2003 (91943) Master qrunner detected subprocess exit (pid: 91953, sig: None, sts: 1, class: IncomingRunner, slice: 1/1) [restarting] Dec 03 03:40:45 2003 (91954) IncomingRunner qrunner started. Dec 03 03:40:45 2003 (91943) Master qrunner detected subprocess exit (pid: 91954, sig: None, sts: 1, class: IncomingRunner, slice: 1/1) [restarting] Dec 03 03:40:47 2003 (91955) IncomingRunner qrunner started. Dec 03 03:40:47 2003 (91943) Master qrunner detected subprocess exit (pid: 91955, sig: None, sts: 1, class: IncomingRunner, slice: 1/1) [restarting] Dec 03 03:40:47 2003 (91956) IncomingRunner qrunner started. Dec 03 03:40:47 2003 (91943) Master qrunner detected subprocess exit (pid: 91956, sig: None, sts: 1, class: IncomingRunner, slice: 1/1) [restarting] Dec 03 03:40:47 2003 (91957) IncomingRunner qrunner started. Dec 03 03:40:47 2003 (91943) Master qrunner detected subprocess exit (pid: 91957, sig: None, sts: 1, class: IncomingRunner, slice: 1/1) [restarting] Dec 03 03:40:48 2003 (91958) IncomingRunner qrunner started. Dec 03 03:40:48 2003 (91943) Master qrunner detected subprocess exit (pid: 91958, sig: None, sts: 1, class: IncomingRunner, slice: 1/1) [restarting] Dec 03 03:40:48 2003 (91959) IncomingRunner qrunner started. Dec 03 03:40:48 2003 (91943) Master qrunner detected subprocess exit (pid: 91959, sig: None, sts: 1, class: IncomingRunner, slice: 1/1) [restarting] Dec 03 03:40:49 2003 (91960) IncomingRunner qrunner started. Dec 03 03:40:49 2003 (91943) Master qrunner detected subprocess exit (pid: 91960, sig: None, sts: 1, class: IncomingRunner, slice: 1/1) [restarting] Dec 03 03:40:50 2003 (91961) IncomingRunner qrunner started. Dec 03 03:40:50 2003 (91943) Master qrunner detected subprocess exit (pid: 91961, sig: None, sts: 1, class: IncomingRunner, slice: 1/1) [restarting] Dec 03 03:40:50 2003 (91943) Qrunner IncomingRunner reached maximum restart limit of 10, not re starting. On the console, I'm getting these errors which might be more useful (just pasting 1 here, the other 9 are exactly the same) Traceback (most recent call last): File "/usr/local/mailman/bin/qrunner", line 270, in ? main() File "/usr/local/mailman/bin/qrunner", line 230, in main qrunner.run() File "/usr/local/mailman/Mailman/Queue/Runner.py", line 65, in run filecnt = self._oneloop() File "/usr/local/mailman/Mailman/Queue/Runner.py", line 93, in _oneloop msg, msgdata = self._switchboard.dequeue(filebase) File "/usr/local/mailman/Mailman/Queue/Switchboard.py", line 158, in dequeue data = self._ext_read(dbfile) File "/usr/local/mailman/Mailman/Queue/Switchboard.py", line 264, in _ext_read dict = marshal.load(fp) EOFError: EOF read where object expected I'm running this on FreeBSD 4.9-STABLE, mailman version 2.1.3, python 2.3.2 (both out of the ports tree). Any help you can send my way is much appreciated. Cheers - Erick emechler(a)techometer.net ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=853235&group_i…

1 0

[ mailman-Bugs-853235 ] IncomingRunner reached maximum restart limit of 10
by SourceForge.net 03 Dec '03

03 Dec '03

Bugs item #853235, was opened at 2003-12-03 03:52 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=853235&group_i… Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Erick Mechler (emechler) Assigned to: Nobody/Anonymous (nobody) Summary: IncomingRunner reached maximum restart limit of 10 Initial Comment: I just upgraded to 2.1 from 2.0.13, and I'm getting these errors when trying to startup the qrunner from the startup script (this is from the $MAILMAN/logs/qrunner log file): Dec 03 03:40:43 2003 (91944) ArchRunner qrunner started. Dec 03 03:40:43 2003 (91950) VirginRunner qrunner started. Dec 03 03:40:43 2003 (91947) IncomingRunner qrunner started. Dec 03 03:40:43 2003 (91945) BounceRunner qrunner started. Dec 03 03:40:44 2003 (91949) OutgoingRunner qrunner started. Dec 03 03:40:44 2003 (91948) NewsRunner qrunner started. Dec 03 03:40:44 2003 (91946) CommandRunner qrunner started. Dec 03 03:40:44 2003 (91951) RetryRunner qrunner started. Dec 03 03:40:44 2003 (91943) Master qrunner detected subprocess exit (pid: 91947, sig: None, sts: 1, class: IncomingRunner, slice: 1/1) [restarting] Dec 03 03:40:44 2003 (91952) IncomingRunner qrunner started. Dec 03 03:40:44 2003 (91943) Master qrunner detected subprocess exit (pid: 91952, sig: None, sts: 1, class: IncomingRunner, slice: 1/1) [restarting] Dec 03 03:40:44 2003 (91953) IncomingRunner qrunner started. Dec 03 03:40:44 2003 (91943) Master qrunner detected subprocess exit (pid: 91953, sig: None, sts: 1, class: IncomingRunner, slice: 1/1) [restarting] Dec 03 03:40:45 2003 (91954) IncomingRunner qrunner started. Dec 03 03:40:45 2003 (91943) Master qrunner detected subprocess exit (pid: 91954, sig: None, sts: 1, class: IncomingRunner, slice: 1/1) [restarting] Dec 03 03:40:47 2003 (91955) IncomingRunner qrunner started. Dec 03 03:40:47 2003 (91943) Master qrunner detected subprocess exit (pid: 91955, sig: None, sts: 1, class: IncomingRunner, slice: 1/1) [restarting] Dec 03 03:40:47 2003 (91956) IncomingRunner qrunner started. Dec 03 03:40:47 2003 (91943) Master qrunner detected subprocess exit (pid: 91956, sig: None, sts: 1, class: IncomingRunner, slice: 1/1) [restarting] Dec 03 03:40:47 2003 (91957) IncomingRunner qrunner started. Dec 03 03:40:47 2003 (91943) Master qrunner detected subprocess exit (pid: 91957, sig: None, sts: 1, class: IncomingRunner, slice: 1/1) [restarting] Dec 03 03:40:48 2003 (91958) IncomingRunner qrunner started. Dec 03 03:40:48 2003 (91943) Master qrunner detected subprocess exit (pid: 91958, sig: None, sts: 1, class: IncomingRunner, slice: 1/1) [restarting] Dec 03 03:40:48 2003 (91959) IncomingRunner qrunner started. Dec 03 03:40:48 2003 (91943) Master qrunner detected subprocess exit (pid: 91959, sig: None, sts: 1, class: IncomingRunner, slice: 1/1) [restarting] Dec 03 03:40:49 2003 (91960) IncomingRunner qrunner started. Dec 03 03:40:49 2003 (91943) Master qrunner detected subprocess exit (pid: 91960, sig: None, sts: 1, class: IncomingRunner, slice: 1/1) [restarting] Dec 03 03:40:50 2003 (91961) IncomingRunner qrunner started. Dec 03 03:40:50 2003 (91943) Master qrunner detected subprocess exit (pid: 91961, sig: None, sts: 1, class: IncomingRunner, slice: 1/1) [restarting] Dec 03 03:40:50 2003 (91943) Qrunner IncomingRunner reached maximum restart limit of 10, not re starting. On the console, I'm getting these errors which might be more useful (just pasting 1 here, the other 9 are exactly the same) Traceback (most recent call last): File "/usr/local/mailman/bin/qrunner", line 270, in ? main() File "/usr/local/mailman/bin/qrunner", line 230, in main qrunner.run() File "/usr/local/mailman/Mailman/Queue/Runner.py", line 65, in run filecnt = self._oneloop() File "/usr/local/mailman/Mailman/Queue/Runner.py", line 93, in _oneloop msg, msgdata = self._switchboard.dequeue(filebase) File "/usr/local/mailman/Mailman/Queue/Switchboard.py", line 158, in dequeue data = self._ext_read(dbfile) File "/usr/local/mailman/Mailman/Queue/Switchboard.py", line 264, in _ext_read dict = marshal.load(fp) EOFError: EOF read where object expected I'm running this on FreeBSD 4.9-STABLE, mailman version 2.1.3, python 2.3.2 (both out of the ports tree). Any help you can send my way is much appreciated. Cheers - Erick emechler(a)techometer.net ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=853235&group_i…

1 0

[ mailman-Bugs-825084 ] HyperArch.py allows empty subjects
by SourceForge.net 01 Dec '03

01 Dec '03

Bugs item #825084, was opened at 2003-10-16 13:49 Message generated for change (Comment added) made by lanclos You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=825084&group_i… Category: Pipermail Group: None Status: Open Resolution: None Priority: 5 Submitted By: Kyle Lanclos (lanclos) Assigned to: Nobody/Anonymous (nobody) Summary: HyperArch.py allows empty subjects Initial Comment: Messages coming into HyperArch.py with a subject of "Re: " (or similar) come out having no subject at all. This is Bad(tm), because the HREF links in the HTML archives are keyed to the subject, and if there's no subject, there's no link. Here's a simple fix, against the 2.1.3 source. --- mailman-2.1.3/Mailman/Archiver/HyperArch.py Sun Sep 21 19:40:51 2003 +++ /opt/mailman/Mailman/Archiver/HyperArch.py Thu Oct 16 13:38:39 2003 @@ -262,6 +262,8 @@ if result: i = result.end(0) self.subject = self.subject[i:] + if self.subject.strip() == EMPTYSTRING: + self.subject = '(no subject)' else: i = -1 # Useful to keep around ---------------------------------------------------------------------- >Comment By: Kyle Lanclos (lanclos) Date: 2003-12-01 08:06 Message: Logged In: YES user_id=888067 I encountered this bug repeatedly when I was using 'arch' to import an old, non-mailman mbox file which contained messages with subjects of "Re:" or "Re: ". HyperArch.py strips the Re: off the subject line, but when it does so, it does not check for an empty string... it assumes that the empty-string check happens earlier in the mail path, which for normal mailman messages, it does. The only time (that I can think of) you would encounter this bug is when you are importing non-mailman correspondence in via the 'arch' command. This situation is not uncommon when converting old mailing lists to mailman. If you still want sample messages that caused this bug at our site, I can provide them, though it is trivial to set up an mbox-formtted message matching this description by manually editing the subject line. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-12-01 07:06 Message: Logged In: YES user_id=12800 I can't reproduce this. Can you provide more information on how your site and list is set up and possibly include a sample message that triggers the bug? Or, if you can find an example of the bug in one of the python.org mailing lists, that would be great. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=825084&group_i…

1 0

[ mailman-Bugs-784706 ] Clarify need for genaliases in UPGRADING
by SourceForge.net 01 Dec '03

01 Dec '03

Bugs item #784706, was opened at 2003-08-07 07:33 Message generated for change (Comment added) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=784706&group_i… Category: configuring/installing Group: 2.1 (stable) >Status: Closed Resolution: None Priority: 4 Submitted By: Thomas Arendsen Hein (thomas_ah) Assigned to: Nobody/Anonymous (nobody) Summary: Clarify need for genaliases in UPGRADING Initial Comment: mailman-2.1.2/UPGRADING says: NOTE: When upgrading to Mailman 2.1beta1, you will need to regenerate your aliases files. There have been many changes to the alias names, the programs they map to, and the name of the wrapper script. See README.<yourMTA> for details of making Mailman work with your mail server. I've upgraded from 2.0.13 to 2.1.2, this is not 2.1beta1, so I don't need to regenerate my aliases files. And the next paragraph says: To regenerate your aliases, use the bin/genaliases script. I've just learned that I don't need to update my aliases files, therefore this is only an information just in case I want to do it, but I don't want it now. To make this clear, you could write: NOTE: You will need to regenerate your aliases files. because this file is distributed with a Mailman version which needs the genaliases step. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-12-01 10:18 Message: Logged In: YES user_id=12800 The instructions have been updated for 2.1.4. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=784706&group_i…

1 0

[ mailman-Bugs-784888 ] Wrong domain in public archives
by SourceForge.net 01 Dec '03

01 Dec '03

Bugs item #784888, was opened at 2003-08-07 13:03 Message generated for change (Comment added) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=784888&group_i… Category: Pipermail Group: 2.1 (stable) >Status: Closed Resolution: None Priority: 5 Submitted By: Rob Brandt (robbrandt) Assigned to: Nobody/Anonymous (nobody) Summary: Wrong domain in public archives Initial Comment: I *think* I've found a bug in 2.12. I've had a longstanding issue with all of my mailing lists pointing to the wrong domain for mail archives. When I originally set up the server, used an initial "recreational" domain name not intended to be used widely. The intention was to switch to the real domain names later once the server went live. I did that, but all of the URLs for archives (only archives) still pointed to the stupid domain name. I intended to fix this in 2.12 by using the fix_url function while I was also fixing a bunch of other stuff. I've needed to move some of my lists to other domains anyway, so this seemed like a good time. So I ran fix_url over almost all of my domains, and tested them as I went. Everything went as planned, except some of them still had the archives pointing to the recreational domain. Then it dawned on me that the ones that didn't get fixed were all *public* archives; the ones that did get fixed were all private. I went to one of the public archives and switched it to private, and the URL to the archives was then OK! Switched it back to public and it was wrong again. So, it seems that this is a bug. Or I've missed a configuration setting somewhere. Thanks Rob ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-12-01 10:16 Message: Logged In: YES user_id=12800 Close as per the 2003-08-11 16:46 comments. ---------------------------------------------------------------------- Comment By: Rob Brandt (robbrandt) Date: 2003-08-11 16:46 Message: Logged In: YES user_id=332197 The problem is resolved, with great help from Richard Barrett. For the sake of posterity, let the bug archives show: * Be sure you have proper virtual host mapping (add_virtualhost()) in mm_cfg.py; * Be sure that the list setting for "Host name this list prefers for email" is in fact your mail exchange address, not a base URL for browsing (which was my problem); * Run fix_url.py ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-08-11 08:15 Message: Logged In: YES user_id=67709 Have you defined your (url_host, mail_host) pair in your mm_cfg.py ? You should state like: add_virtualhost('www.virtual.dom', 'mail.virtual.dom') ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=784888&group_i…

1 0

[ mailman-Bugs-797232 ] senddigests can crash
by SourceForge.net 01 Dec '03

01 Dec '03

Bugs item #797232, was opened at 2003-08-29 07:53 Message generated for change (Settings changed) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=797232&group_i… Category: mail delivery Group: 2.1 (stable) >Status: Closed >Resolution: Duplicate Priority: 5 Submitted By: Sjoerd Mullender (sjoerd) Assigned to: Nobody/Anonymous (nobody) Summary: senddigests can crash Initial Comment: In certain circumstances the senddigests cron job can crash. Here is the traceback: Traceback (most recent call last): File "/var/mailman/cron/senddigests", line 94, in ? main() File "/var/mailman/cron/senddigests", line 86, in main mlist.send_digest_now() File "/var/mailman/Mailman/Digester.py", line 60, in send_digest_now ToDigest.send_digests(self, mboxfp) File "/var/mailman/Mailman/Handlers/ToDigest.py", line 130, in send_digests send_i18n_digests(mlist, mboxfp) File "/var/mailman/Mailman/Handlers/ToDigest.py", line 303, in send_i18n_digests msg = scrubber(mlist, msg) File "/var/mailman/Mailman/Handlers/Scrubber.py", line 308, in process t = t.encode(charset, 'replace') File "/ufs/sjoerd/src/Python/dist/src/Lib/encodings/__init__.py", line 69, in search_function globals(), locals(), _import_tail) ValueError: Empty module name The reason of the crash is that charset in the call to t.encode is the empty string. Why it is that, I don't know, and I don't have the email message that triggered it. But apparently it's possible, so should be protected against. This is with Python 2.3 and current CVS. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-12-01 10:14 Message: Logged In: YES user_id=12800 Duplicate of already closed 834486 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=797232&group_i…

1 0

[ mailman-Bugs-813760 ] digest default has no effect on mass subscribe
by SourceForge.net 01 Dec '03

01 Dec '03

Bugs item #813760, was opened at 2003-09-27 17:53 Message generated for change (Settings changed) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=813760&group_i… Category: (un)subscribing Group: 2.1 (stable) >Status: Closed >Resolution: Works For Me Priority: 5 Submitted By: Matt DeLuco (duke) Assigned to: Nobody/Anonymous (nobody) Summary: digest default has no effect on mass subscribe Initial Comment: When mass subscribing some ~245 members to a list, I wanted them all to receive digests by default. So under Digest Options, I set digest to be the default delivery mode for new users. Upon subscribing all the users (this happens entering email addresses by file or form), not one user was set to receive a digest. I had to go through all of them and manually set it (heh, there's probably an easier way, isn't there.) This is Mailman version 2.1.1, installed by hand (ie: no package system.) Linux 2.4.22, GCC 3.2.3, Python 2.2.3. Gentoo Linux distribution. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-12-01 10:12 Message: Logged In: YES user_id=12800 I just tested this with 2.1.4a0 (cvs) and it works for me. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=813760&group_i…

1 0

[ mailman-Bugs-817243 ] Web member list has extra bad characters via email subscribe
by SourceForge.net 01 Dec '03

01 Dec '03

Bugs item #817243, was opened at 2003-10-03 11:18 Message generated for change (Settings changed) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=817243&group_i… Category: Web/CGI Group: 2.1 (stable) >Status: Closed >Resolution: Works For Me Priority: 5 Submitted By: Dan (ptcheezer) Assigned to: Nobody/Anonymous (nobody) Summary: Web member list has extra bad characters via email subscribe Initial Comment: When I subscribe via an email command with a password, then the user shows up in the memberlist with extra characters like: u ' and The members who were subscribed using the web interface mass-subscription do NOT have any extra characters at all. The user still gets emails from the list, but when you try and click on the user in the admin web interface it will not go to their user page (goes to the General Options page instead) Here is the table row from the Mailman admin interface where you can see the extra characters: <tr> <td><center>u'<INPUT name="amember(a)ap.org_unsub" type="CHECKBOX" value="off" >'</center></td> <td>u'<a href="u\'https://lists.some.org/mailman/options/hrep- agr/amember--at-- ap.org\'">u\'amember(a)ap.org\'</a><br><INPUT name="amember(a)ap.org_realname" type="TEXT" value="" size="23" ><INPUT name="user" type="HIDDEN" value="amember%40ap.org" >'</td> <td>u'<center><INPUT name="amember(a)ap.org_mod" type="CHECKBOX" value="on" CHECKED ></center>'</td> <td><center>u'<INPUT name="amember(a)ap.org_hide" type="CHECKBOX" value="off" >'</center></td> <td><center>u'<INPUT name="amember(a)ap.org_nomail" type="CHECKBOX" value="off" >'</center></td> <td><center>u'<INPUT name="amember(a)ap.org_ack" type="CHECKBOX" value="off" >'</center></td> <td><center>u'<INPUT name="amember(a)ap.org_notmetoo" type="CHECKBOX" value="off" >'</center></td> <td><center>u'<INPUT name="amember(a)ap.org_nodupes" type="CHECKBOX" value="on" CHECKED >'</center></td> <td><center>u'<INPUT name="amember(a)ap.org_digest" type="CHECKBOX" value="off" >'</center></td> <td><center><INPUT name="amember(a)ap.org_plain" type="CHECKBOX" value="on" CHECKED ></center></td> <td>u'<center>\n<Select name="amember(a)ap.org_language">\n <option value="en" Selected> English (USA) </option>\n</Select></center>'</td> </tr> ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-12-01 10:11 Message: Logged In: YES user_id=12800 I can't reproduce this in MM2.1.4a0 (now in cvs). ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=817243&group_i…

1 0

[ mailman-Bugs-825084 ] HyperArch.py allows empty subjects
by SourceForge.net 01 Dec '03

01 Dec '03

Bugs item #825084, was opened at 2003-10-16 16:49 Message generated for change (Comment added) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=825084&group_i… Category: Pipermail Group: None Status: Open Resolution: None Priority: 5 Submitted By: Kyle Lanclos (lanclos) Assigned to: Nobody/Anonymous (nobody) Summary: HyperArch.py allows empty subjects Initial Comment: Messages coming into HyperArch.py with a subject of "Re: " (or similar) come out having no subject at all. This is Bad(tm), because the HREF links in the HTML archives are keyed to the subject, and if there's no subject, there's no link. Here's a simple fix, against the 2.1.3 source. --- mailman-2.1.3/Mailman/Archiver/HyperArch.py Sun Sep 21 19:40:51 2003 +++ /opt/mailman/Mailman/Archiver/HyperArch.py Thu Oct 16 13:38:39 2003 @@ -262,6 +262,8 @@ if result: i = result.end(0) self.subject = self.subject[i:] + if self.subject.strip() == EMPTYSTRING: + self.subject = '(no subject)' else: i = -1 # Useful to keep around ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-12-01 10:06 Message: Logged In: YES user_id=12800 I can't reproduce this. Can you provide more information on how your site and list is set up and possibly include a sample message that triggers the bug? Or, if you can find an example of the bug in one of the python.org mailing lists, that would be great. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=825084&group_i…

1 0