From noreply at sourceforge.net Tue Apr 1 12:06:55 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Apr 1 14:51:39 2003 Subject: [ mailman-Patches-703076 ] Updated patch that allows posting authorization for members Message-ID: Patches item #703076, was opened at 2003-03-13 10:52 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=703076&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nathan Neulinger (nneul) Assigned to: Nobody/Anonymous (nobody) Summary: Updated patch that allows posting authorization for members Initial Comment: This patch allows you to specify +listname in the accept_these_nonmembers, hold_these_nonmembers, reject_these_nonmembers, and discard_these_nonmembers boxes in the list configuration, and will dynamically include the members of those lists. This is very useful when you have lists that forward to other lists. For example: mygroup-leaders mygroup-helpers mygroup-workers with mygroup-all forwarding to each of the above. You could put +mygroup-helpers +mygroup-workers +mygroup-leaders in the accept box for each of those lists, and it will allow any of the members of any of the lists to post to the mygroup-all list. Or similar affect for other configurations. -- Nathan ------------------------------------------------------------ Nathan Neulinger EMail: nneul@umr.edu University of Missouri - Rolla Phone: (573) 341-4841 Computing Services Fax: (573) 341-4216 ---------------------------------------------------------------------- >Comment By: Nathan Neulinger (nneul) Date: 2003-04-01 14:06 Message: Logged In: YES user_id=22767 somehow patch is missing... here it is again... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=703076&group_id=103 From noreply at sourceforge.net Tue Apr 1 12:47:52 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Apr 1 15:32:37 2003 Subject: [ mailman-Patches-713522 ] Spambayes integration Message-ID: Patches item #713522, was opened at 2003-04-01 15:47 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=713522&group_id=103 Category: list administration Group: Mailman 2.2 / 3.0 Status: Open Resolution: None Priority: 5 Submitted By: Barry A. Warsaw (bwarsaw) Assigned to: Nobody/Anonymous (nobody) Summary: Spambayes integration Initial Comment: Here's a patch I developed in Jan 2003 to integrate Spambayes http://spambayes.sf.net into Mailman. It's very experimental but provide here for fun. If people like it I could see it becoming part of Mailman 2.2 or 3.0 You need to separately download the spambayes distutils tarball and drop it in Mailman's misc directory. Check that the version value in misc/Makefile.in matches. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=713522&group_id=103 From noreply at sourceforge.net Tue Apr 1 13:19:58 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Apr 1 16:04:41 2003 Subject: [ mailman-Patches-713522 ] Spambayes integration Message-ID: Patches item #713522, was opened at 2003-04-01 15:47 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=713522&group_id=103 Category: list administration Group: Mailman 2.2 / 3.0 Status: Open Resolution: None Priority: 5 Submitted By: Barry A. Warsaw (bwarsaw) Assigned to: Nobody/Anonymous (nobody) Summary: Spambayes integration Initial Comment: Here's a patch I developed in Jan 2003 to integrate Spambayes http://spambayes.sf.net into Mailman. It's very experimental but provide here for fun. If people like it I could see it becoming part of Mailman 2.2 or 3.0 You need to separately download the spambayes distutils tarball and drop it in Mailman's misc directory. Check that the version value in misc/Makefile.in matches. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-04-01 16:19 Message: Logged In: YES user_id=12800 Oh please gawds of SF, accept my burnt offering of a patch as my supplication to your greatness. I have Checkethed the Holy CheckBox and Fillethed in the Holy TextBox. Now I go to Submitteth this Update. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=713522&group_id=103 From noreply at sourceforge.net Tue Apr 1 13:49:50 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Apr 1 16:36:09 2003 Subject: [ mailman-Patches-713522 ] Spambayes integration Message-ID: Patches item #713522, was opened at 2003-04-01 22:47 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=713522&group_id=103 Category: list administration Group: Mailman 2.2 / 3.0 Status: Open Resolution: None Priority: 5 Submitted By: Barry A. Warsaw (bwarsaw) Assigned to: Nobody/Anonymous (nobody) Summary: Spambayes integration Initial Comment: Here's a patch I developed in Jan 2003 to integrate Spambayes http://spambayes.sf.net into Mailman. It's very experimental but provide here for fun. If people like it I could see it becoming part of Mailman 2.2 or 3.0 You need to separately download the spambayes distutils tarball and drop it in Mailman's misc directory. Check that the version value in misc/Makefile.in matches. ---------------------------------------------------------------------- >Comment By: Simone Piunno (pioppo) Date: 2003-04-01 23:49 Message: Logged In: YES user_id=227443 LOL! ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-04-01 23:19 Message: Logged In: YES user_id=12800 Oh please gawds of SF, accept my burnt offering of a patch as my supplication to your greatness. I have Checkethed the Holy CheckBox and Fillethed in the Holy TextBox. Now I go to Submitteth this Update. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=713522&group_id=103 From noreply at sourceforge.net Tue Apr 1 20:37:29 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Apr 1 23:22:13 2003 Subject: [ mailman-Bugs-710678 ] find_member fails using -w option Message-ID: Bugs item #710678, was opened at 2003-03-27 07:05 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=710678&group_id=103 Category: command line scripts Group: 2.1 (stable) >Status: Closed >Resolution: Accepted Priority: 5 Submitted By: Richard Barrett (ppsys) Assigned to: Nobody/Anonymous (nobody) Summary: find_member fails using -w option Initial Comment: When run with the -w option $prefix/bin/find_member Traceback (most recent call last): File "../../bin/find_member", line 185, in ? main() File "../../bin/find_member", line 168, in main matches = scanlists(options) File "../../bin/find_member", line 115, in scanlists entries = matches.get(addr, {}) UnboundLocalError: local variable 'addr' referenced before assignment The findm-2.1.1-0.1.patch corrects the problem. It should be applied with the follwoing command from with the MM build directory as the current working directory: patch -p1 < path-to-patch-file ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=710678&group_id=103 From noreply at sourceforge.net Tue Apr 1 20:48:03 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Apr 1 23:33:55 2003 Subject: [ mailman-Bugs-707612 ] traceback in senddigests Message-ID: Bugs item #707612, was opened at 2003-03-21 11:56 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=707612&group_id=103 Category: None Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Jan Kellermann (werk21) Assigned to: Nobody/Anonymous (nobody) Summary: traceback in senddigests Initial Comment: my senddigests (cron) aborts with this message. my language-version is german, i am working with the cvs- version. Traceback (most recent call last): File "/usr/local/mailman-2.1//cron/senddigests", line 94, in ? main() File "/usr/local/mailman-2.1//cron/senddigests", line 86, in main mlist.send_digest_now() File "/usr/local/mailman-2.1//Mailman/Digester.py", line 60, in send_digest_now ToDigest.send_digests(self, mboxfp) File "/usr/local/mailman- 2.1//Mailman/Handlers/ToDigest.py", line 123, in send_digests send_i18n_digests(mlist, mboxfp) File "/usr/local/mailman- 2.1//Mailman/Handlers/ToDigest.py", line 295, in send_i18n_digests msg = scrubber(mlist, msg) File "/usr/local/mailman- 2.1//Mailman/Handlers/Scrubber.py", line 308, in process t = t.encode(charset, 'replace') File "/usr/lib/python2.2/encodings/__init__.py", line 51, in search_function mod = __import__(modname,globals(),locals(),'*') ValueError: Empty module name ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-04-01 23:48 Message: Logged In: YES user_id=12800 I can't reproduce this. What version of Python are you using and how did you install it? If from some package manager, are you sure you installed all the relevant Python packages? Check any i18n related packages. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=707612&group_id=103 From noreply at sourceforge.net Tue Apr 1 20:51:39 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Apr 1 23:37:31 2003 Subject: [ mailman-Bugs-707608 ] cvs-version: error in qrunner Message-ID: Bugs item #707608, was opened at 2003-03-21 11:50 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=707608&group_id=103 Category: None Group: 2.1 (stable) >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Jan Kellermann (werk21) Assigned to: Nobody/Anonymous (nobody) Summary: cvs-version: error in qrunner Initial Comment: mailman writes the errormessages *directly to console* and in the error-log. Mar 21 16:11:21 2003 (12591) SHUNTING: 1048241610.7517231+289483353c3e3632ab0892d8ceb 8c936f107bc5e Mar 21 16:15:49 2003 qrunner(12304): Traceback (most recent call last): Mar 21 16:15:49 2003 qrunner(12304): File "/usr/local/mailman-2.1/bin/qrunner", line 270, in ? Mar 21 16:15:49 2003 qrunner(12304): main() Mar 21 16:15:49 2003 qrunner(12304): File "/usr/local/mailman-2.1/bin/qrunner", line 230, in main Mar 21 16:15:49 2003 qrunner(12304): qrunner.run() Mar 21 16:15:49 2003 qrunner(12304): File "/usr/local/mailman- 2.1//Mailman/Queue/Runner.py", line 59, in run Mar 21 16:15:49 2003 qrunner(12304): filecnt = self._oneloop() Mar 21 16:15:49 2003 qrunner(12304): File "/usr/local/mailman- 2.1//Mailman/Queue/Runner.py", line 88, in _oneloop Mar 21 16:15:49 2003 qrunner(12304): msg, msgdata = self._switchboard.dequeue(filebase) Mar 21 16:15:49 2003 qrunner(12304): File "/usr/local/mailman- 2.1//Mailman/Queue/Switchboard.py", line 151, in dequeue Mar 21 16:15:49 2003 qrunner(12304): if data.has_key ('rejection-notice'): Mar 21 16:15:49 2003 qrunner(12304): AttributeError : 'NoneType' object has no attribute 'has_key' Mar 21 16:54:24 2003 qrunner(12191): Traceback (most recent call last): Mar 21 16:54:24 2003 qrunner(12191): File "/usr/local/mailman-2.1/bin/qrunner", line 270, in ? Mar 21 16:54:24 2003 qrunner(12191): main() Mar 21 16:54:24 2003 qrunner(12191): File "/usr/local/mailman-2.1/bin/qrunner", line 230, in main Mar 21 16:54:24 2003 qrunner(12191): qrunner.run() Mar 21 16:54:24 2003 qrunner(12191): File "/usr/local/mailman- 2.1//Mailman/Queue/Runner.py", line 59, in run Mar 21 16:54:24 2003 qrunner(12191): filecnt = self._oneloop() Mar 21 16:54:24 2003 qrunner(12191): File "/usr/local/mailman- 2.1//Mailman/Queue/Runner.py", line 88, in _oneloop Mar 21 16:54:24 2003 qrunner(12191): msg, msgdata = self._switchboard.dequeue(filebase) Mar 21 16:54:24 2003 qrunner(12191): File "/usr/local/mailman- 2.1//Mailman/Queue/Switchboard.py", line 151, in dequeue Mar 21 16:54:24 2003 qrunner(12191): if data.has_key ('rejection-notice'): Mar 21 16:54:24 2003 qrunner(12191): AttributeError : 'NoneType' object has no attribute 'has_key' ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=707608&group_id=103 From noreply at sourceforge.net Tue Apr 1 20:27:37 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Apr 1 23:47:18 2003 Subject: [ mailman-Bugs-711564 ] make install fails, something with bin/update Message-ID: Bugs item #711564, was opened at 2003-03-28 15:56 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=711564&group_id=103 Category: configuring/installing Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: ryan pratt (rhpratt) Assigned to: Nobody/Anonymous (nobody) Summary: make install fails, something with bin/update Initial Comment: I am running mailman 2.1.1, python 2.2.2, gcc 2.95.3 on Solaris 9. I've also tried it on Solaris 8. python seems to be working. import random returns fine. ... ... Compiling /opt/mailman/Mailman/Utils.py ... Compiling /opt/mailman/Mailman/Version.py ... Compiling /opt/mailman/Mailman/__init__.py ... Compiling /opt/mailman/Mailman/htmlformat.py ... Compiling /opt/mailman/Mailman/i18n.py ... Compiling /opt/mailman/Mailman/versions.py ... bin/update: downgrade is detected), nothing will be done.^J^J -h/--help^J Print this text and exit.^J^JUse this script to help you update to the latest release of Mailman from^Jsome previous version. It knows about versions back to 1.0b4 (?).^J""": not found bin/update: Perform all necessary upgrades.^J^JUsage: %(PROGRAM)s [options]^J^JOptions:^J -f/--force^J Force running the upgrade procedures. Normally, if the version number^J of the installed Mailman matches the current version number (or a^J : not found bin/update: import: not found bin/update: import: not found bin/update: import: not found bin/update: import: not found bin/update: import: not found bin/update: import: not found bin/update: import: not found bin/update: import: not found bin/update: import: not found bin/update: from: not found bin/update: from: not found bin/update: from: not found bin/update: from: not found bin/update: from: not found bin/update: from: not found bin/update: from: not found bin/update: from: not found bin/update: FRESH: not found bin/update: NOTFRESH: not found bin/update: syntax error at line 58: `(' unexpected *** Error code 2 make: Fatal error: Command failed for target `update' ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-04-01 23:27 Message: Logged In: YES user_id=12800 What happens if you run bin/update (from the installed location) manually? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=711564&group_id=103 From noreply at sourceforge.net Wed Apr 2 09:33:33 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Apr 2 12:18:08 2003 Subject: [ mailman-Bugs-711564 ] make install fails, something with bin/update Message-ID: Bugs item #711564, was opened at 2003-03-28 13:56 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=711564&group_id=103 Category: configuring/installing Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: ryan pratt (rhpratt) Assigned to: Nobody/Anonymous (nobody) Summary: make install fails, something with bin/update Initial Comment: I am running mailman 2.1.1, python 2.2.2, gcc 2.95.3 on Solaris 9. I've also tried it on Solaris 8. python seems to be working. import random returns fine. ... ... Compiling /opt/mailman/Mailman/Utils.py ... Compiling /opt/mailman/Mailman/Version.py ... Compiling /opt/mailman/Mailman/__init__.py ... Compiling /opt/mailman/Mailman/htmlformat.py ... Compiling /opt/mailman/Mailman/i18n.py ... Compiling /opt/mailman/Mailman/versions.py ... bin/update: downgrade is detected), nothing will be done.^J^J -h/--help^J Print this text and exit.^J^JUse this script to help you update to the latest release of Mailman from^Jsome previous version. It knows about versions back to 1.0b4 (?).^J""": not found bin/update: Perform all necessary upgrades.^J^JUsage: %(PROGRAM)s [options]^J^JOptions:^J -f/--force^J Force running the upgrade procedures. Normally, if the version number^J of the installed Mailman matches the current version number (or a^J : not found bin/update: import: not found bin/update: import: not found bin/update: import: not found bin/update: import: not found bin/update: import: not found bin/update: import: not found bin/update: import: not found bin/update: import: not found bin/update: import: not found bin/update: from: not found bin/update: from: not found bin/update: from: not found bin/update: from: not found bin/update: from: not found bin/update: from: not found bin/update: from: not found bin/update: from: not found bin/update: FRESH: not found bin/update: NOTFRESH: not found bin/update: syntax error at line 58: `(' unexpected *** Error code 2 make: Fatal error: Command failed for target `update' ---------------------------------------------------------------------- >Comment By: ryan pratt (rhpratt) Date: 2003-04-02 10:33 Message: Logged In: YES user_id=744675 I get the same error when I run bin/update from /usr/local/pkgs/mailman which is my $prefix. root[sh]@bourbon# bin/update bin/update: downgrade is detected), nothing will be done.^J^J -h/--help^J Print this text and exit.^J^JUse this script to help you update to the latest release of Mailman from^Jsome previous version. It knows about versions back to 1.0b4 (?).^J""": not found bin/update: Perform all necessary upgrades.^J^JUsage: %(PROGRAM)s [options]^J^JOptions:^J -f/--force^J Force running the upgrade procedures. Normally, if the version number^J of the installed Mailman matches the current version number (or a^J : not found bin/update: import: not found bin/update: import: not found bin/update: import: not found bin/update: import: not found bin/update: import: not found bin/update: import: not found bin/update: import: not found bin/update: import: not found bin/update: import: not found Can't open /var/mail/Mailman Can't open /var/mail/Mailman Can't open /var/mail/Mailman Can't open /var/mail/Mailman.LockFile Can't open /var/mail/Mailman.i18n Can't open /var/mail/Mailman.Queue.Switchboard Can't open /var/mail/Mailman.OldStyleMemberships Can't open /var/mail/Mailman.MemberAdaptor bin/update: FRESH: not found bin/update: NOTFRESH: not found bin/update: syntax error at line 58: `(' unexpected ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-04-01 21:27 Message: Logged In: YES user_id=12800 What happens if you run bin/update (from the installed location) manually? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=711564&group_id=103 From noreply at sourceforge.net Wed Apr 2 12:18:56 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Apr 2 15:03:30 2003 Subject: [ mailman-Bugs-714156 ] list_members fails on addresses with high-bit (?) characters Message-ID: Bugs item #714156, was opened at 2003-04-02 20:18 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=714156&group_id=103 Category: command line scripts Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Cabel Sasser (cabelsa) Assigned to: Nobody/Anonymous (nobody) Summary: list_members fails on addresses with high-bit (?) characters Initial Comment: Version: Mailman 2.1.1 Dear Brilliant Mailman People, I'm somewhat urgently trying to export lists from our old machine (which shuts down at the end of the week) to a brand new server. I've created the lists on the new machine, and am trying to use list_members to export the people, so I can re-import them on the new box. However, list_members is apparently failing on any address with high-bit ("funky") characters, and it appears we have quite a few out of our 100,000+ addresses. Here's the error: Traceback (most recent call last): File "./list_members", line 232, in ? main() File "./list_members", line 207, in main s = formataddr((name, addr)).encode(enc, 'replace') UnicodeError: ASCII decoding error: ordinal not in range(128) Knowing absolutely nothing about Python, I put an extra "print" in that function to see what address it was dying on. Here it is: [root@posh bin]# ./list_members transmit-e 000049941552520092563390-0001@t-online.de 000049941552520092563390-0001@t-online.de 007-orange@hanmail.net 007-orange@hanmail.net [...] 1999818@hitel.net 1999818@hitel.net 1@1.com 1@1.com 1@1.ä?? Traceback (most recent call last): File "./list_members", line 234, in ? main() File "./list_members", line 209, in main s = formataddr((name, addr)).encode(enc, 'replace') UnicodeError: ASCII decoding error: ordinal not in range(128) So it looks like 1@1.ä[something] at least one problem address. Is there any way I can work around this bug until an official update? Just deleting the problem members isn't as easy as it seems (the list is hardcoded to 'www.panic.com', and all the admin forms are pointing to that, but www.panic.com is now the new machine...) Thanks for looking at this! ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=714156&group_id=103 From noreply at sourceforge.net Wed Apr 2 12:19:57 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Apr 2 15:04:32 2003 Subject: [ mailman-Bugs-714156 ] list_members fails on addresses with high-bit (?) characters Message-ID: Bugs item #714156, was opened at 2003-04-02 20:18 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=714156&group_id=103 Category: command line scripts Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Cabel Sasser (cabelsa) Assigned to: Nobody/Anonymous (nobody) Summary: list_members fails on addresses with high-bit (?) characters Initial Comment: Version: Mailman 2.1.1 Dear Brilliant Mailman People, I'm somewhat urgently trying to export lists from our old machine (which shuts down at the end of the week) to a brand new server. I've created the lists on the new machine, and am trying to use list_members to export the people, so I can re-import them on the new box. However, list_members is apparently failing on any address with high-bit ("funky") characters, and it appears we have quite a few out of our 100,000+ addresses. Here's the error: Traceback (most recent call last): File "./list_members", line 232, in ? main() File "./list_members", line 207, in main s = formataddr((name, addr)).encode(enc, 'replace') UnicodeError: ASCII decoding error: ordinal not in range(128) Knowing absolutely nothing about Python, I put an extra "print" in that function to see what address it was dying on. Here it is: [root@posh bin]# ./list_members transmit-e 000049941552520092563390-0001@t-online.de 000049941552520092563390-0001@t-online.de 007-orange@hanmail.net 007-orange@hanmail.net [...] 1999818@hitel.net 1999818@hitel.net 1@1.com 1@1.com 1@1.ä?? Traceback (most recent call last): File "./list_members", line 234, in ? main() File "./list_members", line 209, in main s = formataddr((name, addr)).encode(enc, 'replace') UnicodeError: ASCII decoding error: ordinal not in range(128) So it looks like 1@1.ä[something] at least one problem address. Is there any way I can work around this bug until an official update? Just deleting the problem members isn't as easy as it seems (the list is hardcoded to 'www.panic.com', and all the admin forms are pointing to that, but www.panic.com is now the new machine...) Thanks for looking at this! ---------------------------------------------------------------------- >Comment By: Cabel Sasser (cabelsa) Date: 2003-04-02 20:19 Message: Logged In: YES user_id=665207 I apologize. This is a duplicate of bug #660675. Search before you post a bug, Cabel. Jeez. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=714156&group_id=103 From noreply at sourceforge.net Wed Apr 2 21:40:51 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Apr 3 00:26:34 2003 Subject: [ mailman-Bugs-714156 ] list_members fails on addresses with high-bit (?) characters Message-ID: Bugs item #714156, was opened at 2003-04-02 15:18 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=714156&group_id=103 Category: command line scripts Group: 2.1 (stable) >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Cabel Sasser (cabelsa) Assigned to: Nobody/Anonymous (nobody) Summary: list_members fails on addresses with high-bit (?) characters Initial Comment: Version: Mailman 2.1.1 Dear Brilliant Mailman People, I'm somewhat urgently trying to export lists from our old machine (which shuts down at the end of the week) to a brand new server. I've created the lists on the new machine, and am trying to use list_members to export the people, so I can re-import them on the new box. However, list_members is apparently failing on any address with high-bit ("funky") characters, and it appears we have quite a few out of our 100,000+ addresses. Here's the error: Traceback (most recent call last): File "./list_members", line 232, in ? main() File "./list_members", line 207, in main s = formataddr((name, addr)).encode(enc, 'replace') UnicodeError: ASCII decoding error: ordinal not in range(128) Knowing absolutely nothing about Python, I put an extra "print" in that function to see what address it was dying on. Here it is: [root@posh bin]# ./list_members transmit-e 000049941552520092563390-0001@t-online.de 000049941552520092563390-0001@t-online.de 007-orange@hanmail.net 007-orange@hanmail.net [...] 1999818@hitel.net 1999818@hitel.net 1@1.com 1@1.com 1@1.ä?? Traceback (most recent call last): File "./list_members", line 234, in ? main() File "./list_members", line 209, in main s = formataddr((name, addr)).encode(enc, 'replace') UnicodeError: ASCII decoding error: ordinal not in range(128) So it looks like 1@1.ä[something] at least one problem address. Is there any way I can work around this bug until an official update? Just deleting the problem members isn't as easy as it seems (the list is hardcoded to 'www.panic.com', and all the admin forms are pointing to that, but www.panic.com is now the new machine...) Thanks for looking at this! ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-04-03 00:40 Message: Logged In: YES user_id=12800 Actually, I don't think this one's a duplicate. 660675 talks about "funny" characters in realnames, which should be perfectly legal and Mailman should not choke on. But your message is about funny characters in email addresses, which is not legal. I don't know how, but it appears as though Mailman allowed such bogus addresses into its member database. This will cause you pain, and such addresses should not be allowed. MM2.1.2 will disallow such addresses, but won't clean up your existing member database. Here's an article that might help you with that: http://article.gmane.org/gmane.mail.mailman.user/8487/match=find+members ---------------------------------------------------------------------- Comment By: Cabel Sasser (cabelsa) Date: 2003-04-02 15:19 Message: Logged In: YES user_id=665207 I apologize. This is a duplicate of bug #660675. Search before you post a bug, Cabel. Jeez. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=714156&group_id=103 From noreply at sourceforge.net Wed Apr 2 21:42:13 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Apr 3 00:31:06 2003 Subject: [ mailman-Bugs-660675 ] special characters in realnames Message-ID: Bugs item #660675, was opened at 2003-01-01 09:02 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=660675&group_id=103 Category: None Group: 2.1 (stable) >Status: Closed >Resolution: Fixed Priority: 9 Submitted By: Peer Heinlein (pheinlein) Assigned to: Nobody/Anonymous (nobody) Summary: special characters in realnames Initial Comment: Mailman crashs when realnames of members include special language-specifc characters like german "Umlaute" (äöüß). Traceback (most recent call last): File "/usr/lib/mailman/bin/list_members", line 232, in ? main() File "/usr/lib/mailman/bin/list_members", line 207, in main s = formataddr((name, addr)).encode(enc, 'replace') UnicodeError: ASCII decoding error: ordinal not in range(128) It isn`t possible to get a list of all members of this list with list_members or a who command. Mailman has to be able to handle other signs then A-Z and 0-9 in realnames and mailaddresses. Peer ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-04-03 00:42 Message: Logged In: YES user_id=12800 I believe this is now fixed. If not, Peer please let me know! ---------------------------------------------------------------------- Comment By: Peer Heinlein (pheinlein) Date: 2003-01-29 13:06 Message: Logged In: YES user_id=581680 Hi Barry! This problem is really old now, I wrote it to you many weeks ago. It`s a *hugh* daily problem on our server and I really have to solve this problem and can`t wait any more! It is a middle-big problem that "who" and "list_members" doesn`t work, because the listowners aren't able to extract their own listmembers into a file or a seperate list. I have over 75.000 users in our mailinglists and there is no chance to have a working membership-management without the possibility to extract the membership-lists to work with! And it is a *hugh* problem, that the daily heldmessages-reminders to the admins don`t work! The daily cronjob to send out those reminders dies every day with this ASCII decoding error. And IT IS a problem, when no held-messages-reminders are available for a lot of weeks now! and heldmessage-management isn`t working correctly! We have to handle about 2000 - 4000 held messages in out lists! Please: Could you solve this problem in the really near future and give them a higher precedence? You know, I`ll help you and I`ll send you all the files you`ll possible need to debug an dtrace this error! ---------------------------------------------------------------------- Comment By: Peer Heinlein (pheinlein) Date: 2003-01-16 10:54 Message: Logged In: YES user_id=581680 Using the actual CVS-checkout I still have problems with that. Because of that a lot of list`s doesn`t work properly and mails are shunted. Is it pssoible to clear that problem with a fast fix? Peer ---------------------------------------------------------------------- Comment By: Jorge Becerra (jlbpcuba) Date: 2003-01-07 17:03 Message: Logged In: YES user_id=680844 I think that the bug is on python itself, because is suppossed that encode(enc, 'replace') show no errors at all according to http://www.reportlab.com/i18n/python_unicode_tutorial.html But is the middle i remove from the code and works ok. .encode(enc, 'replace') ---------------------------------------------------------------------- Comment By: Jorge Becerra (jlbpcuba) Date: 2003-01-07 17:03 Message: Logged In: YES user_id=680844 I think that the bug is on python itself, because is suppossed that encode(enc, 'replace') show no errors at all according to http://www.reportlab.com/i18n/python_unicode_tutorial.html But is the middle i remove from the code that and works ok. .encode(enc, 'replace') ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=660675&group_id=103 From noreply at sourceforge.net Thu Apr 3 06:26:37 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Apr 3 09:12:14 2003 Subject: [ mailman-Bugs-714630 ] Moderation-Bit of new lists will not be set Message-ID: Bugs item #714630, was opened at 2003-04-03 14:26 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=714630&group_id=103 Category: Web/CGI Group: None Status: Open Resolution: None Priority: 5 Submitted By: Heiko TObias (htobias) Assigned to: Nobody/Anonymous (nobody) Summary: Moderation-Bit of new lists will not be set Initial Comment: All lists created with Mailman 2.1.1: I can not set the moderation-bit (bottom of member-list) permanent. It only sets the moderation for the current members, and then it turns itself off. On old lists - the moderation-bit will be permanent on or off, so also new members are moderated or not. Thanks! Heiko ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=714630&group_id=103 From noreply at sourceforge.net Thu Apr 3 11:47:12 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Apr 3 14:32:45 2003 Subject: [ mailman-Bugs-714630 ] Moderation-Bit of new lists will not be set Message-ID: Bugs item #714630, was opened at 2003-04-03 09:26 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=714630&group_id=103 Category: Web/CGI >Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Heiko TObias (htobias) Assigned to: Nobody/Anonymous (nobody) Summary: Moderation-Bit of new lists will not be set Initial Comment: All lists created with Mailman 2.1.1: I can not set the moderation-bit (bottom of member-list) permanent. It only sets the moderation for the current members, and then it turns itself off. On old lists - the moderation-bit will be permanent on or off, so also new members are moderated or not. Thanks! Heiko ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=714630&group_id=103 From noreply at sourceforge.net Thu Apr 3 12:58:11 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Apr 3 15:43:40 2003 Subject: [ mailman-Patches-713522 ] Spambayes integration Message-ID: Patches item #713522, was opened at 2003-04-01 22:47 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=713522&group_id=103 Category: list administration Group: Mailman 2.2 / 3.0 Status: Open Resolution: None Priority: 5 Submitted By: Barry A. Warsaw (bwarsaw) Assigned to: Nobody/Anonymous (nobody) Summary: Spambayes integration Initial Comment: Here's a patch I developed in Jan 2003 to integrate Spambayes http://spambayes.sf.net into Mailman. It's very experimental but provide here for fun. If people like it I could see it becoming part of Mailman 2.2 or 3.0 You need to separately download the spambayes distutils tarball and drop it in Mailman's misc directory. Check that the version value in misc/Makefile.in matches. ---------------------------------------------------------------------- >Comment By: Simone Piunno (pioppo) Date: 2003-04-03 22:58 Message: Logged In: YES user_id=227443 I'm testing this patch on a real environment and there are problems, namely: 1. wrong umask when creating spam.pck 2. insuffiently defensive call to .store() 3. creates and loads spam.pck even for lists where use_spambayes==0 4. lots of these: Apr 03 22:20:33 2003 (730) Uncaught runner exception: Apr 03 22:20:33 2003 (730) Traceback (most recent call last): File "/home/mailman21/Mailman/Queue/Runner.py", line 105, in _oneloop self._onefile(msg, msgdata) File "/home/mailman21/Mailman/Queue/Runner.py", line 155, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/home/mailman21/Mailman/Queue/OutgoingRunner.py", line 69, in _dispose mlist.Load() File "/home/mailman21/Mailman/MailList.py", line 626, in Load self._spamdb = hammie.open(path, 0) File "/home/mailman21/pythonlib/spambayes/hammie.py", line 262, in open b = storage.PickledClassifier(filename) File "/home/mailman21/pythonlib/spambayes/storage.py", line 80, in __init__ self.load() File "/home/mailman21/pythonlib/spambayes/storage.py", line 98, in load tempbayes = pickle.load(fp) EOFError The attached patch is an evolution of Barry's one trying to address issues 1-3. 4 is still unsolved, I'm investigating. Additionally, I'd want to add an header to messages publishing the spambayes score, so I've added some line to SpamDetect.py but still without success (the header does not get appended). ---------------------------------------------------------------------- Comment By: Simone Piunno (pioppo) Date: 2003-04-01 23:49 Message: Logged In: YES user_id=227443 LOL! ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-04-01 23:19 Message: Logged In: YES user_id=12800 Oh please gawds of SF, accept my burnt offering of a patch as my supplication to your greatness. I have Checkethed the Holy CheckBox and Fillethed in the Holy TextBox. Now I go to Submitteth this Update. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=713522&group_id=103 From noreply at sourceforge.net Thu Apr 3 12:59:48 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Apr 3 15:44:11 2003 Subject: [ mailman-Patches-713522 ] Spambayes integration Message-ID: Patches item #713522, was opened at 2003-04-01 22:47 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=713522&group_id=103 Category: list administration Group: Mailman 2.2 / 3.0 Status: Open Resolution: None Priority: 5 Submitted By: Barry A. Warsaw (bwarsaw) Assigned to: Nobody/Anonymous (nobody) Summary: Spambayes integration Initial Comment: Here's a patch I developed in Jan 2003 to integrate Spambayes http://spambayes.sf.net into Mailman. It's very experimental but provide here for fun. If people like it I could see it becoming part of Mailman 2.2 or 3.0 You need to separately download the spambayes distutils tarball and drop it in Mailman's misc directory. Check that the version value in misc/Makefile.in matches. ---------------------------------------------------------------------- >Comment By: Simone Piunno (pioppo) Date: 2003-04-03 22:59 Message: Logged In: YES user_id=227443 I'm testing this patch on a real environment and there are problems, namely: 1. wrong umask when creating spam.pck 2. insuffiently defensive call to .store() 3. creates and loads spam.pck even for lists where use_spambayes==0 4. lots of these: Apr 03 22:20:33 2003 (730) Uncaught runner exception: Apr 03 22:20:33 2003 (730) Traceback (most recent call last): File "/home/mailman21/Mailman/Queue/Runner.py", line 105, in _oneloop self._onefile(msg, msgdata) File "/home/mailman21/Mailman/Queue/Runner.py", line 155, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/home/mailman21/Mailman/Queue/OutgoingRunner.py", line 69, in _dispose mlist.Load() File "/home/mailman21/Mailman/MailList.py", line 626, in Load self._spamdb = hammie.open(path, 0) File "/home/mailman21/pythonlib/spambayes/hammie.py", line 262, in open b = storage.PickledClassifier(filename) File "/home/mailman21/pythonlib/spambayes/storage.py", line 80, in __init__ self.load() File "/home/mailman21/pythonlib/spambayes/storage.py", line 98, in load tempbayes = pickle.load(fp) EOFError The attached patch is an evolution of Barry's one trying to address issues 1-3. 4 is still unsolved, I'm investigating. Additionally, I'd want to add an header to messages publishing the spambayes score, so I've added some line to SpamDetect.py but still without success (the header does not get appended). ---------------------------------------------------------------------- Comment By: Simone Piunno (pioppo) Date: 2003-04-03 22:58 Message: Logged In: YES user_id=227443 I'm testing this patch on a real environment and there are problems, namely: 1. wrong umask when creating spam.pck 2. insuffiently defensive call to .store() 3. creates and loads spam.pck even for lists where use_spambayes==0 4. lots of these: Apr 03 22:20:33 2003 (730) Uncaught runner exception: Apr 03 22:20:33 2003 (730) Traceback (most recent call last): File "/home/mailman21/Mailman/Queue/Runner.py", line 105, in _oneloop self._onefile(msg, msgdata) File "/home/mailman21/Mailman/Queue/Runner.py", line 155, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/home/mailman21/Mailman/Queue/OutgoingRunner.py", line 69, in _dispose mlist.Load() File "/home/mailman21/Mailman/MailList.py", line 626, in Load self._spamdb = hammie.open(path, 0) File "/home/mailman21/pythonlib/spambayes/hammie.py", line 262, in open b = storage.PickledClassifier(filename) File "/home/mailman21/pythonlib/spambayes/storage.py", line 80, in __init__ self.load() File "/home/mailman21/pythonlib/spambayes/storage.py", line 98, in load tempbayes = pickle.load(fp) EOFError The attached patch is an evolution of Barry's one trying to address issues 1-3. 4 is still unsolved, I'm investigating. Additionally, I'd want to add an header to messages publishing the spambayes score, so I've added some line to SpamDetect.py but still without success (the header does not get appended). ---------------------------------------------------------------------- Comment By: Simone Piunno (pioppo) Date: 2003-04-01 23:49 Message: Logged In: YES user_id=227443 LOL! ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-04-01 23:19 Message: Logged In: YES user_id=12800 Oh please gawds of SF, accept my burnt offering of a patch as my supplication to your greatness. I have Checkethed the Holy CheckBox and Fillethed in the Holy TextBox. Now I go to Submitteth this Update. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=713522&group_id=103 From noreply at sourceforge.net Thu Apr 3 14:30:19 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Apr 3 17:15:15 2003 Subject: [ mailman-Bugs-714929 ] Incorrect relative path in user options unsubscribe button Message-ID: Bugs item #714929, was opened at 2003-04-03 22:30 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=714929&group_id=103 Category: Web/CGI Group: 2.0.x Status: Open Resolution: None Priority: 5 Submitted By: Matt Noble (mathia-sf) Assigned to: Nobody/Anonymous (nobody) Summary: Incorrect relative path in user options unsubscribe button Initial Comment: I'm am using mailman 2.0.13. The monthly subscription reminder gives the URL http://my.server.com/mailman/options/listname/user@mail.com for changes in the users account. If the user follows this link and clicks the unsubscribe button they get directed to http://my.server.com/mailman/options/handle_opts/listname/user@mail.com and get the error "no such list handle_opts". If the user goes to http://my.server.com/mailman/listinfo/listname and clicks on edit options and then does the unsubscribe they get directed to http://my.server.com/mailman/handle_opts/listname/user@mail.com and it works. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=714929&group_id=103 From noreply at sourceforge.net Fri Apr 4 13:50:17 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Apr 4 16:34:29 2003 Subject: [ mailman-Bugs-715581 ] plain text digest bug in appending messages Message-ID: Bugs item #715581, was opened at 2003-04-04 21:50 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=715581&group_id=103 Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Ricardo Kustner (rixhq) Assigned to: Nobody/Anonymous (nobody) Summary: plain text digest bug in appending messages Initial Comment: Sometimes, messages are incorrectly appended in the plain digests, which cause 2 or more messages to be attached to 1. For example, I got a digest which mentions one message in the Topic list, but at the end of this message, the next message is "glued" to the bottom of it: (...top of first message...) --------------------------------- Do you Yahoo!? Yahoo! Platinum - Watch CBS' NCAA March Madness, live on your desktop!From EMAILADDR@aol.com Fri Mar 28 14:04:32 2003 Return-Path: Delivered-To: fans@list.miss-janet.com (...second message continues with all it's headers and content) As you can see, the "From..." of the second message starts directly after the last character of the first message. Here's a second example: (... top of first message...) peace out: -oscarFrom EMAILADDR@aol.com Tue Apr 1 15:04:42 2003 Return-Path: Delivered-To: fans@list.miss-janet.com (..second message continues...) Again, the "From..." from the next message is glued to the previous message. Is this a simple missing end of line issue or is it more complicated? I can't seem to see a good pattern in it... Ricardo. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=715581&group_id=103 From noreply at sourceforge.net Sun Apr 6 16:41:25 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sun Apr 6 18:25:17 2003 Subject: [ mailman-Patches-713522 ] Spambayes integration Message-ID: Patches item #713522, was opened at 2003-04-01 22:47 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=713522&group_id=103 Category: list administration Group: Mailman 2.2 / 3.0 Status: Open Resolution: None Priority: 5 Submitted By: Barry A. Warsaw (bwarsaw) Assigned to: Nobody/Anonymous (nobody) Summary: Spambayes integration Initial Comment: Here's a patch I developed in Jan 2003 to integrate Spambayes http://spambayes.sf.net into Mailman. It's very experimental but provide here for fun. If people like it I could see it becoming part of Mailman 2.2 or 3.0 You need to separately download the spambayes distutils tarball and drop it in Mailman's misc directory. Check that the version value in misc/Makefile.in matches. ---------------------------------------------------------------------- >Comment By: Simone Piunno (pioppo) Date: 2003-04-07 00:41 Message: Logged In: YES user_id=227443 I'm attaching a safe patch solving all the problems on Barry's one. It must be used together with #715248 (for spambayes 1.0a2) see http://sourceforge.net/tracker/index.php?func=detail&aid=715248&group_id=61702&atid=498103 There are still missing functionalities, e.g. training on false negatives for non-moderated lists. Now I'm working on functionality enhancements. ---------------------------------------------------------------------- Comment By: Simone Piunno (pioppo) Date: 2003-04-03 22:59 Message: Logged In: YES user_id=227443 I'm testing this patch on a real environment and there are problems, namely: 1. wrong umask when creating spam.pck 2. insuffiently defensive call to .store() 3. creates and loads spam.pck even for lists where use_spambayes==0 4. lots of these: Apr 03 22:20:33 2003 (730) Uncaught runner exception: Apr 03 22:20:33 2003 (730) Traceback (most recent call last): File "/home/mailman21/Mailman/Queue/Runner.py", line 105, in _oneloop self._onefile(msg, msgdata) File "/home/mailman21/Mailman/Queue/Runner.py", line 155, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/home/mailman21/Mailman/Queue/OutgoingRunner.py", line 69, in _dispose mlist.Load() File "/home/mailman21/Mailman/MailList.py", line 626, in Load self._spamdb = hammie.open(path, 0) File "/home/mailman21/pythonlib/spambayes/hammie.py", line 262, in open b = storage.PickledClassifier(filename) File "/home/mailman21/pythonlib/spambayes/storage.py", line 80, in __init__ self.load() File "/home/mailman21/pythonlib/spambayes/storage.py", line 98, in load tempbayes = pickle.load(fp) EOFError The attached patch is an evolution of Barry's one trying to address issues 1-3. 4 is still unsolved, I'm investigating. Additionally, I'd want to add an header to messages publishing the spambayes score, so I've added some line to SpamDetect.py but still without success (the header does not get appended). ---------------------------------------------------------------------- Comment By: Simone Piunno (pioppo) Date: 2003-04-03 22:58 Message: Logged In: YES user_id=227443 I'm testing this patch on a real environment and there are problems, namely: 1. wrong umask when creating spam.pck 2. insuffiently defensive call to .store() 3. creates and loads spam.pck even for lists where use_spambayes==0 4. lots of these: Apr 03 22:20:33 2003 (730) Uncaught runner exception: Apr 03 22:20:33 2003 (730) Traceback (most recent call last): File "/home/mailman21/Mailman/Queue/Runner.py", line 105, in _oneloop self._onefile(msg, msgdata) File "/home/mailman21/Mailman/Queue/Runner.py", line 155, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/home/mailman21/Mailman/Queue/OutgoingRunner.py", line 69, in _dispose mlist.Load() File "/home/mailman21/Mailman/MailList.py", line 626, in Load self._spamdb = hammie.open(path, 0) File "/home/mailman21/pythonlib/spambayes/hammie.py", line 262, in open b = storage.PickledClassifier(filename) File "/home/mailman21/pythonlib/spambayes/storage.py", line 80, in __init__ self.load() File "/home/mailman21/pythonlib/spambayes/storage.py", line 98, in load tempbayes = pickle.load(fp) EOFError The attached patch is an evolution of Barry's one trying to address issues 1-3. 4 is still unsolved, I'm investigating. Additionally, I'd want to add an header to messages publishing the spambayes score, so I've added some line to SpamDetect.py but still without success (the header does not get appended). ---------------------------------------------------------------------- Comment By: Simone Piunno (pioppo) Date: 2003-04-01 23:49 Message: Logged In: YES user_id=227443 LOL! ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-04-01 23:19 Message: Logged In: YES user_id=12800 Oh please gawds of SF, accept my burnt offering of a patch as my supplication to your greatness. I have Checkethed the Holy CheckBox and Fillethed in the Holy TextBox. Now I go to Submitteth this Update. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=713522&group_id=103 From noreply at sourceforge.net Sun Apr 6 17:23:47 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sun Apr 6 19:08:49 2003 Subject: [ mailman-Bugs-671303 ] bin/arch --start and --end argument handling Message-ID: Bugs item #671303, was opened at 2003-01-20 13:52 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=671303&group_id=103 Category: Pipermail Group: 2.1 (stable) >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Bryan Fullerton (fehwalker) Assigned to: Nobody/Anonymous (nobody) Summary: bin/arch --start and --end argument handling Initial Comment: bin/arch says (among other things): -s N --start=N Start indexing at article N, where article 0 is the first in the mbox. Defaults to 0. -e M --end=M End indexing at article M. This script is not very efficient with respect to memory management, and for large archives, it may not be possible to index the mbox entirely. For that reason, you can specify the start and end article numbers. However, using --end=[some #] or --start=[some #] results in these errors: % bin/arch --wipe --end=25000 test [...] option --end must not have an argument % bin/arch --wipe --start=25001 test [...] option --start must not have an argument Using --end [some #] or --start [some #] (ie with no =) works fine. So either the help output of bin/arch needs to be amended to remove the ='s, or the argument handling needs to be tweaked to understand ='s. I'm unsure which is preferable. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=671303&group_id=103 From noreply at sourceforge.net Sun Apr 6 17:31:33 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sun Apr 6 19:15:28 2003 Subject: [ mailman-Bugs-672649 ] canonstr -> unicode usernames Message-ID: Bugs item #672649, was opened at 2003-01-22 14:26 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=672649&group_id=103 Category: (un)subscribing Group: 2.1 (stable) >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Donn Cave (donnc) Assigned to: Nobody/Anonymous (nobody) Summary: canonstr -> unicode usernames Initial Comment: Cgi.subscribe.process_form gets a unicode value for fullname, from Utils.canonstr() (return unicode(newstr, charset, 'replace') This came to my attention because it broke OwnerNotification when the email Message couldn't "flatten" itself with the unicode payload. Suspect that's only the beginning of the trouble that will be caused, so I'm hoping we really don't want unicode usernames values as a rule. I fixed it in subscribe.py with fullname = fullname.encode('iso8859-1'), but note that canonstr is used elsewhere like this. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-04-06 19:31 Message: Logged In: YES user_id=12800 I think this bug has been fixed in 2.1.1 or 2.1.2 (cvs). ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-02-15 06:37 Message: Logged In: YES user_id=67709 If your users choose to input latin-1 charcters in fullname, it will be better to set iso-8859-1as english charset. in mm_cfg.py, def _(s): return s LC_DESCRIPTIONS['en'] = (_('English (USA)'), 'iso-8859-1') del _ ---------------------------------------------------------------------- Comment By: Pat Carr (pcarr) Date: 2003-02-12 23:05 Message: Logged In: YES user_id=710070 I stumbled over the same bug, but in my case it was bailing only in the confirm.py script. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=672649&group_id=103 From noreply at sourceforge.net Sun Apr 6 17:32:11 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sun Apr 6 19:17:26 2003 Subject: [ mailman-Bugs-683833 ] Traceback on checkdbs Message-ID: Bugs item #683833, was opened at 2003-02-10 04:48 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=683833&group_id=103 Category: command line scripts Group: 2.1 (stable) >Status: Closed >Resolution: Fixed Priority: 6 Submitted By: Stefan Divjak (stdivjak) Assigned to: Nobody/Anonymous (nobody) Summary: Traceback on checkdbs Initial Comment: The checkdbs script of mailman 2.1.1 quits with a traceback: [mailman@styx cron]$ ./checkdbs Traceback (most recent call last): File "./checkdbs", line 136, in ? main() File "./checkdbs", line 80, in main text += '\n' + pending_requests(mlist) File "./checkdbs", line 123, in pending_requests text = NL.join(pending) UnicodeError: ASCII decoding error: ordinal not in range(128) I tried reverting to mailman 2.1, and everything works fine now. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-04-06 19:32 Message: Logged In: YES user_id=12800 I believe this has been fixed in a slightly different way for 2.1.1 or 2.1.2 (cvs). ---------------------------------------------------------------------- Comment By: Stefan Divjak (stdivjak) Date: 2003-02-18 06:53 Message: Logged In: YES user_id=483131 Patching worked without any errors, and so does the checkdbs script now. Well done! :-) ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-02-18 06:12 Message: Logged In: YES user_id=67709 OK, somehow ^L has disappeared during genrating diff from cvs. I am uploading new patch using non-cvs diff. (You might be able to report error in patch command execution) ---------------------------------------------------------------------- Comment By: Stefan Divjak (stdivjak) Date: 2003-02-18 03:11 Message: Logged In: YES user_id=483131 Unfortunately, there's no difference :-( ... [mailman@styx mailman]$ python - S /home/mailman/cron/checkdbs Traceback (most recent call last): File "/home/mailman/cron/checkdbs", line 138, in ? main() File "/home/mailman/cron/checkdbs", line 80, in main text += '\n' + pending_requests(mlist) File "/home/mailman/cron/checkdbs", line 105, in pending_requests fullname = fullname.encode(lcset, 'replace') NameError: global name 'lcset' is not defined ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-02-17 06:45 Message: Logged In: YES user_id=67709 stdivjak> [mailman@styx cron]# ./checkdbs you should type python -S /path/to/checkdbs ---------------------------------------------------------------------- Comment By: Stefan Divjak (stdivjak) Date: 2003-02-17 00:48 Message: Logged In: YES user_id=483131 [mailman@styx cron]# ./checkdbs Traceback (most recent call last): File "./checkdbs", line 138, in ? main() File "./checkdbs", line 80, in main text += '\n' + pending_requests(mlist) File "./checkdbs", line 105, in pending_requests fullname = fullname.encode(lcset, 'replace') NameError: global name 'lcset' is not defined ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-02-15 06:21 Message: Logged In: YES user_id=67709 increment priority because someone else asked this bug. until merged into CVS. ;-) ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-02-13 05:25 Message: Logged In: YES user_id=67709 Here is a patch. Please try and feedback. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=683833&group_id=103 From noreply at sourceforge.net Sun Apr 6 17:44:15 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sun Apr 6 19:28:07 2003 Subject: [ mailman-Bugs-685040 ] mailmanctl reopen does not reopen all log files Message-ID: Bugs item #685040, was opened at 2003-02-11 20:10 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=685040&group_id=103 Category: command line scripts Group: 2.1 (stable) >Status: Closed >Resolution: Works For Me Priority: 5 Submitted By: Martin Pool (mbp) Assigned to: Nobody/Anonymous (nobody) Summary: mailmanctl reopen does not reopen all log files Initial Comment: In Mailman 2.1: The help for mailmanctl reopen says that it causes all log files to be closed, and reopened the next time they are used. However, it does not seem to cover the qrunner and error logs. After running this command, lsof shows: [root@dp logs]# lsof -p 9207 .... mailmanct 9207 root 0u CHR 136,7 9 /dev/pts/7 mailmanct 9207 root 1u CHR 136,7 9 /dev/pts/7 mailmanct 9207 root 2u CHR 136,7 9 /dev/pts/7 mailmanct 9207 root 3u REG 8,1 116944 2130090 /var/mailman/logs/error.1 mailmanct 9207 root 4u REG 8,1 649 2130251 /var/mailman/logs/qrunner After running it again: [root@dp logs]# lsof -p 9214 .... python 9214 mailman 0u CHR 136,7 9 /dev/pts/7 python 9214 mailman 1u CHR 136,7 9 /dev/pts/7 python 9214 mailman 2u CHR 136,7 9 /dev/pts/7 python 9214 mailman 3u REG 8,1 116944 2130090 /var/mailman/logs/error.1 python 9214 mailman 4u REG 8,1 116944 2130090 /var/mailman/logs/error.1 python 9214 mailman 5u REG 8,1 649 2130251 /var/mailman/logs/qrunner The same is true for the qrunner child processes. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-04-06 19:44 Message: Logged In: YES user_id=12800 This works for me. The fd output from lsof might be misleading. I'll bet the fds are getting reused. Checking the actual files shows that it works properly. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=685040&group_id=103 From noreply at sourceforge.net Sun Apr 6 19:17:58 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sun Apr 6 21:03:01 2003 Subject: [ mailman-Bugs-715581 ] plain text digest bug in appending messages Message-ID: Bugs item #715581, was opened at 2003-04-04 16:50 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=715581&group_id=103 Category: mail delivery Group: 2.1 (stable) >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Ricardo Kustner (rixhq) Assigned to: Nobody/Anonymous (nobody) Summary: plain text digest bug in appending messages Initial Comment: Sometimes, messages are incorrectly appended in the plain digests, which cause 2 or more messages to be attached to 1. For example, I got a digest which mentions one message in the Topic list, but at the end of this message, the next message is "glued" to the bottom of it: (...top of first message...) --------------------------------- Do you Yahoo!? Yahoo! Platinum - Watch CBS' NCAA March Madness, live on your desktop!From EMAILADDR@aol.com Fri Mar 28 14:04:32 2003 Return-Path: Delivered-To: fans@list.miss-janet.com (...second message continues with all it's headers and content) As you can see, the "From..." of the second message starts directly after the last character of the first message. Here's a second example: (... top of first message...) peace out: -oscarFrom EMAILADDR@aol.com Tue Apr 1 15:04:42 2003 Return-Path: Delivered-To: fans@list.miss-janet.com (..second message continues...) Again, the "From..." from the next message is glued to the previous message. Is this a simple missing end of line issue or is it more complicated? I can't seem to see a good pattern in it... Ricardo. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=715581&group_id=103 From noreply at sourceforge.net Sun Apr 6 19:20:39 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sun Apr 6 21:05:10 2003 Subject: [ mailman-Bugs-704912 ] Invitation bug Message-ID: Bugs item #704912, was opened at 2003-03-17 05:51 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=704912&group_id=103 Category: (un)subscribing Group: 2.1 (stable) >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Daniel Buchmann (avalon) Assigned to: Nobody/Anonymous (nobody) Summary: Invitation bug Initial Comment: There seems to be a bug in parsing the confirmation of an invitation to join a mailing list. I suspect this has something to do with MIME decoding of the Subject: header. When sending a reply to the autogenerated invitation (in my case, using pine), with this header: Subject: Re: =?iso-8859-1?q?confirm_55ed0163ec2f0a56ac257f708b 470b6a892935f2?= nothing happened. But when sending a reply with this header (which was the case if I used Netscape Mail or Evolution): Subject: Re: confirm 9924a8cb2e31d2f1605ca6228ff210901ff17aba I was subscribed. Maybe Mailman doesn't decode the Subject: before parsing it? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=704912&group_id=103 From noreply at sourceforge.net Mon Apr 7 06:21:14 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Apr 7 08:05:35 2003 Subject: [ mailman-Bugs-716702 ] checkdbs i18n Message-ID: Bugs item #716702, was opened at 2003-04-07 14: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=716702&group_id=103 Category: command line scripts Group: None Status: Open Resolution: None Priority: 5 Submitted By: Bartosz Sawicki (sawickib) Assigned to: Nobody/Anonymous (nobody) Summary: checkdbs i18n Initial Comment: I've found phrase that could not be translated: Action: dailly checkdbs run Message: reason for pending posts eg. "Post by non-member to a members-only list" In code: bin/checkdbs, line 114, there is: when, sender, subject, reason, text, msgdata = mlist.GetRecord(id) date = time.ctime(when) pending.append(_("""\ From: %(sender)s on %(date)s Subject: %(subject)s Cause: %(reason)s""")) As you see none of "when, sender, subject, reason, text, msgdata" are beeing translated. I agree, that translation of sender or subject is unwated, but variables 'date' and 'reason' should be translated. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=716702&group_id=103 From noreply at sourceforge.net Mon Apr 7 06:44:09 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Apr 7 08:28:05 2003 Subject: [ mailman-Bugs-716702 ] checkdbs i18n Message-ID: Bugs item #716702, was opened at 2003-04-07 08:21 Message generated for change (Settings changed) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=716702&group_id=103 Category: command line scripts >Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Bartosz Sawicki (sawickib) Assigned to: Nobody/Anonymous (nobody) Summary: checkdbs i18n Initial Comment: I've found phrase that could not be translated: Action: dailly checkdbs run Message: reason for pending posts eg. "Post by non-member to a members-only list" In code: bin/checkdbs, line 114, there is: when, sender, subject, reason, text, msgdata = mlist.GetRecord(id) date = time.ctime(when) pending.append(_("""\ From: %(sender)s on %(date)s Subject: %(subject)s Cause: %(reason)s""")) As you see none of "when, sender, subject, reason, text, msgdata" are beeing translated. I agree, that translation of sender or subject is unwated, but variables 'date' and 'reason' should be translated. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=716702&group_id=103 From noreply at sourceforge.net Mon Apr 7 08:26:53 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Apr 7 10:11:22 2003 Subject: [ mailman-Bugs-716754 ] sys.exit handling by script/driver Message-ID: Bugs item #716754, was opened at 2003-04-07 14:26 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=716754&group_id=103 Category: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Richard Barrett (ppsys) Assigned to: Nobody/Anonymous (nobody) Summary: sys.exit handling by script/driver Initial Comment: The code in the $prefix/scripts/driver script concedes that it is valid for a script it is supervising to exit using the sys.exit function rather than just returning from the main function. However, if the script being supervised does use sys.exit, the driver script fails to pass on the output generated by the supervised script. In the case of cgi scripts this means that an internal server error is reported by the http server because no output has been returned. A patch file to fix this problem is available as #668685 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=716754&group_id=103 From noreply at sourceforge.net Mon Apr 7 08:32:53 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Apr 7 10:17:21 2003 Subject: [ mailman-Bugs-716755 ] invalid HTML in page templates Message-ID: Bugs item #716755, was opened at 2003-04-07 14: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=716755&group_id=103 Category: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Richard Barrett (ppsys) Assigned to: Nobody/Anonymous (nobody) Summary: invalid HTML in page templates Initial Comment: A number of page templates in the 2.1.1 release are defective, i.e. the HTML is invalid. A patch file to correct these problems is available through patch #661138, which does the following: Various languages (de, en, es, et, fi, hu, it, ja, lt, nl, pt_BR) ----------------- admindetails.html - removed extraneous P tags from inside UL Swedish templates ----------------- admindetails.html - removed spurious body tags adminpreamble.html - removed spurious body tags article.html - moved stuff from inside BODY tag back to inside HEAD tag headfoot.html - removed spurious body tags French templates ---------------- archidxfoot.html - removed spurious HTML and BODY open tags archidxhead.html - removed spurious HTML and BODY close tags and moved stuff from inside BODY tag back to inside HEAD tag Dutch templates --------------- article.html - added \n to end of file ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=716755&group_id=103 From noreply at sourceforge.net Mon Apr 7 16:37:33 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Apr 7 18:21:18 2003 Subject: [ mailman-Bugs-688751 ] Scrubber/attachment bug on NetBSD Message-ID: Bugs item #688751, was opened at 2003-02-18 11:55 Message generated for change (Comment added) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=688751&group_id=103 Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Eric Ding (ericding) Assigned to: Nobody/Anonymous (nobody) Summary: Scrubber/attachment bug on NetBSD Initial Comment: I'm using Mailman 2.1.1, and have encountered issues with mail delivery of messages with attachments (having to do, I think, with the recent change to use the scrubber on such messages for digests). I actually have ARCHIVE_SCRUBBER set to 0 on my system, since I use MHonArc for archiving. Still, the scrubber is called from ToDigest. As a result of this bug, ANY message with an attachment is currently getting shunted!! :( Here's an example stacktrace from the error log: Feb 18 11:20:55 2003 (7122) Uncaught runner exception: [Errno 1] Operation not permitted: '/home/mailman/archives/private/greengrass_coordinator/attachments/20030217/d2897c2f' Feb 18 11:20:55 2003 (7122) Traceback (most recent call last): File "/home/mailman/Mailman/Queue/Runner.py", line 105, in _oneloop self._onefile(msg, msgdata) File "/home/mailman/Mailman/Queue/Runner.py", line 155, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/home/mailman/Mailman/Queue/IncomingRunner.py", line 130, in _dispose more = self._dopipeline(mlist, msg, msgdata, pipeline) File "/home/mailman/Mailman/Queue/IncomingRunner.py", line 153, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File "/home/mailman/Mailman/Handlers/ToDigest.py", line 82, in process send_digests(mlist, mboxfp) File "/home/mailman/Mailman/Handlers/ToDigest.py", line 123, in send_digests send_i18n_digests(mlist, mboxfp) File "/home/mailman/Mailman/Handlers/ToDigest.py", line 295, in send_i18n_digests msg = scrubber(mlist, msg) File "/home/mailman/Mailman/Handlers/Scrubber.py", line 219, in process url = save_attachment(mlist, part, dir, filter_html=0) File "/home/mailman/Mailman/Handlers/Scrubber.py", line 341, in save_attachment makedirs(fsdir) File "/home/mailman/Mailman/Handlers/Scrubber.py", line 333, in makedirs os.path.walk(dir, twiddle, None) File "/usr/pkg/lib/python2.2/posixpath.py", line 279, in walk func(arg, top, names) File "/home/mailman/Mailman/Handlers/Scrubber.py", line 332, in twiddle os.chmod(dirname, 02775) OSError: [Errno 1] Operation not permitted: '/home/mailman/archives/private/greengrass_coordinator/attachments/20030217/d2897c2f' To work aorund this issue, I've currently commented out lines 331-333 on my system. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-04-07 18:37 Message: Logged In: YES user_id=12800 I need more information for this one. Do you still get the crash if you run check_perms first? I've never seen this on Linux and I don't have a NetBSD box available to see if there's some platform specific problem involved. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=688751&group_id=103 From noreply at sourceforge.net Mon Apr 7 16:38:10 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Apr 7 18:22:30 2003 Subject: [ mailman-Bugs-714630 ] Moderation-Bit of new lists will not be set Message-ID: Bugs item #714630, was opened at 2003-04-03 09:26 Message generated for change (Comment added) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=714630&group_id=103 Category: Web/CGI Group: 2.1 (stable) >Status: Closed >Resolution: Invalid Priority: 5 Submitted By: Heiko TObias (htobias) Assigned to: Nobody/Anonymous (nobody) Summary: Moderation-Bit of new lists will not be set Initial Comment: All lists created with Mailman 2.1.1: I can not set the moderation-bit (bottom of member-list) permanent. It only sets the moderation for the current members, and then it turns itself off. On old lists - the moderation-bit will be permanent on or off, so also new members are moderated or not. Thanks! Heiko ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-04-07 18:38 Message: Logged In: YES user_id=12800 This is working as expected. The default value of the flag on the member page is taken from the default_member_moderation option on the Privacy->Sender Filters page. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=714630&group_id=103 From noreply at sourceforge.net Mon Apr 7 17:09:33 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Apr 7 18:54:24 2003 Subject: [ mailman-Bugs-717096 ] Changing address "globally" if not on all lists fails Message-ID: Bugs item #717096, was opened at 2003-04-07 17:09 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=717096&group_id=103 Category: (un)subscribing Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Joe Peterson (skyrush) Assigned to: Nobody/Anonymous (nobody) Summary: Changing address "globally" if not on all lists fails Initial Comment: If you have a user who is on some, but not all, of the lists on your server, and he/she tries to change his/her address *globally* (using the "change globally" checkbox), the person will get the confirmation email, but when he/she clicks the link in the email and then the button on the page to make the change, it will only change the address on the list originally chosen, and then it will raise a "Bad Confirmation code" error. The problem is that the call, "self.__assertIsMember(member)" in OldStyleMemberships.py fails and raises the error. The isMember() call should have been checked in ApprovedChangeMemberAddress in MailList.py before trying to change the address in the other lists. This statement fixes it: if not mlist.isMember(oldaddr): continue Note that this sort of check *is* done in ChangeMemberName (which I used as an example for the fix): if not mlist.isMember(addr): continue -Joe ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=717096&group_id=103 From noreply at sourceforge.net Mon Apr 7 17:10:56 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Apr 7 18:55:47 2003 Subject: [ mailman-Bugs-717096 ] Changing address "globally" if not on all lists fails Message-ID: Bugs item #717096, was opened at 2003-04-07 17:09 Message generated for change (Settings changed) made by skyrush You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=717096&group_id=103 Category: (un)subscribing Group: 2.1 (stable) Status: Open >Resolution: Fixed Priority: 5 Submitted By: Joe Peterson (skyrush) Assigned to: Nobody/Anonymous (nobody) >Summary: Changing address "globally" if not on all lists fails Initial Comment: If you have a user who is on some, but not all, of the lists on your server, and he/she tries to change his/her address *globally* (using the "change globally" checkbox), the person will get the confirmation email, but when he/she clicks the link in the email and then the button on the page to make the change, it will only change the address on the list originally chosen, and then it will raise a "Bad Confirmation code" error. The problem is that the call, "self.__assertIsMember(member)" in OldStyleMemberships.py fails and raises the error. The isMember() call should have been checked in ApprovedChangeMemberAddress in MailList.py before trying to change the address in the other lists. This statement fixes it: if not mlist.isMember(oldaddr): continue Note that this sort of check *is* done in ChangeMemberName (which I used as an example for the fix): if not mlist.isMember(addr): continue -Joe ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=717096&group_id=103 From noreply at sourceforge.net Mon Apr 7 17:13:50 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Apr 7 18:58:41 2003 Subject: [ mailman-Patches-717100 ] Fix for globally changing address when not on all lists Message-ID: Patches item #717100, was opened at 2003-04-07 17:13 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=717100&group_id=103 Category: list administration Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Joe Peterson (skyrush) Assigned to: Nobody/Anonymous (nobody) Summary: Fix for globally changing address when not on all lists Initial Comment: If you have a user who is on some, but not all, of the lists on your server, and he/she tries to change his/her address *globally* (using the "change globally" checkbox), the person will get the confirmation email, but when he/she clicks the link in the email and then the button on the page to make the change, it will only change the address on the list originally chosen, and then it will raise a "Bad Confirmation code" error. The problem is that the call, "self.__assertIsMember(member)" in OldStyleMemberships.py fails and raises the error. The isMember() call should have been checked in ApprovedChangeMemberAddress in MailList.py before trying to change the address in the other lists. This statement fixes it: if not mlist.isMember(oldaddr): continue Note that this sort of check *is* done in ChangeMemberName (which I used as an example for the fix): if not mlist.isMember(addr): continue -Joe ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=717100&group_id=103 From noreply at sourceforge.net Mon Apr 7 17:23:17 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Apr 7 19:07:34 2003 Subject: [ mailman-Bugs-717110 ] mail commands Message-ID: Bugs item #717110, was opened at 2003-04-07 16:23 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=717110&group_id=103 Category: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Will Yardley (wyardley) Assigned to: Nobody/Anonymous (nobody) Summary: mail commands Initial Comment: when approving a message via email, if you type: Approved: passwrd in the headers of a response to the confirmation message, when the actual password is 'password', the message you're trying to approve is discarded; I think that no action (and an "incorrect password" error message in response) would be more appropriate. Also, as I've mentioned before, it would be very nice if the exact action being performed were listed, rather than the generic "confirmation succeeded" message. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=717110&group_id=103 From noreply at sourceforge.net Mon Apr 7 17:27:43 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Apr 7 19:11:59 2003 Subject: [ mailman-Feature Requests-717113 ] Unique token for message approval Message-ID: Feature Requests item #717113, was opened at 2003-04-07 16:27 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=717113&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Will Yardley (wyardley) Assigned to: Nobody/Anonymous (nobody) Summary: Unique token for message approval Initial Comment: I requested this on mailman-users; going ahead and submitting as a feature request as per your request on the list. ..... >From <20030205223918.GL25693@hq.newdream.net>: It seems like it would be nice to setup a method of confirmation for *approving* messages that uses a unique token instead of the list password; while (hopefully) in most cases, the moderator will be sending approval messages over SSL or from the same machine the list is on, it seems like a bad idea to make the confirmation token the list password (especially in case you accidentally add the 'Approved:' header to the wrong message, or in case someone spoofed a message appearing to be from Mailman in order to try and scam list passwords).... How about generating a unique one time password and having people add this to the Approved: header? This would make it much harder for someone to accidentally disclose the list (or worse, site) password. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=717113&group_id=103 From noreply at sourceforge.net Tue Apr 8 06:57:06 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Apr 8 08:41:33 2003 Subject: [ mailman-Patches-687704 ] use external style sheet config option Message-ID: Patches item #687704, was opened at 2003-02-17 02:05 Message generated for change (Comment added) made by karem_lore You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=687704&group_id=103 Category: Web UI Group: Mailman 2.1 Status: Open Resolution: None Priority: 3 Submitted By: Magnus Stenman (snugge) Assigned to: Nobody/Anonymous (nobody) Summary: use external style sheet config option Initial Comment: Adds an optional stylesheet config option to Defaults.py, and adds the place holders for it into the english templates and the cgis. The style sheet is in a separate file, making per site customization less messy when the templates get modified by Mailman developers. Sample style sheet using verdana/arial in 9pt is included. ---------------------------------------------------------------------- Comment By: Anthony Carter (karem_lore) Date: 2003-04-08 14:57 Message: Logged In: YES user_id=201573 Hi, The stylesheeting sort of works, however the translation of for the archiver (pipermail) doesn't translate to the Bugs item #688751, was opened at 2003-02-18 11:55 Message generated for change (Comment added) made by ericding You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=688751&group_id=103 Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Eric Ding (ericding) Assigned to: Nobody/Anonymous (nobody) Summary: Scrubber/attachment bug on NetBSD Initial Comment: I'm using Mailman 2.1.1, and have encountered issues with mail delivery of messages with attachments (having to do, I think, with the recent change to use the scrubber on such messages for digests). I actually have ARCHIVE_SCRUBBER set to 0 on my system, since I use MHonArc for archiving. Still, the scrubber is called from ToDigest. As a result of this bug, ANY message with an attachment is currently getting shunted!! :( Here's an example stacktrace from the error log: Feb 18 11:20:55 2003 (7122) Uncaught runner exception: [Errno 1] Operation not permitted: '/home/mailman/archives/private/greengrass_coordinator/attachments/20030217/d2897c2f' Feb 18 11:20:55 2003 (7122) Traceback (most recent call last): File "/home/mailman/Mailman/Queue/Runner.py", line 105, in _oneloop self._onefile(msg, msgdata) File "/home/mailman/Mailman/Queue/Runner.py", line 155, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/home/mailman/Mailman/Queue/IncomingRunner.py", line 130, in _dispose more = self._dopipeline(mlist, msg, msgdata, pipeline) File "/home/mailman/Mailman/Queue/IncomingRunner.py", line 153, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File "/home/mailman/Mailman/Handlers/ToDigest.py", line 82, in process send_digests(mlist, mboxfp) File "/home/mailman/Mailman/Handlers/ToDigest.py", line 123, in send_digests send_i18n_digests(mlist, mboxfp) File "/home/mailman/Mailman/Handlers/ToDigest.py", line 295, in send_i18n_digests msg = scrubber(mlist, msg) File "/home/mailman/Mailman/Handlers/Scrubber.py", line 219, in process url = save_attachment(mlist, part, dir, filter_html=0) File "/home/mailman/Mailman/Handlers/Scrubber.py", line 341, in save_attachment makedirs(fsdir) File "/home/mailman/Mailman/Handlers/Scrubber.py", line 333, in makedirs os.path.walk(dir, twiddle, None) File "/usr/pkg/lib/python2.2/posixpath.py", line 279, in walk func(arg, top, names) File "/home/mailman/Mailman/Handlers/Scrubber.py", line 332, in twiddle os.chmod(dirname, 02775) OSError: [Errno 1] Operation not permitted: '/home/mailman/archives/private/greengrass_coordinator/attachments/20030217/d2897c2f' To work aorund this issue, I've currently commented out lines 331-333 on my system. ---------------------------------------------------------------------- >Comment By: Eric Ding (ericding) Date: 2003-04-08 12:07 Message: Logged In: YES user_id=302756 The only problems that check_perms reveals are all the directories that do not have the setgid bit set. I installed with README.BSD in mind, assuming that the setgid bit is unnecessary. Running check_perms -f to turn on that bit has no effect on the behavior. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-04-07 18:37 Message: Logged In: YES user_id=12800 I need more information for this one. Do you still get the crash if you run check_perms first? I've never seen this on Linux and I don't have a NetBSD box available to see if there's some platform specific problem involved. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=688751&group_id=103 From noreply at sourceforge.net Tue Apr 8 13:20:48 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Apr 8 15:05:04 2003 Subject: [ mailman-Patches-717721 ] Re-form site HTML Message-ID: Patches item #717721, was opened at 2003-04-08 20:20 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=717721&group_id=103 Category: Unofficial 2.0 patch Group: Mailman 2.0.x Status: Open Resolution: None Priority: 5 Submitted By: Andrew Aylett (aaylett) Assigned to: Nobody/Anonymous (nobody) Summary: Re-form site HTML Initial Comment: This patch makes (most of) the HTML generated by Mailman XHTML complient, as well as adding CSS and an icon to every page. I'm afraid the icon file is a bit site specific (and not included). The CSS is also not included... You can get the whole lot from http://www.aylett.co.uk/resources/mailman/ and the surrounding site. The site doesn't run this patch any more though... I was meaning to get it tidied up properly, but then 2.1 came out. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=717721&group_id=103 From noreply at sourceforge.net Tue Apr 8 14:04:09 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Apr 8 15:48:29 2003 Subject: [ mailman-Patches-717745 ] CSS support Message-ID: Patches item #717745, was opened at 2003-04-08 21:04 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=717745&group_id=103 Category: Unofficial 2.0 patch Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Andrew Aylett (aaylett) Assigned to: Nobody/Anonymous (nobody) Summary: CSS support Initial Comment: This patch adds CSS support to Mailman 2.1. I have added a couple of template primatives—for adding a stylesheet to the document and for adding HTML to the top of the body of the document (used on my site to add the link in the top-left corner of the page). I have also edited the English pages to use headings instead of font tags in quite a few places and not to colour in table cells in most places, in keeping with my site's style, and changed all the generated HTML to not use capitalised tags (a precursor to making everything XHTML). To see what it looks like in action, visit http://www.aylett.co.uk/mailman/listinfo ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=717745&group_id=103 From noreply at sourceforge.net Tue Apr 8 14:05:18 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Apr 8 15:50:02 2003 Subject: [ mailman-Patches-717745 ] CSS support Message-ID: Patches item #717745, was opened at 2003-04-08 21:04 Message generated for change (Settings changed) made by aaylett You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=717745&group_id=103 Category: Unofficial 2.0 patch Group: Mailman 2.1 Status: Open Resolution: None >Priority: 1 Submitted By: Andrew Aylett (aaylett) Assigned to: Nobody/Anonymous (nobody) Summary: CSS support Initial Comment: This patch adds CSS support to Mailman 2.1. I have added a couple of template primatives—for adding a stylesheet to the document and for adding HTML to the top of the body of the document (used on my site to add the link in the top-left corner of the page). I have also edited the English pages to use headings instead of font tags in quite a few places and not to colour in table cells in most places, in keeping with my site's style, and changed all the generated HTML to not use capitalised tags (a precursor to making everything XHTML). To see what it looks like in action, visit http://www.aylett.co.uk/mailman/listinfo ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=717745&group_id=103 From noreply at sourceforge.net Tue Apr 8 14:06:11 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Apr 8 15:50:27 2003 Subject: [ mailman-Patches-717721 ] Re-form site HTML Message-ID: Patches item #717721, was opened at 2003-04-08 20:20 Message generated for change (Settings changed) made by aaylett You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=717721&group_id=103 Category: Unofficial 2.0 patch Group: Mailman 2.0.x Status: Open Resolution: None >Priority: 1 Submitted By: Andrew Aylett (aaylett) Assigned to: Nobody/Anonymous (nobody) Summary: Re-form site HTML Initial Comment: This patch makes (most of) the HTML generated by Mailman XHTML complient, as well as adding CSS and an icon to every page. I'm afraid the icon file is a bit site specific (and not included). The CSS is also not included... You can get the whole lot from http://www.aylett.co.uk/resources/mailman/ and the surrounding site. The site doesn't run this patch any more though... I was meaning to get it tidied up properly, but then 2.1 came out. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=717721&group_id=103 From noreply at sourceforge.net Tue Apr 8 19:17:50 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Apr 8 21:02:37 2003 Subject: [ mailman-Patches-694902 ] Fix MIME digest attachment Message-ID: Patches item #694902, was opened at 2003-02-28 03:02 Message generated for change (Comment added) made by dwighternest You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=694902&group_id=103 Category: mail delivery Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: Fix MIME digest attachment Initial Comment: ToDigest.py in Mailman 2.1.1 was improved in handling plain text digest but there was a side effect in MIME digest. We should now use copy of Message instance because the original is scrubbed afterwards. ---------------------------------------------------------------------- Comment By: Dwight Ernest (dwighternest) Date: 2003-04-08 21:17 Message: Logged In: YES user_id=740960 After I applied this patch, I started to receive uncaught exceptions leading to 100% of my postings being shunted. Apr 08 10:03:57 2003 (20895) Uncaught runner exception: 'module' object has no attribute 'process' Apr 08 10:03:57 2003 (20895) Traceback (most recent call last): File "/var/mailman/Mailman/Queue/Runner.py", line 105, in _oneloop self._onefile(msg, msgdata) File "/var/mailman/Mailman/Queue/Runner.py", line 155, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/var/mailman/Mailman/Queue/VirginRunner.py", line 38, in _dispose return IncomingRunner._dispose(self, mlist, msg, msgdata) File "/var/mailman/Mailman/Queue/IncomingRunner.py", line 130, in _dispose more = self._dopipeline(mlist, msg, msgdata, pipeline) File "/var/mailman/Mailman/Queue/IncomingRunner.py", line 153, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) AttributeError: 'module' object has no attribute 'process' Apr 08 10:03:57 2003 (20895) SHUNTING: 1049803236.489061+24037ff46bd58f849bf9a9646db1dd90bb863d2c ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=694902&group_id=103 From noreply at sourceforge.net Tue Apr 8 19:29:58 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Apr 8 21:14:06 2003 Subject: [ mailman-Patches-694902 ] Fix MIME digest attachment Message-ID: Patches item #694902, was opened at 2003-02-28 08:02 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=694902&group_id=103 Category: mail delivery Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: Fix MIME digest attachment Initial Comment: ToDigest.py in Mailman 2.1.1 was improved in handling plain text digest but there was a side effect in MIME digest. We should now use copy of Message instance because the original is scrubbed afterwards. ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-04-09 01:29 Message: Logged In: YES user_id=67709 This patch is only 3 lines. Please check if your Handlers/ToDigest.py was properly patched. I can't see anything related to this patch from your traceback log. ---------------------------------------------------------------------- Comment By: Dwight Ernest (dwighternest) Date: 2003-04-09 01:17 Message: Logged In: YES user_id=740960 After I applied this patch, I started to receive uncaught exceptions leading to 100% of my postings being shunted. Apr 08 10:03:57 2003 (20895) Uncaught runner exception: 'module' object has no attribute 'process' Apr 08 10:03:57 2003 (20895) Traceback (most recent call last): File "/var/mailman/Mailman/Queue/Runner.py", line 105, in _oneloop self._onefile(msg, msgdata) File "/var/mailman/Mailman/Queue/Runner.py", line 155, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/var/mailman/Mailman/Queue/VirginRunner.py", line 38, in _dispose return IncomingRunner._dispose(self, mlist, msg, msgdata) File "/var/mailman/Mailman/Queue/IncomingRunner.py", line 130, in _dispose more = self._dopipeline(mlist, msg, msgdata, pipeline) File "/var/mailman/Mailman/Queue/IncomingRunner.py", line 153, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) AttributeError: 'module' object has no attribute 'process' Apr 08 10:03:57 2003 (20895) SHUNTING: 1049803236.489061+24037ff46bd58f849bf9a9646db1dd90bb863d2c ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=694902&group_id=103 From noreply at sourceforge.net Wed Apr 9 02:33:42 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Apr 9 04:18:20 2003 Subject: [ mailman-Bugs-718080 ] lists.domain.com/mailman/create show Bug Error Message-ID: Bugs item #718080, was opened at 2003-04-09 10: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=718080&group_id=103 Category: None Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Marco A. Mateos (speckados) Assigned to: Nobody/Anonymous (nobody) Summary: lists.domain.com/mailman/create show Bug Error Initial Comment: Well, I've install mail man 2.1.1 on RedHat 7.3 with Plesk 5.0.5 panel. I've create aDNS A record for lists.estoyenred.net, and others. Go to http://lists.estoyenred.net/mailman/create a look this: ************** We're sorry, we hit a bug! If you would like to help us identify the problem, please email a copy of this page to the webmaster for this site with a description of what happened. Thanks! Traceback: Traceback (most recent call last): File "/var/mailman/scripts/driver", line 68, in run_main immediate=1) File "/var/mailman/Mailman/Logging/StampedLogger.py", line 52, in __init__ Logger.__init__(self, category, nofail, immediate) File "/var/mailman/Mailman/Logging/Logger.py", line 49, in __init__ self.__get_f() File "/var/mailman/Mailman/Logging/Logger.py", line 67, in __get_f 1) File "/var/tmp/python2-2.2.2-root/usr/lib/python2.2/codecs.py", line 496, in open file = __builtin__.open(filename, mode, buffering) IOError: [Errno 13] Permission denied: '/var/log/mailman/error' Python information: Variable Value sys.version 2.2.2 (#1, Apr 8 2003, 18:41:57) [GCC 2.96 20000731 (Red Hat Linux 7.3 2.96-113)] sys.executable /usr/bin/python2 sys.prefix /usr sys.exec_prefix /usr sys.path /usr sys.platform linux2 Environment variables: Variable Value HTTP_PRAGMA no-cache PYTHONPATH /var/mailman SERVER_SOFTWARE Apache/1.3.27 (Unix) (Red-Hat/Linux) FrontPage/5.0.2.2623 mod_ssl/2.8.12 OpenSSL/0.9.6b DAV/1.0.3 PHP/4.3.1 mod_perl/1.26 SCRIPT_FILENAME /var/mailman/cgi-bin//listinfo SERVER_ADMIN hosting@lomejordeinternet.net SCRIPT_NAME /mailman/listinfo SERVER_SIGNATURE Apache/1.3.27 Server at lists.estoyenred.net Port 80 REQUEST_METHOD GET HTTP_HOST lists.estoyenred.net SERVER_PROTOCOL HTTP/1.0 QUERY_STRING HTTP_CACHE_CONTROL max-age=259200 REQUEST_URI /mailman/listinfo HTTP_ACCEPT text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,video/x-mng,image/png,image/jpeg,image/gif;q=0.2,text/css,*/*;q=0.1 HTTP_ACCEPT_CHARSET ISO-8859-1, utf-8;q=0.66, *;q=0.66 HTTP_USER_AGENT Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20021003 HTTP_CONNECTION keep-alive SERVER_NAME lists.estoyenred.net REMOTE_ADDR 80.58.4.107 HTTP_CLIENT_IP 80.25.130.25 REMOTE_PORT 46324 HTTP_ACCEPT_LANGUAGE es-es, en-us;q=0.66, en;q=0.33 HTTP_X_FORWARDED_FOR 192.168.0.2 80.25.130.25 SERVER_PORT 80 GATEWAY_INTERFACE CGI/1.1 HTTP_VIA 1.1 specka.com:3128 (Squid/2.4.STABLE6), HTTP/1.0 proxy[AC1E0446] (Traffic-Server/5.5.1-58900 [uScM]) HTTP_ACCEPT_ENCODING gzip, deflate, compress;q=0.9 SERVER_ADDR 207.44.220.54 DOCUMENT_ROOT /home/httpd/vhosts/default/htdocs ============================ Im'lost .... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=718080&group_id=103 From noreply at sourceforge.net Wed Apr 9 02:47:24 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Apr 9 04:31:27 2003 Subject: [ mailman-Bugs-718083 ] lists.domain.com/mailman/create show Bug Error Message-ID: Bugs item #718083, was opened at 2003-04-09 10: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=718083&group_id=103 Category: None Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Marco A. Mateos (speckados) Assigned to: Nobody/Anonymous (nobody) Summary: lists.domain.com/mailman/create show Bug Error Initial Comment: Well, I've install mail man 2.1.1 on RedHat 7.3 with Plesk 5.0.5 panel. I've create aDNS A record for lists.estoyenred.net, and others. Go to http://lists.estoyenred.net/mailman/create a look this: ************** We're sorry, we hit a bug! If you would like to help us identify the problem, please email a copy of this page to the webmaster for this site with a description of what happened. Thanks! Traceback: Traceback (most recent call last): File "/var/mailman/scripts/driver", line 68, in run_main immediate=1) File "/var/mailman/Mailman/Logging/StampedLogger.py", line 52, in __init__ Logger.__init__(self, category, nofail, immediate) File "/var/mailman/Mailman/Logging/Logger.py", line 49, in __init__ self.__get_f() File "/var/mailman/Mailman/Logging/Logger.py", line 67, in __get_f 1) File "/var/tmp/python2-2.2.2-root/usr/lib/python2.2/codecs.py", line 496, in open file = __builtin__.open(filename, mode, buffering) IOError: [Errno 13] Permission denied: '/var/log/mailman/error' Python information: Variable Value sys.version 2.2.2 (#1, Apr 8 2003, 18:41:57) [GCC 2.96 20000731 (Red Hat Linux 7.3 2.96-113)] sys.executable /usr/bin/python2 sys.prefix /usr sys.exec_prefix /usr sys.path /usr sys.platform linux2 Environment variables: Variable Value HTTP_PRAGMA no-cache PYTHONPATH /var/mailman SERVER_SOFTWARE Apache/1.3.27 (Unix) (Red-Hat/Linux) FrontPage/5.0.2.2623 mod_ssl/2.8.12 OpenSSL/0.9.6b DAV/1.0.3 PHP/4.3.1 mod_perl/1.26 SCRIPT_FILENAME /var/mailman/cgi-bin//listinfo SERVER_ADMIN hosting@lomejordeinternet.net SCRIPT_NAME /mailman/listinfo SERVER_SIGNATURE Apache/1.3.27 Server at lists.estoyenred.net Port 80 REQUEST_METHOD GET HTTP_HOST lists.estoyenred.net SERVER_PROTOCOL HTTP/1.0 QUERY_STRING HTTP_CACHE_CONTROL max-age=259200 REQUEST_URI /mailman/listinfo HTTP_ACCEPT text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,video/x-mng,image/png,image/jpeg,image/gif;q=0.2,text/css,*/*;q=0.1 HTTP_ACCEPT_CHARSET ISO-8859-1, utf-8;q=0.66, *;q=0.66 HTTP_USER_AGENT Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20021003 HTTP_CONNECTION keep-alive SERVER_NAME lists.estoyenred.net REMOTE_ADDR 80.58.4.107 HTTP_CLIENT_IP 80.25.130.25 REMOTE_PORT 46324 HTTP_ACCEPT_LANGUAGE es-es, en-us;q=0.66, en;q=0.33 HTTP_X_FORWARDED_FOR 192.168.0.2 80.25.130.25 SERVER_PORT 80 GATEWAY_INTERFACE CGI/1.1 HTTP_VIA 1.1 specka.com:3128 (Squid/2.4.STABLE6), HTTP/1.0 proxy[AC1E0446] (Traffic-Server/5.5.1-58900 [uScM]) HTTP_ACCEPT_ENCODING gzip, deflate, compress;q=0.9 SERVER_ADDR 207.44.220.54 DOCUMENT_ROOT /home/httpd/vhosts/default/htdocs ============================ Im'lost .... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=718083&group_id=103 From noreply at sourceforge.net Wed Apr 9 06:15:53 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Apr 9 07:59:20 2003 Subject: [ mailman-Bugs-718199 ] Member administration: cannot show legend Message-ID: Bugs item #718199, was opened at 2003-04-09 14: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=718199&group_id=103 Category: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Daniel Buchmann (avalon) Assigned to: Nobody/Anonymous (nobody) Summary: Member administration: cannot show legend Initial Comment: It is impossible to turn on legend if viewing members beginning with a letter other than 'A', on the membership list page: http://www.mydomain.com/mailman/admin/mylist/members The problem is that neither the "letter" links nor the "legend" link include each other, so when clicking a letter, legend=yes is not included, and when clicking on the "show legend" link, the letter= is not included in the URL. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=718199&group_id=103 From noreply at sourceforge.net Wed Apr 9 11:11:37 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Apr 9 12:56:19 2003 Subject: [ mailman-Patches-687704 ] use external style sheet config option Message-ID: Patches item #687704, was opened at 2003-02-17 02:05 Message generated for change (Comment added) made by karem_lore You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=687704&group_id=103 Category: Web UI Group: Mailman 2.1 Status: Open Resolution: None Priority: 3 Submitted By: Magnus Stenman (snugge) Assigned to: Nobody/Anonymous (nobody) Summary: use external style sheet config option Initial Comment: Adds an optional stylesheet config option to Defaults.py, and adds the place holders for it into the english templates and the cgis. The style sheet is in a separate file, making per site customization less messy when the templates get modified by Mailman developers. Sample style sheet using verdana/arial in 9pt is included. ---------------------------------------------------------------------- Comment By: Anthony Carter (karem_lore) Date: 2003-04-09 19:11 Message: Logged In: YES user_id=201573 Snugge, I'd like to snuggle to tell you how much you just saved me bacon (or rather HOURS of trying to learn Python)... Thanks. ---------------------------------------------------------------------- Comment By: Anthony Carter (karem_lore) Date: 2003-04-08 14:57 Message: Logged In: YES user_id=201573 Hi, The stylesheeting sort of works, however the translation of for the archiver (pipermail) doesn't translate to the Patches item #717745, was opened at 2003-04-08 21:04 Message generated for change (Comment added) made by aaylett You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=717745&group_id=103 Category: Unofficial 2.0 patch Group: Mailman 2.1 Status: Open Resolution: None Priority: 1 Submitted By: Andrew Aylett (aaylett) Assigned to: Nobody/Anonymous (nobody) Summary: CSS support Initial Comment: This patch adds CSS support to Mailman 2.1. I have added a couple of template primatives—for adding a stylesheet to the document and for adding HTML to the top of the body of the document (used on my site to add the link in the top-left corner of the page). I have also edited the English pages to use headings instead of font tags in quite a few places and not to colour in table cells in most places, in keeping with my site's style, and changed all the generated HTML to not use capitalised tags (a precursor to making everything XHTML). To see what it looks like in action, visit http://www.aylett.co.uk/mailman/listinfo ---------------------------------------------------------------------- >Comment By: Andrew Aylett (aaylett) Date: 2003-04-09 18:26 Message: Logged In: YES user_id=167554 Looks pretty similar, I will have to admit... I could wish I'd found it before changing as much as I did :-) Thanks for the pointer... ---------------------------------------------------------------------- Comment By: Anthony Carter (karem_lore) Date: 2003-04-09 18:14 Message: Logged In: YES user_id=201573 Hey, check out patch: [ 687704 ] use external style sheet config option. Regards. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=717745&group_id=103 From noreply at sourceforge.net Wed Apr 9 11:14:20 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Apr 9 13:17:51 2003 Subject: [ mailman-Patches-717745 ] CSS support Message-ID: Patches item #717745, was opened at 2003-04-08 22:04 Message generated for change (Comment added) made by karem_lore You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=717745&group_id=103 Category: Unofficial 2.0 patch Group: Mailman 2.1 Status: Open Resolution: None Priority: 1 Submitted By: Andrew Aylett (aaylett) Assigned to: Nobody/Anonymous (nobody) Summary: CSS support Initial Comment: This patch adds CSS support to Mailman 2.1. I have added a couple of template primatives—for adding a stylesheet to the document and for adding HTML to the top of the body of the document (used on my site to add the link in the top-left corner of the page). I have also edited the English pages to use headings instead of font tags in quite a few places and not to colour in table cells in most places, in keeping with my site's style, and changed all the generated HTML to not use capitalised tags (a precursor to making everything XHTML). To see what it looks like in action, visit http://www.aylett.co.uk/mailman/listinfo ---------------------------------------------------------------------- Comment By: Anthony Carter (karem_lore) Date: 2003-04-09 19:14 Message: Logged In: YES user_id=201573 Hey, check out patch: [ 687704 ] use external style sheet config option. Regards. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=717745&group_id=103 From noreply at sourceforge.net Thu Apr 10 20:48:11 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Apr 10 22:32:40 2003 Subject: [ mailman-Patches-694902 ] Fix MIME digest attachment Message-ID: Patches item #694902, was opened at 2003-02-28 03:02 Message generated for change (Comment added) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=694902&group_id=103 Category: mail delivery Group: Mailman 2.1 >Status: Closed >Resolution: Accepted Priority: 5 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: Fix MIME digest attachment Initial Comment: ToDigest.py in Mailman 2.1.1 was improved in handling plain text digest but there was a side effect in MIME digest. We should now use copy of Message instance because the original is scrubbed afterwards. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-04-10 22:48 Message: Logged In: YES user_id=12800 The patch looks good, so I'm closing this in anticipation that testing will work out. I'm with tkikuchi though, I can't see how this patch could possibly evoke dwighternest's bug. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-04-08 21:29 Message: Logged In: YES user_id=67709 This patch is only 3 lines. Please check if your Handlers/ToDigest.py was properly patched. I can't see anything related to this patch from your traceback log. ---------------------------------------------------------------------- Comment By: Dwight Ernest (dwighternest) Date: 2003-04-08 21:17 Message: Logged In: YES user_id=740960 After I applied this patch, I started to receive uncaught exceptions leading to 100% of my postings being shunted. Apr 08 10:03:57 2003 (20895) Uncaught runner exception: 'module' object has no attribute 'process' Apr 08 10:03:57 2003 (20895) Traceback (most recent call last): File "/var/mailman/Mailman/Queue/Runner.py", line 105, in _oneloop self._onefile(msg, msgdata) File "/var/mailman/Mailman/Queue/Runner.py", line 155, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/var/mailman/Mailman/Queue/VirginRunner.py", line 38, in _dispose return IncomingRunner._dispose(self, mlist, msg, msgdata) File "/var/mailman/Mailman/Queue/IncomingRunner.py", line 130, in _dispose more = self._dopipeline(mlist, msg, msgdata, pipeline) File "/var/mailman/Mailman/Queue/IncomingRunner.py", line 153, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) AttributeError: 'module' object has no attribute 'process' Apr 08 10:03:57 2003 (20895) SHUNTING: 1049803236.489061+24037ff46bd58f849bf9a9646db1dd90bb863d2c ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=694902&group_id=103 From noreply at sourceforge.net Thu Apr 17 07:20:16 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Apr 17 09:20:19 2003 Subject: [ mailman-Bugs-723123 ] Runs out of memory on larger (5M) messages. Message-ID: Bugs item #723123, was opened at 2003-04-17 06:20 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=723123&group_id=103 Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Steve Mertz (xerouz) Assigned to: Nobody/Anonymous (nobody) Summary: Runs out of memory on larger (5M) messages. Initial Comment: When trying to send an email with a 5M attachment, Mailman seems to run out of memory. On the console I get: marcos:mailman {106} 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 59, in run filecnt = self._oneloop() File "/usr/local/mailman/Mailman/Queue/Runner.py", line 111, in _oneloop self._shunt.enqueue(msg, msgdata) File "/usr/local/mailman/Mailman/Queue/Switchboard.py", line 91, in enqueue msgsave = cPickle.dumps(_msg, 1) MemoryError: out of memory The system is: OpenBSD 3.1, with 512M ram. Mailman version 2.1.1 It would be nice to be able to have large attachments as I want to use this for my company's support email which quite often has larger than 10M files attached. Thanks, -- Steve ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=723123&group_id=103 From noreply at sourceforge.net Thu Apr 17 08:34:45 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Apr 17 10:34:56 2003 Subject: [ mailman-Bugs-723123 ] Runs out of memory on larger (5M) messages. Message-ID: Bugs item #723123, was opened at 2003-04-17 06:20 Message generated for change (Settings changed) made by xerouz You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=723123&group_id=103 Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None >Priority: 9 Submitted By: Steve Mertz (xerouz) Assigned to: Nobody/Anonymous (nobody) Summary: Runs out of memory on larger (5M) messages. Initial Comment: When trying to send an email with a 5M attachment, Mailman seems to run out of memory. On the console I get: marcos:mailman {106} 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 59, in run filecnt = self._oneloop() File "/usr/local/mailman/Mailman/Queue/Runner.py", line 111, in _oneloop self._shunt.enqueue(msg, msgdata) File "/usr/local/mailman/Mailman/Queue/Switchboard.py", line 91, in enqueue msgsave = cPickle.dumps(_msg, 1) MemoryError: out of memory The system is: OpenBSD 3.1, with 512M ram. Mailman version 2.1.1 It would be nice to be able to have large attachments as I want to use this for my company's support email which quite often has larger than 10M files attached. Thanks, -- Steve ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=723123&group_id=103 From noreply at sourceforge.net Fri Apr 18 12:24:51 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Apr 18 14:24:54 2003 Subject: [ mailman-Patches-723810 ] qmail MTA alias handler Message-ID: Patches item #723810, was opened at 2003-04-18 14:24 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=723810&group_id=103 Category: configure/install Group: Mailman 2.0.x Status: Open Resolution: None Priority: 5 Submitted By: John T. Shaw (jtshaw) Assigned to: Nobody/Anonymous (nobody) Summary: qmail MTA alias handler Initial Comment: This is a modification of Manual.py that automates the process of creating standard /var/qmail/alias/.qmail- alias files for new lists. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=723810&group_id=103 From noreply at sourceforge.net Fri Apr 18 16:03:51 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Apr 18 18:03:54 2003 Subject: [ mailman-Patches-723918 ] MTA Handler for Procmail Message-ID: Patches item #723918, was opened at 2003-04-18 15:03 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=723918&group_id=103 Category: list administration Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Alan K. Stebbens (akstebbens) Assigned to: Nobody/Anonymous (nobody) Summary: MTA Handler for Procmail Initial Comment: A new MTA handler for inclusion in the "Mailman/MTA" folder. It is used by defining (either in "mm_cfg.py" or in "Defaults.py") MTA as "Procmail". The output file name is defined by "MAILMAN_RC_FILE", which should also be placed in "Defaults.py", and possibly overriden in "mm_cfg.py". The module has creation and deletion hooks for procmail recipe files. This MTA handler will create procmail recipies and place them into the configured file. The procmail MTA handler allows Mailman to be run out of a virtual user account, or to have a single user manage many lists, when the mail delivery is accomplished with procmail as the local delivery agent. The virtual user has a ~/.procmailrc that contains these lines: MAILDIR=$HOME/Mail INCLUDERC=/www/mailman/Mailman/mail/mailman.rc The Mailman/mm_cfg.py contains these lines: MAILMAN_RC_FILE = "mailman.rc" This causes the "mailman.rc" file to be created in to the "mail" subdirectory of the "Mailman" installation directory. Attached is the "Procmail.py" script. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=723918&group_id=103 From noreply at sourceforge.net Fri Apr 18 16:43:26 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Apr 18 18:43:41 2003 Subject: [ mailman-Patches-657951 ] Generate RSS summary in archives Message-ID: Patches item #657951, was opened at 2002-12-23 14:17 Message generated for change (Comment added) made by bwarsaw 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: 7 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: Barry A. Warsaw (bwarsaw) Date: 2003-04-18 18: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 16: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-17 20: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 15: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 14: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 14:27 Message: Logged In: YES user_id=12800 Deferring until post-2.1 ---------------------------------------------------------------------- Comment By: A.M. Kuchling (akuchling) Date: 2002-12-23 14: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 Sat Apr 19 11:48:13 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sat Apr 19 13:48:20 2003 Subject: [ mailman-Patches-707624 ] SMTPDirect doesn't use persistent SMTP connections Message-ID: Patches item #707624, was opened at 2003-03-21 12:26 Message generated for change (Comment added) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=707624&group_id=103 Category: mail delivery Group: Mailman 2.1 >Status: Closed >Resolution: Rejected Priority: 5 Submitted By: Jesús Cea Avión (jcea) Assigned to: Nobody/Anonymous (nobody) Summary: SMTPDirect doesn't use persistent SMTP connections Initial Comment: Mailman 2.1.1 here. "/Mailman/Handlers/SMTPDirect.py" is suppose to reuse SMTP connections up to "mm_cfg.SMTP_MAX_SESSIONS_PER_CONNECTION" different messages. Nevertheless, it's NOT the case: "SMTPDirect" drop the connection when send each message. This is an important CPU hog when mailman has a long queue spool. Here is the patch (sorry, I can't send it as an attach, shame on me). It's fairly trivial : >>>>> Index: SMTPDirect.py =================================================================== RCS file: /opt/src/cvsroot/mailman/Mailman/Handlers/SMTPDirect.py,v retrieving revision 1.1.1.5 retrieving revision 1.1.1.5.2.1 diff -u -u -r1.1.1.5 -r1.1.1.5.2.1 --- SMTPDirect.py 2003/03/20 10:14:58 1.1.1.5 +++ SMTPDirect.py 2003/03/21 16:48:31 1.1.1.5.2.1 @@ -48,7 +48,7 @@ # Manage a connection to the SMTP server -class Connection: +class ConnectionClass: def __init__(self): self.__connect() @@ -79,7 +79,15 @@ def quit(self): self.__conn.quit() + def rset(self) : + self.__conn.rset() + def __del__(self) : + self.quit() + + +Connection=ConnectionClass() + def process(mlist, msg, msgdata): recips = msgdata.get('recips') @@ -130,7 +138,7 @@ # This means at worst, the last chunk for which delivery was attempted # could get duplicates but not every one, and no recips should miss the # message. - conn = Connection() + conn = Connection try: msgdata['undelivered'] = chunks while chunks: @@ -147,7 +155,8 @@ raise del msgdata['undelivered'] finally: - conn.quit() + conn.rset() + # conn.quit() msgdata['recips'] = origrecips # Log the successful post t1 = time.time() <<<<< ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-04-19 13:48 Message: Logged In: YES user_id=12800 I implemented this differently. The fix will be part of Mailman 2.1.2. If you are able, can you check the cvs snapshot as of 19-Apr-2003? ---------------------------------------------------------------------- Comment By: Jesús Cea Avión (jcea) Date: 2003-03-24 02:33 Message: Logged In: YES user_id=97460 The proposed patch causes exceptions if space between messages is greater than SMTP timeout. Corrected patch (I still can't attach a file): >>>>> Index: SMTPDirect.py =================================================================== RCS file: /opt/src/cvsroot/mailman/Mailman/Handlers/SMTPDirect.py,v retrieving revision 1.1.1.5 retrieving revision 1.1.1.5.2.3 diff -u -r1.1.1.5 -r1.1.1.5.2.3 --- SMTPDirect.py 2003/03/20 10:14:58 1.1.1.5 +++ SMTPDirect.py 2003/03/24 07:11:32 1.1.1.5.2.3 @@ -48,7 +48,7 @@ # Manage a connection to the SMTP server -class Connection: +class ConnectionClass: def __init__(self): self.__connect() @@ -58,6 +58,15 @@ self.__numsessions = mm_cfg.SMTP_MAX_SESSIONS_PER_CONNECTION def sendmail(self, envsender, recips, msgtext): + try : + self.__conn.rset() + except : + try : + self.__conn.quit() + except : + pass + self.__connect() + try: results = self.__conn.sendmail(envsender, recips, msgtext) except smtplib.SMTPException: @@ -79,6 +88,11 @@ def quit(self): self.__conn.quit() + def __del__(self) : + self.quit() + + +Connection=ConnectionClass() def process(mlist, msg, msgdata): @@ -130,7 +144,7 @@ # This means at worst, the last chunk for which delivery was attempted # could get duplicates but not every one, and no recips should miss the # message. - conn = Connection() + conn = Connection try: msgdata['undelivered'] = chunks while chunks: @@ -147,7 +161,7 @@ raise del msgdata['undelivered'] finally: - conn.quit() + # conn.quit() msgdata['recips'] = origrecips # Log the successful post t1 = time.time() <<<<< ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=707624&group_id=103 From noreply at sourceforge.net Sat Apr 19 11:50:58 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sat Apr 19 13:51:02 2003 Subject: [ mailman-Patches-717100 ] Fix for globally changing address when not on all lists Message-ID: Patches item #717100, was opened at 2003-04-07 19:13 Message generated for change (Settings changed) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=717100&group_id=103 Category: list administration Group: Mailman 2.1 >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Joe Peterson (skyrush) Assigned to: Nobody/Anonymous (nobody) Summary: Fix for globally changing address when not on all lists Initial Comment: If you have a user who is on some, but not all, of the lists on your server, and he/she tries to change his/her address *globally* (using the "change globally" checkbox), the person will get the confirmation email, but when he/she clicks the link in the email and then the button on the page to make the change, it will only change the address on the list originally chosen, and then it will raise a "Bad Confirmation code" error. The problem is that the call, "self.__assertIsMember(member)" in OldStyleMemberships.py fails and raises the error. The isMember() call should have been checked in ApprovedChangeMemberAddress in MailList.py before trying to change the address in the other lists. This statement fixes it: if not mlist.isMember(oldaddr): continue Note that this sort of check *is* done in ChangeMemberName (which I used as an example for the fix): if not mlist.isMember(addr): continue -Joe ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=717100&group_id=103 From noreply at sourceforge.net Sat Apr 19 11:52:49 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sat Apr 19 13:52:57 2003 Subject: [ mailman-Bugs-718083 ] lists.domain.com/mailman/create show Bug Error Message-ID: Bugs item #718083, was opened at 2003-04-09 04:47 Message generated for change (Settings changed) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=718083&group_id=103 Category: None Group: 2.1 (stable) >Status: Closed >Resolution: Duplicate Priority: 5 Submitted By: Marco A. Mateos (speckados) Assigned to: Nobody/Anonymous (nobody) Summary: lists.domain.com/mailman/create show Bug Error Initial Comment: Well, I've install mail man 2.1.1 on RedHat 7.3 with Plesk 5.0.5 panel. I've create aDNS A record for lists.estoyenred.net, and others. Go to http://lists.estoyenred.net/mailman/create a look this: ************** We're sorry, we hit a bug! If you would like to help us identify the problem, please email a copy of this page to the webmaster for this site with a description of what happened. Thanks! Traceback: Traceback (most recent call last): File "/var/mailman/scripts/driver", line 68, in run_main immediate=1) File "/var/mailman/Mailman/Logging/StampedLogger.py", line 52, in __init__ Logger.__init__(self, category, nofail, immediate) File "/var/mailman/Mailman/Logging/Logger.py", line 49, in __init__ self.__get_f() File "/var/mailman/Mailman/Logging/Logger.py", line 67, in __get_f 1) File "/var/tmp/python2-2.2.2-root/usr/lib/python2.2/codecs.py", line 496, in open file = __builtin__.open(filename, mode, buffering) IOError: [Errno 13] Permission denied: '/var/log/mailman/error' Python information: Variable Value sys.version 2.2.2 (#1, Apr 8 2003, 18:41:57) [GCC 2.96 20000731 (Red Hat Linux 7.3 2.96-113)] sys.executable /usr/bin/python2 sys.prefix /usr sys.exec_prefix /usr sys.path /usr sys.platform linux2 Environment variables: Variable Value HTTP_PRAGMA no-cache PYTHONPATH /var/mailman SERVER_SOFTWARE Apache/1.3.27 (Unix) (Red-Hat/Linux) FrontPage/5.0.2.2623 mod_ssl/2.8.12 OpenSSL/0.9.6b DAV/1.0.3 PHP/4.3.1 mod_perl/1.26 SCRIPT_FILENAME /var/mailman/cgi-bin//listinfo SERVER_ADMIN hosting@lomejordeinternet.net SCRIPT_NAME /mailman/listinfo SERVER_SIGNATURE Apache/1.3.27 Server at lists.estoyenred.net Port 80 REQUEST_METHOD GET HTTP_HOST lists.estoyenred.net SERVER_PROTOCOL HTTP/1.0 QUERY_STRING HTTP_CACHE_CONTROL max-age=259200 REQUEST_URI /mailman/listinfo HTTP_ACCEPT text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,video/x-mng,image/png,image/jpeg,image/gif;q=0.2,text/css,*/*;q=0.1 HTTP_ACCEPT_CHARSET ISO-8859-1, utf-8;q=0.66, *;q=0.66 HTTP_USER_AGENT Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20021003 HTTP_CONNECTION keep-alive SERVER_NAME lists.estoyenred.net REMOTE_ADDR 80.58.4.107 HTTP_CLIENT_IP 80.25.130.25 REMOTE_PORT 46324 HTTP_ACCEPT_LANGUAGE es-es, en-us;q=0.66, en;q=0.33 HTTP_X_FORWARDED_FOR 192.168.0.2 80.25.130.25 SERVER_PORT 80 GATEWAY_INTERFACE CGI/1.1 HTTP_VIA 1.1 specka.com:3128 (Squid/2.4.STABLE6), HTTP/1.0 proxy[AC1E0446] (Traffic-Server/5.5.1-58900 [uScM]) HTTP_ACCEPT_ENCODING gzip, deflate, compress;q=0.9 SERVER_ADDR 207.44.220.54 DOCUMENT_ROOT /home/httpd/vhosts/default/htdocs ============================ Im'lost .... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=718083&group_id=103 From noreply at sourceforge.net Sat Apr 19 11:53:13 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sat Apr 19 13:53:16 2003 Subject: [ mailman-Bugs-717096 ] Changing address "globally" if not on all lists fails Message-ID: Bugs item #717096, was opened at 2003-04-07 19:09 Message generated for change (Settings changed) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=717096&group_id=103 Category: (un)subscribing Group: 2.1 (stable) >Status: Closed Resolution: Fixed Priority: 5 Submitted By: Joe Peterson (skyrush) Assigned to: Nobody/Anonymous (nobody) >Summary: Changing address "globally" if not on all lists fails Initial Comment: If you have a user who is on some, but not all, of the lists on your server, and he/she tries to change his/her address *globally* (using the "change globally" checkbox), the person will get the confirmation email, but when he/she clicks the link in the email and then the button on the page to make the change, it will only change the address on the list originally chosen, and then it will raise a "Bad Confirmation code" error. The problem is that the call, "self.__assertIsMember(member)" in OldStyleMemberships.py fails and raises the error. The isMember() call should have been checked in ApprovedChangeMemberAddress in MailList.py before trying to change the address in the other lists. This statement fixes it: if not mlist.isMember(oldaddr): continue Note that this sort of check *is* done in ChangeMemberName (which I used as an example for the fix): if not mlist.isMember(addr): continue -Joe ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=717096&group_id=103 From noreply at sourceforge.net Sat Apr 19 13:27:38 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sat Apr 19 15:27:43 2003 Subject: [ mailman-Bugs-717110 ] mail commands Message-ID: Bugs item #717110, was opened at 2003-04-07 19:23 Message generated for change (Comment added) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=717110&group_id=103 Category: Web/CGI Group: 2.1 (stable) >Status: Closed >Resolution: Invalid Priority: 5 Submitted By: Will Yardley (wyardley) Assigned to: Nobody/Anonymous (nobody) Summary: mail commands Initial Comment: when approving a message via email, if you type: Approved: passwrd in the headers of a response to the confirmation message, when the actual password is 'password', the message you're trying to approve is discarded; I think that no action (and an "incorrect password" error message in response) would be more appropriate. Also, as I've mentioned before, it would be very nice if the exact action being performed were listed, rather than the generic "confirmation succeeded" message. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-04-19 15:27 Message: Logged In: YES user_id=12800 After re-reading this bug report, I believe Mailman is working as expected. If you read the body of the confirmation message, you'll see that replying to it keeping the subject intact always discards the original message. The way to approve it is to resend the first message in the digest, which is the original held message. Add Approved: password header to the resend, and then reply to the confirmation message to get rid of the old hold. I admit this isn't the most convenient way to do it, but for now that's it. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=717110&group_id=103 From noreply at sourceforge.net Sat Apr 19 14:07:22 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sat Apr 19 16:07:27 2003 Subject: [ mailman-Bugs-716755 ] invalid HTML in page templates Message-ID: Bugs item #716755, was opened at 2003-04-07 10:32 Message generated for change (Settings changed) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=716755&group_id=103 Category: Web/CGI Group: 2.1 (stable) >Status: Closed >Resolution: Accepted Priority: 5 Submitted By: Richard Barrett (ppsys) Assigned to: Nobody/Anonymous (nobody) Summary: invalid HTML in page templates Initial Comment: A number of page templates in the 2.1.1 release are defective, i.e. the HTML is invalid. A patch file to correct these problems is available through patch #661138, which does the following: Various languages (de, en, es, et, fi, hu, it, ja, lt, nl, pt_BR) ----------------- admindetails.html - removed extraneous P tags from inside UL Swedish templates ----------------- admindetails.html - removed spurious body tags adminpreamble.html - removed spurious body tags article.html - moved stuff from inside BODY tag back to inside HEAD tag headfoot.html - removed spurious body tags French templates ---------------- archidxfoot.html - removed spurious HTML and BODY open tags archidxhead.html - removed spurious HTML and BODY close tags and moved stuff from inside BODY tag back to inside HEAD tag Dutch templates --------------- article.html - added \n to end of file ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=716755&group_id=103 From noreply at sourceforge.net Sat Apr 19 14:07:16 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sat Apr 19 16:07:29 2003 Subject: [ mailman-Patches-661138 ] corrects defects in some HTML templates Message-ID: Patches item #661138, was opened at 2003-01-02 10:55 Message generated for change (Settings changed) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=661138&group_id=103 Category: internationalization Group: Mailman 2.1 >Status: Closed >Resolution: Accepted Priority: 5 Submitted By: Richard Barrett (ppsys) Assigned to: Nobody/Anonymous (nobody) Summary: corrects defects in some HTML templates Initial Comment: This patch corrects some defects in HTML templates in the MM 2.1 release. Apply the patch from within the MM 2.1 build directory using the command: patch -p1 < path-to-patch-file The following are changed by the patch Various languages (de, en, es, et, fi, hu, it, ja, lt, nl, pt_BR) ----------------- admindetails.html - removed extraneous P tags from inside UL Swedish templates ----------------- admindetails.html - removed spurious body tags adminpreamble.html - removed spurious body tags article.html - moved stuff from inside BODY tag back to inside HEAD tag headfoot.html - removed spurious body tags French templates ---------------- archidxfoot.html - removed spurious HTML and BODY open tags archidxhead.html - removed spurious HTML and BODY close tags and moved stuff from inside BODY tag back to inside HEAD tag Dutch templates --------------- article.html - added \n to end of file ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-02-10 07:02 Message: Logged In: YES user_id=75166 templates-2.1-0.1.patch is also applicable to MM release 2.1.1 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=661138&group_id=103 From noreply at sourceforge.net Sat Apr 19 14:41:06 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sat Apr 19 16:41:13 2003 Subject: [ mailman-Patches-668685 ] sys.exit handling by script/driver Message-ID: Patches item #668685, was opened at 2003-01-15 14:35 Message generated for change (Settings changed) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=668685&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: sys.exit handling by script/driver Initial Comment: The code in the $prefix/scripts/driver script concedes that it is valid for a script it is supervising to exit using sys.exit rather than just returning from the main function. However, if the script being supervised does use sys.exit, the driver script fails to pass on the output generated by the supervised script. In the case of cgi scripts this means that an internal server error is reported by the http server because no output has been returned. And finding the reason for this is tedious! The attached patch file (driver-2.1-0.1.patch) can applied with the following command with pwd being the MM build directory: patch -p1 < ../ ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-02-10 06:18 Message: Logged In: YES user_id=75166 driver-2.1-0.1.patch is alos applicable to MM release 2.1.1 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=668685&group_id=103 From noreply at sourceforge.net Sat Apr 19 14:41:46 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sat Apr 19 16:41:51 2003 Subject: [ mailman-Bugs-716754 ] sys.exit handling by script/driver Message-ID: Bugs item #716754, was opened at 2003-04-07 10:26 Message generated for change (Settings changed) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=716754&group_id=103 Category: Web/CGI Group: 2.1 (stable) >Status: Closed >Resolution: Accepted Priority: 5 Submitted By: Richard Barrett (ppsys) Assigned to: Nobody/Anonymous (nobody) Summary: sys.exit handling by script/driver Initial Comment: The code in the $prefix/scripts/driver script concedes that it is valid for a script it is supervising to exit using the sys.exit function rather than just returning from the main function. However, if the script being supervised does use sys.exit, the driver script fails to pass on the output generated by the supervised script. In the case of cgi scripts this means that an internal server error is reported by the http server because no output has been returned. A patch file to fix this problem is available as #668685 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=716754&group_id=103 From noreply at sourceforge.net Sat Apr 19 14:47:13 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sat Apr 19 16:47:23 2003 Subject: [ mailman-Bugs-716702 ] checkdbs i18n Message-ID: Bugs item #716702, was opened at 2003-04-07 08:21 Message generated for change (Settings changed) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=716702&group_id=103 Category: command line scripts Group: 2.1 (stable) >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Bartosz Sawicki (sawickib) Assigned to: Nobody/Anonymous (nobody) Summary: checkdbs i18n Initial Comment: I've found phrase that could not be translated: Action: dailly checkdbs run Message: reason for pending posts eg. "Post by non-member to a members-only list" In code: bin/checkdbs, line 114, there is: when, sender, subject, reason, text, msgdata = mlist.GetRecord(id) date = time.ctime(when) pending.append(_("""\ From: %(sender)s on %(date)s Subject: %(subject)s Cause: %(reason)s""")) As you see none of "when, sender, subject, reason, text, msgdata" are beeing translated. I agree, that translation of sender or subject is unwated, but variables 'date' and 'reason' should be translated. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=716702&group_id=103 From noreply at sourceforge.net Sat Apr 19 15:20:11 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sat Apr 19 17:20:16 2003 Subject: [ mailman-Bugs-659011 ] add_members -c publishes member list Message-ID: Bugs item #659011, was opened at 2002-12-27 09:10 Message generated for change (Comment added) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=659011&group_id=103 Category: command line scripts Group: 2.1 (stable) >Status: Closed >Resolution: Fixed Priority: 7 Submitted By: Jost Krieger (jkrieger) Assigned to: Nobody/Anonymous (nobody) Summary: add_members -c publishes member list Initial Comment: add_members -c uses Message.UserNotification for the "Big changes" message. This puts all recipients into the "To:" field, which has already lead to a privacy complaint at our site. Of course it's also a Really Bad Idea with large lists. Jost ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-04-19 17:20 Message: Logged In: YES user_id=12800 I've decided instead to remove -c / --changes-msg. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=659011&group_id=103 From noreply at sourceforge.net Sat Apr 19 15:24:17 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sat Apr 19 17:24:35 2003 Subject: [ mailman-Bugs-662490 ] not mimetype return Message-ID: Bugs item #662490, was opened at 2003-01-05 01:44 Message generated for change (Settings changed) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=662490&group_id=103 Category: Web/CGI Group: 2.1 (stable) >Status: Closed >Resolution: Fixed Priority: 7 Submitted By: Jorge Becerra (jlbpcuba) Assigned to: Nobody/Anonymous (nobody) Summary: not mimetype return Initial Comment: Attachments acces using the Mailman cgi-wrapper (private) don´t get the proper mimetype ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=662490&group_id=103 From noreply at sourceforge.net Sat Apr 19 15:25:10 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sat Apr 19 17:25:20 2003 Subject: [ mailman-Bugs-662472 ] scrubber arbitrary extension change for attachments Message-ID: Bugs item #662472, was opened at 2003-01-04 23:38 Message generated for change (Comment added) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=662472&group_id=103 Category: None Group: 2.1 (stable) >Status: Closed >Resolution: Fixed Priority: 7 Submitted By: Jorge Becerra (jlbpcuba) Assigned to: Nobody/Anonymous (nobody) Summary: scrubber arbitrary extension change for attachments Initial Comment: the archiver scrubber seems to honor the mimetypes, but not the file extensions. He change the extension other , even when use some that have the same mimetypes and don´t keep the same, he changes to the first with the same mimetypes taked from mimetypes.py or some other order. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-04-19 17:25 Message: Logged In: YES user_id=12800 I believe this has been fixed for Mailman 2.1.2 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=662472&group_id=103 From noreply at sourceforge.net Sat Apr 19 15:27:04 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sat Apr 19 17:27:12 2003 Subject: [ mailman-Bugs-667232 ] Collapse CC: header Message-ID: Bugs item #667232, was opened at 2003-01-13 11:20 Message generated for change (Comment added) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=667232&group_id=103 Category: mail delivery Group: 2.1 (stable) >Status: Closed >Resolution: Out of Date Priority: 7 Submitted By: Barry A. Warsaw (bwarsaw) Assigned to: Nobody/Anonymous (nobody) Summary: Collapse CC: header Initial Comment: Some email tools adhere strictly to RFC 2822, which mandates exactly one CC header. Other tools are more lenient and allow multiple CC headers. To interoperate better with more strict tools, Mailman should accept multiple CC headers (it already does) and it should collapse them to a single CC header even if not doing header munging. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-04-19 17:27 Message: Logged In: YES user_id=12800 We do this when we do reply-to munging, which ought to be good enough. Mailman shouldn't compensate for overly strict tools if the original message's CC headers aren't fully compliant. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=667232&group_id=103 From noreply at sourceforge.net Sat Apr 19 14:51:57 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sat Apr 19 17:44:36 2003 Subject: [ mailman-Bugs-670535 ] qrunner stops for no apparent reason Message-ID: Bugs item #670535, was opened at 2003-01-18 22:04 Message generated for change (Comment added) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=670535&group_id=103 Category: mail delivery Group: 2.1 (stable) >Status: Pending Resolution: None Priority: 8 Submitted By: David Gibbs (midrangeman) Assigned to: Nobody/Anonymous (nobody) Summary: qrunner stops for no apparent reason Initial Comment: About once every day or so, qrunner will stop for no apparent reason. The qrunner log file has the following ... Jan 18 14:29:09 2003 (3443) IncomingRunner qrunner caught SIGTERM. Stopping. Jan 18 14:29:09 2003 (3443) IncomingRunner qrunner exiting. Jan 18 14:29:09 2003 (3441) BounceRunner qrunner caught SIGTERM. Stopping. Jan 18 14:29:09 2003 (3441) BounceRunner qrunner exiting. Jan 18 14:29:09 2003 (3445) OutgoingRunner qrunner caught SIGTERM. Stopping. Jan 18 14:29:09 2003 (3445) OutgoingRunner qrunner exiting. Jan 18 14:29:09 2003 (3442) CommandRunner qrunner caught SIGTERM. Stopping. Jan 18 14:29:09 2003 (3442) CommandRunner qrunner exiting. Jan 18 14:29:09 2003 (3446) VirginRunner qrunner caught SIGTERM. Stopping. Jan 18 14:29:09 2003 (3446) VirginRunner qrunner exiting. Jan 18 14:29:09 2003 (3440) ArchRunner qrunner caught SIGTERM. Stopping. Jan 18 14:29:09 2003 (3440) ArchRunner qrunner exiting. Jan 18 14:29:10 2003 (3444) NewsRunner qrunner caught SIGTERM. Stopping. Jan 18 14:29:12 2003 (3444) NewsRunner qrunner exiting. No other log has any indication of what might be happening. Is there a way to increase the logging somewhere so the cause can be identified? ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-04-19 16:51 Message: Logged In: YES user_id=12800 David, have you been able to dig up more information about this problem? I'm moving this to Pending as we have no clue why it's happening for you and cannot reproduce it on any systems we have available to us. ---------------------------------------------------------------------- Comment By: Thomas Wouters (twouters) Date: 2003-03-21 19:54 Message: Logged In: YES user_id=34209 No, having multiple versions of Python should not be causing this. Nor should the SIGALRM handler being triggered cause it, unless something is seriously broken in your setup -- but we've already been there. The only way to see if a SIGTERM is actually being delivered is running the processes under strace or gdb, but this seriously disrupts regular operation. There is no way that i know of to find out where a signal is coming from, once you find out that it really is a signal. If it *isn't* a real signal, I would start looking at libc bugs and other platform bugs. You can try upgrading Python to 2.2.2 (the latest bugfix release) but I would be very suprised if it fixed your problem. RedHat does not have a great reputation for stability, so be sure to check for any RedHat updates. ---------------------------------------------------------------------- Comment By: David Gibbs (midrangeman) Date: 2003-03-17 12:44 Message: Logged In: YES user_id=86339 Additional environment details: Redhat Linux 8.0, uname = "Linux xxx.midrange.com 2.4.18- 26.8.0 #1 Mon Feb 24 10:21:42 EST 2003 i686 i686 i386 GNU/Linux" Python: 2.2.1 CPU: P4 2.4ghz, 512mb RAM Dunno if this makes a difference, but I have the following directories ... /usr/lib/python1.5 /usr/lib/python2.1 /usr/lib/python2.2 Any chance there is a conflict? ---------------------------------------------------------------------- Comment By: David Gibbs (midrangeman) Date: 2003-01-24 13:31 Message: Logged In: YES user_id=86339 I added some debug code to mailmanctl and found out that the sigalarm handler is firing just before the qrunners are terminating. ---------------------------------------------------------------------- Comment By: David Gibbs (midrangeman) Date: 2003-01-22 16:31 Message: Logged In: YES user_id=86339 After some further research, QRUNNER seems to stop after exactly 24 hours of operation. That is, 24 hours after qrunner starts, it ends as if someone killed it with SIGTERM. I know for a fact that nobody is actually doing this ... and no process on my system should be aware of the fact that qrunner is actually running. I will not discount the possiblity that this is an environmental factor, but it seems to me that a daemon process should not be affected by environmental factors. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-01-19 17:46 Message: Logged In: YES user_id=12800 I'm not sure what kind of logging would help. Some process somewhere is SIGTERMing the mailmanctl controller process. There's no way to know where a signal is coming from, so I'm not sure what more you could do in mailmanctl. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=670535&group_id=103 From noreply at sourceforge.net Sat Apr 19 16:09:17 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sat Apr 19 18:09:26 2003 Subject: [ mailman-Bugs-667167 ] Non-digest options configuration help Message-ID: Bugs item #667167, was opened at 2003-01-13 09:11 Message generated for change (Settings changed) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=667167&group_id=103 Category: Web/CGI Group: 2.1 (stable) >Status: Closed >Resolution: Fixed Priority: 7 Submitted By: John Swartzentruber (jswartzen) Assigned to: Nobody/Anonymous (nobody) Summary: Non-digest options configuration help Initial Comment: It would be helpful if the personalized footer fields (eg user_address or user_name) were also listed in the "Details for msg_footer". Or at least a mention that they are listed in the "Details for personalize". ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=667167&group_id=103 From noreply at sourceforge.net Sat Apr 19 16:19:37 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sat Apr 19 18:19:48 2003 Subject: [ mailman-Bugs-665791 ] Hiding e-mail addresses breaks mbox archives Message-ID: Bugs item #665791, was opened at 2003-01-10 10:12 Message generated for change (Comment added) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=665791&group_id=103 Category: Pipermail Group: 2.1 (stable) >Status: Closed >Resolution: Out of Date Priority: 7 Submitted By: A.M. Kuchling (akuchling) Assigned to: Nobody/Anonymous (nobody) Summary: Hiding e-mail addresses breaks mbox archives Initial Comment: (Noticed in the archives for the pycon-organizers list) The archiver will generate mbox separator lines that look like this: >From sholden at holdenweb.com Fri Jan 3 03:53:20 2003 This breaks at least mutt's mbox parsing. The line should use unaltered e-mail address. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-04-19 18:19 Message: Logged In: YES user_id=12800 I believe this was fixed in Mailman 2.1.1 (or at least it's now fixed in cvs for 2.1.2). ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=665791&group_id=103 From noreply at sourceforge.net Sat Apr 19 16:44:01 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sat Apr 19 18:44:05 2003 Subject: [ mailman-Bugs-611185 ] rmlist doesn't delete lock files Message-ID: Bugs item #611185, was opened at 2002-09-18 13:23 Message generated for change (Settings changed) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=611185&group_id=103 Category: command line scripts Group: 2.1 (stable) >Status: Closed >Resolution: Fixed Priority: 7 Submitted By: Linda Julien (leira) Assigned to: Nobody/Anonymous (nobody) Summary: rmlist doesn't delete lock files Initial Comment: I'm using 2.0.13. The rmlist script doesn't delete lock files associated with the list (if any exist). Removing a list and creating a new one with the same name can have unexpected results. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-01-15 12:02 Message: Logged In: YES user_id=12800 Promoting this to a 2.1 (stable) bug, since I doubt the code's changed much here. Need to double check. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=611185&group_id=103 From noreply at sourceforge.net Sat Apr 19 16:55:00 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sat Apr 19 18:55:05 2003 Subject: [ mailman-Bugs-663675 ] Administrative interface vs. non-standard HTTP ports Message-ID: Bugs item #663675, was opened at 2003-01-07 08:02 Message generated for change (Comment added) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=663675&group_id=103 Category: Web/CGI Group: 2.1 (stable) >Status: Closed >Resolution: Works For Me Priority: 7 Submitted By: Fabricio Chalub (chalub) Assigned to: Nobody/Anonymous (nobody) Summary: Administrative interface vs. non-standard HTTP ports Initial Comment: I still find that mailman's administrative interface behaves incorrectly on HTTPDs running on non-standard ports. It simply discards the port information out of the URL, despite DEFAULT_URL* settings. On some pages, the URL to the FORM ACTION is relative (eg, the "General Options" form) while others, it is absolute (eg, the "Membership list"). Looking around the source, I've found lines like this (on Mailman/Cgi/admin.py) adminurl = mlist.GetScriptURL('admin', absolute=1) Changing the value of ABSOLUTE to 0 solved the problem, and I've found it pretty harmless. Any specific reason for the ABSOLUTE=1 setting? ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-04-19 18:55 Message: Logged In: YES user_id=12800 We had lots of problems when non-absolute urls where used, although I don't remember the exact details of the problems. Eventually we'll probably make all urls absolute and get rid of this argument to GetScriptURL(). BTW, this works for me, so I'm closing the bug report. Note that changing the DEFAULT_URL_* variables does not change settings for existing lists. For those you must use bin/withlist to change the web_page_url variable manually. If there are specific links that are broken, then please follow up with those links and I'll look into them. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=663675&group_id=103 From noreply at sourceforge.net Sat Apr 19 18:49:32 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sun Apr 20 22:52:32 2003 Subject: [ mailman-Patches-659021 ] Log open requests daily Message-ID: Patches item #659021, was opened at 2002-12-27 09:42 Message generated for change (Comment added) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=659021&group_id=103 Category: list administration Group: Mailman 2.1 >Status: Pending Resolution: None Priority: 5 Submitted By: Jost Krieger (jkrieger) Assigned to: Nobody/Anonymous (nobody) Summary: Log open requests daily Initial Comment: For large installations, it helps if the site administrator sees if a list slowly turns bad :-) This patch logs the number of open requests from checkdbs. Jost ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-04-19 20:49 Message: Logged In: YES user_id=12800 Moving this to Pending since there's no patch attached. ---------------------------------------------------------------------- Comment By: Thomas Wouters (twouters) Date: 2003-03-10 11:22 Message: Logged In: YES user_id=34209 No patch was attached (sigh, SourceForge.) Are you sure you clicked the 'Check to Upload and Attach a File' box ? I believe you also need to add a 'comment' for a file upload to work. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=659021&group_id=103 From noreply at sourceforge.net Mon Apr 21 18:15:34 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Apr 21 20:15:39 2003 Subject: [ mailman-Patches-725369 ] Remove X-Originating-Email: from anonymous lists Message-ID: Patches item #725369, was opened at 2003-04-21 19:15 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=725369&group_id=103 Category: mail delivery Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Roger Tsang (bluecloud) Assigned to: Nobody/Anonymous (nobody) Summary: Remove X-Originating-Email: from anonymous lists Initial Comment: The email address of the poster is send out to anonymous lists in an X-Originating-Email header. Hotmail adds this header to outgoing messages!!! Patched against Mailman 2.1.1 If you use the source patch, you need to manually recompile your .py to .pyc format and restart Mailman. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=725369&group_id=103 From noreply at sourceforge.net Mon Apr 21 18:21:21 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Apr 21 20:21:24 2003 Subject: [ mailman-Patches-725369 ] Remove X-Originating-Email: for anonymous lists Message-ID: Patches item #725369, was opened at 2003-04-21 19:15 Message generated for change (Settings changed) made by bluecloud You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=725369&group_id=103 Category: mail delivery Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Roger Tsang (bluecloud) Assigned to: Nobody/Anonymous (nobody) >Summary: Remove X-Originating-Email: for anonymous lists Initial Comment: The email address of the poster is send out to anonymous lists in an X-Originating-Email header. Hotmail adds this header to outgoing messages!!! Patched against Mailman 2.1.1 If you use the source patch, you need to manually recompile your .py to .pyc format and restart Mailman. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=725369&group_id=103 From noreply at sourceforge.net Mon Apr 21 19:57:42 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Apr 21 21:57:48 2003 Subject: [ mailman-Patches-725369 ] Remove X-Originating-Email: for anonymous lists Message-ID: Patches item #725369, was opened at 2003-04-21 20:15 Message generated for change (Settings changed) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=725369&group_id=103 Category: mail delivery Group: Mailman 2.1 >Status: Closed >Resolution: Accepted Priority: 5 Submitted By: Roger Tsang (bluecloud) Assigned to: Nobody/Anonymous (nobody) Summary: Remove X-Originating-Email: for anonymous lists Initial Comment: The email address of the poster is send out to anonymous lists in an X-Originating-Email header. Hotmail adds this header to outgoing messages!!! Patched against Mailman 2.1.1 If you use the source patch, you need to manually recompile your .py to .pyc format and restart Mailman. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=725369&group_id=103 From noreply at sourceforge.net Tue Apr 22 07:00:24 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Apr 22 09:00:34 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: Open 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-04-22 13:00 Message: Logged In: YES user_id=67709 Recently, I had a chance to get personal correspondence to refer this patch. To quote his comment, "(it) works like a charm!" So, I am incrementing the priority. :^) ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-02-24 04:34 Message: Logged In: YES user_id=67709 Uploading revised patch to fix more error. Sorry for the people downloaded earlier. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-02-24 01:39 Message: Logged In: YES user_id=67709 update my patch to fix error reported by sumeet File "/list/Mailman/Handlers/Scrubber.py", line 320, in process if not t.endswith('\n'): AttributeError: 'NoneType' object has no attribute 'endswith' ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-02-22 07:05 Message: Logged In: YES user_id=67709 This patch for Scrubber.py now include Bug-ID #691039. save_attachment() now returns (url, size), because in previous code, get_paylaod() is called before calling save_attachment() only to get the size. save_attachment() calls get_payload() inside. We might be able to discard the attachment if get_payload(decode=1) fail. (TBD: return discard message and size 0 ?) ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-02-20 01:31 Message: Logged In: YES user_id=67709 Increment priority because this is now a bug fix. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-02-04 06:08 Message: Logged In: YES user_id=67709 I made a new patch to fix embedded multipart messages are stripped bug. this patch is for CVS. see http://mail.python.org/pipermail/mailman-users/2003-February/026071.html ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-01-20 05:13 Message: Logged In: YES user_id=12800 Reopening so this issue doesn't get lost. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-01-20 04:03 Message: Logged In: YES user_id=67709 We, Japanese, need additional process of stringify and regenerate message instance.. Internal message is in 'euc-jp' but return value of get_content_charset() becomes 'iso-2022-jp' even though the get_payload() returns euc-jp text. The message and part body is converted to iso-2022-jp when it is output to SMTP (or whatever accepts in string format). ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-01-20 02:18 Message: Logged In: YES user_id=12800 Accepted, with changes. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-01-19 00:52 Message: Logged In: YES user_id=67709 Update of patch. Please backout the first one if you have already applied. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=670167&group_id=103 From noreply at sourceforge.net Tue Apr 22 19:29:31 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Apr 22 21:29:39 2003 Subject: [ mailman-Patches-685788 ] fix for Cc: to cc: weirdness Message-ID: Patches item #685788, was opened at 2003-02-13 07:47 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=685788&group_id=103 Category: mail delivery Group: Mailman 2.1 >Status: Closed >Resolution: Fixed Priority: 6 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: fix for Cc: to cc: weirdness Initial Comment: http://mail.python.org/pipermail/mailman-users/2003-February/026353.html describe the problem. It is caused by Mailman/Handlers/AvoidDuplicates.py ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-04-23 01:29 Message: Logged In: YES user_id=67709 This was fixed in 2.1.2 ---------------------------------------------------------------------- Comment By: Thomas Wouters (twouters) Date: 2003-03-10 14:16 Message: Logged In: YES user_id=34209 I wonder if the better solution isn't fixing this in the email package itself, by special-casing the handling of some of the headers. Barry? (I can handle either, I just want to know which I should do :-) ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-02-15 11:17 Message: Logged In: YES user_id=67709 I will be incrementing priority every time I point this patch. ;-) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=685788&group_id=103 From noreply at sourceforge.net Tue Apr 22 21:54:04 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Apr 22 23:54:11 2003 Subject: [ mailman-Bugs-726016 ] confirm crash when admin_notify_mchanges is yes Message-ID: Bugs item #726016, was opened at 2003-04-23 15:54 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=726016&group_id=103 Category: (un)subscribing Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Colin Palmer (tzs) Assigned to: Nobody/Anonymous (nobody) Summary: confirm crash when admin_notify_mchanges is yes Initial Comment: OS is OpenBSD 3.1, same error occurs in Python-2.2 and Python-2.2.2 This happens after getting the confirmation email, following the link in it and clicking on the ''Subscribe to list Listname" button, but only when admin_notify_mchanges is Yes, otherwise it works. This worked in 2.1b3, but is broken in 2.1 and 2.1.1 @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ [----- Mailman Version: 2.1.1 -----] [----- Traceback ------] Traceback (most recent call last): File "/home/mailman/scripts/driver", line 87, in run_main main() File "/home/mailman/Mailman/Cgi/confirm.py", line 110, in main subscription_confirm(mlist, doc, cookie, cgidata) File "/home/mailman/Mailman/Cgi/confirm.py", line 333, in subscription_confirm op, addr, pw, digest, lang = mlist.ProcessConfirmation( File "/home/mailman/Mailman/MailList.py", line 1071, in ProcessConfirmation self.ApprovedAddMember(userdesc) File "/home/mailman/Mailman/MailList.py", line 899, in ApprovedAddMember }, mlist=self) File "/home/mailman/Mailman/Utils.py", line 481, in maketext return wrap(text) File "/home/mailman/Mailman/Utils.py", line 113, in wrap if honor_leading_ws and line[0] in whitespace: UnicodeError: ASCII decoding error: ordinal not in range(128) [----- Python Information -----] sys.version = 2.2 (#1, Apr 12 2002, 22:56:34) [GCC 2.95.3 20010125 (prerelease)] sys.executable = /usr/local/bin/python sys.prefix = /usr/local sys.exec_prefix = /usr/local sys.path = /usr/local sys.platform = openbsd3 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=726016&group_id=103 From noreply at sourceforge.net Tue Apr 22 22:08:46 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Apr 23 00:08:52 2003 Subject: [ mailman-Bugs-726019 ] logger crash when generating tracebacks Message-ID: Bugs item #726019, was opened at 2003-04-23 16:08 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=726019&group_id=103 Category: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Colin Palmer (tzs) Assigned to: Nobody/Anonymous (nobody) Summary: logger crash when generating tracebacks Initial Comment: OpenBSD-3.1, Python-2.2.2, Mailman-2.1.1 When something causes an exception in the CGI scripts, the logger then produces one of its own trying to report it: @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ [----- Mailman Version: 2.1.1 -----] [----- Traceback ------] Traceback (most recent call last): File "/home/mailman/scripts/driver", line 224, in ? run_main() File "/home/mailman/scripts/driver", line 96, in run_main print_traceback(logger) File "/home/mailman/scripts/driver", line 121, in print_traceback print >> logfp, '@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@' File "/home/mailman/Mailman/Logging/StampedLogger.py", line 73, in write Logger.write(self, "%s %s" % (prefix, msg)) File "/home/mailman/Mailman/Logging/Logger.py", line 88, in write msg = unicode(msg, self.__encoding) SystemError: can't resize shared unicode objects [----- Python Information -----] sys.version = 2.2.2 (#1, Apr 22 2003, 22:52:59) [GCC 2.95.3 20010125 (prerelease)] sys.executable = /usr/local/bin/python sys.prefix = /usr/local sys.exec_prefix = /usr/local sys.path = /usr/local sys.platform = openbsd3 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=726019&group_id=103 From noreply at sourceforge.net Wed Apr 23 12:14:20 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Apr 23 14:14:23 2003 Subject: [ mailman-Bugs-726415 ] incorrect pidfile name in init.d script Message-ID: Bugs item #726415, was opened at 2003-04-23 13:14 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=726415&group_id=103 Category: configuring/installing Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: John Dennis (johndennis) Assigned to: Nobody/Anonymous (nobody) Summary: incorrect pidfile name in init.d script Initial Comment: the init.d script (misc/mailmain.in) has the following as the pidfile # pidfile: @prefix@/data/qrunner.pid but Defaults.py defines it as: PIDFILE = os.path.join(DATA_DIR, 'master-qrunner.pid') the name in the init.d scripts should be changed to master-qrunner.pid ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=726415&group_id=103 From noreply at sourceforge.net Wed Apr 23 16:20:25 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Apr 23 18:20:29 2003 Subject: [ mailman-Bugs-726554 ] Mailman and SMTPDirect stop talking, mailing totally fails Message-ID: Bugs item #726554, was opened at 2003-04-23 22:20 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=726554&group_id=103 Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Cabel Sasser (cabelsa) Assigned to: Nobody/Anonymous (nobody) Summary: Mailman and SMTPDirect stop talking, mailing totally fails Initial Comment: I'm using Mailman 2.1 and Mac OS X 10.2.5. When I send my message (a personalized, announce-only list), after the first 150 or so deliveries (out of 19640), Mailman suddenly seems to stop communicating to the SMTP server, and all remaining recipients fail. There are no real good clues in /var/log/mail.log as to why SMTP is getting grumpy. These are the interesting parts of mail.log that appear around the time of failure -- everything else looks fine. -- /var/log/mail.log: Apr 23 15:06:39 newposh sendmail[5928]: h3NM4o0o005928: SYSERR(root): Cannot create ./dfh3NM4o0o005928: File exists [..] Apr 23 15:06:40 newposh sendmail[6251]: h3NM4o0j005928: to=, delay=00:00:01, xdelay=00:00:01, mailer=esmtp, pri=85368, relay=vm4-ext.prodigy.net. [207.115.63.115], dsn=5.3.0, stat=User unknown Apr 23 15:06:40 newposh sendmail[6251]: h3NM4o0j005928: h3NM6ewS006251: DSN: User unknown. -- logs/smtp: Apr 23 15:08:25 2003 (663) All recipients refused: please run connect() first Apr 23 15:08:25 2003 (663) All recipients refused: please run connect() first Apr 23 15:08:25 2003 (663) All recipients refused: please run connect() first Apr 23 15:08:25 2003 (663) All recipients refused: please run connect() first [..etc..] -- logs/error: Apr 23 15:08:25 2003 (663) Uncaught runner exception: please run connect() first Apr 23 15:08:25 2003 (663) Traceback (most recent call last): File "/usr/local/mailman/Mailman/Queue/Runner.py", line 105, in _oneloop self._onefile(msg, msgdata) File "/usr/local/mailman/Mailman/Queue/Runner.py", line 155, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/local/mailman/Mailman/Queue/OutgoingRunner.py", line 61, in _dispose self._func(mlist, msg, msgdata) File "/usr/local/mailman/Mailman/Handlers/SMTPDirect.py", line 150, in process conn.quit() File "/usr/local/mailman/Mailman/Handlers/SMTPDirect.py", line 80, in quit self.__conn.quit() File "/BinaryCache/python/python-3.root~377/usr/lib/ python2.2/smtplib.py", line 671, in quit self.docmd("quit") File "/BinaryCache/python/python-3.root~377/usr/lib/ python2.2/smtplib.py", line 352, in docmd self.putcmd(cmd,args) File "/BinaryCache/python/python-3.root~377/usr/lib/ python2.2/smtplib.py", line 308, in putcmd self.send(str) File "/BinaryCache/python/python-3.root~377/usr/lib/ python2.2/smtplib.py", line 300, in send raise SMTPServerDisconnected('please run connect() first') SMTPServerDisconnected: please run connect() first Apr 23 15:08:25 2003 (663) SHUNTING: 1051135414.712172+5cc02db8df9b882e2bc690b9706a9f7bf56 f273a -- Please let me know if there's anything I can do to help you find the cause of this problem. Thanks! ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=726554&group_id=103 From noreply at sourceforge.net Wed Apr 23 16:21:30 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Apr 23 18:21:33 2003 Subject: [ mailman-Bugs-726554 ] Mailman and SMTPDirect stop talking, mailing totally fails Message-ID: Bugs item #726554, was opened at 2003-04-23 22:20 Message generated for change (Settings changed) made by cabelsa You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=726554&group_id=103 Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None >Priority: 8 Submitted By: Cabel Sasser (cabelsa) >Assigned to: Barry A. Warsaw (bwarsaw) Summary: Mailman and SMTPDirect stop talking, mailing totally fails Initial Comment: I'm using Mailman 2.1 and Mac OS X 10.2.5. When I send my message (a personalized, announce-only list), after the first 150 or so deliveries (out of 19640), Mailman suddenly seems to stop communicating to the SMTP server, and all remaining recipients fail. There are no real good clues in /var/log/mail.log as to why SMTP is getting grumpy. These are the interesting parts of mail.log that appear around the time of failure -- everything else looks fine. -- /var/log/mail.log: Apr 23 15:06:39 newposh sendmail[5928]: h3NM4o0o005928: SYSERR(root): Cannot create ./dfh3NM4o0o005928: File exists [..] Apr 23 15:06:40 newposh sendmail[6251]: h3NM4o0j005928: to=, delay=00:00:01, xdelay=00:00:01, mailer=esmtp, pri=85368, relay=vm4-ext.prodigy.net. [207.115.63.115], dsn=5.3.0, stat=User unknown Apr 23 15:06:40 newposh sendmail[6251]: h3NM4o0j005928: h3NM6ewS006251: DSN: User unknown. -- logs/smtp: Apr 23 15:08:25 2003 (663) All recipients refused: please run connect() first Apr 23 15:08:25 2003 (663) All recipients refused: please run connect() first Apr 23 15:08:25 2003 (663) All recipients refused: please run connect() first Apr 23 15:08:25 2003 (663) All recipients refused: please run connect() first [..etc..] -- logs/error: Apr 23 15:08:25 2003 (663) Uncaught runner exception: please run connect() first Apr 23 15:08:25 2003 (663) Traceback (most recent call last): File "/usr/local/mailman/Mailman/Queue/Runner.py", line 105, in _oneloop self._onefile(msg, msgdata) File "/usr/local/mailman/Mailman/Queue/Runner.py", line 155, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/local/mailman/Mailman/Queue/OutgoingRunner.py", line 61, in _dispose self._func(mlist, msg, msgdata) File "/usr/local/mailman/Mailman/Handlers/SMTPDirect.py", line 150, in process conn.quit() File "/usr/local/mailman/Mailman/Handlers/SMTPDirect.py", line 80, in quit self.__conn.quit() File "/BinaryCache/python/python-3.root~377/usr/lib/ python2.2/smtplib.py", line 671, in quit self.docmd("quit") File "/BinaryCache/python/python-3.root~377/usr/lib/ python2.2/smtplib.py", line 352, in docmd self.putcmd(cmd,args) File "/BinaryCache/python/python-3.root~377/usr/lib/ python2.2/smtplib.py", line 308, in putcmd self.send(str) File "/BinaryCache/python/python-3.root~377/usr/lib/ python2.2/smtplib.py", line 300, in send raise SMTPServerDisconnected('please run connect() first') SMTPServerDisconnected: please run connect() first Apr 23 15:08:25 2003 (663) SHUNTING: 1051135414.712172+5cc02db8df9b882e2bc690b9706a9f7bf56 f273a -- Please let me know if there's anything I can do to help you find the cause of this problem. Thanks! ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=726554&group_id=103 From noreply at sourceforge.net Wed Apr 23 21:27:52 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Apr 23 23:27:58 2003 Subject: [ mailman-Bugs-726554 ] Mailman and SMTPDirect stop talking, mailing totally fails Message-ID: Bugs item #726554, was opened at 2003-04-23 18:20 Message generated for change (Comment added) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=726554&group_id=103 Category: mail delivery Group: 2.1 (stable) >Status: Closed >Resolution: Fixed Priority: 8 Submitted By: Cabel Sasser (cabelsa) Assigned to: Barry A. Warsaw (bwarsaw) Summary: Mailman and SMTPDirect stop talking, mailing totally fails Initial Comment: I'm using Mailman 2.1 and Mac OS X 10.2.5. When I send my message (a personalized, announce-only list), after the first 150 or so deliveries (out of 19640), Mailman suddenly seems to stop communicating to the SMTP server, and all remaining recipients fail. There are no real good clues in /var/log/mail.log as to why SMTP is getting grumpy. These are the interesting parts of mail.log that appear around the time of failure -- everything else looks fine. -- /var/log/mail.log: Apr 23 15:06:39 newposh sendmail[5928]: h3NM4o0o005928: SYSERR(root): Cannot create ./dfh3NM4o0o005928: File exists [..] Apr 23 15:06:40 newposh sendmail[6251]: h3NM4o0j005928: to=, delay=00:00:01, xdelay=00:00:01, mailer=esmtp, pri=85368, relay=vm4-ext.prodigy.net. [207.115.63.115], dsn=5.3.0, stat=User unknown Apr 23 15:06:40 newposh sendmail[6251]: h3NM4o0j005928: h3NM6ewS006251: DSN: User unknown. -- logs/smtp: Apr 23 15:08:25 2003 (663) All recipients refused: please run connect() first Apr 23 15:08:25 2003 (663) All recipients refused: please run connect() first Apr 23 15:08:25 2003 (663) All recipients refused: please run connect() first Apr 23 15:08:25 2003 (663) All recipients refused: please run connect() first [..etc..] -- logs/error: Apr 23 15:08:25 2003 (663) Uncaught runner exception: please run connect() first Apr 23 15:08:25 2003 (663) Traceback (most recent call last): File "/usr/local/mailman/Mailman/Queue/Runner.py", line 105, in _oneloop self._onefile(msg, msgdata) File "/usr/local/mailman/Mailman/Queue/Runner.py", line 155, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/local/mailman/Mailman/Queue/OutgoingRunner.py", line 61, in _dispose self._func(mlist, msg, msgdata) File "/usr/local/mailman/Mailman/Handlers/SMTPDirect.py", line 150, in process conn.quit() File "/usr/local/mailman/Mailman/Handlers/SMTPDirect.py", line 80, in quit self.__conn.quit() File "/BinaryCache/python/python-3.root~377/usr/lib/ python2.2/smtplib.py", line 671, in quit self.docmd("quit") File "/BinaryCache/python/python-3.root~377/usr/lib/ python2.2/smtplib.py", line 352, in docmd self.putcmd(cmd,args) File "/BinaryCache/python/python-3.root~377/usr/lib/ python2.2/smtplib.py", line 308, in putcmd self.send(str) File "/BinaryCache/python/python-3.root~377/usr/lib/ python2.2/smtplib.py", line 300, in send raise SMTPServerDisconnected('please run connect() first') SMTPServerDisconnected: please run connect() first Apr 23 15:08:25 2003 (663) SHUNTING: 1051135414.712172+5cc02db8df9b882e2bc690b9706a9f7bf56 f273a -- Please let me know if there's anything I can do to help you find the cause of this problem. Thanks! ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-04-23 23:27 Message: Logged In: YES user_id=12800 I believe I fixed this for Mailman 2.1.2. If after that's release (RSN, I promise!) if this bug recurs, please reopen this bug report. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=726554&group_id=103 From noreply at sourceforge.net Wed Apr 23 21:34:55 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Apr 23 23:34:59 2003 Subject: [ mailman-Bugs-726415 ] incorrect pidfile name in init.d script Message-ID: Bugs item #726415, was opened at 2003-04-23 14:14 Message generated for change (Settings changed) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=726415&group_id=103 Category: configuring/installing Group: 2.1 (stable) >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: John Dennis (johndennis) Assigned to: Nobody/Anonymous (nobody) Summary: incorrect pidfile name in init.d script Initial Comment: the init.d script (misc/mailmain.in) has the following as the pidfile # pidfile: @prefix@/data/qrunner.pid but Defaults.py defines it as: PIDFILE = os.path.join(DATA_DIR, 'master-qrunner.pid') the name in the init.d scripts should be changed to master-qrunner.pid ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=726415&group_id=103 From noreply at sourceforge.net Thu Apr 24 02:01:55 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Apr 24 04:02:03 2003 Subject: [ mailman-Bugs-726736 ] qrunner hung by spam Message-ID: Bugs item #726736, was opened at 2003-04-24 08:01 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=726736&group_id=103 Category: mail delivery Group: 2.0.x Status: Open Resolution: None Priority: 5 Submitted By: Greg Lindahl (greglindahl) Assigned to: Nobody/Anonymous (nobody) Summary: qrunner hung by spam Initial Comment: I realized no mail had gone out for 6 days, and saw that qrunner was barfing on SOMETHING. This is with Mailman 2.0.6. Even though I'm behind the times, I'd bet this bug could be in 2.1.X -- I just don't know enough Python to see what's going on. I blew away a bunch of files in my qfiles directory; I didn't save the bad message. Apr 24 00:39:01 2003 qrunner(2397): Traceback (innermost last): Apr 24 00:39:01 2003 qrunner(2397): File "/home/mailman/cron/qrunner", line 282, in ? Apr 24 00:39:01 2003 qrunner(2397): kids = main(lock) Apr 24 00:39:01 2003 qrunner(2397): File "/home/mailman/cron/qrunner", line 252, in main Apr 24 00:39:01 2003 qrunner(2397): keepqueued = dispose_message(mlist, msg, msgdata) Apr 24 00:39:01 2003 qrunner(2397): File "/home/mailman/cron/qrunner", line 121, in dispose_message Apr 24 00:39:01 2003 qrunner(2397): if BouncerAPI.ScanMessages(mlist, mimemsg): Apr 24 00:39:01 2003 qrunner(2397): File "/home/mailman/Mailman/Bouncers/BouncerAPI.py", line 59, in ScanMessages Apr 24 00:39:01 2003 qrunner(2397): addrs = func(msg) Apr 24 00:39:01 2003 qrunner(2397): File "/home/mailman/Mailman/Bouncers/Postfix.py", line 39, in process Apr 24 00:39:01 2003 qrunner(2397): more = mfile.next() Apr 24 00:39:01 2003 qrunner(2397): File "/usr/lib/python1.5/multifile.py", line 121, in next Apr 24 00:39:01 2003 qrunner(2397): while self.readline(): pass Apr 24 00:39:01 2003 qrunner(2397): File "/usr/lib/python1.5/multifile.py", line 93, in readline Apr 24 00:39:01 2003 qrunner(2397): if marker == self.section_divider(sep): Apr 24 00:39:01 2003 qrunner(2397): File "/usr/lib/python1.5/multifile.py", line 157, in section_divider Apr 24 00:39:01 2003 qrunner(2397): return "--" + str Apr 24 00:39:01 2003 qrunner(2397): TypeError : illegal argument type for built-in operation ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=726736&group_id=103 From noreply at sourceforge.net Thu Apr 24 02:02:52 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Apr 24 04:02:59 2003 Subject: [ mailman-Bugs-726736 ] qrunner hung by spam Message-ID: Bugs item #726736, was opened at 2003-04-24 08:01 Message generated for change (Settings changed) made by greglindahl You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=726736&group_id=103 Category: mail delivery Group: 2.0.x Status: Open Resolution: None >Priority: 8 Submitted By: Greg Lindahl (greglindahl) Assigned to: Nobody/Anonymous (nobody) Summary: qrunner hung by spam Initial Comment: I realized no mail had gone out for 6 days, and saw that qrunner was barfing on SOMETHING. This is with Mailman 2.0.6. Even though I'm behind the times, I'd bet this bug could be in 2.1.X -- I just don't know enough Python to see what's going on. I blew away a bunch of files in my qfiles directory; I didn't save the bad message. Apr 24 00:39:01 2003 qrunner(2397): Traceback (innermost last): Apr 24 00:39:01 2003 qrunner(2397): File "/home/mailman/cron/qrunner", line 282, in ? Apr 24 00:39:01 2003 qrunner(2397): kids = main(lock) Apr 24 00:39:01 2003 qrunner(2397): File "/home/mailman/cron/qrunner", line 252, in main Apr 24 00:39:01 2003 qrunner(2397): keepqueued = dispose_message(mlist, msg, msgdata) Apr 24 00:39:01 2003 qrunner(2397): File "/home/mailman/cron/qrunner", line 121, in dispose_message Apr 24 00:39:01 2003 qrunner(2397): if BouncerAPI.ScanMessages(mlist, mimemsg): Apr 24 00:39:01 2003 qrunner(2397): File "/home/mailman/Mailman/Bouncers/BouncerAPI.py", line 59, in ScanMessages Apr 24 00:39:01 2003 qrunner(2397): addrs = func(msg) Apr 24 00:39:01 2003 qrunner(2397): File "/home/mailman/Mailman/Bouncers/Postfix.py", line 39, in process Apr 24 00:39:01 2003 qrunner(2397): more = mfile.next() Apr 24 00:39:01 2003 qrunner(2397): File "/usr/lib/python1.5/multifile.py", line 121, in next Apr 24 00:39:01 2003 qrunner(2397): while self.readline(): pass Apr 24 00:39:01 2003 qrunner(2397): File "/usr/lib/python1.5/multifile.py", line 93, in readline Apr 24 00:39:01 2003 qrunner(2397): if marker == self.section_divider(sep): Apr 24 00:39:01 2003 qrunner(2397): File "/usr/lib/python1.5/multifile.py", line 157, in section_divider Apr 24 00:39:01 2003 qrunner(2397): return "--" + str Apr 24 00:39:01 2003 qrunner(2397): TypeError : illegal argument type for built-in operation ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=726736&group_id=103 From noreply at sourceforge.net Thu Apr 24 09:08:43 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Apr 24 11:08:55 2003 Subject: [ mailman-Bugs-723123 ] Runs out of memory on larger (5M) messages. Message-ID: Bugs item #723123, was opened at 2003-04-17 06:20 Message generated for change (Comment added) made by xerouz You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=723123&group_id=103 Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 9 Submitted By: Steve Mertz (xerouz) Assigned to: Nobody/Anonymous (nobody) Summary: Runs out of memory on larger (5M) messages. Initial Comment: When trying to send an email with a 5M attachment, Mailman seems to run out of memory. On the console I get: marcos:mailman {106} 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 59, in run filecnt = self._oneloop() File "/usr/local/mailman/Mailman/Queue/Runner.py", line 111, in _oneloop self._shunt.enqueue(msg, msgdata) File "/usr/local/mailman/Mailman/Queue/Switchboard.py", line 91, in enqueue msgsave = cPickle.dumps(_msg, 1) MemoryError: out of memory The system is: OpenBSD 3.1, with 512M ram. Mailman version 2.1.1 It would be nice to be able to have large attachments as I want to use this for my company's support email which quite often has larger than 10M files attached. Thanks, -- Steve ---------------------------------------------------------------------- >Comment By: Steve Mertz (xerouz) Date: 2003-04-24 08:08 Message: Logged In: YES user_id=61424 Now, I'm getting errors in of a different kind: Apr 24 10:03:18 2003 (22458) Uncaught runner exception: out of memory Apr 24 10:03:18 2003 (22458) Traceback (most recent call last): File "/usr/local/mailman/Mailman/Queue/Runner.py", line 105, in _oneloop self._onefile(msg, msgdata) File "/usr/local/mailman/Mailman/Queue/Runner.py", line 155, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/local/mailman/Mailman/Queue/IncomingRunner.py", line 130, in _dispose more = self._dopipeline(mlist, msg, msgdata, pipeline) File "/usr/local/mailman/Mailman/Queue/IncomingRunner.py", line 153, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File "/usr/local/mailman/Mailman/Handlers/ToDigest.py", line 71, in process g.flatten(msg, unixfrom=1) File "/usr/local/mailman/pythonlib/email/Generator.py", line 100, in flatten self._write(msg) File "/usr/local/mailman/pythonlib/email/Generator.py", line 128, in _write self._dispatch(msg) File "/usr/local/mailman/pythonlib/email/Generator.py", line 154, in _dispatch meth(msg) File "/usr/local/mailman/pythonlib/email/Generator.py", line 267, in _handle_multipart print >> self._fp, '\n--' + boundary + '--', MemoryError: out of memory Apr 24 10:03:18 2003 (22458) SHUNTING: 1051196594.0123+3c7e0d1a0cd1e29359dea6cc2bb51307e06ad0df ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=723123&group_id=103 From noreply at sourceforge.net Thu Apr 24 12:03:27 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Apr 24 14:03:32 2003 Subject: [ mailman-Bugs-717110 ] mail commands Message-ID: Bugs item #717110, was opened at 2003-04-07 16:23 Message generated for change (Comment added) made by wyardley You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=717110&group_id=103 Category: Web/CGI Group: 2.1 (stable) Status: Closed Resolution: Invalid Priority: 5 Submitted By: Will Yardley (wyardley) Assigned to: Nobody/Anonymous (nobody) Summary: mail commands Initial Comment: when approving a message via email, if you type: Approved: passwrd in the headers of a response to the confirmation message, when the actual password is 'password', the message you're trying to approve is discarded; I think that no action (and an "incorrect password" error message in response) would be more appropriate. Also, as I've mentioned before, it would be very nice if the exact action being performed were listed, rather than the generic "confirmation succeeded" message. ---------------------------------------------------------------------- >Comment By: Will Yardley (wyardley) Date: 2003-04-24 11:03 Message: Logged In: YES user_id=751970 Perhaps I'm misreading the message? The message I see says: "If you reply to this message, keeping the Subject: header intact, Mailman will discard the held message. Do this if the message is spam. If you reply to this message and include an Approved: header with the list password in it, the message will be approved for posting to the list. The Approved: header can also appear in the first line of the body of the reply." This seems to say that the *confirmation* message, not the original message should have the 'Approved:' header. Am I reading something wrong here? ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-04-19 12:27 Message: Logged In: YES user_id=12800 After re-reading this bug report, I believe Mailman is working as expected. If you read the body of the confirmation message, you'll see that replying to it keeping the subject intact always discards the original message. The way to approve it is to resend the first message in the digest, which is the original held message. Add Approved: password header to the resend, and then reply to the confirmation message to get rid of the old hold. I admit this isn't the most convenient way to do it, but for now that's it. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=717110&group_id=103 From noreply at sourceforge.net Thu Apr 24 12:03:43 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Apr 24 14:03:48 2003 Subject: [ mailman-Bugs-717110 ] mail commands Message-ID: Bugs item #717110, was opened at 2003-04-07 16:23 Message generated for change (Comment added) made by wyardley You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=717110&group_id=103 Category: Web/CGI Group: 2.1 (stable) Status: Closed Resolution: Invalid Priority: 5 Submitted By: Will Yardley (wyardley) Assigned to: Nobody/Anonymous (nobody) Summary: mail commands Initial Comment: when approving a message via email, if you type: Approved: passwrd in the headers of a response to the confirmation message, when the actual password is 'password', the message you're trying to approve is discarded; I think that no action (and an "incorrect password" error message in response) would be more appropriate. Also, as I've mentioned before, it would be very nice if the exact action being performed were listed, rather than the generic "confirmation succeeded" message. ---------------------------------------------------------------------- >Comment By: Will Yardley (wyardley) Date: 2003-04-24 11:03 Message: Logged In: YES user_id=751970 Perhaps I'm misreading the message? The message I see says: "If you reply to this message, keeping the Subject: header intact, Mailman will discard the held message. Do this if the message is spam. If you reply to this message and include an Approved: header with the list password in it, the message will be approved for posting to the list. The Approved: header can also appear in the first line of the body of the reply." This seems to say that the *confirmation* message, not the original message should have the 'Approved:' header. Am I reading something wrong here? ---------------------------------------------------------------------- Comment By: Will Yardley (wyardley) Date: 2003-04-24 11:03 Message: Logged In: YES user_id=751970 Perhaps I'm misreading the message? The message I see says: "If you reply to this message, keeping the Subject: header intact, Mailman will discard the held message. Do this if the message is spam. If you reply to this message and include an Approved: header with the list password in it, the message will be approved for posting to the list. The Approved: header can also appear in the first line of the body of the reply." This seems to say that the *confirmation* message, not the original message should have the 'Approved:' header. Am I reading something wrong here? ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-04-19 12:27 Message: Logged In: YES user_id=12800 After re-reading this bug report, I believe Mailman is working as expected. If you read the body of the confirmation message, you'll see that replying to it keeping the subject intact always discards the original message. The way to approve it is to resend the first message in the digest, which is the original held message. Add Approved: password header to the resend, and then reply to the confirmation message to get rid of the old hold. I admit this isn't the most convenient way to do it, but for now that's it. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=717110&group_id=103 From noreply at sourceforge.net Thu Apr 24 12:16:01 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Apr 24 14:16:05 2003 Subject: [ mailman-Bugs-717110 ] mail commands Message-ID: Bugs item #717110, was opened at 2003-04-07 19:23 Message generated for change (Comment added) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=717110&group_id=103 Category: Web/CGI Group: 2.1 (stable) >Status: Open Resolution: Invalid Priority: 5 Submitted By: Will Yardley (wyardley) Assigned to: Nobody/Anonymous (nobody) Summary: mail commands Initial Comment: when approving a message via email, if you type: Approved: passwrd in the headers of a response to the confirmation message, when the actual password is 'password', the message you're trying to approve is discarded; I think that no action (and an "incorrect password" error message in response) would be more appropriate. Also, as I've mentioned before, it would be very nice if the exact action being performed were listed, rather than the generic "confirmation succeeded" message. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-04-24 14:16 Message: Logged In: YES user_id=12800 Ah, you're right. Re-opening. Either the message in the confirmation is broken, or the email cmd handler is broken. I won't decide that yet. :) ---------------------------------------------------------------------- Comment By: Will Yardley (wyardley) Date: 2003-04-24 14:03 Message: Logged In: YES user_id=751970 Perhaps I'm misreading the message? The message I see says: "If you reply to this message, keeping the Subject: header intact, Mailman will discard the held message. Do this if the message is spam. If you reply to this message and include an Approved: header with the list password in it, the message will be approved for posting to the list. The Approved: header can also appear in the first line of the body of the reply." This seems to say that the *confirmation* message, not the original message should have the 'Approved:' header. Am I reading something wrong here? ---------------------------------------------------------------------- Comment By: Will Yardley (wyardley) Date: 2003-04-24 14:03 Message: Logged In: YES user_id=751970 Perhaps I'm misreading the message? The message I see says: "If you reply to this message, keeping the Subject: header intact, Mailman will discard the held message. Do this if the message is spam. If you reply to this message and include an Approved: header with the list password in it, the message will be approved for posting to the list. The Approved: header can also appear in the first line of the body of the reply." This seems to say that the *confirmation* message, not the original message should have the 'Approved:' header. Am I reading something wrong here? ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-04-19 15:27 Message: Logged In: YES user_id=12800 After re-reading this bug report, I believe Mailman is working as expected. If you read the body of the confirmation message, you'll see that replying to it keeping the subject intact always discards the original message. The way to approve it is to resend the first message in the digest, which is the original held message. Add Approved: password header to the resend, and then reply to the confirmation message to get rid of the old hold. I admit this isn't the most convenient way to do it, but for now that's it. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=717110&group_id=103 From noreply at sourceforge.net Thu Apr 24 12:22:53 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Apr 24 14:23:05 2003 Subject: [ mailman-Bugs-717110 ] mail commands Message-ID: Bugs item #717110, was opened at 2003-04-07 16:23 Message generated for change (Comment added) made by wyardley You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=717110&group_id=103 Category: Web/CGI Group: 2.1 (stable) Status: Open Resolution: Invalid Priority: 5 Submitted By: Will Yardley (wyardley) Assigned to: Nobody/Anonymous (nobody) Summary: mail commands Initial Comment: when approving a message via email, if you type: Approved: passwrd in the headers of a response to the confirmation message, when the actual password is 'password', the message you're trying to approve is discarded; I think that no action (and an "incorrect password" error message in response) would be more appropriate. Also, as I've mentioned before, it would be very nice if the exact action being performed were listed, rather than the generic "confirmation succeeded" message. ---------------------------------------------------------------------- >Comment By: Will Yardley (wyardley) Date: 2003-04-24 11:22 Message: Logged In: YES user_id=751970 FWIW, in my experience, responding to the confirmation message itself with the proper Approved header works just fine. It's only when the password is incorrect that the message is deleted. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-04-24 11:16 Message: Logged In: YES user_id=12800 Ah, you're right. Re-opening. Either the message in the confirmation is broken, or the email cmd handler is broken. I won't decide that yet. :) ---------------------------------------------------------------------- Comment By: Will Yardley (wyardley) Date: 2003-04-24 11:03 Message: Logged In: YES user_id=751970 Perhaps I'm misreading the message? The message I see says: "If you reply to this message, keeping the Subject: header intact, Mailman will discard the held message. Do this if the message is spam. If you reply to this message and include an Approved: header with the list password in it, the message will be approved for posting to the list. The Approved: header can also appear in the first line of the body of the reply." This seems to say that the *confirmation* message, not the original message should have the 'Approved:' header. Am I reading something wrong here? ---------------------------------------------------------------------- Comment By: Will Yardley (wyardley) Date: 2003-04-24 11:03 Message: Logged In: YES user_id=751970 Perhaps I'm misreading the message? The message I see says: "If you reply to this message, keeping the Subject: header intact, Mailman will discard the held message. Do this if the message is spam. If you reply to this message and include an Approved: header with the list password in it, the message will be approved for posting to the list. The Approved: header can also appear in the first line of the body of the reply." This seems to say that the *confirmation* message, not the original message should have the 'Approved:' header. Am I reading something wrong here? ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-04-19 12:27 Message: Logged In: YES user_id=12800 After re-reading this bug report, I believe Mailman is working as expected. If you read the body of the confirmation message, you'll see that replying to it keeping the subject intact always discards the original message. The way to approve it is to resend the first message in the digest, which is the original held message. Add Approved: password header to the resend, and then reply to the confirmation message to get rid of the old hold. I admit this isn't the most convenient way to do it, but for now that's it. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=717110&group_id=103 From noreply at sourceforge.net Sat Apr 26 12:03:21 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sat Apr 26 14:03:25 2003 Subject: [ mailman-Bugs-728122 ] Unsub instructions difficult to find Message-ID: Bugs item #728122, was opened at 2003-04-26 18: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=728122&group_id=103 Category: (un)subscribing Group: None Status: Open Resolution: None Priority: 5 Submitted By: Anthony E. Greene (tonygreene) Assigned to: Nobody/Anonymous (nobody) Summary: Unsub instructions difficult to find Initial Comment: The default Mailman info page for the list could stand some improvements. I've noticed it over and over and finally decided to contribute to a solution instead of griping about the problem. ;-) I recommend these two changes: 1. Move the administrative "$listname Subscribers" section to the bottom of the page. Admins will know where to look and subscribers should not have to read through admin info to get to the section that concerns them (changing subscription options). 2. Add a standard colored section header titled "Change Options or Unsubscribe". The original format for this section did not clearly indicate that this is the section for unsubscribing. Users have to read the fine print. Reading the fine print is fine for detailed instructions, but the users should have some idea that the unsub instructions are there just by looking at the section header. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=728122&group_id=103 From noreply at sourceforge.net Mon Apr 28 05:01:56 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Apr 28 07:04:36 2003 Subject: [ mailman-Bugs-728836 ] invalid HTML in page templates Message-ID: Bugs item #728836, was opened at 2003-04-28 11:01 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=728836&group_id=103 Category: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Richard Barrett (ppsys) Assigned to: Nobody/Anonymous (nobody) Summary: invalid HTML in page templates Initial Comment: Some page templates in the 2.1.2 release are defective, i.e. the HTML is invalid A patch file to correct these errors is attached. It corrects problems with languages pl and pt which were newly added with MM 2.1.2: admindetails.html - removed extraneous P tags from inside UL The same errors in other language templates were corrected when patch 716755/661138 was merged into the MM 2.1.2 release. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=728836&group_id=103 From noreply at sourceforge.net Mon Apr 28 05:25:06 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Apr 28 07:25:14 2003 Subject: [ mailman-Bugs-728847 ] 2.1.2 Messages.Py Message-ID: Bugs item #728847, was opened at 2003-04-28 19:25 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=728847&group_id=103 Category: command line scripts Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: David English (engush) Assigned to: Nobody/Anonymous (nobody) Summary: 2.1.2 Messages.Py Initial Comment: Fix: Edit line 205 of Messages.py add ) and remove line 206 "errors='replace')" otherwise the following error occurs when creating a new list: lostris:/usr/local/mailman/bin# ./newlist test Enter the email of the person running the list: blah@blah.org Initial test password: To finish creating your mailing list, you must edit your /etc/aliases (or equivalent) file by adding the following lines, and possibly running the `newaliases' program: ## test mailing list test: "|/usr/local/mailman/mail/mailman post test" test-admin: "|/usr/local/mailman/mail/mailman admin test" test-bounces: "|/usr/local/mailman/mail/mailman bounces test" test-confirm: "|/usr/local/mailman/mail/mailman confirm test" test-join: "|/usr/local/mailman/mail/mailman join test" test-leave: "|/usr/local/mailman/mail/mailman leave test" test-owner: "|/usr/local/mailman/mail/mailman owner test" test-request: "|/usr/local/mailman/mail/mailman request test" test-subscribe: "|/usr/local/mailman/mail/mailman subscribe test" test-unsubscribe: "|/usr/local/mailman/mail/mailman unsubscribe test" Hit enter to notify test owner... Traceback (most recent call last): File "./newlist", line 219, in ? main() File "./newlist", line 211, in main text, mlist.preferred_language) File "/usr/local/mailman/Mailman/Message.py", line 206, in __init__ errors='replace') TypeError: __init__() got an unexpected keyword argument 'errors' lostris:/usr/local/mailman/bin# ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=728847&group_id=103 From noreply at sourceforge.net Mon Apr 28 08:31:24 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Apr 28 10:31:27 2003 Subject: [ mailman-Patches-644810 ] Sendmail mailer in Python Message-ID: Patches item #644810, was opened at 2002-11-27 16:27 Message generated for change (Comment added) made by ppsys You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=644810&group_id=103 Category: mail delivery Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Richard Barrett (ppsys) Assigned to: Nobody/Anonymous (nobody) Summary: Sendmail mailer in Python Initial Comment: This patch provide a Python implementation (with C wrapper) of a Sendmail mailer, if Sendmail is your MTA of choice, which removes the necessity of maintining an aliases database on your Mailman server. All subject to a bunch of conditions most prominent of which is that the server has to be pretty much dedicated to MM. This patch draws on an original contribution by David Champion which is included in the contrib directory of the Mailman 2.1b distribution as mm-handler. See the README.SENDMAIL.mailer installed by this patch for differences between this and David's Perl original and more information of what you are getting into if you use this patch. Versions of the patch for MM 2.0.13 and MM 2.1b5 are available. This patch requires patch 644797 to be installed before it. In the MM build directory say: patch -p1 < patch-filename ---------------------------------------------------------------------- >Comment By: Richard Barrett (ppsys) Date: 2003-04-28 14:31 Message: Logged In: YES user_id=75166 mailer-2.1.2-0.1.patch.gz removes support for MM 2.0.13 mail aliases from the mailer and is MM 2.1.2 compatible ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-02-10 11:50 Message: Logged In: YES user_id=75166 mailer-2.1-0.3.patch is also applicable to MM release 2.1.1 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-01-16 15:30 Message: Logged In: YES user_id=75166 mailer-2.1-0.3.patch and mailer-2.0.13-0.4.patch have VERP handling added and a new feature to rejct delivery of mail to existing lists by adding the lists names to a SUSPENDED_LISTS dictionary variable defined in mm_cfg.py. This is equivalent to deleting list aliases from the aliases file, while leaving the list itself in place, in a conventional sendmail configuration. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-01-03 18:19 Message: Logged In: YES user_id=75166 the mm_mailer script in mailer-2.1-0.2.patch now handles VERP'ed return addresses in bounced mail which I missed in the original implementation ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-01-02 16:34 Message: Logged In: YES user_id=75166 mailer-2.1-0.1.patch is a revision of the patch for MM 2.1 compatibility ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-12-11 12:16 Message: Logged In: YES user_id=75166 mailer-2.1b6-0.1.patch is MM 2.1b6 compatible. It also folds the case of listname and servername for compaiblity with MMs naive belief that listnames are case all lower case. case "(Email addresses are not case sensitive, but they are sensitive to almost everything else :-)" ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-12-03 17:37 Message: Logged In: YES user_id=75166 Fix for permissions related exceptions being generated by the subprocess spawned by mm_mailer script ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-12-03 17:36 Message: Logged In: YES user_id=75166 Fix for permissions related exceptions being generated by the subprocess spawned by mm_mailer script. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-11-27 16:29 Message: Logged In: YES user_id=75166 version for MM 2.1b5 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=644810&group_id=103 From noreply at sourceforge.net Mon Apr 28 08:34:54 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Apr 28 10:35:01 2003 Subject: [ mailman-Patches-444879 ] Archive indexer control to improve index Message-ID: Patches item #444879, was opened at 2001-07-26 18:01 Message generated for change (Comment added) made by ppsys You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=444879&group_id=103 Category: Pipermail Group: Mailman 2.2 / 3.0 Status: Open Resolution: None Priority: 3 Submitted By: Richard Barrett (ppsys) Assigned to: Barry A. Warsaw (bwarsaw) Summary: Archive indexer control to improve index Initial Comment: This patch is applicable to Mailman 2.0.6 release and supercedes ealier patches 401669 and 402422. This patch should improve the quality of search results returned by search engines such as htdig (http://www.htdig.org) where the seach engine's index builder responds to strings embedded in the html pages that are the subject of the indexing. The changes in this patch: 1. allow strings for enabling and disabling indexing to be defined in mm_cfg.py. 2. embeds those strings in the pages generated as the html version of a list's archive. By default nothing in the html changes. To get the desired effect, you must define ARCHIVE_INDEXING_ENABLE and ARCHIVE_INDEXING_DISABLE in mm_cfg.py You probably want to run this patch as follows: cd patch -p1 < See also the associated patch for integrating the htdig search software with mailman's internal archiver ouput. ---------------------------------------------------------------------- >Comment By: Richard Barrett (ppsys) Date: 2003-04-28 14:34 Message: Logged In: YES user_id=75166 indexing-2.1.2-0.1.patch.gz is revised for MM 2.1.2 compatibility. Before applying thisversion of the patch you must also apply Bug fix patch #728836 to the source distribution ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-02-10 15:49 Message: Logged In: YES user_id=75166 indexing-2.1.1-0.1.patch.gz introduces no functional change but applies without offset warnings to MM 2.1.1 Before applying this patch to the MM 2.1 source distribution you must apply patch 661138 (corrects defects in some HTML templates) to the distribution ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-01-02 16:05 Message: Logged In: YES user_id=75166 indexing-2.1-0.1.patch is a revised version of the patch that is compatible with MM 2.1. Before applying this patch to the MM 2.1 source distribution you must apply patch 661138 (corrects defects in some HTML templates) to the distribution ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-12-11 11:55 Message: Logged In: YES user_id=75166 indexing-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-11 11:53 Message: Logged In: YES user_id=75166 indexing-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-11 11:52 Message: Logged In: YES user_id=75166 indexing-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-11-27 10:22 Message: Logged In: YES user_id=75166 indexing-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:40 Message: Logged In: YES user_id=75166 indexing-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-30 11:39 Message: Logged In: YES user_id=75166 indexing-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-08-14 16:46 Message: Logged In: YES user_id=75166 indexing-2.1b3-0.1.patch is a revised version of the patch that is compatible with MM 2.1b3 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-08-08 17:32 Message: Logged In: YES user_id=75166 An additional file, README.NOINDEXtags is added to indexing-2.0.13-0.3.patch version that discusses the issue of what tags to use for controlling various search engine indexers. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-08-08 17:19 Message: Logged In: YES user_id=75166 An error when building the indexing-2.1b2-0.1.patch meant that copies of the originals of two of the files modified by this version of the patch were added when the patch was run. indexing-2.1b2-0.1.patch removes this error. However, the original error is benign and can be corrected by deleting the extra files HyperArch.py.orig and Defaults.py.in.orig. An additional file, README.NOINDEXtags is added that discusses the issue of what tags to use for controlling various search engine indexers. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-08-08 14:19 Message: Logged In: YES user_id=12800 Another question: is there no standard (de-facto or otherwise) for generic markup that tells indexers not to index a particular section? IOW, for ARCHIVE_INDEXING_ENABLE and ARCHIVE_INDEXING_DISABLE, is there some generic value that would instruct most (all?) indexers to ignore that section? Or does it necessarily have to be indexer specific? I'm thinking of the situation where you might have ht://Dig installed locally, but your archives are still being spidered by external indexers. It would be good if something more generic could be added to Defaults.py.in ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-08-08 14:14 Message: Logged In: YES user_id=12800 Looking at the 2.1b2 patch, why does it try to create HyperArch.py.orig and Defaults.py.in.orig? Are those included in the patch by mistake? ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-08-05 10:08 Message: Logged In: YES user_id=75166 indexing-2.0.13-0.2.patch just adds a GPL notice to the patch ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-08-01 16:33 Message: Logged In: YES user_id=75166 indexing-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:23 Message: Logged In: YES user_id=75166 indexing-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 14:11 Message: Logged In: YES user_id=75166 indexing-2.0.11-0.1.patch should apply without problems to MM 2.0.12 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-05-23 09:50 Message: Logged In: YES user_id=75166 indexing-2.0.11-0.1.patch is a revised version of the patch that is compatible with MM 2.0.11 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-04-19 10:53 Message: Logged In: YES user_id=75166 indexing-2.0.9-0.1.patch should apply without problems to MM 2.0.10 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-04-08 17:43 Message: Logged In: YES user_id=75166 indexing-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:14 Message: Logged In: YES user_id=75166 indexing-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. Corrects problem noted or 5 Mar 2002 by nobody ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2002-03-05 21:41 Message: Logged In: NO When applying this patch I get an error with Hunk 1 and Defaults.py is not updated. This happens with the a clean download of the latest cvs installation (5 Mar 2002). Any ideas what the problem is? ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2001-12-17 16:53 Message: Logged In: YES user_id=75166 indexing-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 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2001-12-13 16:48 Message: Logged In: YES user_id=75166 indexing-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. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2001-11-28 11:07 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:03 Message: Logged In: YES user_id=75166 This patch should also apply without problems to MM 2.0.7 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=444879&group_id=103 From noreply at sourceforge.net Mon Apr 28 08:40:40 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Apr 28 10:40:46 2003 Subject: [ mailman-Patches-644797 ] Revised mailer exit status Message-ID: Patches item #644797, was opened at 2002-11-27 15:56 Message generated for change (Comment added) made by ppsys You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=644797&group_id=103 Category: mail delivery Group: Mailman 2.2 / 3.0 Status: Open Resolution: None Priority: 5 Submitted By: Richard Barrett (ppsys) Assigned to: Nobody/Anonymous (nobody) Summary: Revised mailer exit status Initial Comment: This patch modifies the Python scripts in $prefix/scripts/ that are used by the MTA to deliver incoming mail to Mailman. The exit statuses now returned are drawn from the mail related values defined in /usr/include/sysexits.h This allows the MTA to return more meaningful responses to the sender when rejecting mail. It also allows a more sympathetic treatment of mail in the event that the Python script suffers an unexpected exception when handling incoming email. Such exceptions are now logged to MM's $prefix/logs/erro in all but the most extreme error cases and the internal information about the Python exception is not passed into the response to the sender. There are two patch versions; one for MM 2.0.13 and the other for MM 2.1b5 in the MM build directory say: patch -p1 < patch-filename ---------------------------------------------------------------------- >Comment By: Richard Barrett (ppsys) Date: 2003-04-28 14:40 Message: Logged In: YES user_id=75166 exitstatus-2.1.2-0.1.patch is a revision of the patch for MM 2.1.2 compatibility ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-02-10 11:42 Message: Logged In: YES user_id=75166 exitstatus-2.1-0.1.patch is alos applicable to MM release 2.1.1 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-01-02 16:30 Message: Logged In: YES user_id=75166 exitstatus-2.1-0.1.patch is a revision of the patch for MM 2.1 compatibility ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-12-24 03:29 Message: Logged In: YES user_id=12800 Sorry Richard, I have to defer this one. It's too much for me to think about for MM2.1. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-12-11 11:58 Message: Logged In: YES user_id=75166 exitstatus-2.1b6-0.1.patch is a revision of the patch for MM 2.1b6 compatibility ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-11-27 15:58 Message: Logged In: YES user_id=75166 version for MM 2.1b5 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=644797&group_id=103 From noreply at sourceforge.net Mon Apr 28 08:46:20 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Apr 28 10:46:51 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-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 Mon Apr 28 08:37:43 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Apr 28 11:12:38 2003 Subject: [ mailman-Patches-444879 ] Archive indexer control to improve index Message-ID: Patches item #444879, was opened at 2001-07-26 18:01 Message generated for change (Comment added) made by ppsys You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=444879&group_id=103 Category: Pipermail Group: Mailman 2.2 / 3.0 Status: Open Resolution: None Priority: 3 Submitted By: Richard Barrett (ppsys) Assigned to: Barry A. Warsaw (bwarsaw) Summary: Archive indexer control to improve index Initial Comment: This patch is applicable to Mailman 2.0.6 release and supercedes ealier patches 401669 and 402422. This patch should improve the quality of search results returned by search engines such as htdig (http://www.htdig.org) where the seach engine's index builder responds to strings embedded in the html pages that are the subject of the indexing. The changes in this patch: 1. allow strings for enabling and disabling indexing to be defined in mm_cfg.py. 2. embeds those strings in the pages generated as the html version of a list's archive. By default nothing in the html changes. To get the desired effect, you must define ARCHIVE_INDEXING_ENABLE and ARCHIVE_INDEXING_DISABLE in mm_cfg.py You probably want to run this patch as follows: cd patch -p1 < See also the associated patch for integrating the htdig search software with mailman's internal archiver ouput. ---------------------------------------------------------------------- >Comment By: Richard Barrett (ppsys) Date: 2003-04-28 14:37 Message: Logged In: YES user_id=75166 indexing-2.1.2-0.1.patch.gz no longer needs patch #661138 to be applied as that patch was incorporated in the MM 2.1.2 release ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-04-28 14:34 Message: Logged In: YES user_id=75166 indexing-2.1.2-0.1.patch.gz is revised for MM 2.1.2 compatibility. Before applying thisversion of the patch you must also apply Bug fix patch #728836 to the source distribution ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-02-10 15:49 Message: Logged In: YES user_id=75166 indexing-2.1.1-0.1.patch.gz introduces no functional change but applies without offset warnings to MM 2.1.1 Before applying this patch to the MM 2.1 source distribution you must apply patch 661138 (corrects defects in some HTML templates) to the distribution ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-01-02 16:05 Message: Logged In: YES user_id=75166 indexing-2.1-0.1.patch is a revised version of the patch that is compatible with MM 2.1. Before applying this patch to the MM 2.1 source distribution you must apply patch 661138 (corrects defects in some HTML templates) to the distribution ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-12-11 11:55 Message: Logged In: YES user_id=75166 indexing-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-11 11:53 Message: Logged In: YES user_id=75166 indexing-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-11 11:52 Message: Logged In: YES user_id=75166 indexing-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-11-27 10:22 Message: Logged In: YES user_id=75166 indexing-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:40 Message: Logged In: YES user_id=75166 indexing-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-30 11:39 Message: Logged In: YES user_id=75166 indexing-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-08-14 16:46 Message: Logged In: YES user_id=75166 indexing-2.1b3-0.1.patch is a revised version of the patch that is compatible with MM 2.1b3 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-08-08 17:32 Message: Logged In: YES user_id=75166 An additional file, README.NOINDEXtags is added to indexing-2.0.13-0.3.patch version that discusses the issue of what tags to use for controlling various search engine indexers. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-08-08 17:19 Message: Logged In: YES user_id=75166 An error when building the indexing-2.1b2-0.1.patch meant that copies of the originals of two of the files modified by this version of the patch were added when the patch was run. indexing-2.1b2-0.1.patch removes this error. However, the original error is benign and can be corrected by deleting the extra files HyperArch.py.orig and Defaults.py.in.orig. An additional file, README.NOINDEXtags is added that discusses the issue of what tags to use for controlling various search engine indexers. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-08-08 14:19 Message: Logged In: YES user_id=12800 Another question: is there no standard (de-facto or otherwise) for generic markup that tells indexers not to index a particular section? IOW, for ARCHIVE_INDEXING_ENABLE and ARCHIVE_INDEXING_DISABLE, is there some generic value that would instruct most (all?) indexers to ignore that section? Or does it necessarily have to be indexer specific? I'm thinking of the situation where you might have ht://Dig installed locally, but your archives are still being spidered by external indexers. It would be good if something more generic could be added to Defaults.py.in ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-08-08 14:14 Message: Logged In: YES user_id=12800 Looking at the 2.1b2 patch, why does it try to create HyperArch.py.orig and Defaults.py.in.orig? Are those included in the patch by mistake? ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-08-05 10:08 Message: Logged In: YES user_id=75166 indexing-2.0.13-0.2.patch just adds a GPL notice to the patch ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-08-01 16:33 Message: Logged In: YES user_id=75166 indexing-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:23 Message: Logged In: YES user_id=75166 indexing-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 14:11 Message: Logged In: YES user_id=75166 indexing-2.0.11-0.1.patch should apply without problems to MM 2.0.12 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-05-23 09:50 Message: Logged In: YES user_id=75166 indexing-2.0.11-0.1.patch is a revised version of the patch that is compatible with MM 2.0.11 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-04-19 10:53 Message: Logged In: YES user_id=75166 indexing-2.0.9-0.1.patch should apply without problems to MM 2.0.10 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2002-04-08 17:43 Message: Logged In: YES user_id=75166 indexing-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:14 Message: Logged In: YES user_id=75166 indexing-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. Corrects problem noted or 5 Mar 2002 by nobody ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2002-03-05 21:41 Message: Logged In: NO When applying this patch I get an error with Hunk 1 and Defaults.py is not updated. This happens with the a clean download of the latest cvs installation (5 Mar 2002). Any ideas what the problem is? ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2001-12-17 16:53 Message: Logged In: YES user_id=75166 indexing-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 ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2001-12-13 16:48 Message: Logged In: YES user_id=75166 indexing-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. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2001-11-28 11:07 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:03 Message: Logged In: YES user_id=75166 This patch should also apply without problems to MM 2.0.7 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=444879&group_id=103 From noreply at sourceforge.net Mon Apr 28 09:44:31 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Apr 28 11:45:08 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-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 Wed Apr 30 14:06:44 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Apr 30 16:06:48 2003 Subject: [ mailman-Bugs-730405 ] NNTP -> Mail ignores filter_mime_types Message-ID: Bugs item #730405, was opened at 2003-04-30 22:06 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=730405&group_id=103 Category: nntp/news Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Matthias Andree (m-a) Assigned to: Nobody/Anonymous (nobody) Summary: NNTP -> Mail ignores filter_mime_types Initial Comment: I have configured filter_mime_types to include text/html, otherwise, I left the 2.1.2 defaults unchanged. When I send a mail with HTML and plain text (multipart/alternative) as mail to the list, the HTML part gets stripped out properly, leaving a text/plain mail behind. If I post a mixed HTML/plain mail to the newsgroup, the text/html part remains in the mail that gets forwarded into the list. I would like to have the text/html part removed also when the mail is pulled in via NNTP (seems I'll have to make the mail <-> news gateway one-way and only allow mail -> news, but not the other way around). I cannot provide a patch (unacquainted with both Python and Mailman code), but I will test patches sent my way or attached to this tracker item, time permitting (allow me some days for testing). Thanks in advance. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=730405&group_id=103