From noreply at sourceforge.net Mon Dec 1 04:32:25 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Dec 1 04:32:31 2003 Subject: [ mailman-Bugs-851970 ] crash running archiver: StringIO: expected read buffer, list Message-ID: Bugs item #851970, was opened at 2003-12-01 20:32 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=851970&group_id=103 Category: Pipermail Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Martin Pool (mbp) Assigned to: Nobody/Anonymous (nobody) Summary: crash running archiver: StringIO: expected read buffer, list Initial Comment: Hi, I'm trying to import some messages into an archive using the arch command in 2.1.3. This mostly works, except that a few messages that seem otherwise well-formed are causing an exception: mailman@dp:private$ python -i /usr/local/mailman/bin/arch distcc /tmp/crash2 #00000 <1066876904.6827.10.camel@lisa.thedoh.com> Pickling archive state into /var/mailman/archives/private/distcc/pipermail.pck Traceback (most recent call last): File "/usr/local/mailman/bin/arch", line 187, in ? main() File "/usr/local/mailman/bin/arch", line 175, in main archiver.processUnixMailbox(fp, start, end) File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 558, in processUnixMailbox a = self._makeArticle(m, self.sequence) File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 626, in _makeArticle mlist=self.maillist) File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 255, in __init__ self.__super_init(message, sequence, keepHeaders) File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 216, in __init__ s = StringIO(message.get_payload()) TypeError: expected read buffer, list found The problem seems to be that cStringIO (unlike plain StringIO) cannot take a list as a read buffer. It will only accept a string. I'm using Python 2.2.2 (#1, Jan 30 2003, 21:26:22) [GCC 2.96 20000731 (Red Hat Linux 7.3 2.96-112)] on linux2 But cStringIO's behaviour seems to be the same even on Python 2.3.2. The doc string for pythonlib/email/Message.py's get_payload() function says """Return a reference to the payload. The payload will either be a list object or a string. If you mutate the list object, you modify the message's payload in place. Optional i returns that index into the payload. I think this has to be a bug, because if it returns a list it will certainly break cStringIO. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=851970&group_id=103 From noreply at sourceforge.net Mon Dec 1 04:43:08 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Dec 1 04:43:14 2003 Subject: [ mailman-Bugs-851970 ] crash running archiver: StringIO: expected read buffer, list Message-ID: Bugs item #851970, was opened at 2003-12-01 20:32 Message generated for change (Comment added) made by mbp You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=851970&group_id=103 Category: Pipermail Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Martin Pool (mbp) Assigned to: Nobody/Anonymous (nobody) Summary: crash running archiver: StringIO: expected read buffer, list Initial Comment: Hi, I'm trying to import some messages into an archive using the arch command in 2.1.3. This mostly works, except that a few messages that seem otherwise well-formed are causing an exception: mailman@dp:private$ python -i /usr/local/mailman/bin/arch distcc /tmp/crash2 #00000 <1066876904.6827.10.camel@lisa.thedoh.com> Pickling archive state into /var/mailman/archives/private/distcc/pipermail.pck Traceback (most recent call last): File "/usr/local/mailman/bin/arch", line 187, in ? main() File "/usr/local/mailman/bin/arch", line 175, in main archiver.processUnixMailbox(fp, start, end) File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 558, in processUnixMailbox a = self._makeArticle(m, self.sequence) File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 626, in _makeArticle mlist=self.maillist) File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 255, in __init__ self.__super_init(message, sequence, keepHeaders) File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 216, in __init__ s = StringIO(message.get_payload()) TypeError: expected read buffer, list found The problem seems to be that cStringIO (unlike plain StringIO) cannot take a list as a read buffer. It will only accept a string. I'm using Python 2.2.2 (#1, Jan 30 2003, 21:26:22) [GCC 2.96 20000731 (Red Hat Linux 7.3 2.96-112)] on linux2 But cStringIO's behaviour seems to be the same even on Python 2.3.2. The doc string for pythonlib/email/Message.py's get_payload() function says """Return a reference to the payload. The payload will either be a list object or a string. If you mutate the list object, you modify the message's payload in place. Optional i returns that index into the payload. I think this has to be a bug, because if it returns a list it will certainly break cStringIO. ---------------------------------------------------------------------- >Comment By: Martin Pool (mbp) Date: 2003-12-01 20:43 Message: Logged In: YES user_id=521 Not only is get_payload() returning a list, but it's not even a list of strings. So it's no wonder that StringIO is having trouble. For the sample message I quoted, get_payload() returns a 2-element list where the elements are instances of Mailman.Message.Message. I wonder if I have an old/buggy pythonlib/email library for some reason, or if some old cruft on redhat is causing the problem? All of the relevant code seems reasonably close to python 2.3. And anyhow, the mailman docs say that only python 2.1 is required. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=851970&group_id=103 From noreply at sourceforge.net Mon Dec 1 04:51:06 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Dec 1 04:51:11 2003 Subject: [ mailman-Bugs-851970 ] crash running archiver: StringIO: expected read buffer, list Message-ID: Bugs item #851970, was opened at 2003-12-01 20:32 Message generated for change (Comment added) made by mbp You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=851970&group_id=103 Category: Pipermail Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Martin Pool (mbp) Assigned to: Nobody/Anonymous (nobody) Summary: crash running archiver: StringIO: expected read buffer, list Initial Comment: Hi, I'm trying to import some messages into an archive using the arch command in 2.1.3. This mostly works, except that a few messages that seem otherwise well-formed are causing an exception: mailman@dp:private$ python -i /usr/local/mailman/bin/arch distcc /tmp/crash2 #00000 <1066876904.6827.10.camel@lisa.thedoh.com> Pickling archive state into /var/mailman/archives/private/distcc/pipermail.pck Traceback (most recent call last): File "/usr/local/mailman/bin/arch", line 187, in ? main() File "/usr/local/mailman/bin/arch", line 175, in main archiver.processUnixMailbox(fp, start, end) File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 558, in processUnixMailbox a = self._makeArticle(m, self.sequence) File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 626, in _makeArticle mlist=self.maillist) File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 255, in __init__ self.__super_init(message, sequence, keepHeaders) File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 216, in __init__ s = StringIO(message.get_payload()) TypeError: expected read buffer, list found The problem seems to be that cStringIO (unlike plain StringIO) cannot take a list as a read buffer. It will only accept a string. I'm using Python 2.2.2 (#1, Jan 30 2003, 21:26:22) [GCC 2.96 20000731 (Red Hat Linux 7.3 2.96-112)] on linux2 But cStringIO's behaviour seems to be the same even on Python 2.3.2. The doc string for pythonlib/email/Message.py's get_payload() function says """Return a reference to the payload. The payload will either be a list object or a string. If you mutate the list object, you modify the message's payload in place. Optional i returns that index into the payload. I think this has to be a bug, because if it returns a list it will certainly break cStringIO. ---------------------------------------------------------------------- >Comment By: Martin Pool (mbp) Date: 2003-12-01 20:51 Message: Logged In: YES user_id=521 I think this was my error. We had ARCHIVE_SCRUBBER=0 while we were using MHonArc, but I see that has to be left on the default for Pipermail to work. ---------------------------------------------------------------------- Comment By: Martin Pool (mbp) Date: 2003-12-01 20:43 Message: Logged In: YES user_id=521 Not only is get_payload() returning a list, but it's not even a list of strings. So it's no wonder that StringIO is having trouble. For the sample message I quoted, get_payload() returns a 2-element list where the elements are instances of Mailman.Message.Message. I wonder if I have an old/buggy pythonlib/email library for some reason, or if some old cruft on redhat is causing the problem? All of the relevant code seems reasonably close to python 2.3. And anyhow, the mailman docs say that only python 2.1 is required. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=851970&group_id=103 From noreply at sourceforge.net Mon Dec 1 05:13:08 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Dec 1 05:13:18 2003 Subject: [ mailman-Bugs-851970 ] crash running archiver: StringIO: expected read buffer, list Message-ID: Bugs item #851970, was opened at 2003-12-01 20:32 Message generated for change (Settings changed) made by mbp You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=851970&group_id=103 Category: Pipermail Group: 2.1 (stable) >Status: Closed >Resolution: Invalid Priority: 5 Submitted By: Martin Pool (mbp) Assigned to: Nobody/Anonymous (nobody) Summary: crash running archiver: StringIO: expected read buffer, list Initial Comment: Hi, I'm trying to import some messages into an archive using the arch command in 2.1.3. This mostly works, except that a few messages that seem otherwise well-formed are causing an exception: mailman@dp:private$ python -i /usr/local/mailman/bin/arch distcc /tmp/crash2 #00000 <1066876904.6827.10.camel@lisa.thedoh.com> Pickling archive state into /var/mailman/archives/private/distcc/pipermail.pck Traceback (most recent call last): File "/usr/local/mailman/bin/arch", line 187, in ? main() File "/usr/local/mailman/bin/arch", line 175, in main archiver.processUnixMailbox(fp, start, end) File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 558, in processUnixMailbox a = self._makeArticle(m, self.sequence) File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 626, in _makeArticle mlist=self.maillist) File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 255, in __init__ self.__super_init(message, sequence, keepHeaders) File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 216, in __init__ s = StringIO(message.get_payload()) TypeError: expected read buffer, list found The problem seems to be that cStringIO (unlike plain StringIO) cannot take a list as a read buffer. It will only accept a string. I'm using Python 2.2.2 (#1, Jan 30 2003, 21:26:22) [GCC 2.96 20000731 (Red Hat Linux 7.3 2.96-112)] on linux2 But cStringIO's behaviour seems to be the same even on Python 2.3.2. The doc string for pythonlib/email/Message.py's get_payload() function says """Return a reference to the payload. The payload will either be a list object or a string. If you mutate the list object, you modify the message's payload in place. Optional i returns that index into the payload. I think this has to be a bug, because if it returns a list it will certainly break cStringIO. ---------------------------------------------------------------------- >Comment By: Martin Pool (mbp) Date: 2003-12-01 21:13 Message: Logged In: YES user_id=521 My mistake, turning the Scrubber back on fixed it. ---------------------------------------------------------------------- Comment By: Martin Pool (mbp) Date: 2003-12-01 20:51 Message: Logged In: YES user_id=521 I think this was my error. We had ARCHIVE_SCRUBBER=0 while we were using MHonArc, but I see that has to be left on the default for Pipermail to work. ---------------------------------------------------------------------- Comment By: Martin Pool (mbp) Date: 2003-12-01 20:43 Message: Logged In: YES user_id=521 Not only is get_payload() returning a list, but it's not even a list of strings. So it's no wonder that StringIO is having trouble. For the sample message I quoted, get_payload() returns a 2-element list where the elements are instances of Mailman.Message.Message. I wonder if I have an old/buggy pythonlib/email library for some reason, or if some old cruft on redhat is causing the problem? All of the relevant code seems reasonably close to python 2.3. And anyhow, the mailman docs say that only python 2.1 is required. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=851970&group_id=103 From noreply at sourceforge.net Mon Dec 1 10:06:14 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Dec 1 10:06:20 2003 Subject: [ mailman-Bugs-825084 ] HyperArch.py allows empty subjects Message-ID: 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_id=103 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_id=103 From noreply at sourceforge.net Mon Dec 1 10:11:06 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Dec 1 10:11:17 2003 Subject: [ mailman-Bugs-817243 ] Web member list has extra bad characters via email subscribe Message-ID: 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_id=103 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:
u''
u'u\'amember@ap.org\'
' u'
'
u''
u''
u''
u''
u''
u''
u'
\n
' ---------------------------------------------------------------------- >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_id=103 From noreply at sourceforge.net Mon Dec 1 10:13:00 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Dec 1 10:13:17 2003 Subject: [ mailman-Bugs-813760 ] digest default has no effect on mass subscribe Message-ID: 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_id=103 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_id=103 From noreply at sourceforge.net Mon Dec 1 10:14:48 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Dec 1 10:15:59 2003 Subject: [ mailman-Bugs-797232 ] senddigests can crash Message-ID: 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_id=103 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_id=103 From noreply at sourceforge.net Mon Dec 1 10:16:36 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Dec 1 10:16:53 2003 Subject: [ mailman-Bugs-784888 ] Wrong domain in public archives Message-ID: 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_id=103 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_id=103 From noreply at sourceforge.net Mon Dec 1 10:18:42 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Dec 1 10:18:52 2003 Subject: [ mailman-Bugs-784706 ] Clarify need for genaliases in UPGRADING Message-ID: 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_id=103 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. 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_id=103 From noreply at sourceforge.net Mon Dec 1 11:06:20 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Dec 1 11:07:37 2003 Subject: [ mailman-Bugs-825084 ] HyperArch.py allows empty subjects Message-ID: 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_id=103 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_id=103 From noreply at sourceforge.net Wed Dec 3 06:52:40 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Dec 3 06:52:43 2003 Subject: [ mailman-Bugs-853235 ] IncomingRunner reached maximum restart limit of 10 Message-ID: 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_id=103 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@techometer.net ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=853235&group_id=103 From noreply at sourceforge.net Wed Dec 3 06:53:25 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Dec 3 06:53:28 2003 Subject: [ mailman-Bugs-853235 ] IncomingRunner reached maximum restart limit of 10 Message-ID: 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_id=103 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@techometer.net ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=853235&group_id=103 From noreply at sourceforge.net Thu Dec 4 04:04:15 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Dec 4 04:04:25 2003 Subject: [ mailman-Bugs-853235 ] IncomingRunner reached maximum restart limit of 10 Message-ID: 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_id=103 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@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_id=103 From noreply at sourceforge.net Thu Dec 4 07:27:45 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Dec 4 07:27:50 2003 Subject: [ mailman-Bugs-853996 ] Mail sending 4 times Message-ID: Bugs item #853996, was opened at 2003-12-04 12:27 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=853996&group_id=103 Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Denis (d3n) Assigned to: Nobody/Anonymous (nobody) Summary: Mail sending 4 times Initial Comment: Hi, I have upgraded mailman on debian from 2.0.3. to 2.1.1-5.1 Since this upgrade, i have a big problem.All the request messages, reminder of subscription, ... are sending 4times. Denis ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=853996&group_id=103 From noreply at sourceforge.net Fri Dec 5 18:00:03 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Dec 5 18:00:12 2003 Subject: [ mailman-Bugs-855096 ] bin/check_perms is wrong for *BSD Message-ID: Bugs item #855096, was opened at 2003-12-05 17: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=855096&group_id=103 Category: configuring/installing Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Eric Schnoebelen (schnoebe) Assigned to: Nobody/Anonymous (nobody) Summary: bin/check_perms is wrong for *BSD Initial Comment: bin/check_perms _assumes_ that you're running on an OS that requires the setgid bit on directories to have the directory ownership information propagate to files created in that directory. This is wrong for BSD derived operating systems. bin/check_perms should be modified to understand this, rather than operating on false assumptions. I've attached a patch that solves the problem. Forgive the style (if any) as this is the first time I've wacked on Python. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=855096&group_id=103 From noreply at sourceforge.net Mon Dec 8 11:38:03 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Dec 8 11:38:46 2003 Subject: [ mailman-Bugs-420482 ] Bad info in monthly reminder headers Message-ID: Bugs item #420482, was opened at 2001-05-01 12:35 Message generated for change (Comment added) made by robellis You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=420482&group_id=103 Category: mail delivery Group: 2.0.x Status: Closed Resolution: Fixed Priority: 5 Submitted By: D.J. Atkinson (deejster) Assigned to: Nobody/Anonymous (nobody) Summary: Bad info in monthly reminder headers Initial Comment: It appears that "Return-Path", "Sender", "Errors- To", "X-BeenThere" are all being set to the incorrect list when sending out the monthly info. [on the 4 list servers that I run, it turned out to be the alphabetically first list in all 4 cases] See the example below where dj@subscriber.com is a member of "junk" and "testa" yet "Return- Path", "Sender", "Errors-To" and "X-BeenThere" are all attributed to the "alist", and if subscriber.com bounced the message for some reason, "alist-admin" would be wondering why s/he couldn't find him amongst the list members. [BTW - this is information exactly as I received it for my subscriptions on one server. Domains and IPs are the only things changed (for privacy).] In a perfect world this wouldn't be an issue, however, the poor admin of alist (example headers below) receives all the returns from all list reminders that get sent out every month (and is starting to get tired of it). Wouldn't it be better if these were attributed to (one of) the list(s) that the subscriber is a member of? Or if not that, shouldn't they at least be attributed to mailman-owner (as in the "From" header field)? Return-Path: Received: from listhost.net (listhost.net [10.0.0.1]) by mail.subscriber.com (8.9.2/8.9.2) with SMTP id FAA01735 for ; Tue, 1 May 2001 05:06:37 -0600 (MDT) Received: from listhost.net (localhost [127.0.0.1]) by listhost.net (8.9.3/8.9.3) with ESMTP id FAA18897 for ; Tue, 1 May 2001 05:06:18 -0600 (MDT) Date: Tue, 1 May 2001 05:06:18 -0600 (MDT) Message-Id: <200105011106.FAA18897@listhost.net> Subject: listhost.net mailing list memberships reminder From: mailman-owner@listhost.net To: dj@subscriber.com X-No-Archive: yes X-Ack: no Sender: alist-admin@listhost.net Errors-To: alist-admin@listhost.net X-BeenThere: alist@listhost.net X-Mailman-Version: 2.0.1 Precedence: bulk X-UIDL: c3f7736e3c6bdbe9eb75e264e35e8768 Passwords for dj@subscriber.com: List Password // URL ---- -------- junk@listhost.net http://listhost.net/mailman/options/junk/dj% 40subscriber.com testa@listhost.net http://listhost.net/mailman/options/testa/dj% 40subscriber.com ---------------------------------------------------------------------- Comment By: Rob Ellis (robellis) Date: 2003-12-08 11:38 Message: Logged In: YES user_id=338888 A fix/workaround for anyone who might still be running 2.0.x -- create a list for sending password reminders, e.g. 'mm-reminders', and make this change to cron/mailpasswds: < a_public_list = None --- > # a_public_list = None > some_admin_list = 'mm-reminders' > a_public_list = MailList.MailList(some_admin_list, lock=0) ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-04-05 14:07 Message: Logged In: YES user_id=12800 Note that in MM2.0, all reminders appear to come from the first public list at your site. This is a design flaw that's fixed in MM2.1. ---------------------------------------------------------------------- Comment By: Russell Whitaker (whitaker) Date: 2001-12-10 19:59 Message: Logged In: YES user_id=68054 I should have added this information: the problem was seen in our (my company's) Mailman 2.0.6 and 2.0.8 installations. In the meantime, we have disabled the monthly 'mailpasswds' cron entry for security reasons. Russell Whitaker ---------------------------------------------------------------------- Comment By: Russell Whitaker (whitaker) Date: 2001-12-10 19:57 Message: Logged In: YES user_id=68054 Is this issue fixed in subsequent (post 2.0.1) versions of Mailman? For that matter, is this issue going to be assigned a fixer? Thanks, Russell Whitaker ---------------------------------------------------------------------- Comment By: Paula B Morrison (morri027) Date: 2001-08-06 11:38 Message: Logged In: YES user_id=290757 We are experiencing the same problem - the return mail for all lists is going to the administrators of another list. However, the list that is getting the return mail is NOT the first list alphabetically. ---------------------------------------------------------------------- Comment By: Sean Reifschneider (jafo) Date: 2001-05-03 02:16 Message: Logged In: YES user_id=81797 Hmm, I just verified this on one the messages sent out on one of our boxes running Mailman 2.0.4. FYI. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=420482&group_id=103 From noreply at sourceforge.net Mon Dec 8 16:33:10 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Dec 8 16:33:15 2003 Subject: [ mailman-Bugs-856474 ] Double quotes in user names get stripped in web interface Message-ID: Bugs item #856474, was opened at 2003-12-08 22:33 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=856474&group_id=103 Category: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Axel Beckert (xtaran) Assigned to: Nobody/Anonymous (nobody) Summary: Double quotes in user names get stripped in web interface Initial Comment: Wenn I enter some Usernames containing double quotes, e.g. Axel "Testing Monkey" Beckert everything after the first double quote goes into bit nirvana, equal if I enter this while subscribing or in the member list in the administrative interface. Single quotes work fine, though. Using Mailman 2.1.3 on Linux with Postfix as MTA. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=856474&group_id=103 From noreply at sourceforge.net Mon Dec 8 16:43:08 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Dec 8 16:43:10 2003 Subject: [ mailman-Bugs-856480 ] bin/addlang mentioned in documentation but non-existent Message-ID: Bugs item #856480, was opened at 2003-12-08 22:43 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=856480&group_id=103 Category: documentation Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Axel Beckert (xtaran) Assigned to: Nobody/Anonymous (nobody) Summary: bin/addlang mentioned in documentation but non-existent Initial Comment: On http://www.list.org/site.html, there is written: addlang Use this to add language support to a specific list. The site itself must have the language pack to add already installed. Note that removing language support from a list requires you to manually rm the lists/yourlist/lang subdirectory. Neither in 2.1.3 nor in 2.1 CVS HEAD, there is such an file nor an similiar named file (checked with "find Mailman-CVS/ -iname 'add*lang*'") So this part of the documentation should be marked either als "outdated" or as "upcoming feature", depending on what matches. :-) http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq04.009.htp seems to be ok. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=856480&group_id=103 From noreply at sourceforge.net Mon Dec 8 19:03:37 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Dec 8 19:03:40 2003 Subject: [ mailman-Bugs-856565 ] mailto link to site admin contains webserver port Message-ID: Bugs item #856565, was opened at 2003-12-09 01:03 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=856565&group_id=103 Category: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Axel Beckert (xtaran) Assigned to: Nobody/Anonymous (nobody) Summary: mailto link to site admin contains webserver port Initial Comment: If you access Mailman's web interface via some other port than 80, i.e. the port number is specified in the URL and therefore in the Host header, it's also present in the site admin mailto link. Example: If the Mailman URL is e.g. http://localhost:8001/mailman/listinfo then the site admin mailto link reads mailman@localhost:8001 which isn't what it should be. Fix: Strip the colon and port number before outputting the host name for the email address. Found in Mailman 2.1.3 on Linux using Postfix as MTA (which probably should matter very much in this case ;-). ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=856565&group_id=103 From noreply at sourceforge.net Sat Dec 13 14:47:32 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sun Dec 14 00:01:34 2003 Subject: [ mailman-Bugs-856480 ] bin/addlang mentioned in documentation but non-existent Message-ID: Bugs item #856480, was opened at 2003-12-08 16:43 Message generated for change (Comment added) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=856480&group_id=103 Category: documentation Group: 2.1 (stable) >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Axel Beckert (xtaran) Assigned to: Nobody/Anonymous (nobody) Summary: bin/addlang mentioned in documentation but non-existent Initial Comment: On http://www.list.org/site.html, there is written: addlang Use this to add language support to a specific list. The site itself must have the language pack to add already installed. Note that removing language support from a list requires you to manually rm the lists/yourlist/lang subdirectory. Neither in 2.1.3 nor in 2.1 CVS HEAD, there is such an file nor an similiar named file (checked with "find Mailman-CVS/ -iname 'add*lang*'") So this part of the documentation should be marked either als "outdated" or as "upcoming feature", depending on what matches. :-) http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq04.009.htp seems to be ok. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-12-13 14:47 Message: Logged In: YES user_id=12800 I removed addlang description from site.ht. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=856480&group_id=103 From noreply at sourceforge.net Sun Dec 14 12:58:32 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sun Dec 14 12:58:40 2003 Subject: [ mailman-Bugs-777444 ] mailmanctl doesn't setgroups when run as root Message-ID: Bugs item #777444, was opened at 2003-07-25 06:02 Message generated for change (Comment added) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=777444&group_id=103 Category: security/privacy Group: 2.1 (stable) >Status: Closed >Resolution: Accepted Priority: 5 Submitted By: Richard Barrett (ppsys) Assigned to: Nobody/Anonymous (nobody) Summary: mailmanctl doesn't setgroups when run as root Initial Comment: When mailmanctl is executed as root the checkprivs function performs setgid and setuid to reduce the process privileges. But mailmanctl fails to set the supplemental groups of the process to those of the setuid'ed user, effectively leaving the processes with the same group privileges as root and, potentially, without the group privileges of the setuid'ed user. This patch uses os.setgroups() to fix that. Problem definition and solution by Jonas Meurer. I'm just filing the bug fix for him. Apply the patch from within the Mailman build directory with: patch -p1 < path-to-patch-file ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-12-14 12:58 Message: Logged In: YES user_id=12800 Accepted for Mailman 2.1.4, with a slight recoding; note that os.setgroups() isn't available in Python 2.1, which we still support. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-09-30 16:45 Message: Logged In: YES user_id=75166 grpsec-2.1.3-0.1.patch is a MM 2.1.3 compatible version of the patch ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=777444&group_id=103 From noreply at sourceforge.net Sun Dec 14 21:27:48 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sun Dec 14 21:27:52 2003 Subject: [ mailman-Patches-860135 ] handle DiscardMessage in ToDigest handler Message-ID: Patches item #860135, was opened at 2003-12-15 13:27 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=860135&group_id=103 Category: mail delivery Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Martin Pool (mbp) Assigned to: Nobody/Anonymous (nobody) Summary: handle DiscardMessage in ToDigest handler Initial Comment: Our scrubber was raising DiscardMessage exceptions when trying to scrub messages from the digest. This situation may have arisen because of a configuration change that allowed some messages to get into the digest mailbox when they would previously have been scrubbed out. In any case, it was causing exceptions like this: Traceback (most recent call last): File "/usr/local/mailman/cron/senddigests", line 94, in ? main() File "/usr/local/mailman/cron/senddigests", line 86, in main mlist.send_digest_now() File "/usr/local/mailman/Mailman/Digester.py", line 60, in send_digest_now ToDigest.send_digests(self, mboxfp) File "/usr/local/mailman/Mailman/Handlers/ToDigest.py", line 131, in send_digests send_i18n_digests(mlist, mboxfp) File "/usr/local/mailman/Mailman/Handlers/ToDigest.py", line 304, in send_i18n_digests msg = scrubber(mlist, msg) File "/usr/local/mailman/Mailman/Handlers/Scrubber.py", line 178, in process raise DiscardMessage Mailman.Errors.DiscardMessage It seems reasonable to have the ToDigest handler respond to these exceptions by discarding the message, per this patch --- ToDigest.py.orig Mon Dec 15 02:21:51 2003 +++ ToDigest.py Mon Dec 15 02:23:19 2003 @@ -44,6 +44,7 @@ from Mailman import Utils from Mailman import Message from Mailman import i18n +from Mailman import Errors from Mailman.Mailbox import Mailbox from Mailman.MemberAdaptor import ENABLED from Mailman.Handlers.Decorate import decorate @@ -301,7 +302,10 @@ print >> plainmsg, separator30 print >> plainmsg # Use Mailman.Handlers.Scrubber.process() to get plain text - msg = scrubber(mlist, msg) + try: + msg = scrubber(mlist, msg) + except (Errors.DiscardMessage): + continue # Honor the default setting for h in mm_cfg.PLAIN_DIGEST_KEEP_HEADERS: if msg[h]: ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=860135&group_id=103 From noreply at sourceforge.net Mon Dec 15 09:52:03 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Dec 15 09:52:06 2003 Subject: [ mailman-Bugs-860372 ] reply-to munging copy from header Message-ID: Bugs item #860372, was opened at 2003-12-15 09: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=860372&group_id=103 Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 7 Submitted By: Barry A. Warsaw (bwarsaw) Assigned to: Barry A. Warsaw (bwarsaw) Summary: reply-to munging copy from header Initial Comment: There should be a reply-to munging option to copy the from header into the reply-to header. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=860372&group_id=103 From noreply at sourceforge.net Mon Dec 15 11:13:15 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Dec 15 11:13:42 2003 Subject: [ mailman-Patches-444884 ] Integration of Mailman & htdig for archi Message-ID: Patches item #444884, was opened at 2001-07-26 18:27 Message generated for change (Comment added) made by ppsys You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=444884&group_id=103 Category: Unofficial 2.0 patch Group: Mailman 2.2 / 3.0 Status: Open Resolution: None Priority: 3 Submitted By: Richard Barrett (ppsys) Assigned to: Barry A. Warsaw (bwarsaw) Summary: Integration of Mailman & htdig for archi Initial Comment: This patch is applicable to Mailman 2.0.6 release that has had search enhancement patch 444879 patch installed - if your Defaults.py has the ARCHIVE_INDEXING_ENABLE and ARCHIVE_INDEXING_DISABLE in it then you've got that patch. It replaces earlier patches 401670 and 402423 and is mainly to correct some problems arising from fixes introduced into Mailman by bug fix releases since the 402423 patch. This patch integrates htdig with Mailman and provides: 1. per list search facility with a search form on the list's TOC page. 2. maintenance of privacy of private archives which requires the user to establish their credentials via the normal private archive access before any access via htdig is allowed. 3. a common base URL for both public and private archive access via htsearch results so that htdig indices are unaffected by changingan archive from private to public and vice versa. All access to archives via htdig is controlled by a new wrapped cgi- bin script called htdig.py. 4. a new cron activated script and extra crontab entry which runs htdig regularly to maintain the per list search indices. 5. automatic creation, deletion and maintenance of htdig configuration files and such. Beyond installing htdig and telling Mailman where it is via mm_cfg you do not have to do any other setup. Well not quite you do have to set up a single per installation symlink to allow htdig to find the automatically generated per list htdig configuration files. You probably want to run this patch as follows: cd patch -p1 < ---------------------------------------------------------------------- >Comment By: Richard Barrett (ppsys) Date: 2003-12-15 16:13 Message: Logged In: YES user_id=75166 htdig-2.1.3-0.5.patch modifies htdig.py and private.py; the security changes introduced by htdig-2.1.3-0.2 patch to these scripts incorrectly blocked access to the listname.mbox/listname.mbox file. The 0.5 revision of the patch corrects this error. This problem and a suggested fix were pointed out to me in a private email by Stephan Berndts stb-mm at spline.de ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-10-22 14:55 Message: Logged In: YES user_id=75166 htdig-2.1.3-0.4.patch provides minor improvements in handling of HTTP request handled by htidg.py which lead to the user receiving an authentication challenge. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-10-19 21:13 Message: Logged In: YES user_id=75166 htdig-2.1.3-0.3.patch.gz add minor private archive security improvements to the patch for MM 2.1.3 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-09-30 20:14 Message: Logged In: YES user_id=75166 htdig-2.1.3-0.1.patch is a MM 2.1.3 compatible version of the patch ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-06-06 17:47 Message: Logged In: YES user_id=75166 last comment should have read: htdig-2.1.2-0.4.patch.gz corrects an error in 2 scripts, mmsearch.py and remote_mmsearch, which caused an exception if list archives were being accessed via HTTPS and a search was performed. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-06-06 17:45 Message: Logged In: YES user_id=75166 htdig-2.1.2-0.3.patch.gz corrects an error in 2 scripts, mmsearch.py and remote_mmsearch, which caused an exception if list archives were being accessed via HTTPS and a search was performed. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-05-01 19:00 Message: Logged In: YES user_id=75166 htdig-2.1.2-0.3.patch.gz adds some minor performance improvement in template handling in MM 2.1.2 You should consider also applying this bug-fis patch: [ 730769 ] template access hierarchy is broken http://sourceforge.net/tracker/index.php? func=detail&aid=730769&group_id=103&atid=100103 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-04-28 15:44 Message: Logged In: YES user_id=75166 htdig-2.1.2-0.2.patch.gz corrects error in file uploaded as htdig-2.1.2-0.1.patch.gz. Sorry for any inconvenience. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-04-28 14:46 Message: Logged In: YES user_id=75166 htdig-2.1.2-0.1.patch.gz is a revised version for MM 2.1.2 compatibility. It also incoporates a previosuly unpublished change to overcome a potential problem with htdig excluced urls - see the INSTALL.htdig-mm file for more information ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-03-21 18:29 Message: Logged In: YES user_id=75166 htdig-2.1.1-0.4.patch.gz fixes a problem with mmsearch handling multi-page search results from htsearch. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-03-21 17:54 Message: Logged In: YES user_id=75166 htdig-2.1.1-0.3.patch.gz fixes a fault when mmsearch.py is rasing an excpetion because it has had a problem running htsearch ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-03-20 14:10 Message: Logged In: YES user_id=75166 htdig-2.1.1-0.2.patch.gz close a security exploit which allows leakage of information held in htdig's per-list search indexes to users not authorized to view private list archives. Read file INSTALL.htdig-mm installed by this patch for details and instructions for upgrading MM installations using earlier versions of this patch ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-02-10 15:50 Message: Logged In: YES user_id=75166 htdig-2.1.1-0.1.patch.gz introduces no functional change but applies without offset warnings to MM 2.1.1 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-02-05 18:12 Message: Logged In: YES user_id=75166 It seems it is possible, if this patch is installed, for a list's htdig conf file and the list specific htdig index db files to be read directly through the web interface for list archives. Even if this patch isn't installed it seems a list's pipermail.pck file can also be read directly through the web interface for list archives. This seems to be true for accesses via /pipermail for public lists and via /mailman/private for private lists. The problem does not occur for htdig search results accessed via /mailman/htdig as the htdig.py script is more protective than private.py Broadly speaking the data affected is availble to a user in normal operation which is why I do not consider the issue to be a security breach as such. Adding the following RewriteRule to Apache's httpd.conf prevents the situation, assuming you got the RewriteEngine On: RewriteRule ^(/pipermail/.*)/(pipermail.pck|htdig/[^/]*)$ $1/index.html [F] RewriteRule ^(/mailman/private/.*)/(pipermail.pck|htdig/[^/]*)$ $1/index.htm l [F] You could, of course, substitute an R flag for the F flag on the RewriteRules and be more hacker friendly. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-01-22 14:20 Message: Logged In: YES user_id=75166 htdig-2.1-0.3.patch corrects yet another bug in htdig.py. Hope that all of them! Stops use of obsolete config variable DEFAULT_HOST in several files. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-01-15 20:18 Message: Logged In: YES user_id=75166 htdig-2.1-0.2.patch corrects a bug in htdig.py and deals with an adverse interaction between htdig.py and a bug in $prefix/scripts/driver (see #668685 for a patch to fix this). It also improves the content type and security handling by htdig.py for MM 2.1 version of patch ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-01-15 20:14 Message: Logged In: YES user_id=75166 Uploaded wrong file mailer-2.0.13-0.4.patch on last attempt. Should have been htdig-2.0.13-0.4.patch which improves the content type and security handling by htdig.py for MM 2.0.13 version of patch. Please ignore mailer-2.0.13-0.4.patch file ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-01-15 20:09 Message: Logged In: YES user_id=75166 mailer-2.0.13-0.4.patch improves the content type and security handling by htdig.py for MM 2.0.13 version of patch ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-01-02 16:07 Message: Logged In: YES user_id=75166 htdig-2.1-0.1.patch is a revised version of the patch that is compatible with MM 2.1 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-12-11 11:48 Message: Logged In: YES user_id=75166 htdig-2.1b6-0.1.patch is a revised version of the patch that is compatible with MM 2.1b6 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-12-04 10:53 Message: Logged In: YES user_id=75166 htdig-2.0.13-0.3.patch corrects a minor typo in text appearing in the list TOC after the patch is applied. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-11-27 10:24 Message: Logged In: YES user_id=75166 htdig-2.1b5-0.1.patch is a revised version of the patch that is compatible with MM 2.1b5 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-10-30 11:43 Message: Logged In: YES user_id=75166 htdig-2.1b4-0.1.patch is a revised version of the patch that is compatible with MM 2.1b4 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-10-14 11:50 Message: Logged In: YES user_id=75166 htdig-2.1b3-0.3.patch removes use of the file() function, used instead of the open() function, in three cron scripts added by the patch. Use of the file() function created an unnecessary dependency on Python 2.2 ---------------------------------------------------------------------- Comment By: Colin Mackinlay (cmackinlay) Date: 2002-10-12 16:51 Message: Logged In: YES user_id=624179 Got a workaround! The line referred to in the traceback: file(rundig_run_file, 'w').close() is used to create a 'rundig_last_run' file of lenght 0 bytes Creating this manually (or copying it) means the line isn't called and everything seems to work. Either file() is not a valid function call or my python is broken - I'm not literate enough in python to know the answer though! ---------------------------------------------------------------------- Comment By: Colin Mackinlay (cmackinlay) Date: 2002-10-06 14:18 Message: Logged In: YES user_id=624179 Just rebuilt MM as 2.1b3 with htdig. Upgraded lists which had htdig before work fine New lists give the obvious error: Unable to read word database file Did you run htmerge? Running the cronjob doesn't fix as it used to, message is: Output from command /usr/bin/python - S /usr/local/mailman/cron/nightly_htdig .. Traceback (most recent call last): File "/usr/local/mailman/cron/nightly_htdig", line 153, in ? main() File "/usr/local/mailman/cron/nightly_htdig", line 118, in main file(rundig_run_file, 'w').close() NameError: global name 'file' is not defined The archive/htdig folder only contains the xx.conf file, but no db.xx files If I copy in db.xx files from another list then the problem goes away (except I've now got an invalid set of references!) Is this my elementary error or is it more sinister?! ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-08-15 11:02 Message: Logged In: YES user_id=75166 htdig-2.1b3-0.2.patch corrects a dumb syntax error in htdig- 2.1b3-0.1.patch which will typically show up as logged errors in the operation of the ArchRunner qrunner at line 721 of HyperArch.py ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-08-14 16:51 Message: Logged In: YES user_id=75166 htdig-2.1b3-0.1.patch is a revised version of the patch that is compatible with MM 2.1b3 ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-08-08 16:33 Message: Logged In: YES user_id=12800 I've sent Richard some comments off-line about this patch. Meta comments: the 2.0.x patches can't be officially supported, but I'm going to create an unofficial patches page off the wiki for where the 2.0 patches can be migrated. I think this patch set is too big for MM2.1, but if it's cleaned up as per my private message, let's re-evaluate it for MM2.2 (or 3.0). ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-08-05 10:11 Message: Logged In: YES user_id=75166 htdig-2.0.13-0.2.patch just adds a GPL notice to the patch ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-08-01 16:35 Message: Logged In: YES user_id=75166 htdig-2.1b2-0.1.patch is a revised version of the patch that is compatible with MM 2.1b2 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-07-30 11:25 Message: Logged In: YES user_id=75166 htdig-2.0.13-0.1.patch is purely cosmetic to get no mumble application to MM 2.0.13 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-07-25 15:07 Message: Logged In: YES user_id=75166 Do not use htdig-2.0.12-0.1.patch there is an error in it. Use htdig-2.0.12-0.2.patch instead ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-07-25 14:10 Message: Logged In: YES user_id=75166 htdig-2.0.12-0.1.patch is a revised version of the patch that applies without complaint to MM 2.0.12. It also add a facility for adding site wide htdig configuration attributes to all list specific htdig configuration files. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-05-23 09:59 Message: Logged In: YES user_id=75166 htdig-2.0.11-0.1.patch is a revised version of the patch that is compatible with MM 2.0.11 This version removes an incompatibility with Python 2.2 which caused warning messages to be generated when any of the family cron/nightly_htdig scripts were run. Some guidance on file access permissions for some htdig database files needed by rundig have been added to installation notes. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-04-19 10:59 Message: Logged In: YES user_id=75166 htdig-2.0.10-0.1.patch is a revised version of the patch that is compatible with MM 2.0.10 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-04-08 17:46 Message: Logged In: YES user_id=75166 htdig-2.0.9-0.1.patch is a revised version of the patch that is compatible with MM 2.0.9 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-03-06 16:22 Message: Logged In: YES user_id=75166 htdig-2.1cvs-20020306.patch is a revised version of the patch that is compatible with the code published in mailman CVS on sourceforge as 12:30 GMT 6 Mar 2002 Known deficiency is that the non-English versions of files under $build/templates still contain text in English and need translations I cannot do. Also the necessary pygettext activity and subsequent translations in files under $build/messages remain to be done. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2001-12-17 16:56 Message: Logged In: YES user_id=75166 htdig-2.1cvs-20011217.patch is a revised version of the patch that is compatible with the code published in mailman CVS on sourceforge as 11:50 GMT 17 Dec 2001 The only known deficiency is that the non-English versions of files under $build/templates still contain text in English and need translations I cannot do. Also the necessary pygettext activity and subsequent translations in files under $build/messages remain to be done. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2001-12-13 16:58 Message: Logged In: YES user_id=75166 htdig-2.1a3-0.1.patch is a revised version of the patch that is compatible with the code published in mailman-2.1a3.tgz on sourceforge. The only known deficiency is that the non-English versions of files under $build/templates still contain text in English and need translations I cannot do. Also the necessary pygettext activity and subsequent translations in files under $build/messages remain to be done. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2001-11-28 17:33 Message: Logged In: YES user_id=75166 The htdig-2.0.8-0.1.patch version of the patch resolves a problem that can arise with htdig indexing if the web_page_url for a list uses other than the http addressing (some folks want to use https). While specified as for MM 2.0.8 the revised patch should work OK with 2.0.7, 2.0.6 and probably back as far as 2.0.3. If you do not have the requirement for using other than http addressing in you lists web_page_urls it probably isn't worth the trouble of upgrading to this patch level. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2001-11-28 11:08 Message: Logged In: YES user_id=75166 This patch should also apply without problems to MM 2.0.8 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2001-11-27 12:00 Message: Logged In: YES user_id=75166 This patch should also apply without problems to Mm 2.0.7 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2001-11-09 11:54 Message: Logged In: YES user_id=75166 The htdig-2.0.6-03.patch version of the patch makes some previously hard-coded things configurable and enhances the capability to run the htdig searches and indexing on a different machine to the one delivering Mailman and Mailman's web UI. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=444884&group_id=103 From noreply at sourceforge.net Tue Dec 16 00:16:29 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Dec 16 00:16:34 2003 Subject: [ mailman-Patches-860135 ] handle DiscardMessage in ToDigest handler Message-ID: Patches item #860135, was opened at 2003-12-14 21:27 Message generated for change (Settings changed) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=860135&group_id=103 Category: mail delivery Group: Mailman 2.1 >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Martin Pool (mbp) Assigned to: Nobody/Anonymous (nobody) Summary: handle DiscardMessage in ToDigest handler Initial Comment: Our scrubber was raising DiscardMessage exceptions when trying to scrub messages from the digest. This situation may have arisen because of a configuration change that allowed some messages to get into the digest mailbox when they would previously have been scrubbed out. In any case, it was causing exceptions like this: Traceback (most recent call last): File "/usr/local/mailman/cron/senddigests", line 94, in ? main() File "/usr/local/mailman/cron/senddigests", line 86, in main mlist.send_digest_now() File "/usr/local/mailman/Mailman/Digester.py", line 60, in send_digest_now ToDigest.send_digests(self, mboxfp) File "/usr/local/mailman/Mailman/Handlers/ToDigest.py", line 131, in send_digests send_i18n_digests(mlist, mboxfp) File "/usr/local/mailman/Mailman/Handlers/ToDigest.py", line 304, in send_i18n_digests msg = scrubber(mlist, msg) File "/usr/local/mailman/Mailman/Handlers/Scrubber.py", line 178, in process raise DiscardMessage Mailman.Errors.DiscardMessage It seems reasonable to have the ToDigest handler respond to these exceptions by discarding the message, per this patch --- ToDigest.py.orig Mon Dec 15 02:21:51 2003 +++ ToDigest.py Mon Dec 15 02:23:19 2003 @@ -44,6 +44,7 @@ from Mailman import Utils from Mailman import Message from Mailman import i18n +from Mailman import Errors from Mailman.Mailbox import Mailbox from Mailman.MemberAdaptor import ENABLED from Mailman.Handlers.Decorate import decorate @@ -301,7 +302,10 @@ print >> plainmsg, separator30 print >> plainmsg # Use Mailman.Handlers.Scrubber.process() to get plain text - msg = scrubber(mlist, msg) + try: + msg = scrubber(mlist, msg) + except (Errors.DiscardMessage): + continue # Honor the default setting for h in mm_cfg.PLAIN_DIGEST_KEEP_HEADERS: if msg[h]: ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=860135&group_id=103 From noreply at sourceforge.net Tue Dec 16 01:50:43 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Dec 16 01:50:49 2003 Subject: [ mailman-Bugs-780051 ] senddigests crashes when a whole message is discarded Message-ID: Bugs item #780051, was opened at 2003-07-30 16:25 Message generated for change (Comment added) made by hatukanezumi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=780051&group_id=103 Category: mail delivery Group: 2.1 (stable) Status: Open >Resolution: Duplicate Priority: 5 Submitted By: Hatuka*nezumi (hatukanezumi) Assigned to: Nobody/Anonymous (nobody) Summary: senddigests crashes when a whole message is discarded Initial Comment: Traceback (most recent call last): File "/usr/local/mailman/cron/senddigests", line 94, in ? main() File "/usr/local/mailman/cron/senddigests", line 86, in main mlist.send_digest_now() File "/usr/local/mailman/Mailman/Digester.py", line 60, in send_digest_now ToDigest.send_digests(self, mboxfp) File "/usr/local/mailman/Mailman/Handlers/ToDigest.py", line 130, in send_digests send_i18n_digests(mlist, mboxfp) File "/usr/local/mailman/Mailman/Handlers/ToDigest.py", line 303, in send_i18n_digests msg = scrubber(mlist, msg) File "/usr/local/mailman/Mailman/Handlers/Scrubber.py", line 179, in process raise DiscardMessage Mailman.Errors.DiscardMessage ---------------------------------------------------------------------- >Comment By: Hatuka*nezumi (hatukanezumi) Date: 2003-12-16 15:50 Message: Logged In: YES user_id=529503 this is duplicate to patch #860135. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=780051&group_id=103 From noreply at sourceforge.net Tue Dec 16 07:52:23 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Dec 16 07:52:30 2003 Subject: [ mailman-Bugs-780051 ] senddigests crashes when a whole message is discarded Message-ID: Bugs item #780051, was opened at 2003-07-30 03:25 Message generated for change (Settings changed) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=780051&group_id=103 Category: mail delivery Group: 2.1 (stable) >Status: Closed Resolution: Duplicate Priority: 5 Submitted By: Hatuka*nezumi (hatukanezumi) Assigned to: Nobody/Anonymous (nobody) Summary: senddigests crashes when a whole message is discarded Initial Comment: Traceback (most recent call last): File "/usr/local/mailman/cron/senddigests", line 94, in ? main() File "/usr/local/mailman/cron/senddigests", line 86, in main mlist.send_digest_now() File "/usr/local/mailman/Mailman/Digester.py", line 60, in send_digest_now ToDigest.send_digests(self, mboxfp) File "/usr/local/mailman/Mailman/Handlers/ToDigest.py", line 130, in send_digests send_i18n_digests(mlist, mboxfp) File "/usr/local/mailman/Mailman/Handlers/ToDigest.py", line 303, in send_i18n_digests msg = scrubber(mlist, msg) File "/usr/local/mailman/Mailman/Handlers/Scrubber.py", line 179, in process raise DiscardMessage Mailman.Errors.DiscardMessage ---------------------------------------------------------------------- Comment By: Hatuka*nezumi (hatukanezumi) Date: 2003-12-16 01:50 Message: Logged In: YES user_id=529503 this is duplicate to patch #860135. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=780051&group_id=103 From noreply at sourceforge.net Tue Dec 16 18:15:54 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Dec 16 18:15:56 2003 Subject: [ mailman-Bugs-861346 ] "From" needs to be escaped in archives Message-ID: Bugs item #861346, was opened at 2003-12-16 18: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=861346&group_id=103 Category: None Group: 2.0.x Status: Open Resolution: None Priority: 5 Submitted By: Tim Altman (roynuj) Assigned to: Nobody/Anonymous (nobody) Summary: "From" needs to be escaped in archives Initial Comment: Problem: List archives are stored in the MBOX format, according to RFC 822 and Unix man pages[1]. Lines in message bodies starting with the word "From" need to be correctly escaped/stuffed in the archives (according to the Unix man pages[1] or RFC2646 ?4. 1), so clients importing the messages may correctly recognize message boundaries. This does not occur in Mailman MBOX archives. [1] http://www.gsp.com/cgi-bin/man.cgi? section=5&topic=mbox ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=861346&group_id=103 From noreply at sourceforge.net Tue Dec 16 18:21:08 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Dec 16 18:21:12 2003 Subject: [ mailman-Bugs-861349 ] List-ID able to contain invalid characters Message-ID: Bugs item #861349, was opened at 2003-12-16 18:21 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=861349&group_id=103 Category: mail delivery Group: 2.0.x Status: Open Resolution: None Priority: 5 Submitted By: Tim Altman (roynuj) Assigned to: Nobody/Anonymous (nobody) Summary: List-ID able to contain invalid characters Initial Comment: Problem: List administrators are able to use illegal "List-ID" headers with Mailman. Legal characters in a non-quoted list-id description are: ALPHA / DIGIT / "!" / "#" / "$" / "%" / "&" / "'" / "&" / "'" / "*" / "+" / "-" / "/" / "=" / "?" / "^" / "_" / "`" / "{" / "|" / "}" / "~". Thus, if a List-ID contains an illegal character, it should either be quoted or an error should occur. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=861349&group_id=103 From noreply at sourceforge.net Thu Dec 18 10:04:40 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Dec 18 10:04:47 2003 Subject: [ mailman-Bugs-861346 ] "From" needs to be escaped in archives Message-ID: Bugs item #861346, was opened at 2003-12-16 18:15 Message generated for change (Comment added) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=861346&group_id=103 Category: None Group: 2.0.x >Status: Closed >Resolution: Wont Fix Priority: 5 Submitted By: Tim Altman (roynuj) Assigned to: Nobody/Anonymous (nobody) Summary: "From" needs to be escaped in archives Initial Comment: Problem: List archives are stored in the MBOX format, according to RFC 822 and Unix man pages[1]. Lines in message bodies starting with the word "From" need to be correctly escaped/stuffed in the archives (according to the Unix man pages[1] or RFC2646 ?4. 1), so clients importing the messages may correctly recognize message boundaries. This does not occur in Mailman MBOX archives. [1] http://www.gsp.com/cgi-bin/man.cgi? section=5&topic=mbox ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-12-18 10:04 Message: Logged In: YES user_id=12800 Please upgrade to Mailman 2.1. This won't be fixed in the 2.0.x line. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=861346&group_id=103 From noreply at sourceforge.net Thu Dec 18 10:05:32 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Dec 18 10:05:35 2003 Subject: [ mailman-Bugs-861349 ] List-ID able to contain invalid characters Message-ID: Bugs item #861349, was opened at 2003-12-16 18:21 Message generated for change (Comment added) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=861349&group_id=103 Category: mail delivery Group: 2.0.x >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Tim Altman (roynuj) Assigned to: Nobody/Anonymous (nobody) Summary: List-ID able to contain invalid characters Initial Comment: Problem: List administrators are able to use illegal "List-ID" headers with Mailman. Legal characters in a non-quoted list-id description are: ALPHA / DIGIT / "!" / "#" / "$" / "%" / "&" / "'" / "&" / "'" / "*" / "+" / "-" / "/" / "=" / "?" / "^" / "_" / "`" / "{" / "|" / "}" / "~". Thus, if a List-ID contains an illegal character, it should either be quoted or an error should occur. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-12-18 10:05 Message: Logged In: YES user_id=12800 This won't be fixed in the 2.0.x line, but it will be fixed in Mailman 2.1.4. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=861349&group_id=103 From noreply at sourceforge.net Fri Dec 19 02:08:40 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Dec 19 02:08:49 2003 Subject: [ mailman-Bugs-861346 ] "From" needs to be escaped in archives Message-ID: Bugs item #861346, was opened at 2003-12-16 18:15 Message generated for change (Comment added) made by roynuj You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=861346&group_id=103 Category: None Group: 2.0.x Status: Closed Resolution: Wont Fix Priority: 5 Submitted By: Tim Altman (roynuj) Assigned to: Nobody/Anonymous (nobody) Summary: "From" needs to be escaped in archives Initial Comment: Problem: List archives are stored in the MBOX format, according to RFC 822 and Unix man pages[1]. Lines in message bodies starting with the word "From" need to be correctly escaped/stuffed in the archives (according to the Unix man pages[1] or RFC2646 ?4. 1), so clients importing the messages may correctly recognize message boundaries. This does not occur in Mailman MBOX archives. [1] http://www.gsp.com/cgi-bin/man.cgi? section=5&topic=mbox ---------------------------------------------------------------------- >Comment By: Tim Altman (roynuj) Date: 2003-12-19 02:08 Message: Logged In: YES user_id=932696 Is this already fixed in 2.1.x, then? ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-12-18 10:04 Message: Logged In: YES user_id=12800 Please upgrade to Mailman 2.1. This won't be fixed in the 2.0.x line. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=861346&group_id=103 From noreply at sourceforge.net Fri Dec 19 07:31:06 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Dec 19 07:31:09 2003 Subject: [ mailman-Bugs-862906 ] mail subscription adds u' ' Message-ID: Bugs item #862906, was opened at 2003-12-19 12: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=862906&group_id=103 Category: None Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Sylvie Greverend (sylvieg) Assigned to: Nobody/Anonymous (nobody) Summary: mail subscription adds u' ' Initial Comment: mailman 2.1.3 french when using the mail feature to subcribe (a mail with to: newsletter-request@ww.com subject: subscribe foobar nodigest address=foobar@xx.com The adress that appears in the administrative validation pannel is u'foobar@xx.com ' instead of foobar@xx.com A u' ' has been added thank you sylvie ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=862906&group_id=103 From noreply at sourceforge.net Sun Dec 21 10:49:09 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sun Dec 21 10:49:12 2003 Subject: [ mailman-Bugs-863989 ] Postfix delayed notification not recognized. Message-ID: Bugs item #863989, was opened at 2003-12-21 16: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=863989&group_id=103 Category: bounce detection Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Matthias Andree (m-a) Assigned to: Nobody/Anonymous (nobody) Summary: Postfix delayed notification not recognized. Initial Comment: Hi, I am running Mailman 2.1.3 (stable) with Postfix 2.0.16-20031022. It seems to be running fine with the VERP patch (it is comfortably surprising to see how much Mailman has matured since the unusable 1.1 version - I hated 1.1 but I do like 2.1! You've done wonderful work.) However I have one problem that I cannot resolve myself: Mailman apparently does not parse Postfix' delayed notification which is apparently RFC-1894 conformant (Postfix hasn't been updated to RFC-3464 yet). On superficial inspection, it looks as though Mailman's Bouncers/DSN.py should handle it and return "Stop", as but I'm getting this "uncaught bounce" message which I interpret as "haven't figured anything reasonable from this bounce". The unintelligible bounce is attached and has had mail addresses changed (sed) and the delayed mail header removed for privacy reasons. I can provide the full message to a developer on request, but I cat not put it into a public bug tracker. The MIME structure of Postfix' delay notification is: 1 multipart/report 1.1 text/plain 1.2 message/delivery-status 1.3 text/rfc822-headers The message/delivery-status part has "Action: delayed" in the 2nd header block. See for yourself. Am I misunderstanding Mailman or is Mailman misunderstanding Postfix? Thanks in advance. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=863989&group_id=103 From noreply at sourceforge.net Mon Dec 22 12:58:42 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Dec 22 12:58:45 2003 Subject: [ mailman-Bugs-861346 ] "From" needs to be escaped in archives Message-ID: Bugs item #861346, was opened at 2003-12-16 18:15 Message generated for change (Comment added) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=861346&group_id=103 Category: None Group: 2.0.x Status: Closed Resolution: Wont Fix Priority: 5 Submitted By: Tim Altman (roynuj) Assigned to: Nobody/Anonymous (nobody) Summary: "From" needs to be escaped in archives Initial Comment: Problem: List archives are stored in the MBOX format, according to RFC 822 and Unix man pages[1]. Lines in message bodies starting with the word "From" need to be correctly escaped/stuffed in the archives (according to the Unix man pages[1] or RFC2646 ?4. 1), so clients importing the messages may correctly recognize message boundaries. This does not occur in Mailman MBOX archives. [1] http://www.gsp.com/cgi-bin/man.cgi? section=5&topic=mbox ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-12-22 12:58 Message: Logged In: YES user_id=12800 Yes, in 2.1.3. ---------------------------------------------------------------------- Comment By: Tim Altman (roynuj) Date: 2003-12-19 02:08 Message: Logged In: YES user_id=932696 Is this already fixed in 2.1.x, then? ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-12-18 10:04 Message: Logged In: YES user_id=12800 Please upgrade to Mailman 2.1. This won't be fixed in the 2.0.x line. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=861346&group_id=103 From noreply at sourceforge.net Mon Dec 22 16:46:05 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Dec 22 16:46:10 2003 Subject: [ mailman-Patches-864674 ] Fix: Not able to substitute user login with admin login Message-ID: Patches item #864674, was opened at 2003-12-22 22:46 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=864674&group_id=103 Category: Web UI Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Stephan Berndts (berndts) Assigned to: Nobody/Anonymous (nobody) Summary: Fix: Not able to substitute user login with admin login Initial Comment: As a site admin one sometimes wants to view the private archives of a mailing list. This was possible without problems in older Mailman (2.0.x) installations. Mailman 2.1.3 rejects such login attempts. This patch solves this problem, which I also reported as a bug. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=864674&group_id=103 From noreply at sourceforge.net Mon Dec 22 16:47:43 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Dec 22 16:47:46 2003 Subject: [ mailman-Bugs-864676 ] Not able to substitute user login with admin login Message-ID: Bugs item #864676, was opened at 2003-12-22 22:47 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=864676&group_id=103 Category: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Stephan Berndts (berndts) Assigned to: Nobody/Anonymous (nobody) Summary: Not able to substitute user login with admin login Initial Comment: As a site or list admin I sometimes want to view the private archives of a mailing list. This was possible without problems in older Mailman installations. Mailman 2.1 rejects my login attempts. I even found the reason for the problem: For example in Mailman/Cgi/private.py (nearly the same code exists in roster.py) the authentication is done by calling the following code in line 116: if not mlist.WebAuthenticate((mm_cfg.AuthUser, mm_cfg.AuthListModerator, mm_cfg.AuthListAdmin, mm_cfg.AuthSiteAdmin), password, username): If I try to login with the site password I do not enter a username. Keep this in mind :) In WebAuthenticate (found in SecurityManager. py, l. 203) the authcontexts are passed to Authenticate (also in SecurityManager.py, l. 124) if no cookie exists yet. There the function authenticateMember (OldStyleMemberships.py, l. 105) is called (l. 195) for the first entry in authcontexts (AuthUser) and calls getMemberPassword (OldStyleMemberships.py, l. 99) which raises an Errors.NotAMemberError exception; that's ok as I did not provide a username. But: The exception is first handled in WebAuthenticate, bypassing Authenticate were all possible authcontexts should be given a try before returning a failure. I submitted a patch (#864674) which puts a try-except-block around the call of authenticateMember in SecurityManager.py (l. 195) which prevents exiting the for-loop before all possible authcontexts are checked. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=864676&group_id=103 From noreply at sourceforge.net Mon Dec 22 16:59:28 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Dec 22 16:59:43 2003 Subject: [ mailman-Bugs-864676 ] Not able to substitute user login with admin login Message-ID: Bugs item #864676, was opened at 2003-12-22 22:47 Message generated for change (Comment added) made by berndts You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=864676&group_id=103 Category: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Stephan Berndts (berndts) Assigned to: Nobody/Anonymous (nobody) Summary: Not able to substitute user login with admin login Initial Comment: As a site or list admin I sometimes want to view the private archives of a mailing list. This was possible without problems in older Mailman installations. Mailman 2.1 rejects my login attempts. I even found the reason for the problem: For example in Mailman/Cgi/private.py (nearly the same code exists in roster.py) the authentication is done by calling the following code in line 116: if not mlist.WebAuthenticate((mm_cfg.AuthUser, mm_cfg.AuthListModerator, mm_cfg.AuthListAdmin, mm_cfg.AuthSiteAdmin), password, username): If I try to login with the site password I do not enter a username. Keep this in mind :) In WebAuthenticate (found in SecurityManager. py, l. 203) the authcontexts are passed to Authenticate (also in SecurityManager.py, l. 124) if no cookie exists yet. There the function authenticateMember (OldStyleMemberships.py, l. 105) is called (l. 195) for the first entry in authcontexts (AuthUser) and calls getMemberPassword (OldStyleMemberships.py, l. 99) which raises an Errors.NotAMemberError exception; that's ok as I did not provide a username. But: The exception is first handled in WebAuthenticate, bypassing Authenticate were all possible authcontexts should be given a try before returning a failure. I submitted a patch (#864674) which puts a try-except-block around the call of authenticateMember in SecurityManager.py (l. 195) which prevents exiting the for-loop before all possible authcontexts are checked. ---------------------------------------------------------------------- >Comment By: Stephan Berndts (berndts) Date: 2003-12-22 22:59 Message: Logged In: YES user_id=129854 Sorry for the -stuff. It makes the bug report hard to read -- I intented the opposite :( I hoped it would work ... and found no documentation about reporting bugs. Stephan ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=864676&group_id=103 From noreply at sourceforge.net Mon Dec 22 17:33:03 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Dec 22 17:33:07 2003 Subject: [ mailman-Bugs-864700 ] Extra period in attachment name problem Message-ID: Bugs item #864700, was opened at 2003-12-22 14:33 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=864700&group_id=103 Category: None Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Kevin W. Gagel (kwgagel) Assigned to: Nobody/Anonymous (nobody) Summary: Extra period in attachment name problem Initial Comment: Having more than one period "." in the name of an attachment causes mailman to disregard portions of the file name, including the extention of the file. For example a file named: PRESIDENT'S NEWSLETTER NO. 2 - 2003-2004 ACADEMIC December.pdf Results in a file attachment of: PRESIDENT'S_NEWSLETTER_NO._2_-_2003- 2004_ACADEMIC (the above is wraped by the textbox input). Sending the same file attachment directly to a user does not cause this problem. Sending it through mailman does result in the change to the file name and extenton. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=864700&group_id=103 From noreply at sourceforge.net Tue Dec 23 14:35:57 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Dec 23 14:36:35 2003 Subject: [ mailman-Patches-657951 ] Generate RSS summary in archives Message-ID: Patches item #657951, was opened at 2002-12-23 19:17 Message generated for change (Comment added) made by codewhacker You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=657951&group_id=103 Category: Pipermail Group: Mailman 2.2 / 3.0 Status: Open Resolution: None Priority: 9 Submitted By: A.M. Kuchling (akuchling) Assigned to: Nobody/Anonymous (nobody) Summary: Generate RSS summary in archives Initial Comment: Here's a first-draft patch. Things that need fixing: * The generated RSS feed needs to be validated. (It passed the W3C's RDF validator, but RSS validators still need to be checked.) * The date should be given in YYYY-MM-DD format, which requires parsing the .fromdate attribute. * How do I get the URL for an archived message? The generated RSS currently just uses the filename, which is wrong. How do I get at the PUBLIC_ARCHIVE_URL setting? * Getting the most recent N postings is inefficient; the code loops through all of the archived messages and takes the last N of them. We could add .last() and .prev() methods to the Database class, but that's more ambitious for 2.1beta than I like. (Would be nice to get this into 2.1final...) * The list index page should have a LINK element pointing to the RSS file. Please make any comments you have, and I'll rework the patch accordingly. ---------------------------------------------------------------------- Comment By: Roy M. Silvernail (codewhacker) Date: 2003-12-23 19:35 Message: Logged In: YES user_id=670974 I'm trying to enrich the RSS output by adding a proper [description] and a [content:encoded] module, but I am having the devil's own time locating the raw message text. Be happy to contribute a patch if you can point me to the raw content (without the italics markup for quoting). Thanks! ---------------------------------------------------------------------- Comment By: Michael Weber (wookiew) Date: 2003-09-10 16:29 Message: Logged In: YES user_id=863445 So far the patch is included (by the way: i hope that Defaults.py.in in the patch *means* Defaults.py ) and mailman get a restart. Hopefully i add the two lines in listinfo.html ( /de/ because we have german speaking lists) and take a look for the xml file). After search the whole device (only to be sure) i can say: There is no file like this. Is another patch need before? Another setup to make? I cant find any hint here... so i have to ask. But the idea is great... if it work on my lists its genious... regards, Michael running version 2.1.1 ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-09-02 04:15 Message: Logged In: YES user_id=12800 Bumping priority. ---------------------------------------------------------------------- Comment By: A.M. Kuchling (akuchling) Date: 2003-07-15 18:55 Message: Logged In: YES user_id=11375 OK, done! This patch is now ready to go in: some people have looked at the RSS and haven't spotted any problems. Barry, can I please get CVS write access to check this in? ---------------------------------------------------------------------- Comment By: A.M. Kuchling (akuchling) Date: 2003-07-11 01:00 Message: Logged In: YES user_id=11375 Attaching correct version of the patch. ---------------------------------------------------------------------- Comment By: A.M. Kuchling (akuchling) Date: 2003-07-11 00:52 Message: Logged In: YES user_id=11375 Here at last is an updated version of the patch that's crawling closer to being complete. There's now a RSS_NUM_ARTICLES setting in Defaults.py, the generated URLs are correct, and I modified the English template to link to the RSS file. Remaining things: check the generated RSS for correctness; edit all of the other language templates to include the RSS file (I may ask for CVS write access to do that). It would be really nice if the Mailman upgrade script could update existing general list information pages to include the LINK element; any suggestion about how to go about that? ---------------------------------------------------------------------- Comment By: Dan Brickley (danbri) Date: 2003-06-22 15:00 Message: Logged In: YES user_id=7830 OK, I've regenerated the patch with some code which works for me. http://rdfweb.org/2003/06/mailman-rss/rsspatch Health warning: * I suspect it may fail in conditions when get_archives() returns a list not a string (does this ever happen?). * See also problems mentioned below, regenerating partial archives seems tricky. Hope this is useful anyways... Dan ---------------------------------------------------------------------- Comment By: Dan Brickley (danbri) Date: 2003-06-22 11:48 Message: Logged In: YES user_id=7830 I thought I'd have a look at this myself, though have modest knowledge of both Python and MailMan. In the course of trying to patch the patch, I tried running the archiver over just the last couple of messages, to speed things along: "../../bin/arch -s 4390 rdfweb-dev". Traceback (most recent call last): File "../../bin/arch", line 187, in ? main() File "../../bin/arch", line 177, in main archiver.close() File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 310, in close self.write_TOC() File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 1082, in write_TOC rss.write(self.RSS()) File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 769, in RSS date, msgid = self.database.dateIndex.first() AttributeError: HyperDatabase instance has no attribute 'dateIndex' Not sure what's going on there, but this seemed as good a place of any to keep note of it. Investigating... ---------------------------------------------------------------------- Comment By: Dan Brickley (danbri) Date: 2003-06-22 11:04 Message: Logged In: YES user_id=7830 Does anyone have a patch to remove the hardwiring of "2002-December" and get the appropriate date from mailman somehow? ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-04-18 22:43 Message: Logged In: YES user_id=12800 Andrew, to get the url for the archived message use mlist.GetBaseArchiveURL(), which knows about private vs. public archives, the host name and the list name. From there you should be able to tack on just the part of the path under "archives/private/listname". See Mailman/Handlers/Scrubber.py for an example. Only other minor comment: NUM_ARTICLES can probably go in Defaults.py.in ---------------------------------------------------------------------- Comment By: Justin Mason (jmason) Date: 2003-03-26 21:49 Message: Logged In: YES user_id=935 big thumbs up from me too. Much better solution than http://taint.org/mmrss/ ;) ---------------------------------------------------------------------- Comment By: Uche Ogbuji (uche) Date: 2003-03-18 01:09 Message: Logged In: YES user_id=38966 I'd like to add my vote to this item. This is a fantastic idea, Andrew. Thanks. --Uche ---------------------------------------------------------------------- Comment By: A.M. Kuchling (akuchling) Date: 2002-12-23 20:42 Message: Logged In: YES user_id=11375 Updated patch: * Dates are now rendered as ISO-8601 (date only, not the time of the message) * By hard-wiring 2002-December, I got the RSS to validate using Mark Pilgrim's validator. ---------------------------------------------------------------------- Comment By: captain larry (captainlarry) Date: 2002-12-23 19:36 Message: Logged In: YES user_id=147905 Just voting for support here. This is *great* thanks for the patch and I hope the maintainers include it as soon as it's appropriate :) Adam. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-12-23 19:27 Message: Logged In: YES user_id=12800 Deferring until post-2.1 ---------------------------------------------------------------------- Comment By: A.M. Kuchling (akuchling) Date: 2002-12-23 19:21 Message: Logged In: YES user_id=11375 Argh; SF choked on the file upload. Attaching the patch again... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=657951&group_id=103 From noreply at sourceforge.net Wed Dec 24 11:59:57 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Dec 24 12:00:09 2003 Subject: [ mailman-Bugs-835332 ] Stops bloat in pipermail article databases Message-ID: Bugs item #835332, was opened at 2003-11-03 17:04 Message generated for change (Comment added) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=835332&group_id=103 Category: Pipermail Group: 2.1 (stable) >Status: Closed >Resolution: Accepted Priority: 5 Submitted By: Richard Barrett (ppsys) Assigned to: Nobody/Anonymous (nobody) Summary: Stops bloat in pipermail article databases Initial Comment: The standard pipermail archiving code saves the body text, in HTML format, of every article in the -article database of each archived list. This bloats the size of these databases. Because they are pickled data structures, which are loaded into memory in their entirety when archiving operations for a list are being handled, this bloat can substantially prejudice archiver performance and in the limit, for lists carrying heavy traffic and/or receiving large text postings, bring archiving to a grinding halt. This patch changes HyperArch.py and pipermail.py so that the data stored in the pipermail $archives/private/ /database/-article does not include the body text, in HTML format, of each article. This reduces the size of the -article database for each list. The benefits of this are most pronounced with high traffic lists and those to which large text postings are made. The patch also adds a script $prefix/bin/rb-arch which will remove any body text, in HTML format, from existing - article databases; this junk HTML is no longer added when new articles are added to the databases but existing junk HTML is not deleted unless this script is run. The alternative is to run $prefix/bin/arch for a list. Apply the patch from within the Mailman build directory using the command: patch -p1 < path-to-patch-file You use this patch at your own risk and I would appreciate feedback about whether it works for you if you use it or/and any problems you encounter with the patch. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-12-24 11:59 Message: Logged In: YES user_id=12800 Accepted for MM2.1.4. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=835332&group_id=103 From noreply at sourceforge.net Wed Dec 24 12:27:11 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Dec 24 12:27:22 2003 Subject: [ mailman-Patches-828811 ] Reduced listinfo and admin CGI process size Message-ID: Patches item #828811, was opened at 2003-10-23 06:30 Message generated for change (Comment added) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=828811&group_id=103 Category: Web UI Group: Mailman 2.1 >Status: Closed >Resolution: Accepted Priority: 5 Submitted By: Richard Barrett (ppsys) Assigned to: Nobody/Anonymous (nobody) Summary: Reduced listinfo and admin CGI process size Initial Comment: When the CGI scripts listinfo.py and admin.py are generating an overview page listing all the advertised mailing lists, they accumulate in memory a MailingList object for every mailing list to appear on the page. For sites with a large number of lists this can lead to the CGI process becoming quite large. This patch changes the behaviour so that what is accumulated in memory by the scripts is only the information about each list that is necessary to generate the overview page. This should reduce the maximum size reached by the CGI process during their execution. This patch can be applied by running the following command with either $build or $prefix as the current directory, that is, you can apply the patch in the build directory before running ./configure and make install or to the installed system: patch -p1 < path-to-patch-file ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-12-24 12:27 Message: Logged In: YES user_id=12800 Accepted for MM2.1.4 ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-10-23 11:39 Message: Logged In: YES user_id=12800 I haven't looked at the patch, but +1 on the idea. Thanks! ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=828811&group_id=103 From noreply at sourceforge.net Wed Dec 24 12:29:22 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Dec 24 12:29:30 2003 Subject: [ mailman-Patches-760567 ] moderation request message content Message-ID: Patches item #760567, was opened at 2003-06-25 11:25 Message generated for change (Comment added) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=760567&group_id=103 Category: list administration Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Richard Barrett (ppsys) Assigned to: Nobody/Anonymous (nobody) Summary: moderation request message content Initial Comment: This patch makes per-list configurable the inclusion of the body of messages that require moderation in the request messages sent to list moderators. This patch has similar objectives to those of patch #593674 but is a simpler implementation. This adds one list attribute, which can be set or unset via the web admin GUI, and which controls whether the moderated message body is included in the moderator request. Apply the attached patch file with the MM build directory as the current working directory using the command: patch -p1 < path-to-patch-file ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-12-24 12:29 Message: Logged In: YES user_id=12800 I'm going to defer this one until 2.1.5 since I don't want to add any new list attributes at this late date. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-09-30 16:43 Message: Logged In: YES user_id=75166 modinc-2.1.3-0.1.patch is a MM 2.1.3 compatible version of the patch ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-06-25 13:21 Message: Logged In: YES user_id=75166 Missed one changed file from initial patch ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=760567&group_id=103 From noreply at sourceforge.net Wed Dec 24 14:16:46 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Dec 24 14:16:50 2003 Subject: [ mailman-Bugs-865489 ] tunable rejection message for non-members? Message-ID: Bugs item #865489, was opened at 2003-12-24 14:16 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=865489&group_id=103 Category: security/privacy Group: None Status: Open Resolution: None Priority: 5 Submitted By: David Abrahams (david_abrahams) Assigned to: Nobody/Anonymous (nobody) Summary: tunable rejection message for non-members? Initial Comment: I got this at the end of a bitter complaint from someone who couldn't figure out how to get into our mailing lists starting from GMane: > I also recommend cleaning up the newsgroup registration procedure so > that people who are not aware of the unusual requirement of > pre-registration are told why it exists and how to deal with it. > For example, I got this back when I first tried to post: > > You are not allowed to post to this mailing list, and your message has > been automatically rejected. If you think that your messages are > being rejected in error, contact the mailing list owner at > boost-users-owner@lists.boost.org. It appears Mailman allows us to tune the message that "moderated members" get when they post. Ours is: You are posting to a moderated mailing list from an email address that is not subscribed to the list. To facilitate the moderators job, we insist that all postings come from email addresses that are subscribed to the list (this does not mean that you have to receive individual emails from the list, or that you can't use a news group alias to access and post to the list, just that you must register first). Please visit http://lists.boost.org/mailman/listinfo.cgi/boost to register with the list. Thankyou, The Boost List Moderators Unfortunately, it doesn't seem to have a way to tune the message given to users who aren't members. If we want to keep spammers out by requiring registration before posting, *and* we want to moderate first-time posts, but we want users to get a nice explanation of how to get posting privileges, what can we do? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=865489&group_id=103 From noreply at sourceforge.net Thu Dec 25 00:02:00 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Dec 25 00:02:10 2003 Subject: [ mailman-Bugs-864700 ] Extra period in attachment name problem Message-ID: Bugs item #864700, was opened at 2003-12-22 17:33 Message generated for change (Comment added) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=864700&group_id=103 Category: None Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Kevin W. Gagel (kwgagel) Assigned to: Nobody/Anonymous (nobody) Summary: Extra period in attachment name problem Initial Comment: Having more than one period "." in the name of an attachment causes mailman to disregard portions of the file name, including the extention of the file. For example a file named: PRESIDENT'S NEWSLETTER NO. 2 - 2003-2004 ACADEMIC December.pdf Results in a file attachment of: PRESIDENT'S_NEWSLETTER_NO._2_-_2003- 2004_ACADEMIC (the above is wraped by the textbox input). Sending the same file attachment directly to a user does not cause this problem. Sending it through mailman does result in the change to the file name and extenton. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-12-25 00:02 Message: Logged In: YES user_id=12800 Please upload a message which exibits this behavior. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=864700&group_id=103 From noreply at sourceforge.net Thu Dec 25 07:10:02 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Dec 25 07:10:07 2003 Subject: [ mailman-Patches-636412 ] discard old pending posts Message-ID: Patches item #636412, was opened at 2002-11-11 00:39 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=636412&group_id=103 Category: None Group: Mailman 2.2 / 3.0 >Status: Closed Resolution: None Priority: 7 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: discard old pending posts Initial Comment: This short script will help you to discard old pending posts. I put it in cron dir and run daily with this crontab entry: 55 7 * * * /usr/local/bin/python -S /home/mailman/cron/auto_discard | mail mailman-owner I hope this idea is integrated in cron/checkdb. (sorry I have no time to work now) ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-12-25 12:10 Message: Logged In: YES user_id=67709 closing this patch in favor of #790494. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-03-13 19:52 Message: Logged In: YES user_id=12800 Upping the priority ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-11-18 23:29 Message: Logged In: YES user_id=12800 This would be cool to add to cron/checkdbs. Here are some ideas - either have a MAX_REQUEST_AGE value in Defaults.py or a max_request_age attribute on lists if you want this to be different per-list (which might be a good idea since this is dependent on how often the list admins clear their pendings) - in the checkdbs message, keep a record of how many old ones you expire and mention it in the user notification. e.g. 17 old requests automatically expired. I'll mark this as for MM2.1 group, but it's really going to be pushed back until the following release. ---------------------------------------------------------------------- Comment By: Victor Nolton (ven-x) Date: 2002-11-11 01:37 Message: Logged In: YES user_id=646258 Thank ya! worked perfect! Thank you ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=636412&group_id=103 From noreply at sourceforge.net Thu Dec 25 07:35:47 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Dec 25 07:35:50 2003 Subject: [ mailman-Patches-865661 ] Collection of i18n patches Message-ID: Patches item #865661, was opened at 2003-12-25 12:35 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=865661&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: Collection of i18n patches Initial Comment: This patch works for 1. _at_ substitution for archive. 2. MIME decoded subject and message body in admindb pending post list. 3. i18n personalization. 4. Header/Footer charset adjusting for multiple charset. (works for Latin-15/1 problem, I believe.) 5. i18n message held notice. 6. fix for scrubber bug (atatched message). 7. i18n checkdbs. This collection of patch is for most recent CVS (2.1.4b) as of 12/25/2003 and I hope this is included in 2.1.4-release. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=865661&group_id=103 From noreply at sourceforge.net Thu Dec 25 07:36:54 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Dec 25 07:36:58 2003 Subject: [ mailman-Patches-865661 ] Collection of i18n patches Message-ID: Patches item #865661, was opened at 2003-12-25 12:35 Message generated for change (Settings changed) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=865661&group_id=103 Category: None Group: None Status: Open Resolution: None >Priority: 9 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: Collection of i18n patches Initial Comment: This patch works for 1. _at_ substitution for archive. 2. MIME decoded subject and message body in admindb pending post list. 3. i18n personalization. 4. Header/Footer charset adjusting for multiple charset. (works for Latin-15/1 problem, I believe.) 5. i18n message held notice. 6. fix for scrubber bug (atatched message). 7. i18n checkdbs. This collection of patch is for most recent CVS (2.1.4b) as of 12/25/2003 and I hope this is included in 2.1.4-release. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=865661&group_id=103 From noreply at sourceforge.net Thu Dec 25 07:40:36 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Dec 25 07:40:54 2003 Subject: [ mailman-Patches-670167 ] fix i18n attachment description in archive Message-ID: Patches item #670167, was opened at 2003-01-18 05:58 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=670167&group_id=103 Category: Pipermail Group: Mailman 2.1 >Status: Closed Resolution: Accepted Priority: 8 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: fix i18n attachment description in archive Initial Comment: Bug-ID 669081 (Major attachment handling bug!) is caused inaccurate handling of charset in Scrubber.py. This is caused by misuse of email functions (or by bug in email package). In Scrubber.py, attempt is made to get message charset by part.get_charset() but it returns only None, as far as I experimented. In this patch, message charset is extracted from regular expression pattern in content-type header. This also set the charset of internally crafted message part. ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-12-25 12:40 Message: Logged In: YES user_id=67709 I have opened a new tracker for collection of i18n patch #865661. So, closing this patch. ---------------------------------------------------------------------- Comment By: Guillaume Rousse (guillomovitch) Date: 2003-11-14 09:36 Message: Logged In: YES user_id=144568 What is the status of this patch for mailman 2.1.3 ? ---------------------------------------------------------------------- Comment By: Hugh Caley (hcaley) Date: 2003-05-30 17:23 Message: Logged In: YES user_id=17460 I patched version 2.1.2 of Mail man with patch Scrubber.py.patch.030224.txt, using "patch -p0 Patches item #664209, was opened at 2003-01-08 06:14 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=664209&group_id=103 Category: internationalization Group: Mailman 2.1 >Status: Closed Resolution: None Priority: 7 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: best effort to keep text/plain Initial Comment: When a message come in different charset than list specific one, Decorate.py adds the header and footer in mime attatchments. This patch tries to keep the good-old plain text format by making these texts into unicode and encode in list preferred charset. If it fails, the messages will get mime-multiparted as was the case without this patch. ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-12-25 12:43 Message: Logged In: YES user_id=67709 merged into #865661. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-05-12 00:10 Message: Logged In: YES user_id=67709 If you personalize delivery, i18n user name cause error because the name is stored in unicode. I merge this fix into this Decorate.py.patch.txt ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-02-20 11:42 Message: Logged In: YES user_id=67709 Sorry, there was a error in the previous patch. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-02-20 01:24 Message: Logged In: YES user_id=67709 Refine the code and increment priority. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-01-08 07:34 Message: Logged In: YES user_id=67709 Expand this patch to base64 encoded plain text. apply the second patch Decorate.py.diff2 to the original Decorate.py ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=664209&group_id=103 From noreply at sourceforge.net Thu Dec 25 07:43:45 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Dec 25 07:43:50 2003 Subject: [ mailman-Patches-865661 ] Collection of i18n patches Message-ID: Patches item #865661, was opened at 2003-12-25 12:35 Message generated for change (Settings changed) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=865661&group_id=103 >Category: internationalization >Group: Mailman 2.1 Status: Open Resolution: None Priority: 9 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: Collection of i18n patches Initial Comment: This patch works for 1. _at_ substitution for archive. 2. MIME decoded subject and message body in admindb pending post list. 3. i18n personalization. 4. Header/Footer charset adjusting for multiple charset. (works for Latin-15/1 problem, I believe.) 5. i18n message held notice. 6. fix for scrubber bug (atatched message). 7. i18n checkdbs. This collection of patch is for most recent CVS (2.1.4b) as of 12/25/2003 and I hope this is included in 2.1.4-release. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=865661&group_id=103 From noreply at sourceforge.net Thu Dec 25 07:45:08 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Dec 25 07:45:12 2003 Subject: [ mailman-Patches-672389 ] admindb.py and admin/user notice i18n subject Message-ID: Patches item #672389, was opened at 2003-01-22 12:05 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=672389&group_id=103 Category: internationalization Group: Mailman 2.1 >Status: Closed Resolution: None Priority: 5 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: admindb.py and admin/user notice i18n subject Initial Comment: When a message is hold for approval, notices are sent to the user and administrator. The administrator can later process the message with admindb cgi interface. When an i18n message was held, the subject is shown as mime encoded string and not easily readable. This patch decode the header and show the subject in the list preferred charset. ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-12-25 12:45 Message: Logged In: YES user_id=67709 merged into #865661. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-01-23 00:38 Message: Logged In: YES user_id=67709 I have to change cron/checkdbs also. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=672389&group_id=103 From noreply at sourceforge.net Thu Dec 25 07:48:24 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Dec 25 07:48:35 2003 Subject: [ mailman-Patches-667026 ] HyperArch.py unicode substitution Message-ID: Patches item #667026, was opened at 2003-01-13 07:42 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=667026&group_id=103 Category: Pipermail Group: Mailman 2.1 >Status: Closed Resolution: None Priority: 6 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: HyperArch.py unicode substitution Initial Comment: bin/arch and HyperArch.py produced error when i18n characters are present in the message body. I suspect that the text is in unicode string. This patch tests if text is unicode and then make the substitute string unicode. File "/usr/home/mailman/mailman-21/Mailman/Archiver/pipermail.py", line 592, i n add_article temp = self.format_article(article) File "/usr/home/mailman/mailman-21/Mailman/Archiver/HyperArch.py", line 1192, in format_article self.__processbody_URLquote(lines) File "/usr/home/mailman/mailman-21/Mailman/Archiver/HyperArch.py", line 1131, in __processbody_URLquote text = re.sub('@', _(' at '), text) File "/usr/local/lib/python2.1/sre.py", line 63, in sub return _compile(pattern, 0).sub(repl, string, count) File "/usr/local/lib/python2.1/sre.py", line 164, in _sub return _subn(pattern, template, string, count)[0] File "/usr/local/lib/python2.1/sre.py", line 185, in _subn append(filter(m)) File "/usr/local/lib/python2.1/sre.py", line 173, in filter return sre_parse.expand_template(template, match) File "/usr/local/lib/python2.1/sre_parse.py", line 732, in expand_template return string.join(literals, sep) File "/usr/local/lib/python2.1/string.py", line 128, in join return sep.join(words) UnicodeError: ASCII decoding error: ordinal not in range(128) ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-12-25 12:48 Message: Logged In: YES user_id=67709 merged into #865661. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-02-20 00:26 Message: Logged In: YES user_id=67709 I think this deserves to be included in next release (2.1.2). So, increment priority and clean up old patch. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-02-04 06:45 Message: Logged In: YES user_id=67709 Update this patch for small bug. Charset defaults to 'us-ascii'. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=667026&group_id=103 From noreply at sourceforge.net Fri Dec 26 02:11:42 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Dec 26 02:11:53 2003 Subject: [ mailman-Patches-865661 ] Collection of i18n patches Message-ID: Patches item #865661, was opened at 2003-12-25 12:35 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=865661&group_id=103 Category: internationalization Group: Mailman 2.1 Status: Open Resolution: None Priority: 9 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: Collection of i18n patches Initial Comment: This patch works for 1. _at_ substitution for archive. 2. MIME decoded subject and message body in admindb pending post list. 3. i18n personalization. 4. Header/Footer charset adjusting for multiple charset. (works for Latin-15/1 problem, I believe.) 5. i18n message held notice. 6. fix for scrubber bug (atatched message). 7. i18n checkdbs. This collection of patch is for most recent CVS (2.1.4b) as of 12/25/2003 and I hope this is included in 2.1.4-release. ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-12-26 07:11 Message: Logged In: YES user_id=67709 Update of patch. espacially: 1. improve in 4 above 2. Use of CJKCodecs instead of Japanese and Korean. Now we can use Chinese. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=865661&group_id=103 From noreply at sourceforge.net Fri Dec 26 02:16:02 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Dec 26 02:16:09 2003 Subject: [ mailman-Patches-865661 ] Collection of i18n patches Message-ID: Patches item #865661, was opened at 2003-12-25 12:35 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=865661&group_id=103 Category: internationalization Group: Mailman 2.1 Status: Open Resolution: None Priority: 9 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: Collection of i18n patches Initial Comment: This patch works for 1. _at_ substitution for archive. 2. MIME decoded subject and message body in admindb pending post list. 3. i18n personalization. 4. Header/Footer charset adjusting for multiple charset. (works for Latin-15/1 problem, I believe.) 5. i18n message held notice. 6. fix for scrubber bug (atatched message). 7. i18n checkdbs. This collection of patch is for most recent CVS (2.1.4b) as of 12/25/2003 and I hope this is included in 2.1.4-release. ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-12-26 07:16 Message: Logged In: YES user_id=67709 u Uploading CJKCodecs 1.0 because their site has only CVS and no package to download. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-12-26 07:11 Message: Logged In: YES user_id=67709 Update of patch. espacially: 1. improve in 4 above 2. Use of CJKCodecs instead of Japanese and Korean. Now we can use Chinese. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=865661&group_id=103 From noreply at sourceforge.net Fri Dec 26 02:20:44 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Dec 26 02:20:54 2003 Subject: [ mailman-Patches-865661 ] Collection of i18n patches Message-ID: Patches item #865661, was opened at 2003-12-25 12:35 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=865661&group_id=103 Category: internationalization Group: Mailman 2.1 Status: Open Resolution: None Priority: 9 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: Collection of i18n patches Initial Comment: This patch works for 1. _at_ substitution for archive. 2. MIME decoded subject and message body in admindb pending post list. 3. i18n personalization. 4. Header/Footer charset adjusting for multiple charset. (works for Latin-15/1 problem, I believe.) 5. i18n message held notice. 6. fix for scrubber bug (atatched message). 7. i18n checkdbs. This collection of patch is for most recent CVS (2.1.4b) as of 12/25/2003 and I hope this is included in 2.1.4-release. ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-12-26 07:20 Message: Logged In: YES user_id=67709 You may need patch email package to properly encode plain text with base64. (And others for Japanese messages) ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-12-26 07:16 Message: Logged In: YES user_id=67709 u Uploading CJKCodecs 1.0 because their site has only CVS and no package to download. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-12-26 07:11 Message: Logged In: YES user_id=67709 Update of patch. espacially: 1. improve in 4 above 2. Use of CJKCodecs instead of Japanese and Korean. Now we can use Chinese. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=865661&group_id=103 From noreply at sourceforge.net Fri Dec 26 02:23:44 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Dec 26 02:23:48 2003 Subject: [ mailman-Patches-865661 ] Collection of i18n patches Message-ID: Patches item #865661, was opened at 2003-12-25 12:35 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=865661&group_id=103 Category: internationalization Group: Mailman 2.1 Status: Open Resolution: None Priority: 9 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: Collection of i18n patches Initial Comment: This patch works for 1. _at_ substitution for archive. 2. MIME decoded subject and message body in admindb pending post list. 3. i18n personalization. 4. Header/Footer charset adjusting for multiple charset. (works for Latin-15/1 problem, I believe.) 5. i18n message held notice. 6. fix for scrubber bug (atatched message). 7. i18n checkdbs. This collection of patch is for most recent CVS (2.1.4b) as of 12/25/2003 and I hope this is included in 2.1.4-release. ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-12-26 07:23 Message: Logged In: YES user_id=67709 Sorry but CJKCodecs was too big to upload in this patch area. You can download it from http://mm.tkikuchi.net/CJKCodecs-1.0.tar.gz Cheers, ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-12-26 07:20 Message: Logged In: YES user_id=67709 You may need patch email package to properly encode plain text with base64. (And others for Japanese messages) ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-12-26 07:16 Message: Logged In: YES user_id=67709 u Uploading CJKCodecs 1.0 because their site has only CVS and no package to download. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-12-26 07:11 Message: Logged In: YES user_id=67709 Update of patch. espacially: 1. improve in 4 above 2. Use of CJKCodecs instead of Japanese and Korean. Now we can use Chinese. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=865661&group_id=103 From noreply at sourceforge.net Fri Dec 26 11:37:14 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Dec 26 11:37:17 2003 Subject: [ mailman-Bugs-864676 ] Not able to substitute user login with admin login Message-ID: Bugs item #864676, was opened at 2003-12-22 16:47 Message generated for change (Comment added) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=864676&group_id=103 Category: Web/CGI Group: 2.1 (stable) >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Stephan Berndts (berndts) Assigned to: Nobody/Anonymous (nobody) Summary: Not able to substitute user login with admin login Initial Comment: As a site or list admin I sometimes want to view the private archives of a mailing list. This was possible without problems in older Mailman installations. Mailman 2.1 rejects my login attempts. I even found the reason for the problem: For example in Mailman/Cgi/private.py (nearly the same code exists in roster.py) the authentication is done by calling the following code in line 116: if not mlist.WebAuthenticate((mm_cfg.AuthUser, mm_cfg.AuthListModerator, mm_cfg.AuthListAdmin, mm_cfg.AuthSiteAdmin), password, username): If I try to login with the site password I do not enter a username. Keep this in mind :) In WebAuthenticate (found in SecurityManager. py, l. 203) the authcontexts are passed to Authenticate (also in SecurityManager.py, l. 124) if no cookie exists yet. There the function authenticateMember (OldStyleMemberships.py, l. 105) is called (l. 195) for the first entry in authcontexts (AuthUser) and calls getMemberPassword (OldStyleMemberships.py, l. 99) which raises an Errors.NotAMemberError exception; that's ok as I did not provide a username. But: The exception is first handled in WebAuthenticate, bypassing Authenticate were all possible authcontexts should be given a try before returning a failure. I submitted a patch (#864674) which puts a try-except-block around the call of authenticateMember in SecurityManager.py (l. 195) which prevents exiting the for-loop before all possible authcontexts are checked. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-12-26 11:37 Message: Logged In: YES user_id=12800 Thanks for the bug report and patch. This makes it into 2.1.4. ---------------------------------------------------------------------- Comment By: Stephan Berndts (berndts) Date: 2003-12-22 16:59 Message: Logged In: YES user_id=129854 Sorry for the -stuff. It makes the bug report hard to read -- I intented the opposite :( I hoped it would work ... and found no documentation about reporting bugs. Stephan ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=864676&group_id=103 From noreply at sourceforge.net Fri Dec 26 11:37:40 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Dec 26 11:37:44 2003 Subject: [ mailman-Patches-864674 ] Fix: Not able to substitute user login with admin login Message-ID: Patches item #864674, was opened at 2003-12-22 16:46 Message generated for change (Comment added) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=864674&group_id=103 Category: Web UI Group: Mailman 2.1 >Status: Closed >Resolution: Accepted Priority: 5 Submitted By: Stephan Berndts (berndts) Assigned to: Nobody/Anonymous (nobody) Summary: Fix: Not able to substitute user login with admin login Initial Comment: As a site admin one sometimes wants to view the private archives of a mailing list. This was possible without problems in older Mailman (2.0.x) installations. Mailman 2.1.3 rejects such login attempts. This patch solves this problem, which I also reported as a bug. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-12-26 11:37 Message: Logged In: YES user_id=12800 Accepted for 2.1.4, with changes. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=864674&group_id=103 From noreply at sourceforge.net Fri Dec 26 11:58:52 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Dec 26 11:59:00 2003 Subject: [ mailman-Patches-790494 ] built-in automatic discard Message-ID: Patches item #790494, was opened at 2003-08-18 08:20 Message generated for change (Settings changed) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=790494&group_id=103 Category: list administration Group: Mailman 2.1 Status: Open Resolution: None >Priority: 7 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: built-in automatic discard Initial Comment: This patch is a revision of #636412 (discard old pending post) script. While the script was to be run by cron, this patch gives full feature of 1. site wide default of MAX_DAYS_TO_HOLD in Defaults.py (mm_cfg.py). 2. list admin can set list specific max_days_to_hold through Web GUI 3. integreate in cron/checkdbs and reports the number of discarded messages. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=790494&group_id=103 From noreply at sourceforge.net Fri Dec 26 12:00:27 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Dec 26 12:00:32 2003 Subject: [ mailman-Patches-865661 ] Collection of i18n patches Message-ID: Patches item #865661, was opened at 2003-12-25 07:35 Message generated for change (Comment added) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=865661&group_id=103 Category: internationalization Group: Mailman 2.1 Status: Open Resolution: None Priority: 9 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: Collection of i18n patches Initial Comment: This patch works for 1. _at_ substitution for archive. 2. MIME decoded subject and message body in admindb pending post list. 3. i18n personalization. 4. Header/Footer charset adjusting for multiple charset. (works for Latin-15/1 problem, I believe.) 5. i18n message held notice. 6. fix for scrubber bug (atatched message). 7. i18n checkdbs. This collection of patch is for most recent CVS (2.1.4b) as of 12/25/2003 and I hope this is included in 2.1.4-release. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-12-26 12:00 Message: Logged In: YES user_id=12800 Can you explain more what you mean by: "You may need patch email package to properly encode plain text with base64. (And others for Japanese messages)" ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-12-26 02:23 Message: Logged In: YES user_id=67709 Sorry but CJKCodecs was too big to upload in this patch area. You can download it from http://mm.tkikuchi.net/CJKCodecs-1.0.tar.gz Cheers, ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-12-26 02:20 Message: Logged In: YES user_id=67709 You may need patch email package to properly encode plain text with base64. (And others for Japanese messages) ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-12-26 02:16 Message: Logged In: YES user_id=67709 u Uploading CJKCodecs 1.0 because their site has only CVS and no package to download. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-12-26 02:11 Message: Logged In: YES user_id=67709 Update of patch. espacially: 1. improve in 4 above 2. Use of CJKCodecs instead of Japanese and Korean. Now we can use Chinese. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=865661&group_id=103 From noreply at sourceforge.net Fri Dec 26 13:23:50 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Dec 26 13:24:01 2003 Subject: [ mailman-Patches-865661 ] Collection of i18n patches Message-ID: Patches item #865661, was opened at 2003-12-25 07:35 Message generated for change (Comment added) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=865661&group_id=103 Category: internationalization Group: Mailman 2.1 Status: Open Resolution: None Priority: 9 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: Collection of i18n patches Initial Comment: This patch works for 1. _at_ substitution for archive. 2. MIME decoded subject and message body in admindb pending post list. 3. i18n personalization. 4. Header/Footer charset adjusting for multiple charset. (works for Latin-15/1 problem, I believe.) 5. i18n message held notice. 6. fix for scrubber bug (atatched message). 7. i18n checkdbs. This collection of patch is for most recent CVS (2.1.4b) as of 12/25/2003 and I hope this is included in 2.1.4-release. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-12-26 13:23 Message: Logged In: YES user_id=12800 Okay, I see the patches to email/Charset.py and email/Encoders.py. I think I understand the fix to Encoders.py, but not really the fix to Charset.py. Could you explain in more detail? Also, please provide test cases for these changes. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-12-26 12:00 Message: Logged In: YES user_id=12800 Can you explain more what you mean by: "You may need patch email package to properly encode plain text with base64. (And others for Japanese messages)" ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-12-26 02:23 Message: Logged In: YES user_id=67709 Sorry but CJKCodecs was too big to upload in this patch area. You can download it from http://mm.tkikuchi.net/CJKCodecs-1.0.tar.gz Cheers, ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-12-26 02:20 Message: Logged In: YES user_id=67709 You may need patch email package to properly encode plain text with base64. (And others for Japanese messages) ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-12-26 02:16 Message: Logged In: YES user_id=67709 u Uploading CJKCodecs 1.0 because their site has only CVS and no package to download. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-12-26 02:11 Message: Logged In: YES user_id=67709 Update of patch. espacially: 1. improve in 4 above 2. Use of CJKCodecs instead of Japanese and Korean. Now we can use Chinese. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=865661&group_id=103 From noreply at sourceforge.net Fri Dec 26 13:36:01 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Dec 26 13:36:12 2003 Subject: [ mailman-Patches-865661 ] Collection of i18n patches Message-ID: Patches item #865661, was opened at 2003-12-25 07:35 Message generated for change (Comment added) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=865661&group_id=103 Category: internationalization Group: Mailman 2.1 Status: Open Resolution: None Priority: 9 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: Collection of i18n patches Initial Comment: This patch works for 1. _at_ substitution for archive. 2. MIME decoded subject and message body in admindb pending post list. 3. i18n personalization. 4. Header/Footer charset adjusting for multiple charset. (works for Latin-15/1 problem, I believe.) 5. i18n message held notice. 6. fix for scrubber bug (atatched message). 7. i18n checkdbs. This collection of patch is for most recent CVS (2.1.4b) as of 12/25/2003 and I hope this is included in 2.1.4-release. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-12-26 13:36 Message: Logged In: YES user_id=12800 See attached Encoders.py-for-py234.txt for a patch to Encoders.py that doesn't break the Python 2.3.x test suite. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-12-26 13:23 Message: Logged In: YES user_id=12800 Okay, I see the patches to email/Charset.py and email/Encoders.py. I think I understand the fix to Encoders.py, but not really the fix to Charset.py. Could you explain in more detail? Also, please provide test cases for these changes. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-12-26 12:00 Message: Logged In: YES user_id=12800 Can you explain more what you mean by: "You may need patch email package to properly encode plain text with base64. (And others for Japanese messages)" ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-12-26 02:23 Message: Logged In: YES user_id=67709 Sorry but CJKCodecs was too big to upload in this patch area. You can download it from http://mm.tkikuchi.net/CJKCodecs-1.0.tar.gz Cheers, ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-12-26 02:20 Message: Logged In: YES user_id=67709 You may need patch email package to properly encode plain text with base64. (And others for Japanese messages) ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-12-26 02:16 Message: Logged In: YES user_id=67709 u Uploading CJKCodecs 1.0 because their site has only CVS and no package to download. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-12-26 02:11 Message: Logged In: YES user_id=67709 Update of patch. espacially: 1. improve in 4 above 2. Use of CJKCodecs instead of Japanese and Korean. Now we can use Chinese. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=865661&group_id=103 From noreply at sourceforge.net Fri Dec 26 15:47:37 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Dec 26 15:47:45 2003 Subject: [ mailman-Patches-865661 ] Collection of i18n patches Message-ID: Patches item #865661, was opened at 2003-12-25 07:35 Message generated for change (Comment added) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=865661&group_id=103 Category: internationalization Group: Mailman 2.1 Status: Open Resolution: None Priority: 9 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: Collection of i18n patches Initial Comment: This patch works for 1. _at_ substitution for archive. 2. MIME decoded subject and message body in admindb pending post list. 3. i18n personalization. 4. Header/Footer charset adjusting for multiple charset. (works for Latin-15/1 problem, I believe.) 5. i18n message held notice. 6. fix for scrubber bug (atatched message). 7. i18n checkdbs. This collection of patch is for most recent CVS (2.1.4b) as of 12/25/2003 and I hope this is included in 2.1.4-release. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-12-26 15:47 Message: Logged In: YES user_id=12800 In Scrubber.py, can you explain more why this part is there: + # TK: We (Japanese) need to stringify and re-generate the message + # instance because multiple charsets are used. + try: + msg = message_from_string(str(msg)) + except UnicodeError: + pass IOW, why do you need to stringify and then re-parse the message? Can you provide an example message that this fixes? ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-12-26 13:36 Message: Logged In: YES user_id=12800 See attached Encoders.py-for-py234.txt for a patch to Encoders.py that doesn't break the Python 2.3.x test suite. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-12-26 13:23 Message: Logged In: YES user_id=12800 Okay, I see the patches to email/Charset.py and email/Encoders.py. I think I understand the fix to Encoders.py, but not really the fix to Charset.py. Could you explain in more detail? Also, please provide test cases for these changes. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-12-26 12:00 Message: Logged In: YES user_id=12800 Can you explain more what you mean by: "You may need patch email package to properly encode plain text with base64. (And others for Japanese messages)" ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-12-26 02:23 Message: Logged In: YES user_id=67709 Sorry but CJKCodecs was too big to upload in this patch area. You can download it from http://mm.tkikuchi.net/CJKCodecs-1.0.tar.gz Cheers, ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-12-26 02:20 Message: Logged In: YES user_id=67709 You may need patch email package to properly encode plain text with base64. (And others for Japanese messages) ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-12-26 02:16 Message: Logged In: YES user_id=67709 u Uploading CJKCodecs 1.0 because their site has only CVS and no package to download. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-12-26 02:11 Message: Logged In: YES user_id=67709 Update of patch. espacially: 1. improve in 4 above 2. Use of CJKCodecs instead of Japanese and Korean. Now we can use Chinese. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=865661&group_id=103 From noreply at sourceforge.net Fri Dec 26 17:47:03 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Dec 26 17:47:15 2003 Subject: [ mailman-Patches-865661 ] Collection of i18n patches Message-ID: Patches item #865661, was opened at 2003-12-25 07:35 Message generated for change (Comment added) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=865661&group_id=103 Category: internationalization Group: Mailman 2.1 Status: Open Resolution: None Priority: 9 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: Collection of i18n patches Initial Comment: This patch works for 1. _at_ substitution for archive. 2. MIME decoded subject and message body in admindb pending post list. 3. i18n personalization. 4. Header/Footer charset adjusting for multiple charset. (works for Latin-15/1 problem, I believe.) 5. i18n message held notice. 6. fix for scrubber bug (atatched message). 7. i18n checkdbs. This collection of patch is for most recent CVS (2.1.4b) as of 12/25/2003 and I hope this is included in 2.1.4-release. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-12-26 17:47 Message: Logged In: YES user_id=12800 The Utils.py patch to include oneline() had some problems: - it didn't import email.Header or define UEMPTYSTRING - it shouldn't use oneline as a local var if the function is called oneline Both are fixable. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-12-26 15:47 Message: Logged In: YES user_id=12800 In Scrubber.py, can you explain more why this part is there: + # TK: We (Japanese) need to stringify and re-generate the message + # instance because multiple charsets are used. + try: + msg = message_from_string(str(msg)) + except UnicodeError: + pass IOW, why do you need to stringify and then re-parse the message? Can you provide an example message that this fixes? ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-12-26 13:36 Message: Logged In: YES user_id=12800 See attached Encoders.py-for-py234.txt for a patch to Encoders.py that doesn't break the Python 2.3.x test suite. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-12-26 13:23 Message: Logged In: YES user_id=12800 Okay, I see the patches to email/Charset.py and email/Encoders.py. I think I understand the fix to Encoders.py, but not really the fix to Charset.py. Could you explain in more detail? Also, please provide test cases for these changes. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-12-26 12:00 Message: Logged In: YES user_id=12800 Can you explain more what you mean by: "You may need patch email package to properly encode plain text with base64. (And others for Japanese messages)" ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-12-26 02:23 Message: Logged In: YES user_id=67709 Sorry but CJKCodecs was too big to upload in this patch area. You can download it from http://mm.tkikuchi.net/CJKCodecs-1.0.tar.gz Cheers, ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-12-26 02:20 Message: Logged In: YES user_id=67709 You may need patch email package to properly encode plain text with base64. (And others for Japanese messages) ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-12-26 02:16 Message: Logged In: YES user_id=67709 u Uploading CJKCodecs 1.0 because their site has only CVS and no package to download. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-12-26 02:11 Message: Logged In: YES user_id=67709 Update of patch. espacially: 1. improve in 4 above 2. Use of CJKCodecs instead of Japanese and Korean. Now we can use Chinese. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=865661&group_id=103 From noreply at sourceforge.net Fri Dec 26 19:58:36 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Dec 26 19:58:58 2003 Subject: [ mailman-Patches-865661 ] Collection of i18n patches Message-ID: Patches item #865661, was opened at 2003-12-25 07:35 Message generated for change (Settings changed) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=865661&group_id=103 Category: internationalization Group: Mailman 2.1 >Status: Closed >Resolution: Accepted Priority: 9 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: Collection of i18n patches Initial Comment: This patch works for 1. _at_ substitution for archive. 2. MIME decoded subject and message body in admindb pending post list. 3. i18n personalization. 4. Header/Footer charset adjusting for multiple charset. (works for Latin-15/1 problem, I believe.) 5. i18n message held notice. 6. fix for scrubber bug (atatched message). 7. i18n checkdbs. This collection of patch is for most recent CVS (2.1.4b) as of 12/25/2003 and I hope this is included in 2.1.4-release. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-12-26 19:58 Message: Logged In: YES user_id=12800 I have applied all but the Decorate.py chunk and the Scrubber.py chunk. For Scrubber, please answer the questions below. For Decorate, I'm a little uncomfortable with apply this big of a patch so late in the game. My suggestion would be to split the remaining two patches up into separate (new) SF tracker items. I'm closing this one. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-12-26 17:47 Message: Logged In: YES user_id=12800 The Utils.py patch to include oneline() had some problems: - it didn't import email.Header or define UEMPTYSTRING - it shouldn't use oneline as a local var if the function is called oneline Both are fixable. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-12-26 15:47 Message: Logged In: YES user_id=12800 In Scrubber.py, can you explain more why this part is there: + # TK: We (Japanese) need to stringify and re-generate the message + # instance because multiple charsets are used. + try: + msg = message_from_string(str(msg)) + except UnicodeError: + pass IOW, why do you need to stringify and then re-parse the message? Can you provide an example message that this fixes? ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-12-26 13:36 Message: Logged In: YES user_id=12800 See attached Encoders.py-for-py234.txt for a patch to Encoders.py that doesn't break the Python 2.3.x test suite. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-12-26 13:23 Message: Logged In: YES user_id=12800 Okay, I see the patches to email/Charset.py and email/Encoders.py. I think I understand the fix to Encoders.py, but not really the fix to Charset.py. Could you explain in more detail? Also, please provide test cases for these changes. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-12-26 12:00 Message: Logged In: YES user_id=12800 Can you explain more what you mean by: "You may need patch email package to properly encode plain text with base64. (And others for Japanese messages)" ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-12-26 02:23 Message: Logged In: YES user_id=67709 Sorry but CJKCodecs was too big to upload in this patch area. You can download it from http://mm.tkikuchi.net/CJKCodecs-1.0.tar.gz Cheers, ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-12-26 02:20 Message: Logged In: YES user_id=67709 You may need patch email package to properly encode plain text with base64. (And others for Japanese messages) ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-12-26 02:16 Message: Logged In: YES user_id=67709 u Uploading CJKCodecs 1.0 because their site has only CVS and no package to download. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-12-26 02:11 Message: Logged In: YES user_id=67709 Update of patch. espacially: 1. improve in 4 above 2. Use of CJKCodecs instead of Japanese and Korean. Now we can use Chinese. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=865661&group_id=103 From noreply at sourceforge.net Fri Dec 26 20:03:09 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Dec 26 20:03:15 2003 Subject: [ mailman-Bugs-853996 ] Mail sending 4 times Message-ID: Bugs item #853996, was opened at 2003-12-04 07:27 Message generated for change (Comment added) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=853996&group_id=103 Category: mail delivery Group: 2.1 (stable) >Status: Pending Resolution: None Priority: 5 Submitted By: Denis (d3n) Assigned to: Nobody/Anonymous (nobody) Summary: Mail sending 4 times Initial Comment: Hi, I have upgraded mailman on debian from 2.0.3. to 2.1.1-5.1 Since this upgrade, i have a big problem.All the request messages, reminder of subscription, ... are sending 4times. Denis ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-12-26 20:03 Message: Logged In: YES user_id=12800 Be sure you are not using the Sendmail.py DELIVERY_MODULE (check your mm_cfg.py file and Defaults.py). You want to use SMTPDirect.py as your delivery module. If that's not the problem, you'll have to get more information, since AFAIK, we've never seen this problem before. Check your mta logs and your mailman logs. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=853996&group_id=103 From noreply at sourceforge.net Fri Dec 26 20:04:41 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Dec 26 20:04:45 2003 Subject: [ mailman-Bugs-829982 ] MakeCookie/WebAuthent fail when a user changes the password Message-ID: Bugs item #829982, was opened at 2003-10-25 00:51 Message generated for change (Comment added) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=829982&group_id=103 Category: Web/CGI Group: 2.1 (stable) >Status: Pending Resolution: None Priority: 9 Submitted By: Pablo Chamorro C. (pchamorro) Assigned to: Nobody/Anonymous (nobody) Summary: MakeCookie/WebAuthent fail when a user changes the password Initial Comment: I just created a new list and I suscribed some users, but when a user changes his password Mailman shows this sad message: Bug in Mailman version 2.1.3 We're sorry, we hit a bug! .... Traceback: Traceback (most recent call last): File "/var/mailman/scripts/driver", line 87, in run_main main() File "/var/mailman/Mailman/Cgi/private.py", line 120, in main password, username): File "/var/mailman/Mailman/SecurityManager.py", line 219, in WebAuthenticate print self.MakeCookie(ac, user) File "/var/mailman/Mailman/SecurityManager.py", line 228, in MakeCookie raise ValueError ValueError I could reproduce this error in other server and with others lists and users. I was trying under RH 9.0. Please help me... ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-12-26 20:04 Message: Logged In: YES user_id=12800 Changing status to pending, since more information is needed. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-11-24 21:19 Message: Logged In: YES user_id=12800 Please provide me with a set of instructions that will reproducibly cause the crash. I am unable to make it happen in my test set up. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=829982&group_id=103 From noreply at sourceforge.net Sat Dec 27 01:50:14 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sat Dec 27 01:51:53 2003 Subject: [ mailman-Bugs-863989 ] Postfix delayed notification not recognized. Message-ID: Bugs item #863989, was opened at 2003-12-21 10:49 Message generated for change (Comment added) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=863989&group_id=103 Category: bounce detection Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Matthias Andree (m-a) Assigned to: Nobody/Anonymous (nobody) Summary: Postfix delayed notification not recognized. Initial Comment: Hi, I am running Mailman 2.1.3 (stable) with Postfix 2.0.16-20031022. It seems to be running fine with the VERP patch (it is comfortably surprising to see how much Mailman has matured since the unusable 1.1 version - I hated 1.1 but I do like 2.1! You've done wonderful work.) However I have one problem that I cannot resolve myself: Mailman apparently does not parse Postfix' delayed notification which is apparently RFC-1894 conformant (Postfix hasn't been updated to RFC-3464 yet). On superficial inspection, it looks as though Mailman's Bouncers/DSN.py should handle it and return "Stop", as but I'm getting this "uncaught bounce" message which I interpret as "haven't figured anything reasonable from this bounce". The unintelligible bounce is attached and has had mail addresses changed (sed) and the delayed mail header removed for privacy reasons. I can provide the full message to a developer on request, but I cat not put it into a public bug tracker. The MIME structure of Postfix' delay notification is: 1 multipart/report 1.1 text/plain 1.2 message/delivery-status 1.3 text/rfc822-headers The message/delivery-status part has "Action: delayed" in the 2nd header block. See for yourself. Am I misunderstanding Mailman or is Mailman misunderstanding Postfix? Thanks in advance. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-12-27 01:50 Message: Logged In: YES user_id=12800 Hmm, I get Stop when I run this message through the DSN.py bounce processor, so as near as I can tell, this is working properly. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=863989&group_id=103 From noreply at sourceforge.net Sat Dec 27 02:45:33 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sat Dec 27 02:45:36 2003 Subject: [ mailman-Bugs-862906 ] mail subscription adds u' ' Message-ID: Bugs item #862906, was opened at 2003-12-19 07:31 Message generated for change (Settings changed) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=862906&group_id=103 Category: None Group: 2.1 (stable) >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Sylvie Greverend (sylvieg) Assigned to: Nobody/Anonymous (nobody) Summary: mail subscription adds u' ' Initial Comment: mailman 2.1.3 french when using the mail feature to subcribe (a mail with to: newsletter-request@ww.com subject: subscribe foobar nodigest address=foobar@xx.com The adress that appears in the administrative validation pannel is u'foobar@xx.com ' instead of foobar@xx.com A u' ' has been added thank you sylvie ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=862906&group_id=103 From noreply at sourceforge.net Sat Dec 27 02:56:15 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sat Dec 27 02:56:18 2003 Subject: [ mailman-Bugs-789501 ] README.MACOSX Message-ID: Bugs item #789501, was opened at 2003-08-15 16:52 Message generated for change (Settings changed) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=789501&group_id=103 Category: documentation Group: 2.1 (stable) >Status: Closed >Resolution: Accepted Priority: 5 Submitted By: Robert Daeley (daeley) Assigned to: Nobody/Anonymous (nobody) Summary: README.MACOSX Initial Comment: The README.MACOSX file that came with the 2.1.2 download refers to this URL re "Kathleen Webb posted her experiences in getting Mailman running on Jaguar using Sendmail." -- http://mail.python.org/pipermail/mailman-users/2002-October/022947.html The URL should be: http://mail.python.org/pipermail/mailman-users/2002-October/022944.html ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=789501&group_id=103 From noreply at sourceforge.net Sat Dec 27 02:59:32 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sat Dec 27 02:59:40 2003 Subject: [ mailman-Patches-866238 ] Scrubber for multi-charset language Message-ID: Patches item #866238, was opened at 2003-12-27 07:59 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=866238&group_id=103 Category: internationalization Group: Mailman 2.1 Status: Open Resolution: None Priority: 7 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: Scrubber for multi-charset language Initial Comment: Mailman i18n allows multi-charset for one language eg. for Japanese, 'iso-2022-jp' for mail message and 'euc-jp' for HTML and internal texts. Scrubber.py fails to recognize the latter charset by using get_content_charset() which is getting the mail message charset. Example of this bug is in http://snow.is.kochi-u.ac.jp/pipermail2/mailman2/2003-December/000013.html while we want to get http://snow.is.kochi-u.ac.jp/pipermail2/mailman2/2003-December/000017.html (Compare using their source because your browser may not capable of displaying japanese fonts) This patch tries to use get_charset() first, and if it is empty, use get_content_charset(). Note that the former returns Charset instance not charset string. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=866238&group_id=103 From noreply at sourceforge.net Sat Dec 27 03:02:18 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sat Dec 27 03:02:32 2003 Subject: [ mailman-Patches-865661 ] Collection of i18n patches Message-ID: Patches item #865661, was opened at 2003-12-25 12:35 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=865661&group_id=103 Category: internationalization Group: Mailman 2.1 Status: Closed Resolution: Accepted Priority: 9 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: Collection of i18n patches Initial Comment: This patch works for 1. _at_ substitution for archive. 2. MIME decoded subject and message body in admindb pending post list. 3. i18n personalization. 4. Header/Footer charset adjusting for multiple charset. (works for Latin-15/1 problem, I believe.) 5. i18n message held notice. 6. fix for scrubber bug (atatched message). 7. i18n checkdbs. This collection of patch is for most recent CVS (2.1.4b) as of 12/25/2003 and I hope this is included in 2.1.4-release. ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-12-27 08:02 Message: Logged In: YES user_id=67709 Thank you and OK, Barry. I have submitted a new patch for Scrubber.py which is more descriptive about the problem, I believe. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-12-27 00:58 Message: Logged In: YES user_id=12800 I have applied all but the Decorate.py chunk and the Scrubber.py chunk. For Scrubber, please answer the questions below. For Decorate, I'm a little uncomfortable with apply this big of a patch so late in the game. My suggestion would be to split the remaining two patches up into separate (new) SF tracker items. I'm closing this one. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-12-26 22:47 Message: Logged In: YES user_id=12800 The Utils.py patch to include oneline() had some problems: - it didn't import email.Header or define UEMPTYSTRING - it shouldn't use oneline as a local var if the function is called oneline Both are fixable. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-12-26 20:47 Message: Logged In: YES user_id=12800 In Scrubber.py, can you explain more why this part is there: + # TK: We (Japanese) need to stringify and re-generate the message + # instance because multiple charsets are used. + try: + msg = message_from_string(str(msg)) + except UnicodeError: + pass IOW, why do you need to stringify and then re-parse the message? Can you provide an example message that this fixes? ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-12-26 18:36 Message: Logged In: YES user_id=12800 See attached Encoders.py-for-py234.txt for a patch to Encoders.py that doesn't break the Python 2.3.x test suite. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-12-26 18:23 Message: Logged In: YES user_id=12800 Okay, I see the patches to email/Charset.py and email/Encoders.py. I think I understand the fix to Encoders.py, but not really the fix to Charset.py. Could you explain in more detail? Also, please provide test cases for these changes. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-12-26 17:00 Message: Logged In: YES user_id=12800 Can you explain more what you mean by: "You may need patch email package to properly encode plain text with base64. (And others for Japanese messages)" ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-12-26 07:23 Message: Logged In: YES user_id=67709 Sorry but CJKCodecs was too big to upload in this patch area. You can download it from http://mm.tkikuchi.net/CJKCodecs-1.0.tar.gz Cheers, ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-12-26 07:20 Message: Logged In: YES user_id=67709 You may need patch email package to properly encode plain text with base64. (And others for Japanese messages) ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-12-26 07:16 Message: Logged In: YES user_id=67709 u Uploading CJKCodecs 1.0 because their site has only CVS and no package to download. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-12-26 07:11 Message: Logged In: YES user_id=67709 Update of patch. espacially: 1. improve in 4 above 2. Use of CJKCodecs instead of Japanese and Korean. Now we can use Chinese. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=865661&group_id=103 From noreply at sourceforge.net Sat Dec 27 20:14:18 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sat Dec 27 20:16:51 2003 Subject: [ mailman-Patches-866238 ] Scrubber for multi-charset language Message-ID: Patches item #866238, was opened at 2003-12-27 07:59 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=866238&group_id=103 Category: internationalization Group: Mailman 2.1 Status: Open Resolution: None >Priority: 8 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: Scrubber for multi-charset language Initial Comment: Mailman i18n allows multi-charset for one language eg. for Japanese, 'iso-2022-jp' for mail message and 'euc-jp' for HTML and internal texts. Scrubber.py fails to recognize the latter charset by using get_content_charset() which is getting the mail message charset. Example of this bug is in http://snow.is.kochi-u.ac.jp/pipermail2/mailman2/2003-December/000013.html while we want to get http://snow.is.kochi-u.ac.jp/pipermail2/mailman2/2003-December/000017.html (Compare using their source because your browser may not capable of displaying japanese fonts) This patch tries to use get_charset() first, and if it is empty, use get_content_charset(). Note that the former returns Charset instance not charset string. ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-12-28 01:14 Message: Logged In: YES user_id=67709 Uploading a revised patch to include bug #759841 (multipart/alternative archive) patch. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=866238&group_id=103 From noreply at sourceforge.net Sat Dec 27 20:17:36 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sat Dec 27 20:20:53 2003 Subject: [ mailman-Bugs-759841 ] Multipart/mixed issues in archives Message-ID: Bugs item #759841, was opened at 2003-06-24 14:22 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=759841&group_id=103 Category: Pipermail Group: 2.1 (stable) Status: Open Resolution: None >Priority: 8 Submitted By: Pug Bainter (phelim_gervase) Assigned to: Nobody/Anonymous (nobody) Summary: Multipart/mixed issues in archives Initial Comment: We are having problems with mailing lists that are not being properly stripped down to text content in the archives. When there is multipart/mixed, it doesn't pull the multipart/alternative sections into their appropriate text portions. For example, from content such as the following: ============================================================================== >From ... [...] Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/mixed; boundary=------------InterScan_NT_MIME_Boundary [...] This is a multi-part message in MIME format. --------------InterScan_NT_MIME_Boundary Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C336A1.2C7564BC" Content-Transfer-Encoding: 7bit ------_=_NextPart_001_01C336A1.2C7564BC Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Kevin has a pending checkin that addresses the minss/maxss issue. =20 [...] ------_=_NextPart_001_01C336A1.2C7564BC Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: quoted-printable Message= [...] ============================================================================== I only get the following: ============================================================================== [64bit-compiler-analysis] RE: vpr analysis Syyyy Kyyyyy syyyk at yyy.com Thu Jun 19 14:27:16 CDT 2003 Previous message: [64bit-compiler-analysis] 06-19-03 MSFT 64-Bit C/C++ compiler +improvement discussion Next message: [64bit-compiler-analysis] RE: vpr analysis Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] -------------------------------------------------------------------------------- Skipped content of type multipart/alternative -------------------------------------------------------------------------------- Previous message: [64bit-compiler-analysis] 06-19-03 MSFT 64-Bit C/C++ compiler +improvement discussion Next message: [64bit-compiler-analysis] RE: vpr analysis Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] -------------------------------------------------------------------------------- More information about the 64bit-compiler-analysis mailing list ============================================================================== As you can see, the actual content of the multipart/alternative portion [text/plain and text/html] were completely stripped out instead of being shown a plain text. ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-12-28 01:17 Message: Logged In: YES user_id=67709 The patch by q7joey is merged into my Scrubber.py patch #866238. I hope Barry can integrate it in 2.1.4. ---------------------------------------------------------------------- Comment By: Joe Pruett (q7joey) Date: 2003-09-27 16:48 Message: Logged In: YES user_id=559223 i have a few line patch that seems to make it do what is expected. i can't see how to attach via sourceforge yet, so i'll paste it here: --- /usr/local/src/mailman-2.1.2/Mailman/Handlers/Scrubber.py Fri Feb 7 23:13:50 2003 +++ ./Scrubber.py Sat Sep 27 08:58:46 2003 @@ -286,11 +286,13 @@ # BAW: Martin's original patch suggested we might want to try # generalizing to utf-8, and that's probably a good idea (eventually). text = [] - for part in msg.get_payload(): + for part in msg.walk(): + if part.get_main_type() == 'multipart': + continue # All parts should be scrubbed to text/plain by now. partctype = part.get_content_type() if partctype <> 'text/plain': - text.append(_('Skipped content of type %(partctype)s')) + text.append(_('Skipped content of type %(partctype)s\n')) continue try: t = part.get_payload(decode=1) ---------------------------------------------------------------------- Comment By: Martin RJ. Cleaver (mrjc) Date: 2003-09-27 07:23 Message: Logged In: YES user_id=50125 This fails for many of my users as they habitually attach a photo of themselves in their signatures. They are incredulous at the idea that mailman can't handle it. Thanks ---------------------------------------------------------------------- Comment By: Joe Pruett (q7joey) Date: 2003-09-27 01:26 Message: Logged In: YES user_id=559223 i agree that this should be a high priority issue. a simple message with just multipart/alternative will show up in the archive ok, but if there is any other kind of attachment, then the entire multipart section is skipped and you just get a link for the extra attachment for download/view ability. i haven't started to look at the code (and i'm not a python/mailman person), but i'll report anything i can find. ---------------------------------------------------------------------- Comment By: Martin RJ. Cleaver (mrjc) Date: 2003-09-22 13:34 Message: Logged In: YES user_id=50125 Additionally I think it is appropriate to up the priority on this bug as it causes key functionality to fail. ---------------------------------------------------------------------- Comment By: Martin RJ. Cleaver (mrjc) Date: 2003-09-22 13:26 Message: Logged In: YES user_id=50125 This is causing me real problems! Is there any known workarounds? If I can't fix this I might have to use a different package as presently all my archives are useless! ---------------------------------------------------------------------- Comment By: Pug Bainter (phelim_gervase) Date: 2003-06-24 17:01 Message: Logged In: YES user_id=484284 This appears to be within: def process(mlist, msg, msgdata=None): at around line 276, but I saw no way of making it recurse for multipart/[mixed|alternative] sub-MIME parts. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=759841&group_id=103 From noreply at sourceforge.net Sun Dec 28 17:48:45 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sun Dec 28 17:48:50 2003 Subject: [ mailman-Bugs-785450 ] scripts/driver bug Message-ID: Bugs item #785450, was opened at 2003-08-08 11:37 Message generated for change (Comment added) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=785450&group_id=103 Category: None Group: 2.1 (stable) >Status: Closed >Resolution: Invalid Priority: 5 Submitted By: Kevin N Carpenter (kevinc_63366) Assigned to: Nobody/Anonymous (nobody) Summary: scripts/driver bug Initial Comment: One of my primary list is broke. The other lists appear to be fine. Any help would be greatly appreciated! Note that this occurred in 2.1.0 - I upgraded to 2.1.2 but the problem still exist. Bug in Mailman version 2.1.2 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/admindb.py", line 85, in main mlist = MailList.MailList(listname, lock=0) File "/usr/local/mailman/Mailman/MailList.py", line 124, in __init__ self.Load() File "/usr/local/mailman/Mailman/MailList.py", line 583, in Load dict, e = self.__load(file) File "/usr/local/mailman/Mailman/MailList.py", line 556, in __load dict = loadfunc(fp) UnpicklingError: invalid load key, 'n'. ------------------------------------------------------------- ------------------- Python information: Variable Value sys.version 2.2.3 (#1, Aug 7 2003, 19:30:01) [GCC 3.2.3 20030422 (Gentoo Linux 1.4 3.2.3-r1, propolice)] sys.executable /usr/bin/python sys.prefix /usr sys.exec_prefix /usr sys.path /usr sys.platform linux2 ------------------------------------------------------------- ------------------- Environment variables: Variable Value PYTHONPATH /usr/local/mailman SERVER_SOFTWARE Apache/1.3.27 (Unix) (Gentoo/Linux) PHP/4.3.1 SCRIPT_FILENAME /home/mailman/cgi-bin/admindb SERVER_ADMIN root@localhost SCRIPT_NAME /mailman/admindb SERVER_SIGNATURE Apache/1.3.27 Server at mail.seaplace.org Port 80 REQUEST_METHOD GET HTTP_HOST www.seaplace.org PATH_INFO /reefkeepers SERVER_PROTOCOL HTTP/1.0 QUERY_STRING REQUEST_URI /mailman/admindb/reefkeepers HTTP_ACCEPT */* PATH_TRANSLATED /home/httpd/htdocs/reefkeepers HTTP_USER_AGENT Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; Mon_AutoConfig_v1.02_STL; .NET CLR 1.0.3705; .NET CLR 1.1.4322) HTTP_CONNECTION keep-alive SERVER_NAME mail.seaplace.org REMOTE_ADDR 199.89.234.122 HTTP_X_FORWARDED_FOR 10.133.116.235 REMOTE_PORT 21100 HTTP_ACCEPT_LANGUAGE en-us HTTP_VIA 1.1 ics_server.monsanto.com (ICS 2.2.76) SERVER_ADDR 66.128.118.35 SERVER_PORT 80 GATEWAY_INTERFACE CGI/1.1 HTTP_ACCEPT_ENCODING gzip, deflate UNIQUE_ID PzPApEKAdiMAAF4RtrM DOCUMENT_ROOT /home/httpd/htdocs ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-12-28 17:48 Message: Logged In: YES user_id=12800 This is caused by a corruption in your list's config.pck file. You should move the config.pck.back file to config.pck to restore your list's configuration to the last uncorrupted state. If that doesn't work, you'll have to restore it from backup. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=785450&group_id=103 From noreply at sourceforge.net Sun Dec 28 17:50:54 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sun Dec 28 17:51:04 2003 Subject: [ mailman-Bugs-776850 ] German version: confusing interface Message-ID: Bugs item #776850, was opened at 2003-07-24 06:09 Message generated for change (Comment added) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=776850&group_id=103 Category: Web/CGI Group: None Status: Open Resolution: None Priority: 5 Submitted By: Jan Kellermann (werk21) Assigned to: Peer Heinlein (pheinlein) Summary: German version: confusing interface Initial Comment: In the membership area are two submit buttons: "Submit your Changes" and "set". The 2nd on is to set everyone's moderation bit. In the german version they are "?nderungen vornehmen" and "?nderung ?bernehmen" which is too similar, leading users to wrongly submit. Please change this in the language-module. thx Jan Kellermann ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-12-28 17:50 Message: Logged In: YES user_id=12800 Peer, is this bug still valid? If not, please close this bug report. ---------------------------------------------------------------------- Comment By: Jan Kellermann (werk21) Date: 2003-07-24 06:13 Message: Logged In: YES user_id=737219 BTW you can please change "Membership Management" in "Mitgliederverwaltung" and "Privacy Options" in "Sicherheitseinstellungen" as used in older versions. :) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=776850&group_id=103 From noreply at sourceforge.net Sun Dec 28 22:40:37 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sun Dec 28 22:40:47 2003 Subject: [ mailman-Bugs-863989 ] Postfix delayed notification not recognized. Message-ID: Bugs item #863989, was opened at 2003-12-21 16:49 Message generated for change (Comment added) made by m-a You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=863989&group_id=103 Category: bounce detection Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Matthias Andree (m-a) Assigned to: Nobody/Anonymous (nobody) Summary: Postfix delayed notification not recognized. Initial Comment: Hi, I am running Mailman 2.1.3 (stable) with Postfix 2.0.16-20031022. It seems to be running fine with the VERP patch (it is comfortably surprising to see how much Mailman has matured since the unusable 1.1 version - I hated 1.1 but I do like 2.1! You've done wonderful work.) However I have one problem that I cannot resolve myself: Mailman apparently does not parse Postfix' delayed notification which is apparently RFC-1894 conformant (Postfix hasn't been updated to RFC-3464 yet). On superficial inspection, it looks as though Mailman's Bouncers/DSN.py should handle it and return "Stop", as but I'm getting this "uncaught bounce" message which I interpret as "haven't figured anything reasonable from this bounce". The unintelligible bounce is attached and has had mail addresses changed (sed) and the delayed mail header removed for privacy reasons. I can provide the full message to a developer on request, but I cat not put it into a public bug tracker. The MIME structure of Postfix' delay notification is: 1 multipart/report 1.1 text/plain 1.2 message/delivery-status 1.3 text/rfc822-headers The message/delivery-status part has "Action: delayed" in the 2nd header block. See for yourself. Am I misunderstanding Mailman or is Mailman misunderstanding Postfix? Thanks in advance. ---------------------------------------------------------------------- >Comment By: Matthias Andree (m-a) Date: 2003-12-29 04:40 Message: Logged In: YES user_id=2788 Urgh. Did I say I have these narrow edit forms and line breaking behind my back without preview? Please apologize the awful formatting. ---------------------------------------------------------------------- Comment By: Matthias Andree (m-a) Date: 2003-12-29 04:38 Message: Logged In: YES user_id=2788 Hum, looks like this issue isn't Postfix specific, but affects all systems that send a delay notification. "logs/bounce" contains: Dec 27 20:35:45 2003 (2053) bounce message w/no discernable addresses: Dec 27 20:35:45 2003 (2053) forwarding unrecognized, message-id: If I save exactly this mail (I checked the Message-ID) and feed it to onebounce.py, I'm getting "DSN got Stop", so that part is fine. I've dug a bit deeper, and noticed a difference between onebounce.py and BouncerAPI.ScanMessages. See lines 65ff in BouncerAPI.py: addrs = sys.modules[modname].process(msg) if addrs is Stop: # One of the detectors recognized the bounce, but there were no # addresses to extract. Return the empty list. return [] I wonder if ScanMessages() is doing the right thing, mapping Stop to []. Evidently, the BounceRunner assumes [] is a parse failure (no addresses returned) and ultimately forwards the "delay notification" to the admin contrary to original DSN.py "Stop" intent. To me, it seems as though ScanMessages needed a fix that allows it to propagate both states, "bounce recognized, no addresses" and "bounce unrecognized", back to its caller. I wonder if the "Stop" condition should be exposed to the BounceRunner or some other interface extension in ScanMessages. What do you think? ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-12-27 07:50 Message: Logged In: YES user_id=12800 Hmm, I get Stop when I run this message through the DSN.py bounce processor, so as near as I can tell, this is working properly. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=863989&group_id=103 From noreply at sourceforge.net Sun Dec 28 22:38:37 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sun Dec 28 22:43:30 2003 Subject: [ mailman-Bugs-863989 ] Postfix delayed notification not recognized. Message-ID: Bugs item #863989, was opened at 2003-12-21 16:49 Message generated for change (Comment added) made by m-a You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=863989&group_id=103 Category: bounce detection Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Matthias Andree (m-a) Assigned to: Nobody/Anonymous (nobody) Summary: Postfix delayed notification not recognized. Initial Comment: Hi, I am running Mailman 2.1.3 (stable) with Postfix 2.0.16-20031022. It seems to be running fine with the VERP patch (it is comfortably surprising to see how much Mailman has matured since the unusable 1.1 version - I hated 1.1 but I do like 2.1! You've done wonderful work.) However I have one problem that I cannot resolve myself: Mailman apparently does not parse Postfix' delayed notification which is apparently RFC-1894 conformant (Postfix hasn't been updated to RFC-3464 yet). On superficial inspection, it looks as though Mailman's Bouncers/DSN.py should handle it and return "Stop", as but I'm getting this "uncaught bounce" message which I interpret as "haven't figured anything reasonable from this bounce". The unintelligible bounce is attached and has had mail addresses changed (sed) and the delayed mail header removed for privacy reasons. I can provide the full message to a developer on request, but I cat not put it into a public bug tracker. The MIME structure of Postfix' delay notification is: 1 multipart/report 1.1 text/plain 1.2 message/delivery-status 1.3 text/rfc822-headers The message/delivery-status part has "Action: delayed" in the 2nd header block. See for yourself. Am I misunderstanding Mailman or is Mailman misunderstanding Postfix? Thanks in advance. ---------------------------------------------------------------------- >Comment By: Matthias Andree (m-a) Date: 2003-12-29 04:38 Message: Logged In: YES user_id=2788 Hum, looks like this issue isn't Postfix specific, but affects all systems that send a delay notification. "logs/bounce" contains: Dec 27 20:35:45 2003 (2053) bounce message w/no discernable addresses: Dec 27 20:35:45 2003 (2053) forwarding unrecognized, message-id: If I save exactly this mail (I checked the Message-ID) and feed it to onebounce.py, I'm getting "DSN got Stop", so that part is fine. I've dug a bit deeper, and noticed a difference between onebounce.py and BouncerAPI.ScanMessages. See lines 65ff in BouncerAPI.py: addrs = sys.modules[modname].process(msg) if addrs is Stop: # One of the detectors recognized the bounce, but there were no # addresses to extract. Return the empty list. return [] I wonder if ScanMessages() is doing the right thing, mapping Stop to []. Evidently, the BounceRunner assumes [] is a parse failure (no addresses returned) and ultimately forwards the "delay notification" to the admin contrary to original DSN.py "Stop" intent. To me, it seems as though ScanMessages needed a fix that allows it to propagate both states, "bounce recognized, no addresses" and "bounce unrecognized", back to its caller. I wonder if the "Stop" condition should be exposed to the BounceRunner or some other interface extension in ScanMessages. What do you think? ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-12-27 07:50 Message: Logged In: YES user_id=12800 Hmm, I get Stop when I run this message through the DSN.py bounce processor, so as near as I can tell, this is working properly. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=863989&group_id=103 From noreply at sourceforge.net Wed Dec 31 10:13:08 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Dec 31 10:13:16 2003 Subject: [ mailman-Bugs-776850 ] German version: confusing interface Message-ID: Bugs item #776850, was opened at 2003-07-24 12:09 Message generated for change (Settings changed) made by pheinlein You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=776850&group_id=103 Category: Web/CGI Group: None >Status: Closed Resolution: None Priority: 5 Submitted By: Jan Kellermann (werk21) Assigned to: Peer Heinlein (pheinlein) Summary: German version: confusing interface Initial Comment: In the membership area are two submit buttons: "Submit your Changes" and "set". The 2nd on is to set everyone's moderation bit. In the german version they are "?nderungen vornehmen" and "?nderung ?bernehmen" which is too similar, leading users to wrongly submit. Please change this in the language-module. thx Jan Kellermann ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-12-28 23:50 Message: Logged In: YES user_id=12800 Peer, is this bug still valid? If not, please close this bug report. ---------------------------------------------------------------------- Comment By: Jan Kellermann (werk21) Date: 2003-07-24 12:13 Message: Logged In: YES user_id=737219 BTW you can please change "Membership Management" in "Mitgliederverwaltung" and "Privacy Options" in "Sicherheitseinstellungen" as used in older versions. :) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=776850&group_id=103 From noreply at sourceforge.net Wed Dec 31 10:31:57 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Dec 31 10:32:34 2003 Subject: [ mailman-Bugs-660733 ] pipermail date handling Message-ID: Bugs item #660733, was opened at 2003-01-01 18:29 Message generated for change (Comment added) made by followme You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=660733&group_id=103 Category: Pipermail Group: 2.1 (stable) Status: Open Resolution: None Priority: 7 Submitted By: Bryan Fullerton (fehwalker) Assigned to: Nobody/Anonymous (nobody) Summary: pipermail date handling Initial Comment: I moved my first list to mailman 2.1 and tried to re-generate the pipermail archives (just, ya know, to see how it'd work :), and got the following traceback. This is a list that's been around for a long time (archives back to 1995), and the .mbox file was generated from a majordomo/hypermail archive when it was moved to mailman 2.0 a couple of years ago. Here's a ls -l of the .mbox file: -rw-rw-r-- 1 mailman mailman 17741891 Jan 1 10:36 bryans-list.mbox Here's the traceback: Updating HTML for article 467 Updating HTML for article 468 Updating HTML for article 469 Updating HTML for article 473 Updating HTML for article 472 Pickling archive state into /home/mailman-2.1/archives/private/bryans-list/pipermail.pck Traceback (most recent call last): File "bin/arch", line 187, in ? main() File "bin/arch", line 175, in main archiver.processUnixMailbox(fp, start, end) File "/home/mailman-2.1/Mailman/Archiver/pipermail.py", line 544, in processUnixMailbox m = mbox.next() File "/usr/local/lib/python2.2/mailbox.py", line 34, in next return self.factory(_Subfile(self.fp, start, stop)) File "/home/mailman-2.1/Mailman/Mailbox.py", line 79, in scrubber return mailbox.scrub(msg) File "/home/mailman-2.1/Mailman/Mailbox.py", line 99, in scrub return self._scrubber(self._mlist, msg) File "/home/mailman-2.1/Mailman/Handlers/Scrubber.py", line 132, in process dir = calculate_attachments_dir(mlist, msg, msgdata) File "/home/mailman-2.1/Mailman/Handlers/Scrubber.py", line 93, in calculate_attachments_dir datedir = safe_strftime(fmt, now) File "/home/mailman-2.1/Mailman/Handlers/Scrubber.py", line 77, in safe_strftime return time.strftime(fmt, floatsecs) TypeError: argument must be 9-item sequence, not None I'm guessing it's a header problem in one of the messages, but I'm not sure what. Thanks, Bryan ---------------------------------------------------------------------- Comment By: Zoran Dzelajlija (followme) Date: 2003-12-31 16:31 Message: Logged In: YES user_id=106281 I can confirm this with 2.1.2. Is there a simple way to make arch guess dates better? I would settle for arch using the date of the previous message, but I don't know wher to start digging in the code. ---------------------------------------------------------------------- Comment By: Bryan Fullerton (fehwalker) Date: 2003-01-01 19:45 Message: Logged In: YES user_id=660772 After some investigation, the following (admittedly invalid) date headers cause tracebacks similar to the above. After reformatting them I'm able to generate the archive. Date: 25 Aug 95 18.00 Date: Thursday, 30 October 1997 3:02pm PT Date: Mon, 29 Nov 1999 Pacific Standard Time Note that these messages *didn't* cause bin/arch|pipermail in mailman 2.0.x to fail, though it probably didn't parse them properly. Perhaps trapping the error and/or skipping these messages might be more useful? It also appears that bin/arch is throwing all messages with dates it can't figure out (after the above were removed) into the current day. An example can be seen at http://lists.samurai.com/pipermail/bryans-list/2003-January/thread.html . I'm unsure if there's any way to better handle this, but just wanted to note it - I can create a separate bug report if it's important. Thanks, Bryan ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=660733&group_id=103 From noreply at sourceforge.net Wed Dec 31 12:11:44 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Dec 31 12:11:50 2003 Subject: [ mailman-Feature Requests-824944 ] Yahoogroups Message-ID: Feature Requests item #824944, was opened at 2003-10-16 11:35 Message generated for change (Comment added) made by mainecoder You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=824944&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Alex (halloalex) Assigned to: Nobody/Anonymous (nobody) Summary: Yahoogroups Initial Comment: Hi, I consider to install Mailman on my server to host several communities. But unfortunately up till now Mailman is only designed for mailing lists. So it doesnt offer the possibility to upload files, etc. To be honest, I also think that the design of Yahoogroups is more userfriendly. Has anybody ever thought about to enhance Mailman, so that it can compete with Yahoogroups? Greetings from Alex, who appreciates every hint in this direction ---------------------------------------------------------------------- Comment By: Joe (mainecoder) Date: 2003-12-31 12:11 Message: Logged In: YES user_id=941049 Competition for YahooGroups should be a priority. There are a number of applications that currently exist and can be combined to produce a similar product. The weak link however is a userfriendly Web interface. Create a Web look and feel like Snitz Forums with the power of Mailman... this is the first step to building a true alternative for YahooGroups. ---------------------------------------------------------------------- Comment By: Alex (halloalex) Date: 2003-10-17 12:51 Message: Logged In: YES user_id=767295 Well, unfortunately I am just a poor student with basic computer knowledge and all of my websites are non-profit- projects. So I guess I am not really helpful for you. However, if anyone develops something like Yahoogroups or maybe knows a company that already offers such a script, please inform me. For a stable version I would not even hesitate to pay - lets say- up to 350 to 400 US. Regards, alex ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-10-16 13:16 Message: Logged In: YES user_id=12800 Sure. Introduce me to the VC with money burning holes in his pockets and I think we could do something killer. :) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=824944&group_id=103