From noreply at sourceforge.net Wed Jan 1 06:02:07 2003 From: noreply at sourceforge.net (noreply@sourceforge.net) Date: Wed Jan 1 09:01:48 2003 Subject: [Mailman-Developers] [ mailman-Bugs-660675 ] special characters in realnames Message-ID: Bugs item #660675, was opened at 2003-01-01 15: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: Open Resolution: None Priority: 7 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 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=660675&group_id=103 From chuqui at plaidworks.com Wed Jan 1 08:50:09 2003 From: chuqui at plaidworks.com (Chuq Von Rospach) Date: Wed Jan 1 11:50:22 2003 Subject: [Mailman-Developers] 2.1 bug? Message-ID: <16C493BD-1DA9-11D7-954B-0003934516A8@plaidworks.com> I'm still running rc1, but.. Got this traceback in my mailbox this morning from the mailpasswd message. Does this also imply anyone beyond this didn't get a password mailed? Any chance of finding out what address caused this? Traceback (most recent call last): File "/usr/local/mailman/cron/mailpasswds", line 216, in ? main() File "/usr/local/mailman/cron/mailpasswds", line 200, in main text, poplang) File "/usr/local/mailman/Mailman/Message.py", line 203, in __init__ self['Subject'] = Header(subject, charset, header_name='Subject') File "/usr/local/mailman/pythonlib/email/Header.py", line 164, in __init__ self.append(s, charset) File "/usr/local/mailman/pythonlib/email/Header.py", line 230, in append ustr = unicode(s, incodec) LookupError: unknown encoding -- Chuq Von Rospach, Architech chuqui@plaidworks.com -- http://www.plaidworks.com/chuqui/blog/ Yes, I am an agent of Satan, but my duties are largely ceremonial. From sb.list at sb.org Wed Jan 1 12:12:12 2003 From: sb.list at sb.org (Stonewall Ballard) Date: Wed Jan 1 12:16:17 2003 Subject: [Mailman-Developers] email comparison bug? Message-ID: One of my users got two notices for her two lists at one domain, instead of one notice with two password/URLs. One of the lists has her address all lower case, and the other is capped like this: HerName@aol.com They're exactly the same otherwise. Is this a bug in 2.1's comparison function that it uses to group accounts for "global" operations and monthly notices? This is with 2.1 final. - Stoney -- Stonewall Ballard stoney@sb.org http://stoney.sb.org/ From noreply at sourceforge.net Wed Jan 1 09:29:36 2003 From: noreply at sourceforge.net (noreply@sourceforge.net) Date: Wed Jan 1 12:29:13 2003 Subject: [Mailman-Developers] [ mailman-Bugs-660733 ] bin/arch traceback Message-ID: Bugs item #660733, was opened at 2003-01-01 12:29 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=660733&group_id=103 Category: Pipermail Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Bryan Fullerton (fehwalker) Assigned to: Nobody/Anonymous (nobody) Summary: bin/arch traceback Initial Comment: I moved my first list to mailman 2.1 and tried to re-generate the pipermail archives (just, ya know, to see how it'd work :), and got the following traceback. This is a list that's been around for a long time (archives back to 1995), and the .mbox file was generated from a majordomo/hypermail archive when it was moved to mailman 2.0 a couple of years ago. Here's a ls -l of the .mbox file: -rw-rw-r-- 1 mailman mailman 17741891 Jan 1 10:36 bryans-list.mbox Here's the traceback: Updating HTML for article 467 Updating HTML for article 468 Updating HTML for article 469 Updating HTML for article 473 Updating HTML for article 472 Pickling archive state into /home/mailman-2.1/archives/private/bryans-list/pipermail.pck Traceback (most recent call last): File "bin/arch", line 187, in ? main() File "bin/arch", line 175, in main archiver.processUnixMailbox(fp, start, end) File "/home/mailman-2.1/Mailman/Archiver/pipermail.py", line 544, in processUnixMailbox m = mbox.next() File "/usr/local/lib/python2.2/mailbox.py", line 34, in next return self.factory(_Subfile(self.fp, start, stop)) File "/home/mailman-2.1/Mailman/Mailbox.py", line 79, in scrubber return mailbox.scrub(msg) File "/home/mailman-2.1/Mailman/Mailbox.py", line 99, in scrub return self._scrubber(self._mlist, msg) File "/home/mailman-2.1/Mailman/Handlers/Scrubber.py", line 132, in process dir = calculate_attachments_dir(mlist, msg, msgdata) File "/home/mailman-2.1/Mailman/Handlers/Scrubber.py", line 93, in calculate_attachments_dir datedir = safe_strftime(fmt, now) File "/home/mailman-2.1/Mailman/Handlers/Scrubber.py", line 77, in safe_strftime return time.strftime(fmt, floatsecs) TypeError: argument must be 9-item sequence, not None I'm guessing it's a header problem in one of the messages, but I'm not sure what. Thanks, Bryan ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=660733&group_id=103 From sb.list at sb.org Wed Jan 1 12:43:01 2003 From: sb.list at sb.org (Stonewall Ballard) Date: Wed Jan 1 12:46:17 2003 Subject: [Mailman-Developers] email comparison bug? In-Reply-To: Message-ID: I've also discovered that bin/find_member lists addresses as separate people, like this: Foo@aol.com found in: List 1 foo@aol.com found in: List 2 List 3 The user options page won't let me change to . It says "You are already using that email address". It seems that the desire to have case-preserving addresses conflicts with the basic identity of a subscriber, as determined by their case-insensitive address. - Stoney On 1/1/03 12:12 PM, "Stonewall Ballard" wrote: > One of my users got two notices for her two lists at one domain, instead of > one notice with two password/URLs. > > One of the lists has her address all lower case, and the other is capped > like this: HerName@aol.com > > They're exactly the same otherwise. Is this a bug in 2.1's comparison > function that it uses to group accounts for "global" operations and monthly > notices? > > This is with 2.1 final. > > - Stoney From jwblist at olympus.net Wed Jan 1 09:47:24 2003 From: jwblist at olympus.net (John W Baxter) Date: Wed Jan 1 12:47:44 2003 Subject: [Mailman-Developers] email comparison bug? In-Reply-To: References: Message-ID: At 12:12 -0500 1/1/2003, Stonewall Ballard wrote: >One of my users got two notices for her two lists at one domain, instead of >one notice with two password/URLs. > >One of the lists has her address all lower case, and the other is capped >like this: HerName@aol.com > >They're exactly the same otherwise. Is this a bug in 2.1's comparison >function that it uses to group accounts for "global" operations and monthly >notices? > >This is with 2.1 final. I don't know how Mailman can be expected to know which domains treat address local parts caselessly (hint: almost all) and which treat them casefully (hint: the RFCs still allow it). Since *can* be a different account than is , I think we're stuck, even though it almost never is. When there is a sitewide database of Mailman users...we'll STILL be stuck, I fear, although the GUI might allow a user to say the equivalent of "that's me, too." Exim, as one MTA by way of example, defaults to caseless operation although it carefully preserves the local part case. It can be configured (with one config file line) to consider local part case. I'm sure those code paths get less testing and exercising than the caseless ones do. --John -- John Baxter jwblist@olympus.net Port Ludlow, WA, USA From sb.list at sb.org Wed Jan 1 13:03:28 2003 From: sb.list at sb.org (Stonewall Ballard) Date: Wed Jan 1 13:06:17 2003 Subject: [Mailman-Developers] email comparison bug? In-Reply-To: Message-ID: On 1/1/03 12:47 PM, "John W Baxter" wrote: > I don't know how Mailman can be expected to know which domains treat > address local parts caselessly (hint: almost all) and which treat them > casefully (hint: the RFCs still allow it). > > Since *can* be a different account than is , I think > we're stuck, even though it almost never is. When there is a sitewide > database of Mailman users...we'll STILL be stuck, I fear, although the GUI > might allow a user to say the equivalent of "that's me, too." If Mailman wants to model identity (which it claims to do via the "global" checkbox), it need to do so correctly. That means comparing addresses caselessly unless explicitly told otherwise. If Mailman maintained a list of domains that had to be handled casefully, I imagine that it would be empty, but would handle the remote possibility that somewhere there was someone stupid enough to set up a mail system that cared about case. At the very least, it should let me change the case of an email address. It can't say both "these are different addresses" and "it's already that address". - Stoney From noreply at sourceforge.net Wed Jan 1 10:45:35 2003 From: noreply at sourceforge.net (noreply@sourceforge.net) Date: Wed Jan 1 13:45:16 2003 Subject: [Mailman-Developers] [ mailman-Bugs-660733 ] bin/arch traceback Message-ID: Bugs item #660733, was opened at 2003-01-01 12:29 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=660733&group_id=103 Category: Pipermail Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Bryan Fullerton (fehwalker) Assigned to: Nobody/Anonymous (nobody) Summary: bin/arch traceback Initial Comment: I moved my first list to mailman 2.1 and tried to re-generate the pipermail archives (just, ya know, to see how it'd work :), and got the following traceback. This is a list that's been around for a long time (archives back to 1995), and the .mbox file was generated from a majordomo/hypermail archive when it was moved to mailman 2.0 a couple of years ago. Here's a ls -l of the .mbox file: -rw-rw-r-- 1 mailman mailman 17741891 Jan 1 10:36 bryans-list.mbox Here's the traceback: Updating HTML for article 467 Updating HTML for article 468 Updating HTML for article 469 Updating HTML for article 473 Updating HTML for article 472 Pickling archive state into /home/mailman-2.1/archives/private/bryans-list/pipermail.pck Traceback (most recent call last): File "bin/arch", line 187, in ? main() File "bin/arch", line 175, in main archiver.processUnixMailbox(fp, start, end) File "/home/mailman-2.1/Mailman/Archiver/pipermail.py", line 544, in processUnixMailbox m = mbox.next() File "/usr/local/lib/python2.2/mailbox.py", line 34, in next return self.factory(_Subfile(self.fp, start, stop)) File "/home/mailman-2.1/Mailman/Mailbox.py", line 79, in scrubber return mailbox.scrub(msg) File "/home/mailman-2.1/Mailman/Mailbox.py", line 99, in scrub return self._scrubber(self._mlist, msg) File "/home/mailman-2.1/Mailman/Handlers/Scrubber.py", line 132, in process dir = calculate_attachments_dir(mlist, msg, msgdata) File "/home/mailman-2.1/Mailman/Handlers/Scrubber.py", line 93, in calculate_attachments_dir datedir = safe_strftime(fmt, now) File "/home/mailman-2.1/Mailman/Handlers/Scrubber.py", line 77, in safe_strftime return time.strftime(fmt, floatsecs) TypeError: argument must be 9-item sequence, not None I'm guessing it's a header problem in one of the messages, but I'm not sure what. Thanks, Bryan ---------------------------------------------------------------------- >Comment By: Bryan Fullerton (fehwalker) Date: 2003-01-01 13:45 Message: Logged In: YES user_id=660772 After some investigation, the following (admittedly invalid) date headers cause tracebacks similar to the above. After reformatting them I'm able to generate the archive. Date: 25 Aug 95 18.00 Date: Thursday, 30 October 1997 3:02pm PT Date: Mon, 29 Nov 1999 Pacific Standard Time Note that these messages *didn't* cause bin/arch|pipermail in mailman 2.0.x to fail, though it probably didn't parse them properly. Perhaps trapping the error and/or skipping these messages might be more useful? It also appears that bin/arch is throwing all messages with dates it can't figure out (after the above were removed) into the current day. An example can be seen at http://lists.samurai.com/pipermail/bryans-list/2003-January/thread.html . I'm unsure if there's any way to better handle this, but just wanted to note it - I can create a separate bug report if it's important. Thanks, Bryan ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=660733&group_id=103 From barry at python.org Wed Jan 1 20:38:15 2003 From: barry at python.org (Barry A. Warsaw) Date: Wed Jan 1 20:38:44 2003 Subject: [Mailman-Developers] 2.1 bug? References: <16C493BD-1DA9-11D7-954B-0003934516A8@plaidworks.com> Message-ID: <15891.38919.70324.489230@gargle.gargle.HOWL> >>>>> "CVR" == Chuq Von Rospach writes: CVR> I'm still running rc1, but.. CVR> Got this traceback in my mailbox this morning from the CVR> mailpasswd message. Does this also imply anyone beyond this CVR> didn't get a password mailed? I'm sure it does. CVR> Any chance of finding out what address caused this? I think this is caused by a weird language being used, one that has a charset for which we don't know the encoding. Do you have any non-English lists? If you decide to instrument mailpasswds to figure this out , I'd be interested to know what `poplang' is before the call to Message.UserNotification(), say just before line 197. Add something like: syslog('debug', 'poplang: %s', poplang) and tail the logs/debug file as you run cron/mailpasswds manually. -Barry From barry at python.org Wed Jan 1 20:40:09 2003 From: barry at python.org (Barry A. Warsaw) Date: Wed Jan 1 20:40:38 2003 Subject: [Mailman-Developers] email comparison bug? References: Message-ID: <15891.39033.652705.517967@gargle.gargle.HOWL> >>>>> "SB" == Stonewall Ballard writes: SB> One of my users got two notices for her two lists at one SB> domain, instead of one notice with two password/URLs. SB> One of the lists has her address all lower case, and the other SB> is capped like this: HerName@aol.com Were these lists that you upgraded, or were these new-to-MM2.1 lists? If you upgraded them, what did you upgrade them from? SB> They're exactly the same otherwise. Is this a bug in 2.1's SB> comparison function that it uses to group accounts for SB> "global" operations and monthly notices? It's a bug that you could subscribe both addresses to your list. They are supposed to be the same member record, which is case insensitive. I'm really interested in how you got both addresses subscribed. Check logs/subscribe if you're not sure. -Barry From barry at python.org Wed Jan 1 20:47:01 2003 From: barry at python.org (Barry A. Warsaw) Date: Wed Jan 1 20:47:30 2003 Subject: [Mailman-Developers] email comparison bug? References: Message-ID: <15891.39445.507181.514568@gargle.gargle.HOWL> >>>>> "SB" == Stonewall Ballard writes: SB> One of my users got two notices for her two lists at one SB> domain, instead of one notice with two password/URLs. SB> One of the lists has her address all lower case, and the other SB> is capped like this: HerName@aol.com SB> They're exactly the same otherwise. Is this a bug in 2.1's SB> comparison function that it uses to group accounts for SB> "global" operations and monthly notices? SB> This is with 2.1 final. Ah, I re-read this, and tested it with two lists. Yes, it's definitely a bug with the monthly notices (it should group them case insensitively). I'll try to fix that, and also check the global operations. -Barry From barry at python.org Wed Jan 1 20:49:44 2003 From: barry at python.org (Barry A. Warsaw) Date: Wed Jan 1 20:50:15 2003 Subject: [Mailman-Developers] email comparison bug? References: Message-ID: <15891.39608.6563.638323@gargle.gargle.HOWL> >>>>> "SB" == Stonewall Ballard writes: SB> One of the lists has her address all lower case, and the other SB> is capped like this: HerName@aol.com Sorry for the frenetic responses... Here's the comment in mailpasswds: # BAW: we group by cpaddress because although it's highly # likely, there's no guarantee that person@list1 is the same # as PERSON@list2. Sigh. `cpaddress' being the case-preserved (i.e. subscribed) address. I think this comment is wrong because it's not list1 and list2 we care about, it's person@example.com vs. PERSON@example.com, and everywhere else in Mailman we equate these two addresses, so we should do the same in mailpasswds. -Barry From chuqui at plaidworks.com Wed Jan 1 20:05:37 2003 From: chuqui at plaidworks.com (Chuq Von Rospach) Date: Wed Jan 1 23:05:54 2003 Subject: [Mailman-Developers] more on that password crash. Message-ID: <731FF698-1E07-11D7-954B-0003934516A8@plaidworks.com> I think I found it. Turns out a couple of things weren't compiling right on MacOS X (the japanese and chinese language additions). that turns out to be a minor bug in how MacOS X ships a python config file. More details here: (maybe this should get faqqed?) -- Chuq Von Rospach, Architech chuqui@plaidworks.com -- http://www.plaidworks.com/chuqui/blog/ No! No! Dead girl, OFF the table! -- Shrek From barry at python.org Wed Jan 1 23:24:29 2003 From: barry at python.org (Barry A. Warsaw) Date: Wed Jan 1 23:24:58 2003 Subject: [Mailman-Developers] email comparison bug? References: Message-ID: <15891.48893.86073.856287@gargle.gargle.HOWL> >>>>> "SB" == Stonewall Ballard writes: SB> I've also discovered that bin/find_member lists addresses as SB> separate people, like this: | Foo@aol.com found in: | List 1 | foo@aol.com found in: | List 2 | List 3 This one's documented to work this way: % bin/find_member -h ... Address matches are case-insensitive, but case-preserved addresses are displayed. -Barry From jon at csh.rit.edu Wed Jan 1 23:27:00 2003 From: jon at csh.rit.edu (Jon Parise) Date: Wed Jan 1 23:27:04 2003 Subject: [Mailman-Developers] Fwd: bin/rmlist too bold removing entries from postfix aliases file Message-ID: <20030102042700.GA124@csh.rit.edu> I just realized this conversation occured on the mailman-users list while it would be more appropriately discussed on the developers' list. -- Jon Parise (jon@csh.rit.edu) :: http://www.csh.rit.edu/~jon/ -------------- next part -------------- An embedded message was scrubbed... From: Jon Parise Subject: Re: [Mailman-Users] bin/rmlist too bold removing entries from postfix aliases file Date: Wed, 1 Jan 2003 21:43:58 -0500 Size: 5225 Url: http://mail.python.org/pipermail/mailman-developers/attachments/20030101/909a59a1/attachment.eml From barry at python.org Wed Jan 1 23:28:09 2003 From: barry at python.org (Barry A. Warsaw) Date: Wed Jan 1 23:28:36 2003 Subject: [Mailman-Developers] email comparison bug? References: Message-ID: <15891.49113.21565.766392@gargle.gargle.HOWL> >>>>> "JWB" == John W Baxter writes: JWB> Since *can* be a different account than is JWB> , I think we're stuck, even though it almost never JWB> is. When there is a sitewide database of Mailman JWB> users...we'll STILL be stuck, I fear, although the GUI might JWB> allow a user to say the equivalent of "that's me, too." Mailman's policy is that membership is by case-insensitive email address, and it preserves the case of the subscribed address only for the recipient address (either envelope or From:). When there's a unified user database (read: Mailman 3.0), an email address with any combination of case will still point to the same user record, but it may be possible for users to add delivery addresses with different cases. -Barry From barry at python.org Thu Jan 2 01:05:31 2003 From: barry at python.org (Barry A. Warsaw) Date: Thu Jan 2 01:06:07 2003 Subject: [Mailman-Developers] more on that password crash. References: <731FF698-1E07-11D7-954B-0003934516A8@plaidworks.com> Message-ID: <15891.54955.971767.338492@gargle.gargle.HOWL> >>>>> "CVR" == Chuq Von Rospach writes: CVR> I think I found it. Turns out a couple of things weren't CVR> compiling right on MacOS X (the japanese and chinese language CVR> additions). that turns out to be a minor bug in how MacOS X CVR> ships a python config file. CVR> More details here: CVR> CVR> (maybe this should get faqqed?) I posted a follow up in the forum linked off your blog. It looks liek a from-source build of Python 2.2.2 doesn't have this problem, so it's only Apple's Python distro that seems to be affected. I've no idea how that gets built, so the best I can guess is that it's an Apple goof-up. (Aside: Chuq, how can we better help Apple with their Python stuff?) Please do add a FAQwiz entry, and if you can write something up for README.MACOSX that'd be awesome. Actually, that file's a little lean anyway, so any info you'd like to add, please just send it my way. :) -Barry From barry at python.org Thu Jan 2 01:22:10 2003 From: barry at python.org (Barry A. Warsaw) Date: Thu Jan 2 01:22:41 2003 Subject: [Mailman-Developers] Fwd: bin/rmlist too bold removing entries from postfix aliases file References: <20030102042700.GA124@csh.rit.edu> Message-ID: <15891.55954.509267.507266@gargle.gargle.HOWL> >>>>> "JP" == Jon Parise writes: JP> I just realized this conversation occured on the mailman-users JP> list while it would be more appropriately discussed on the JP> developers' list. Jon, your patch was perfect. It's been applied. Thanks. -Barry From chuqui at plaidworks.com Wed Jan 1 22:24:02 2003 From: chuqui at plaidworks.com (Chuq Von Rospach) Date: Thu Jan 2 01:24:19 2003 Subject: [Mailman-Developers] more on that password crash. In-Reply-To: <15891.54955.971767.338492@gargle.gargle.HOWL> Message-ID: On Wednesday, January 1, 2003, at 10:05 PM, Barry A. Warsaw wrote: > I posted a follow up in the forum linked off your blog. It looks liek > a from-source build of Python 2.2.2 doesn't have this problem, so it's > only Apple's Python distro that seems to be affected. I've no idea > how that gets built, so the best I can guess is that it's an Apple > goof-up. agreed. it's a little bit of sloppiness, where they appended a -arch ppc instead of replacing the -arch i386. This keeps the multi-byte character stuff from compiling. And I bet since I've had that stuff enabled for testing, someone on my list has set that to their language, so when we tried to send the password, it barfed. I'm going to wait a week or so and then resend passwords... > (Aside: Chuq, how can we better help Apple with their Python stuff?) dunno. but I'll check. > Please do add a FAQwiz entry, and if you can write something up for > README.MACOSX that'd be awesome. Actually, that file's a little lean > anyway, so any info you'd like to add, please just send it my way. :) > I've got that on my list. First chance I get. Right now, I'm beating sendmail into a pulp on the xServe and trying to build an ssh tunnel for a tool to send email on remote machines instead of feeding into port 25 (why? Because solaris is butt slow compared to the Xserves, and I run out of resources, so I'm using scp and ssh to offload the delivery onto the xServe before firing up the script) -- Chuq Von Rospach, Architech chuqui@plaidworks.com -- http://www.plaidworks.com/chuqui/blog/ Very funny, Scotty. Now beam my clothes down here, will you? From noreply at sourceforge.net Thu Jan 2 07:55:21 2003 From: noreply at sourceforge.net (noreply@sourceforge.net) Date: Thu Jan 2 10:54:52 2003 Subject: [Mailman-Developers] [ mailman-Patches-661138 ] corrects defects in some HTML templates Message-ID: Patches item #661138, was opened at 2003-01-02 15:55 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: Open Resolution: None 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 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=661138&group_id=103 From noreply at sourceforge.net Thu Jan 2 08:05:31 2003 From: noreply at sourceforge.net (noreply@sourceforge.net) Date: Thu Jan 2 11:05:04 2003 Subject: [Mailman-Developers] [ mailman-Patches-444879 ] Archive indexer control to improve index Message-ID: Patches item #444879, was opened at 2001-07-26 18:01 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-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 Thu Jan 2 08:07:45 2003 From: noreply at sourceforge.net (noreply@sourceforge.net) Date: Thu Jan 2 11:07:40 2003 Subject: [Mailman-Developers] [ mailman-Patches-444884 ] Integration of Mailman & htdig for archi Message-ID: Patches item #444884, was opened at 2001-07-26 18:27 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=444884&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: 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-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 Thu Jan 2 08:30:31 2003 From: noreply at sourceforge.net (noreply@sourceforge.net) Date: Thu Jan 2 11:30:00 2003 Subject: [Mailman-Developers] [ mailman-Patches-644797 ] Revised mailer exit status Message-ID: Patches item #644797, was opened at 2002-11-27 15:56 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-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 Thu Jan 2 08:34:30 2003 From: noreply at sourceforge.net (noreply@sourceforge.net) Date: Thu Jan 2 11:33:58 2003 Subject: [Mailman-Developers] [ mailman-Patches-644810 ] Sendmail mailer in Python Message-ID: Patches item #644810, was opened at 2002-11-27 16:27 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-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 barry at python.org Thu Jan 2 22:45:35 2003 From: barry at python.org (Barry A. Warsaw) Date: Thu Jan 2 22:46:04 2003 Subject: [Mailman-Developers] Re: [Mailman-Users] "Invite" vs. autoresponders References: Message-ID: <15893.1887.211840.413961@gargle.gargle.HOWL> [I'm moving this discussion to mailman-developers. -BAW] >>>>> "SB" == Stonewall Ballard writes: SB> I've recently discovered that vacation autoresponders will SB> subscribe recipients to Mailman lists when they get "invited". Dang. This is because the From address contains the confirmation cookie encoded in the address. This might kill this idea for ease-of-use confirmations. SB> This is not good. It makes the feature dangerous if you've SB> promised to not subscribe anyone without their assent. Can you submit a bug report on this? We'll have to decide what to do long term. SB> Is there any way to avoid this problem, other than not using SB> the feature? This is yet another reason to move to URLs with SB> unique keys instead of using passwords. Such a URL could be SB> embedded in the invitation message. Take away the From header cookie and that's essentially what you've got in the invitation message. I'm up for any other ideas. -Barry From jwblist at olympus.net Thu Jan 2 21:59:38 2003 From: jwblist at olympus.net (John W Baxter) Date: Fri Jan 3 00:59:59 2003 Subject: [Mailman-Developers] email comparison bug? In-Reply-To: <15891.49113.21565.766392@gargle.gargle.HOWL> References: <15891.49113.21565.766392@gargle.gargle.HOWL> Message-ID: At 23:28 -0500 1/1/2003, Barry A. Warsaw wrote: >>>>>> "JWB" == John W Baxter writes: > > JWB> Since *can* be a different account than is > JWB> , I think we're stuck, even though it almost never > JWB> is. When there is a sitewide database of Mailman > JWB> users...we'll STILL be stuck, I fear, although the GUI might > JWB> allow a user to say the equivalent of "that's me, too." > >Mailman's policy is that membership is by case-insensitive email >address, and it preserves the case of the subscribed address only for >the recipient address (either envelope or From:). > >When there's a unified user database (read: Mailman 3.0), an email >address with any combination of case will still point to the same user >record, but it may be possible for users to add delivery addresses >with different cases. To me, it sounds reasonable. To folks in the last holdout case-sensitive local part domain, it likely doesn't. ;-) And given the policy, the behavior I defended is indeed wrong. --John (who doesn't know anyone in that last holdout case sensitive local part domain) -- John Baxter jwblist@olympus.net Port Ludlow, WA, USA Soggy mail is caused by postage dew. From jwblist at olympus.net Thu Jan 2 22:05:27 2003 From: jwblist at olympus.net (John W Baxter) Date: Fri Jan 3 01:05:43 2003 Subject: [Mailman-Developers] more on that password crash. In-Reply-To: <15891.54955.971767.338492@gargle.gargle.HOWL> References: <731FF698-1E07-11D7-954B-0003934516A8@plaidworks.com> <15891.54955.971767.338492@gargle.gargle.HOWL> Message-ID: At 1:05 -0500 1/2/2003, Barry A. Warsaw wrote: >(Aside: Chuq, how can we better help Apple with their Python stuff?) Sending the info along to Jack Jansen (email address widely known, but still I'd rather not stick it in here--will send privately if needed). --John -- John Baxter jwblist@olympus.net Port Ludlow, WA, USA From fil at rezo.net Fri Jan 3 11:49:51 2003 From: fil at rezo.net (Fil) Date: Fri Jan 3 05:49:56 2003 Subject: [Mailman-Developers] Re: [Mailman-Users] "Invite" vs. autoresponders In-Reply-To: <15893.1887.211840.413961@gargle.gargle.HOWL> References: <15893.1887.211840.413961@gargle.gargle.HOWL> Message-ID: <20030103104950.GE1220@rezo.net> > SB> I've recently discovered that vacation autoresponders will > SB> subscribe recipients to Mailman lists when they get "invited". > > Dang. This is because the From address contains the confirmation > cookie encoded in the address. This might kill this idea for > ease-of-use confirmations. I would imagine that, if the autoresponder is set to answer emails coming with a 'Precedence: list' header, the bug is with them, not with Mailman. You don't want to kill a good functionality just because most autoresponders are very poorly written - avoiding loops is enough ;) -- Fil From sb.list at sb.org Fri Jan 3 08:52:25 2003 From: sb.list at sb.org (Stonewall Ballard) Date: Fri Jan 3 08:55:13 2003 Subject: [Mailman-Developers] Re: [Mailman-Users] "Invite" vs. autoresponders In-Reply-To: <20030103104950.GE1220@rezo.net> Message-ID: On 1/3/03 5:49 AM, "Fil" wrote: >> SB> I've recently discovered that vacation autoresponders will >> SB> subscribe recipients to Mailman lists when they get "invited". >> >> Dang. This is because the From address contains the confirmation >> cookie encoded in the address. This might kill this idea for >> ease-of-use confirmations. > > I would imagine that, if the autoresponder is set to answer emails coming > with a 'Precedence: list' header, the bug is with them, not with Mailman. > You don't want to kill a good functionality just because most autoresponders > are very poorly written - avoiding loops is enough ;) Blaming the client doesn't work. These people are being subscribed to a list without their knowledge or assent. That's a fatal error to the list manager. - Stoney From noreply at sourceforge.net Fri Jan 3 06:56:44 2003 From: noreply at sourceforge.net (noreply@sourceforge.net) Date: Fri Jan 3 09:56:11 2003 Subject: [Mailman-Developers] [ mailman-Bugs-563336 ] Unexpected MMBadUserError with MM-2.0.11 Message-ID: Bugs item #563336, was opened at 2002-06-01 16:48 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=563336&group_id=103 Category: (un)subscribing Group: 2.0.x Status: Open Resolution: None Priority: 1 Submitted By: Federico Sevilla III (jijo) Assigned to: Nobody/Anonymous (nobody) Summary: Unexpected MMBadUserError with MM-2.0.11 Initial Comment: Just upgraded to Mailman 2.0.11. The upgrade itself worked fine, and basic tests after the upgrade seem to have worked okay, and mail has been getting delivered. However I got an email (as administrator) about an unexpected Mailman error. I have yet to get a complaint from our users so I do not know exactly what caused the problem. All I can deduce from the logs is that at around the same time, someone was subscribing/unsubscribing via email. The error message I got by email was: -----[ START ]----- An unexpected Mailman error has occurred in MailCommandHandler.ParseMailCommands(). Here is the traceback: Traceback (most recent call last): File "/usr/lib/mailman/Mailman/MailCommandHandler.py", line 223, in ParseMailCommands self.__dispatch[cmd](args, line, msg) File "/usr/lib/mailman/Mailman/MailCommandHandler.py", line 364, in ProcessSetCmd self.ConfirmUserPassword(sender, args[2]) File "/usr/lib/mailman/Mailman/SecurityManager.py", line 144, in ConfirmUserPassword raise Errors.MMBadUserError MMBadUserError -----[ END ]----- Some more miscellaneous information: - system is Debian GNU/Linux - mailman package is mailman-2.0.11-1 - python package is python-2.1.3-3 If anyone has tips as to where to dig for more information on the cause of this unexpected error, please do let me know and I will be more than happy to supply the missing details. It would also help calm my nerves if I knew whether this was fatal or not. :) ---------------------------------------------------------------------- Comment By: Uche Ogbuji (uche) Date: 2003-01-03 14:56 Message: Logged In: YES user_id=38966 Hmm. Looks as if Barry lowered the priority for this with no comment. I think that's unfortunate. I just ran into this as well. If this is truly just some user getting their password wrong, why isn't the exception trapped, and the user allowed to try again? This is the reason this puzzles me so: putting in the wrong password is a common thing to do. I myself sometimes trip up the password to my list admin areas. So when mailman goes out of its way to send me an e-mail with such a traceback, it makes me wonder whether something especially nasty is going on. A better message would help a lot. I'd be grateful for some note on this open issue from the developers, at least. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=563336&group_id=103 From noreply at sourceforge.net Fri Jan 3 10:19:18 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Jan 3 13:18:39 2003 Subject: [Mailman-Developers] [ mailman-Patches-644810 ] Sendmail mailer in Python Message-ID: Patches item #644810, was opened at 2002-11-27 16:27 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-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 pioppo at ferrara.linux.it Fri Jan 3 20:02:33 2003 From: pioppo at ferrara.linux.it (Simone Piunno) Date: Fri Jan 3 14:09:50 2003 Subject: [Mailman-Developers] removing .mo from CVS? In-Reply-To: <15890.6679.815374.10775@gargle.gargle.HOWL> References: <15890.6679.815374.10775@gargle.gargle.HOWL> Message-ID: <20030103190222.GA7302@ferrara.linux.it> On Tue, Dec 31, 2002 at 05:28:39PM -0500, Barry A. Warsaw wrote: > After nearly two years of development, we are happy to announce the Great work! Now I have a suggestion: supported languages are steadily growing and keeping both .po and .mo in CVS means roughly doubling the "cvs update" time. after some quick statistics, 2.1 already scores: mailman/ 20M mailman/templates/ 3M mailman/messages/ 11M mailman/messages/*/LC_MESSAGES/*.mo: 5M On a slow connection this can by very annoying. We could remove .mo files from CVS, cause they could be rebuilt automatically by make (ok, the user would be forced to have msgfmt installed on his system). I think this could be done at least on -HEAD. Bye Simone -- Adde parvum parvo magnus acervus erit. Simone Piunno, FerraraLUG - http://members.ferrara.linux.it/pioppo From noreply at sourceforge.net Fri Jan 3 23:15:55 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sat Jan 4 02:15:17 2003 Subject: [Mailman-Developers] [ mailman-Bugs-563336 ] Unexpected MMBadUserError with MM-2.0.11 Message-ID: Bugs item #563336, was opened at 2002-06-01 12:48 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=563336&group_id=103 Category: (un)subscribing Group: 2.0.x >Status: Closed >Resolution: Wont Fix Priority: 1 Submitted By: Federico Sevilla III (jijo) Assigned to: Nobody/Anonymous (nobody) Summary: Unexpected MMBadUserError with MM-2.0.11 Initial Comment: Just upgraded to Mailman 2.0.11. The upgrade itself worked fine, and basic tests after the upgrade seem to have worked okay, and mail has been getting delivered. However I got an email (as administrator) about an unexpected Mailman error. I have yet to get a complaint from our users so I do not know exactly what caused the problem. All I can deduce from the logs is that at around the same time, someone was subscribing/unsubscribing via email. The error message I got by email was: -----[ START ]----- An unexpected Mailman error has occurred in MailCommandHandler.ParseMailCommands(). Here is the traceback: Traceback (most recent call last): File "/usr/lib/mailman/Mailman/MailCommandHandler.py", line 223, in ParseMailCommands self.__dispatch[cmd](args, line, msg) File "/usr/lib/mailman/Mailman/MailCommandHandler.py", line 364, in ProcessSetCmd self.ConfirmUserPassword(sender, args[2]) File "/usr/lib/mailman/Mailman/SecurityManager.py", line 144, in ConfirmUserPassword raise Errors.MMBadUserError MMBadUserError -----[ END ]----- Some more miscellaneous information: - system is Debian GNU/Linux - mailman package is mailman-2.0.11-1 - python package is python-2.1.3-3 If anyone has tips as to where to dig for more information on the cause of this unexpected error, please do let me know and I will be more than happy to supply the missing details. It would also help calm my nerves if I knew whether this was fatal or not. :) ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-01-04 02:15 Message: Logged In: YES user_id=12800 I lowered the priority in a ham-handed approach to concentrating on MM2.1 bugs. I simply don't have the time to continue to support the 2.0 branch for anything other than critical security problems (which this isn't). Plus, you should at least upgrade to 2.0.13, the latest stable release of the 2.0 branch! :) This is very likely fixed in 2.1 as the entire mail command handler (and so much else :) has been rewritten. I'm closing this as won't fix. I recommend upgrading to 2.1. ---------------------------------------------------------------------- Comment By: Uche Ogbuji (uche) Date: 2003-01-03 09:56 Message: Logged In: YES user_id=38966 Hmm. Looks as if Barry lowered the priority for this with no comment. I think that's unfortunate. I just ran into this as well. If this is truly just some user getting their password wrong, why isn't the exception trapped, and the user allowed to try again? This is the reason this puzzles me so: putting in the wrong password is a common thing to do. I myself sometimes trip up the password to my list admin areas. So when mailman goes out of its way to send me an e-mail with such a traceback, it makes me wonder whether something especially nasty is going on. A better message would help a lot. I'd be grateful for some note on this open issue from the developers, at least. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=563336&group_id=103 From noreply at sourceforge.net Sat Jan 4 06:18:21 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sat Jan 4 09:17:32 2003 Subject: [Mailman-Developers] [ mailman-Bugs-662127 ] Race condition with summary modification screen Message-ID: Bugs item #662127, was opened at 2003-01-04 14:18 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=662127&group_id=103 Category: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: David Shaw (dmshaw) Assigned to: Nobody/Anonymous (nobody) Summary: Race condition with summary modification screen Initial Comment: I just upgraded to 2.1 and noticed an interesting race condition with the summary version of the moderation page. Take this timeline: 1) user@example.com sends 3 messages to the list 2) moderator visits summary moderation page and sees the 3 messages 3) user@example.com sends another message to the list 4) moderator clicks "discard" and submits The end result is that Mailman discards 4 messages, including the latest one that the moderator did not get to see. This does not happen with the old-style "details" version of the moderation page. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=662127&group_id=103 From noreply at sourceforge.net Sat Jan 4 08:05:22 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sat Jan 4 11:04:30 2003 Subject: [Mailman-Developers] [ mailman-Bugs-662163 ] Autoreplies confirm subscription invitations Message-ID: Bugs item #662163, was opened at 2003-01-04 11:05 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=662163&group_id=103 Category: (un)subscribing Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Stonewall Ballard (stoneyb) Assigned to: Nobody/Anonymous (nobody) Summary: Autoreplies confirm subscription invitations Initial Comment: I'm not sure of the exact circumstances (maybe personalization needs to be on), bu t i fyou "invite" people to join a mailing list, or, presumably, if someone sends a message to list-join, and there is an autoresponder at that address, the address is subscribed to the list without the subscriber being aware of it. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=662163&group_id=103 From stoney at sb.org Sat Jan 4 11:12:52 2003 From: stoney at sb.org (Stonewall Ballard) Date: Sat Jan 4 11:15:15 2003 Subject: [Mailman-Developers] Strangely broken list discovered Message-ID: I have a list that is one of about ten in a particular domain. The list has been unused for about 8 months (it's a seasonal thing), but someone sent a message to it, and the moderator message I got had the wrong URL in it. The list is at the domain , but some poking around at it showed that the admindb part thought that it was at . Everything else about it seemed ok, but I couldn't handle any admin requests because all the links on the admindb pages were pointing to the www host. I dumped the list out with config_list, but there was no mention of in there. Not having any other ideas, I deleted and recreated the list, and now all is well. I still have the list files on a backup if someone (i.e. Barry) wants to take a look at this. Since I don't know what version of Mailman created the list, possibly a 2.0 variant or early 2.1 beta, I can't say whether this is a real bug, but I wanted this to go on record in case it happens to someone else. - Stoney -- Stonewall Ballard stoney@sb.org http://stoney.sb.org/ From noreply at sourceforge.net Sat Jan 4 10:23:36 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sat Jan 4 13:22:46 2003 Subject: [Mailman-Developers] [ mailman-Feature Requests-662277 ] Encryption feature Message-ID: Feature Requests item #662277, was opened at 2003-01-04 18:23 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=662277&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: David Shaw (dmshaw) Assigned to: Nobody/Anonymous (nobody) Summary: Encryption feature Initial Comment: A feature that would allow a listmember to submit a PGP/GnuPG key to Mailman and thereafter all mail sent to that listmember would be encrypted with that key. Obviously, this would imply individual mail delivery to that user as it would no longer be possible to send the same mail to everyone. Also obviously, this would only really be possible for list servers with some spare CPU cycles... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=662277&group_id=103 From noreply at sourceforge.net Sat Jan 4 10:59:37 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sat Jan 4 13:58:47 2003 Subject: [Mailman-Developers] [ mailman-Feature Requests-662277 ] Encryption feature Message-ID: Feature Requests item #662277, was opened at 2003-01-04 13:23 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=662277&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: David Shaw (dmshaw) Assigned to: Nobody/Anonymous (nobody) Summary: Encryption feature Initial Comment: A feature that would allow a listmember to submit a PGP/GnuPG key to Mailman and thereafter all mail sent to that listmember would be encrypted with that key. Obviously, this would imply individual mail delivery to that user as it would no longer be possible to send the same mail to everyone. Also obviously, this would only really be possible for list servers with some spare CPU cycles... ---------------------------------------------------------------------- Comment By: Matthew Davis (big-dog) Date: 2003-01-04 13:59 Message: Logged In: YES user_id=34240 Take a look at http://sourceforge.net/tracker/index.php?func=detail&aid=645297&group_id=103&atid=300103 I think it's for one of the beta's. But it should get you pointed in the right direction. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=662277&group_id=103 From noreply at sourceforge.net Sat Jan 4 11:59:37 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sat Jan 4 14:58:51 2003 Subject: [Mailman-Developers] [ mailman-Patches-645297 ] Add PGP support Message-ID: Patches item #645297, was opened at 2002-11-28 14:54 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=645297&group_id=103 Category: None Group: Mailman 2.2 / 3.0 Status: Open Resolution: None Priority: 5 Submitted By: Ben Laurie (benl) Assigned to: Nobody/Anonymous (nobody) Summary: Add PGP support Initial Comment: Support PGP encrypted lists using GnuPG. ---------------------------------------------------------------------- Comment By: David Shaw (dmshaw) Date: 2003-01-04 19:59 Message: Logged In: YES user_id=606006 Another vote of support. I actually submitted an enhancement request earlier today for exactly this. ---------------------------------------------------------------------- Comment By: captain larry (captainlarry) Date: 2002-12-23 19:37 Message: Logged In: YES user_id=147905 Adding a vote of support for this patch. Please add it as soon as it's appropriate! I've been waiting a long time for this functionality and I'd hate to see the patch bitrot. :-) Adam. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-12-12 03:56 Message: Logged In: YES user_id=12800 I have to defer this patch until after MM2.1 since we're about ready for the first release candidate. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=645297&group_id=103 From noreply at sourceforge.net Sat Jan 4 12:30:10 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sat Jan 4 15:29:18 2003 Subject: [Mailman-Developers] [ mailman-Feature Requests-662324 ] Per-user anonymous posting Message-ID: Feature Requests item #662324, was opened at 2003-01-04 20:30 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=662324&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: David Shaw (dmshaw) Assigned to: Nobody/Anonymous (nobody) Summary: Per-user anonymous posting Initial Comment: It would be useful for list members to have the ability to post anonymously to the list. This would entail mangling the "From" address in some way (pushing it through SHA-1?), and possibly searching the message body for the member's email address for similar mangling. Obviously this would not be complete anonymitity, as Mailman and the list admin needs to know what the real address for the user is, but it would be sufficient to keep the list members anonymous from each other. This is similar to the current anonymous_list feature, but different in that anonymous users and non-anonymous users can interact on the same list. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=662324&group_id=103 From noreply at sourceforge.net Sat Jan 4 13:20:35 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sat Jan 4 16:19:42 2003 Subject: [Mailman-Developers] [ mailman-Feature Requests-662334 ] Remove additional recpients from postings Message-ID: Feature Requests item #662334, was opened at 2003-01-04 16:20 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=662334&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Stonewall Ballard (stoneyb) Assigned to: Nobody/Anonymous (nobody) Summary: Remove additional recpients from postings Initial Comment: I have a serious problem with people cc'ing lists along with other recipients. It's a bad idea for those other recipients to have their email addresses exposed via the lists, and it's a lot of trouble to get people to re-send messages with the other recpients stripped out. Lists should have a configuration flag that removes all recpients from the TO and CC headers except for the list address. This must happen before archiving. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=662334&group_id=103 From jwblist at olympus.net Sat Jan 4 14:58:58 2003 From: jwblist at olympus.net (John W Baxter) Date: Sat Jan 4 17:59:18 2003 Subject: [Mailman-Developers] Re: [Mailman-Users] "Invite" vs. autoresponders In-Reply-To: <20030103104950.GE1220@rezo.net> References: <15893.1887.211840.413961@gargle.gargle.HOWL> <20030103104950.GE1220@rezo.net> Message-ID: At 11:49 +0100 1/3/2003, Fil wrote: >> SB> I've recently discovered that vacation autoresponders will >> SB> subscribe recipients to Mailman lists when they get "invited". >> >> Dang. This is because the From address contains the confirmation >> cookie encoded in the address. This might kill this idea for >> ease-of-use confirmations. > >I would imagine that, if the autoresponder is set to answer emails coming >with a 'Precedence: list' header, the bug is with them, not with Mailman. >You don't want to kill a good functionality just because most autoresponders >are very poorly written - avoiding loops is enough ;) Well, there are different needs for different Mailman sites. If you have to convince your provider that every address in your list truly wanted to be there, it's "unhandy" for there to be such a simple example of involuntary subscription, which the provider can demonstrate at will. Same for sites which choose to block phoney "opt in" schemes, and which contain members of your list. --John -- John Baxter jwblist@olympus.net Port Ludlow, WA, USA From noreply at sourceforge.net Sat Jan 4 20:38:06 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sat Jan 4 23:37:11 2003 Subject: [Mailman-Developers] [ mailman-Bugs-662472 ] scrubber arbitrary extension change for attachments Message-ID: Bugs item #662472, was opened at 2003-01-04 23:38 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: Open Resolution: None Priority: 5 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. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=662472&group_id=103 From noreply at sourceforge.net Sat Jan 4 22:44:56 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sun Jan 5 01:44:00 2003 Subject: [Mailman-Developers] [ mailman-Bugs-662490 ] not mimetype return Message-ID: Bugs item #662490, was opened at 2003-01-05 01:44 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: Open Resolution: None Priority: 5 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 Jan 4 23:41:00 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sun Jan 5 02:40:03 2003 Subject: [Mailman-Developers] [ mailman-Bugs-662504 ] Mailman Admin Notification Racing Message-ID: Bugs item #662504, was opened at 2003-01-05 02:41 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=662504&group_id=103 Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Ian Wilson (tacgeek) Assigned to: Nobody/Anonymous (nobody) Summary: Mailman Admin Notification Racing Initial Comment: Hi folks; When a non-list member sends a message to a list, I start to receive emails in a race format...up to about 20 a minute in some instances. Here's how to replicate problem (for those who need to know, and please understand I'm not being a smartbutt, but someone who is just confused with this behavior). 1.) Create new list 2.) Add your email in list administrator's area 3.) Save 4.) Send an email to list from a non-subscribed list 5.) Watch the fireworks on your Admin Email I'm having to go in, stop qrunner, then delete the request.db file before starting qrunner before the race condition stops. Any help would be appreciated! Ian ian@dysfunctional-household.org ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=662504&group_id=103 From fil at rezo.net Mon Jan 6 00:17:31 2003 From: fil at rezo.net (Fil) Date: Sun Jan 5 18:17:36 2003 Subject: [Mailman-Developers] bad address Message-ID: <20030105231731.GB14572@rezo.net> Hi, a bad address (albray@xxxxx.com@, notice the trailing @) has made it into a list ; and I just can't take it out from the web interface or via bin/remove_members : mailman@miel:~$ bin/remove_members -n spip-dev albray@xxxxx.com@ Traceback (most recent call last): File "bin/remove_members", line 179, in ? main() File "bin/remove_members", line 169, in main userack) File "/usr/local/mailman/Mailman/MailList.py", line 921, in ApprovedDeleteMember self.removeMember(emailaddr) File "/usr/local/mailman/Mailman/OldStyleMemberships.py", line 217, in removeMember self.__assertIsMember(member) File "/usr/local/mailman/Mailman/OldStyleMemberships.py", line 113, in __assertIsMember raise Errors.NotAMemberError, member Mailman.Errors.NotAMemberError: albray@xxxxx.com -- Fil From noreply at sourceforge.net Mon Jan 6 11:18:52 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Jan 6 14:18:39 2003 Subject: [Mailman-Developers] [ mailman-Bugs-660733 ] pipermail date handling Message-ID: Bugs item #660733, was opened at 2003-01-01 12:29 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=660733&group_id=103 Category: Pipermail Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Bryan Fullerton (fehwalker) Assigned to: Nobody/Anonymous (nobody) >Summary: pipermail date handling Initial Comment: I moved my first list to mailman 2.1 and tried to re-generate the pipermail archives (just, ya know, to see how it'd work :), and got the following traceback. This is a list that's been around for a long time (archives back to 1995), and the .mbox file was generated from a majordomo/hypermail archive when it was moved to mailman 2.0 a couple of years ago. Here's a ls -l of the .mbox file: -rw-rw-r-- 1 mailman mailman 17741891 Jan 1 10:36 bryans-list.mbox Here's the traceback: Updating HTML for article 467 Updating HTML for article 468 Updating HTML for article 469 Updating HTML for article 473 Updating HTML for article 472 Pickling archive state into /home/mailman-2.1/archives/private/bryans-list/pipermail.pck Traceback (most recent call last): File "bin/arch", line 187, in ? main() File "bin/arch", line 175, in main archiver.processUnixMailbox(fp, start, end) File "/home/mailman-2.1/Mailman/Archiver/pipermail.py", line 544, in processUnixMailbox m = mbox.next() File "/usr/local/lib/python2.2/mailbox.py", line 34, in next return self.factory(_Subfile(self.fp, start, stop)) File "/home/mailman-2.1/Mailman/Mailbox.py", line 79, in scrubber return mailbox.scrub(msg) File "/home/mailman-2.1/Mailman/Mailbox.py", line 99, in scrub return self._scrubber(self._mlist, msg) File "/home/mailman-2.1/Mailman/Handlers/Scrubber.py", line 132, in process dir = calculate_attachments_dir(mlist, msg, msgdata) File "/home/mailman-2.1/Mailman/Handlers/Scrubber.py", line 93, in calculate_attachments_dir datedir = safe_strftime(fmt, now) File "/home/mailman-2.1/Mailman/Handlers/Scrubber.py", line 77, in safe_strftime return time.strftime(fmt, floatsecs) TypeError: argument must be 9-item sequence, not None I'm guessing it's a header problem in one of the messages, but I'm not sure what. Thanks, Bryan ---------------------------------------------------------------------- Comment By: Bryan Fullerton (fehwalker) Date: 2003-01-01 13:45 Message: Logged In: YES user_id=660772 After some investigation, the following (admittedly invalid) date headers cause tracebacks similar to the above. After reformatting them I'm able to generate the archive. Date: 25 Aug 95 18.00 Date: Thursday, 30 October 1997 3:02pm PT Date: Mon, 29 Nov 1999 Pacific Standard Time Note that these messages *didn't* cause bin/arch|pipermail in mailman 2.0.x to fail, though it probably didn't parse them properly. Perhaps trapping the error and/or skipping these messages might be more useful? It also appears that bin/arch is throwing all messages with dates it can't figure out (after the above were removed) into the current day. An example can be seen at http://lists.samurai.com/pipermail/bryans-list/2003-January/thread.html . I'm unsure if there's any way to better handle this, but just wanted to note it - I can create a separate bug report if it's important. Thanks, Bryan ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=660733&group_id=103 From noreply at sourceforge.net Mon Jan 6 11:20:43 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Jan 6 14:21:02 2003 Subject: [Mailman-Developers] [ mailman-Bugs-663272 ] held message notice options Message-ID: Bugs item #663272, was opened at 2003-01-06 14:20 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=663272&group_id=103 Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Bryan Fullerton (fehwalker) Assigned to: Nobody/Anonymous (nobody) Summary: held message notice options Initial Comment: I notice that in mm2.1 the "a message has been held" notices to list owners/moderators now include the content of the message. When spam is held, this can result as the notice itself being tagged as spam, which causes them to be thrown in my spam folder. Is there an option to use the smaller sized notices like in 2.0.x? If not, could there be one? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=663272&group_id=103 From Dan.Mick at Sun.COM Mon Jan 6 10:49:39 2003 From: Dan.Mick at Sun.COM (Dan Mick) Date: Mon Jan 6 14:55:04 2003 Subject: [Mailman-Developers] Strangely broken list discovered In-Reply-To: References: Message-ID: <3E19CFC3.4030303@sun.com> Stonewall Ballard wrote: > I have a list that is one of about ten in a particular domain. The list has > been unused for about 8 months (it's a seasonal thing), but someone sent a > message to it, and the moderator message I got had the wrong URL in it. > > The list is at the domain , but some poking around at it > showed that the admindb part thought that it was at . > Everything else about it seemed ok, but I couldn't handle any admin requests > because all the links on the admindb pages were pointing to the www host. > > I dumped the list out with config_list, but there was no mention of > in there. Not having any other ideas, I deleted and recreated > the list, and now all is well. > > I still have the list files on a backup if someone (i.e. Barry) wants to > take a look at this. Since I don't know what version of Mailman created the > list, possibly a 2.0 variant or early 2.1 beta, I can't say whether this is > a real bug, but I wanted this to go on record in case it happens to someone > else. > > - Stoney > See bin/fix_url.py. From noreply at sourceforge.net Mon Jan 6 16:43:09 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Jan 6 19:43:28 2003 Subject: [Mailman-Developers] [ mailman-Bugs-663421 ] Links on admindb script discard pending posts Message-ID: Bugs item #663421, was opened at 2003-01-06 18:43 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=663421&group_id=103 Category: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: David Gibbs (midrangeman) Assigned to: Nobody/Anonymous (nobody) Summary: Links on admindb script discard pending posts Initial Comment: I get my daily notification of pending posts that didn't go through (mostly spam), I click on the link and the admindb script is launched as normal. I see the summary of the held posts, but if I click on the details link, all the held posts go away. All the radio buttons on the summary form were set to "Defer". The post log file shows the following for one of the posts that was dumped ... Jan 06 10:06:44 2003 (22141) openerp400: Discarded posting: From: winleather002@yahoo.com Subject: =?ISO-8859-1?Q?Happy New Year?= ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=663421&group_id=103 From noreply at sourceforge.net Tue Jan 7 02:04:01 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Jan 7 05:04:14 2003 Subject: [Mailman-Developers] [ mailman-Bugs-663593 ] Traceback when changing email address Message-ID: Bugs item #663593, was opened at 2003-01-07 11:04 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=663593&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: Traceback when changing email address Initial Comment: I got this traceback when trying to change a member's email address on his options page. His name contained a non-ASCII character, which is probably why this happened. Traceback (most recent call last): File "/home/mailman/scripts/driver", line 87, in run_main main() File "/home/mailman/Mailman/Cgi/options.py", line 269, in main if membername and membername <> oldname: UnicodeError: ASCII decoding error: ordinal not in range(128) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=663593&group_id=103 From noreply at sourceforge.net Tue Jan 7 05:02:14 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Jan 7 10:03:48 2003 Subject: [Mailman-Developers] [ mailman-Bugs-663675 ] Administrative interface vs. non-standard HTTP ports Message-ID: Bugs item #663675, was opened at 2003-01-07 11:02 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: Open Resolution: None Priority: 5 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? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=663675&group_id=103 From noreply at sourceforge.net Tue Jan 7 12:46:00 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Jan 7 15:46:07 2003 Subject: [Mailman-Developers] [ mailman-Patches-645513 ] qmail VERP-enabled delivery handler Message-ID: Patches item #645513, was opened at 2002-11-29 15:58 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=645513&group_id=103 Category: mail delivery Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Colin Palmer (tzs) Assigned to: Nobody/Anonymous (nobody) Summary: qmail VERP-enabled delivery handler Initial Comment: This is based on Peter D. Gray's popen-avoiding Sendmail.py module, tweaked so it can use qmail-inject instead of sendmail and ask qmail to do VERP when the message is delivered, which is much faster than getting Mailman to do it at message injection time. You'll need the following in mm_cfg.py: DELIVERY_MODULE = 'Qmail' SENDMAIL_CMD = '/var/qmail/bin/qmail-inject' DO_QMAIL_VERP = 1 ---------------------------------------------------------------------- >Comment By: Colin Palmer (tzs) Date: 2003-01-08 09:46 Message: Logged In: YES user_id=658762 Oops, should have been comparing it's function with 'SMTPDirect' as well as 'Sendmail'... this version should work a lot better. It doesn't support personalisation or mailman-generated VERP headers, but should do everything else now. Read the the comments at the top of the module for things that need to be in mm_cfg.py for it to work. ---------------------------------------------------------------------- Comment By: Ed Lau (edlau) Date: 2002-12-25 13:32 Message: Logged In: YES user_id=675094 Running as listed except DO_QMAIL_VERP = 0, messages don't appear to have the footer tacked on at the bottom. Everything else (header-wise) seems there. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=645513&group_id=103 From noreply at sourceforge.net Tue Jan 7 14:03:35 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Jan 7 23:01:12 2003 Subject: [Mailman-Developers] [ 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: Open Resolution: None Priority: 7 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: 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 Tue Jan 7 14:03:23 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Jan 7 23:04:31 2003 Subject: [Mailman-Developers] [ 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: Open Resolution: None Priority: 7 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: 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 edlau at ucf.ics.uci.edu Tue Jan 7 21:42:55 2003 From: edlau at ucf.ics.uci.edu (Edmund Lau) Date: Wed Jan 8 00:43:31 2003 Subject: [Mailman-Developers] Qmail Doc patch for 2.1 Message-ID: Qmail people: This is a documentation patch for the README.QMAIL file. There's not much testing here, but Barry would you consider applying it? I'm cc'ing -users so they will be brought up to speed on the new 2.1. -Ed --- README.QMAIL.old 2002-04-05 13:24:10.000000000 -0800 +++ README.QMAIL 2003-01-07 21:37:58.000000000 -0800 @@ -2,14 +2,6 @@ Copyright (C) 1998,1999,2000,2001,2002 by the Free Software Foundation, Inc. 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA -MORE INFORMATION - -You might be interested in some information that Norbert Bollow has -written about Mailman and Qmail integration, available here: - - http://mailman.cis.to/qmail-verh/ - - QMAIL ISSUES There are some issues that users of the qmail mail transport agent @@ -115,10 +107,11 @@ your lists (if for some reason you can/will not have them automatically picked up using "contrib/qmail-to-mailman.py"): +This script is for the Mailman 2.0 series: #!/bin/sh if [ $# = 1 ]; then i=$1 - echo Making links to $i... + echo Making links to $i in the current directory... echo "|preline /home/mailman/mail/mailman post $i" > .qmail-$i echo "|preline /home/mailman/mail/mailman mailowner $i" > .qmail-$i-admin echo "|preline /home/mailman/mail/mailman mailowner $i" > .qmail-$i-owner @@ -126,6 +119,62 @@ echo "|preline /home/mailman/mail/mailman mailcmd $i" > .qmail-$i-request fi +This script is for the Mailman 2.1 series: +#!/bin/sh +if [ $# = 1 ]; then + i=$1 + echo Making links to $i in the current directory... + echo "|preline /home/mailman/mail/mailman post $i" > .qmail-$i + echo "|preline /home/mailman/mail/mailman admin $i" > .qmail-$i-admin + echo "|preline /home/mailman/mail/mailman bounces $i" > .qmail-$i-bounces + # The following line is for VERP + # echo "|preline /home/mailman/mail/mailman bounces $i" > .qmail-$i-bounces-default + echo "|preline /home/mailman/mail/mailman confirm $i" > .qmail-$i-confirm + echo "|preline /home/mailman/mail/mailman join $i" > .qmail-$i-join + echo "|preline /home/mailman/mail/mailman leave $i" > .qmail-$i-leave + echo "|preline /home/mailman/mail/mailman owner $i" > .qmail-$i-owner + echo "|preline /home/mailman/mail/mailman request $i" > .qmail-$i-request + echo "|preline /home/mailman/mail/mailman subscribe $i" > .qmail-$i-subscribe + echo "|preline /home/mailman/mail/mailman unsubscribe $i" > .qmail-$i-unsubscribe +fi + +INFORMATION ON VERP + +You will note in the alias generating script for 2.1 above, there is a +line for VERP that has been commented out. If you are interested in VERP +there are two options. The first option is to allow Mailman to do the +VERP formatting. To activate this, uncomment that line and add the +following lines to your mm_cfg.py file: + +VERP_FORMAT = '%(bounces)s-+%(mailbox)s=%(host)s' +VERP_REGEXP = r'^(?P.*?)-\+(?P[^=]+)=(?P[^@]+)@.*$' + +The second option is a patch on SourceForge located at: + +http://sourceforge.net/tracker/?func=detail&atid=300103&aid=645513&group_id=103 + +This patch currently needs more testing and might best be suitable for +developers or people well familiar with qmail. Having said that, this +patch is the more qmail-friendly approach resulting in large performance +gains. + +VIRTUAL MAIL SERVER + +As mentioned in the ISSUES area for a virtual mail server, a patch under +testing is located at: + +http://sf.net/tracker/index.php?func=detail&aid=621257&group_id=103&atid=300103 + +Again, this patch is for people familiar with their qmail installation. + +MORE INFORMATION + +You might be interested in some information on modifying footers that +Norbert Bollow has written about Mailman and Qmail integration, available +here: + + http://mailman.cis.to/qmail-verh/ + Local Variables: mode: text From noreply at sourceforge.net Tue Jan 7 22:11:20 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Jan 8 01:10:26 2003 Subject: [Mailman-Developers] [ mailman-Patches-643011 ] bug: Scrubbed messages are re-decoded Message-ID: Patches item #643011, was opened at 2002-11-24 19:21 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=643011&group_id=103 Category: Pipermail Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Hatuka*nezumi (hatukanezumi) Assigned to: Nobody/Anonymous (nobody) Summary: bug: Scrubbed messages are re-decoded Initial Comment: Content-Transfer-Encoding must be cleared. ---------------------------------------------------------------------- >Comment By: Hatuka*nezumi (hatukanezumi) Date: 2003-01-08 15:11 Message: Logged In: YES user_id=529503 This seems to be fixed at rev. 2.18. Please delete. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-12-24 12:32 Message: Logged In: YES user_id=12800 Could you give more details about why this patch is necessary? If you have message examples, please attach them (don't paste them into a comment). ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=643011&group_id=103 From noreply at sourceforge.net Tue Jan 7 22:14:30 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Jan 8 01:13:35 2003 Subject: [Mailman-Developers] [ mailman-Patches-664209 ] best effort to keep text/plain Message-ID: Patches item #664209, was opened at 2003-01-08 06:14 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=664209&group_id=103 Category: internationalization Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: best effort to keep text/plain Initial Comment: When a message come in different charset than list specific one, Decorate.py adds the header and footer in mime attatchments. This patch tries to keep the good-old plain text format by making these texts into unicode and encode in list preferred charset. If it fails, the messages will get mime-multiparted as was the case without this patch. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=664209&group_id=103 From noreply at sourceforge.net Tue Jan 7 23:34:06 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Jan 8 02:33:17 2003 Subject: [Mailman-Developers] [ mailman-Patches-664209 ] best effort to keep text/plain Message-ID: Patches item #664209, was opened at 2003-01-08 06:14 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=664209&group_id=103 Category: internationalization Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: best effort to keep text/plain Initial Comment: When a message come in different charset than list specific one, Decorate.py adds the header and footer in mime attatchments. This patch tries to keep the good-old plain text format by making these texts into unicode and encode in list preferred charset. If it fails, the messages will get mime-multiparted as was the case without this patch. ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-01-08 07:34 Message: Logged In: YES user_id=67709 Expand this patch to base64 encoded plain text. apply the second patch Decorate.py.diff2 to the original Decorate.py ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=664209&group_id=103 From noreply at sourceforge.net Wed Jan 8 00:01:43 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Jan 8 03:00:50 2003 Subject: [Mailman-Developers] [ mailman-Bugs-663593 ] Traceback when changing email address Message-ID: Bugs item #663593, was opened at 2003-01-07 11:04 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=663593&group_id=103 Category: Web/CGI Group: 2.1 (stable) >Status: Deleted >Resolution: Duplicate Priority: 5 Submitted By: Daniel Buchmann (avalon) Assigned to: Nobody/Anonymous (nobody) Summary: Traceback when changing email address Initial Comment: I got this traceback when trying to change a member's email address on his options page. His name contained a non-ASCII character, which is probably why this happened. Traceback (most recent call last): File "/home/mailman/scripts/driver", line 87, in run_main main() File "/home/mailman/Mailman/Cgi/options.py", line 269, in main if membername and membername <> oldname: UnicodeError: ASCII decoding error: ordinal not in range(128) ---------------------------------------------------------------------- >Comment By: Daniel Buchmann (avalon) Date: 2003-01-08 09:01 Message: Logged In: YES user_id=184577 Deleting this bug report, as this is a dupe of bug #660675 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=663593&group_id=103 From noreply at sourceforge.net Wed Jan 8 01:49:16 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Jan 8 04:48:26 2003 Subject: [Mailman-Developers] [ mailman-Patches-645513 ] qmail VERP-enabled delivery handler Message-ID: Patches item #645513, was opened at 2002-11-28 18:58 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=645513&group_id=103 Category: mail delivery Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Colin Palmer (tzs) Assigned to: Nobody/Anonymous (nobody) Summary: qmail VERP-enabled delivery handler Initial Comment: This is based on Peter D. Gray's popen-avoiding Sendmail.py module, tweaked so it can use qmail-inject instead of sendmail and ask qmail to do VERP when the message is delivered, which is much faster than getting Mailman to do it at message injection time. You'll need the following in mm_cfg.py: DELIVERY_MODULE = 'Qmail' SENDMAIL_CMD = '/var/qmail/bin/qmail-inject' DO_QMAIL_VERP = 1 ---------------------------------------------------------------------- Comment By: Ed Lau (edlau) Date: 2003-01-08 01:49 Message: Logged In: YES user_id=675094 using the version released 2003-01-07 17:27, with DO_QMAIL_VERP = 0, any post to a list gets posted to all members properly, but also gets shunted. This happened because I didn't have QMAIL_LOG_EVERY_MESSAGE, QMAIL_LOG_SUCCESS, or QMAIL_LOG_FAILURE defined. Is the Email shunted, yet posted event supposed to happen? I'll be testing out VERP later on ---------------------------------------------------------------------- Comment By: Colin Palmer (tzs) Date: 2003-01-07 12:46 Message: Logged In: YES user_id=658762 Oops, should have been comparing it's function with 'SMTPDirect' as well as 'Sendmail'... this version should work a lot better. It doesn't support personalisation or mailman-generated VERP headers, but should do everything else now. Read the the comments at the top of the module for things that need to be in mm_cfg.py for it to work. ---------------------------------------------------------------------- Comment By: Ed Lau (edlau) Date: 2002-12-24 16:32 Message: Logged In: YES user_id=675094 Running as listed except DO_QMAIL_VERP = 0, messages don't appear to have the footer tacked on at the bottom. Everything else (header-wise) seems there. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=645513&group_id=103 From barry at python.org Wed Jan 8 07:47:36 2003 From: barry at python.org (Barry A. Warsaw) Date: Wed Jan 8 07:48:39 2003 Subject: [Mailman-Developers] Qmail Doc patch for 2.1 References: Message-ID: <15900.7656.334436.851124@gargle.gargle.HOWL> EL> This is a documentation patch for the README.QMAIL file. EL> There's not much testing here, but Barry would you consider EL> applying it? Sure, if other qmailers like it. Can you upload it as a patch to SF? Thanks, -Barry From noreply at sourceforge.net Wed Jan 8 04:50:48 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Jan 8 07:49:53 2003 Subject: [Mailman-Developers] [ mailman-Patches-643011 ] bug: Scrubbed messages are re-decoded Message-ID: Patches item #643011, was opened at 2002-11-24 05:21 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=643011&group_id=103 Category: Pipermail Group: Mailman 2.1 >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Hatuka*nezumi (hatukanezumi) Assigned to: Nobody/Anonymous (nobody) Summary: bug: Scrubbed messages are re-decoded Initial Comment: Content-Transfer-Encoding must be cleared. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-01-08 07:50 Message: Logged In: YES user_id=12800 Thanks for the follow up. ---------------------------------------------------------------------- Comment By: Hatuka*nezumi (hatukanezumi) Date: 2003-01-08 01:11 Message: Logged In: YES user_id=529503 This seems to be fixed at rev. 2.18. Please delete. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-12-23 22:32 Message: Logged In: YES user_id=12800 Could you give more details about why this patch is necessary? If you have message examples, please attach them (don't paste them into a comment). ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=643011&group_id=103 From noreply at sourceforge.net Wed Jan 8 08:30:33 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Jan 8 11:29:02 2003 Subject: [Mailman-Developers] [ mailman-Bugs-664466 ] 2.0 cookies break 2.1 web auth Message-ID: Bugs item #664466, was opened at 2003-01-08 11:30 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=664466&group_id=103 Category: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Bryan Fullerton (fehwalker) Assigned to: Nobody/Anonymous (nobody) Summary: 2.0 cookies break 2.1 web auth Initial Comment: (as discussed on mailman-users) If there are *any* mm2.0 cookies in the URI-space mm2.1 looks in, the following code will always raise a Cookie.CookieException and return 0. # Treat the cookie data as simple strings, and do application level # decoding as necessary. By using SimpleCookie, we prevent any kind # of security breach due to untrusted cookie data being unpickled # (which is quite unsafe). try: c = Cookie.SimpleCookie(cookiedata) except Cookie.CookieError: return 0 If python's Cookie code (or at least SimpleCookie) doesn't like cookies with :'s in them that'd explain it. This is rather a problem for anyone thinking they could run both mm2.0 and mm2.1 mapped into the same URI-space. Simply put, you can't (without re-auth'ing with every action in 2.1 lists), unless the mm2.1 code is rewritten to handle that exception better. Or unless you nuke all your cookies after every use of a 2.0 list (not just logout - in my testing that doesn't actually remove the cookie, just the cookie's contents). The good news is that this should be no problem once everything is moved to 2.1. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=664466&group_id=103 From noreply at sourceforge.net Wed Jan 8 11:24:29 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Jan 8 14:22:59 2003 Subject: [Mailman-Developers] [ mailman-Bugs-664575 ] mailman 2.1 tarball permissions Message-ID: Bugs item #664575, was opened at 2003-01-08 14:24 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=664575&group_id=103 Category: configuring/installing Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Barry A. Warsaw (bwarsaw) Assigned to: Nobody/Anonymous (nobody) Summary: mailman 2.1 tarball permissions Initial Comment: The tarball contains world writeable directories and files by default. This may be a problem on systems where users do not have a sane umask or safe directory permissions, allowing an attacker to modify source code that is later compiled (usually as root) and that is installed setuid/setgid (allowing for easy insertion of backdoors). kurt@seifried.org ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=664575&group_id=103 From noreply at sourceforge.net Wed Jan 8 11:57:22 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Jan 8 14:56:10 2003 Subject: [Mailman-Developers] [ mailman-Patches-664611 ] Updated README.QMAIL doc patch Message-ID: Patches item #664611, was opened at 2003-01-08 11:57 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=664611&group_id=103 Category: documentation Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Ed Lau (edlau) Assigned to: Nobody/Anonymous (nobody) Summary: Updated README.QMAIL doc patch Initial Comment: Main item: distinction between MM2.0 & MM2.1 alias generation scripts. Also, information on VERP ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=664611&group_id=103 From noreply at sourceforge.net Wed Jan 8 12:09:02 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Jan 8 15:08:50 2003 Subject: [Mailman-Developers] [ mailman-Patches-645513 ] qmail VERP-enabled delivery handler Message-ID: Patches item #645513, was opened at 2002-11-29 15:58 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=645513&group_id=103 Category: mail delivery Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Colin Palmer (tzs) Assigned to: Nobody/Anonymous (nobody) Summary: qmail VERP-enabled delivery handler Initial Comment: This is based on Peter D. Gray's popen-avoiding Sendmail.py module, tweaked so it can use qmail-inject instead of sendmail and ask qmail to do VERP when the message is delivered, which is much faster than getting Mailman to do it at message injection time. You'll need the following in mm_cfg.py: DELIVERY_MODULE = 'Qmail' SENDMAIL_CMD = '/var/qmail/bin/qmail-inject' DO_QMAIL_VERP = 1 ---------------------------------------------------------------------- >Comment By: Colin Palmer (tzs) Date: 2003-01-09 09:09 Message: Logged In: YES user_id=658762 Yes, python throws an exception if they (or any other config options) are undefined. Set them to 'None' if you don't want logging to happen. ---------------------------------------------------------------------- Comment By: Ed Lau (edlau) Date: 2003-01-08 22:49 Message: Logged In: YES user_id=675094 using the version released 2003-01-07 17:27, with DO_QMAIL_VERP = 0, any post to a list gets posted to all members properly, but also gets shunted. This happened because I didn't have QMAIL_LOG_EVERY_MESSAGE, QMAIL_LOG_SUCCESS, or QMAIL_LOG_FAILURE defined. Is the Email shunted, yet posted event supposed to happen? I'll be testing out VERP later on ---------------------------------------------------------------------- Comment By: Colin Palmer (tzs) Date: 2003-01-08 09:46 Message: Logged In: YES user_id=658762 Oops, should have been comparing it's function with 'SMTPDirect' as well as 'Sendmail'... this version should work a lot better. It doesn't support personalisation or mailman-generated VERP headers, but should do everything else now. Read the the comments at the top of the module for things that need to be in mm_cfg.py for it to work. ---------------------------------------------------------------------- Comment By: Ed Lau (edlau) Date: 2002-12-25 13:32 Message: Logged In: YES user_id=675094 Running as listed except DO_QMAIL_VERP = 0, messages don't appear to have the footer tacked on at the bottom. Everything else (header-wise) seems there. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=645513&group_id=103 From colinp at waikato.ac.nz Thu Jan 9 09:20:02 2003 From: colinp at waikato.ac.nz (Colin Palmer) Date: Wed Jan 8 15:20:41 2003 Subject: [Mailman-Developers] Qmail Doc patch for 2.1 In-Reply-To: <15900.7656.334436.851124@gargle.gargle.HOWL> Message-ID: On Wed, 8 Jan 2003, Barry A. Warsaw wrote: > EL> This is a documentation patch for the README.QMAIL file. > EL> There's not much testing here, but Barry would you consider > EL> applying it? > Sure, if other qmailers like it. It looks good to me. -- ** Colin Palmer, Systems and Development Group, University of Waikato, NZ ** From colinp at waikato.ac.nz Thu Jan 9 11:27:33 2003 From: colinp at waikato.ac.nz (Colin Palmer) Date: Wed Jan 8 17:28:12 2003 Subject: [Mailman-Developers] small 2.1 bin/sync_members fix Message-ID: It dies with an 'UnboundLocalError:' for me otherwise: --- sync_members~ Wed Jan 8 08:41:08 2003 +++ sync_members Thu Jan 9 09:49:51 2003 @@ -255,6 +255,7 @@ try: if not dryrun: mlist.ApprovedAddMember(userdesc, welcome, notifyadmin) + enc = sys.getdefaultencoding() s = email.Utils.formataddr((name, addr)).encode(enc, 'replace') print _('Added : %(s)s') except Errors.MMAlreadyAMember: -- ** Colin Palmer, Systems and Development Group, University of Waikato, NZ ** From noreply at sourceforge.net Wed Jan 8 15:31:02 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Jan 8 18:29:31 2003 Subject: [Mailman-Developers] [ mailman-Bugs-663421 ] Links on admindb script discard pending posts Message-ID: Bugs item #663421, was opened at 2003-01-06 18:43 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=663421&group_id=103 Category: Web/CGI Group: 2.1 (stable) >Status: Closed >Resolution: Rejected Priority: 5 Submitted By: David Gibbs (midrangeman) Assigned to: Nobody/Anonymous (nobody) Summary: Links on admindb script discard pending posts Initial Comment: I get my daily notification of pending posts that didn't go through (mostly spam), I click on the link and the admindb script is launched as normal. I see the summary of the held posts, but if I click on the details link, all the held posts go away. All the radio buttons on the summary form were set to "Defer". The post log file shows the following for one of the posts that was dumped ... Jan 06 10:06:44 2003 (22141) openerp400: Discarded posting: From: winleather002@yahoo.com Subject: =?ISO-8859-1?Q?Happy New Year?= ---------------------------------------------------------------------- >Comment By: David Gibbs (midrangeman) Date: 2003-01-08 17:31 Message: Logged In: YES user_id=86339 Don't ask me what was going on ... but it fixed itself. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=663421&group_id=103 From claw at kanga.nu Wed Jan 8 16:04:39 2003 From: claw at kanga.nu (J C Lawrence) Date: Wed Jan 8 19:04:46 2003 Subject: [Mailman-Developers] RFQ: Member moderation feature. Message-ID: <8474.1042070679@kanga.nu> In discussion with one of my list members an idea arose to help reduce moderator load and (better) allow posters to guide/control the threads they create: Assuming a fully moderated list: 1) A poster may indicate on their posting that they wish to moderate the subsequent thread. This could be done by custom header or special first line in a special format on the message. 2) All posts on that thread are then held for their approval, and they can view that moderation queue as if they were a first class list moderator, with the only difference being that they can only see and process the posts held for them, and won't see the posts held for other members or the list in general. 3) The real moderator(s) view of the moderation queue will show all messages. 4) A member moderator can defer, accept, reject, or discard the messages in his queue, just as per a normal moderator EXCEPT that in all cases the commands have no effect other than annotating the message for the real moderator. (ie the member moderator supplies hints to the real moderator). 5) The real moderator in reviewing his moderation queue will see normal messages, messages in member moderator queues, and annotated messages from member moderated queues. Messages being held on member moderation queues will be annotated to that effect. Any commands that a real moderator applies to any messages (no matter its status) in his moderation queue take place instantly (ie he's God and can do anything with final decisions resting with the real moderator). 6) A messages arrive on a member moderated thread the member moderator is emailed a standard "held message" email just like a real moderator. In fact the same message could be sent to both moderators, with the body of the message stating that the message is member moderated and who by. This could be extended for partially moderated or unmoderated lists by replacing #4 above with: 4a) A member moderator can defer, accept, reject, or discard the messages in his queue with the following results: Defer -- message remains held in his queue. Accept -- Message is broadcast or held as per any moderation flag applied to the poster. Reject -- Message is annotated with the member's proposed rejection message and left in the real moderator's moderation queue. Discard -- Message is annotated with the member's proposed discard reason and left in the real moderator's moderation queue. All the above assumes that member moderation is via the web only. I consider this acceptable. Yeah, moderation via email is great, but it doesn't have to be in version 1.0 of the feature. -*- Implementation notes: Tracing threads is unreliable. Not all MUAs properly support or generate References: or In-Reply-To: headers. For those that do, tracing and tracking Message-IDs is the (only) reliable route. I propose that when a thread/message becomes member moderated that Mailman log the Subject: header and Message-ID. Any subsequent message which has that Message-ID in an In-Reply-To: or References: header and has a Subject: which is (at least) a prefix substring (accounting for "Re:" etc) of the saved Subject: will be held for member moderation. Attempts by a member to moderate a thread already member moderated will be refused/rejected/denied/whatever. A member may however fork a thread and moderate the new fork _IF_ he changes the Subject: header as that breaks the check above. If desired we can support the ability for a member moderator to resign from moderating a thread (web interface again). Commentary: Currently Mailman has poor supports in general for multiple moderators. The above annotation features go a long way to better supporting multiple moderators. Adding a general moderation queue annotation feature would be a very useful as a way for moderators to pass each other notes as to held messages, as well as for single moderators to keep notes for themselves. -*- As a final tweak, and I find this one particularly delightful, I'd like to see a text field with a controlling checkbox in the displayed headers for a message held for moderation. If the checkbox is checked by a real or member moderator and text entered in the field, the held message will have its Subject: header edited/replaced ala: Subject: Newly entered text here (Was: Old subject goes here) Note that this would effectively allow a member moderator to fork a thread out of his control. More specifically this would be the only extent to which member moderators could edit held messages. Real moderators would retain normal abilities to edit message text. -*- Background reasoning: Moderated lists have a core scaling problem WRT moderator overload. This feature allows moderation to be (partially) distributed without bypassing moderator control. A frequent complaint on higher volume focused lists is thread creep/fan-out. The original poster wanted to investigate a specific area (ie define and maintain focus) but the thread forked and charged off in another direction. This feature would allow such a member moderator to help guide the thread in the direction he wants without bypassing or removing the real moderator's function. -- J C Lawrence ---------(*) Satan, oscillate my metallic sonatas. claw@kanga.nu He lived as a devil, eh? http://www.kanga.nu/~claw/ Evil is a name of a foeman, as I live. From rodolfo at pilas.net Wed Jan 8 21:12:00 2003 From: rodolfo at pilas.net (Rodolfo Pilas) Date: Wed Jan 8 19:06:14 2003 Subject: [Mailman-Developers] Anti-Virus Message-ID: <1042071119.1373.76.camel@localhost> I have just download latest CVS version of MM and I am installing it. I use Postfix + procmail + AnomySanitizer + AVP_Antivirus + MailMan Today when I send a message to a mailinglist of users of my server I have the problem that the AnomySanitizer and AntiVirus scan each copy of message for each user. This causes a very important overload for the server. In other words, a message to a list AllOfMyUsers@mydomain.com tavel the following way: message -> SMTP -> mailman post AllOfMyUsers -> (many copies) -> procmail -> AnomySanitizer -> Antivirus -> user1 mailmbox -> procmail -> AnomySanitizer -> Antivirus -> user2 mailmbox -> procmail -> AnomySanitizer -> Antivirus -> user3 mailmbox I would like to move the Sanitizer+Antivirus check before MM make many copies of the message and to check only one time. Something like this: message -> SMTP -> mailman post AllOfMyUsers -> AnomySanitizer -> Antivirus -> (many copies) -> procmail -> user1 mailmbox -> procmail -> user2 mailmbox -> procmail -> user3 mailmbox Can you tell me a tip to do that? -- Rodolfo Pilas From david at midrange.com Wed Jan 8 20:22:13 2003 From: david at midrange.com (David Gibbs) Date: Wed Jan 8 21:22:23 2003 Subject: [Mailman-Developers] Re: Anti-Virus References: <1042071119.1373.76.camel@localhost> Message-ID: "Rodolfo Pilas" wrote in message news:1042071119.1373.76.camel@localhost... > Today when I send a message to a mailinglist of users of my server I > have the problem that the AnomySanitizer and AntiVirus scan each copy of > message for each user. This causes a very important overload for the > server. I had the same quandry ... I was able to solve the problem by setting up multiple instances of sendmail ... one instance listening only on 127.0.0.1, which handled the mailman traffic and didn't do any virus scanning (I use MailScanner), and another instance listening on my other IP's (which does scan for viruses). When mail comes in from the outside, it gets scanned for viruses and handed off to Mailman. When mailman processes the message, it does NOT get scanned, because mailman connects on 127.0.0.1. Although I don't know how you would do it with Postfix, I'm sure it can be done. The scanner I use is MailScanner (http://www.mailscanner.info) ... it supports postfix, so you might be able to get information there on how to implement using your scanner. david From noreply at sourceforge.net Wed Jan 8 19:50:53 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Jan 8 22:49:20 2003 Subject: [Mailman-Developers] [ mailman-Patches-664611 ] Updated README.QMAIL doc patch Message-ID: Patches item #664611, was opened at 2003-01-08 11:57 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=664611&group_id=103 Category: documentation Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Ed Lau (edlau) Assigned to: Nobody/Anonymous (nobody) Summary: Updated README.QMAIL doc patch Initial Comment: Main item: distinction between MM2.0 & MM2.1 alias generation scripts. Also, information on VERP ---------------------------------------------------------------------- >Comment By: Ed Lau (edlau) Date: 2003-01-08 19:50 Message: Logged In: YES user_id=675094 Didn't look like SF got my patch the first time. It's attached now ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=664611&group_id=103 From noreply at sourceforge.net Wed Jan 8 22:15:32 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Jan 9 01:14:02 2003 Subject: [Mailman-Developers] [ mailman-Bugs-663421 ] Links on admindb script discard pending posts Message-ID: Bugs item #663421, was opened at 2003-01-06 19:43 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=663421&group_id=103 Category: Web/CGI Group: 2.1 (stable) Status: Closed Resolution: Rejected Priority: 5 Submitted By: David Gibbs (midrangeman) Assigned to: Nobody/Anonymous (nobody) Summary: Links on admindb script discard pending posts Initial Comment: I get my daily notification of pending posts that didn't go through (mostly spam), I click on the link and the admindb script is launched as normal. I see the summary of the held posts, but if I click on the details link, all the held posts go away. All the radio buttons on the summary form were set to "Defer". The post log file shows the following for one of the posts that was dumped ... Jan 06 10:06:44 2003 (22141) openerp400: Discarded posting: From: winleather002@yahoo.com Subject: =?ISO-8859-1?Q?Happy New Year?= ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-01-09 01:15 Message: Logged In: YES user_id=12800 I don't know which is scarier, the initial report or the follow up ;) ---------------------------------------------------------------------- Comment By: David Gibbs (midrangeman) Date: 2003-01-08 18:31 Message: Logged In: YES user_id=86339 Don't ask me what was going on ... but it fixed itself. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=663421&group_id=103 From noreply at sourceforge.net Wed Jan 8 23:24:11 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Jan 9 02:22:36 2003 Subject: [Mailman-Developers] [ mailman-Patches-664611 ] Updated README.QMAIL doc patch Message-ID: Patches item #664611, was opened at 2003-01-08 11:57 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=664611&group_id=103 Category: documentation Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Ed Lau (edlau) Assigned to: Nobody/Anonymous (nobody) Summary: Updated README.QMAIL doc patch Initial Comment: Main item: distinction between MM2.0 & MM2.1 alias generation scripts. Also, information on VERP ---------------------------------------------------------------------- >Comment By: Ed Lau (edlau) Date: 2003-01-08 23:24 Message: Logged In: YES user_id=675094 Directory paths have changed to reflect new installations vs upgrading from prior installs ---------------------------------------------------------------------- Comment By: Ed Lau (edlau) Date: 2003-01-08 19:50 Message: Logged In: YES user_id=675094 Didn't look like SF got my patch the first time. It's attached now ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=664611&group_id=103 From tkikuchi at is.kochi-u.ac.jp Fri Jan 10 09:16:39 2003 From: tkikuchi at is.kochi-u.ac.jp (Tokio Kikuchi) Date: Thu Jan 9 19:16:43 2003 Subject: [Mailman-Developers] What's wrong with the mailman-users archive? Message-ID: <3E1E10E7.6080606@is.kochi-u.ac.jp> Hi, As of 0900 JST (+0900), http://mail.python.org/pipermail/mailman-users/2003-January/date.html shows 12 messages archived but it also says there are 311 messages. Looks like all the messages before Wed Jan 8 13:55:56 EST 2003 (in January 2003) are gone ! What happened ? Tokio From noreply at sourceforge.net Thu Jan 9 17:28:34 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Jan 9 20:35:42 2003 Subject: [Mailman-Developers] [ mailman-Feature Requests-232489 ] RFE: Option to drop implicit destination messages Message-ID: Feature Requests item #232489, was opened at 2001-02-15 19:06 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=232489&group_id=103 Category: configuring/installing Group: None Status: Open Resolution: None Priority: 4 Submitted By: Karsten Thygesen (karthy) Assigned to: Nobody/Anonymous (nobody) Summary: RFE: Option to drop implicit destination messages Initial Comment: Many lists receive huge loads of spam with iimplicit destination (BCc). I would like an option to bounce their postings with information about, that implicit destinations is not allowed and then _not_ inform the administrator of the list. As admin, it is not unusual to receive more than 30 administrative mails pr. list pr. day. When running many lists, this can be quite a burden. ---------------------------------------------------------------------- Comment By: Ken Yap (ken_yap) Date: 2003-01-10 12:28 Message: Logged In: YES user_id=23461 Is this implemented in the latest release? Anybody know? Anyway I found a way around it. I send all admin mail to a webmail mailbox which I check perhaps once a few months. I'm so sick of getting reminded to delete spam that I don't care if some silly subscriber doesn't know the posting rules. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2002-08-05 00:49 Message: Logged In: NO I second this. For a public list this option is de rigeur. I admin a couple of lists, and with only a couple of exceptions, ALL MAIL with implicit destinations were spam. It's a burden on the admin to have to discard these. To add injury to insult, mailman insists on reminding me every couple of hours to deal with the spam. I don't know why you people didn't think of this long ago. Please, please, please, implement this option, and let the list admin decide if this is the default policy for the list. I have suffered enough. I am capable of implementing the changes required and would have done so, but these are sourceforge lists beyond my control. I asked sourceforge to implement this option and they said it was up to the developers. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2001-08-14 22:20 Message: Logged In: NO We're getting flooded with this as well on the EROS project lists. I don't think an autorespond is a good idea, but a silent discard would be EXTREMELY useful. It's annoying enough that I've been trying to find the time to dig in to the code... ---------------------------------------------------------------------- Comment By: Thomas Wouters (twouters) Date: 2001-03-03 10:52 Message: Logged In: YES user_id=34209 Moved to feature requests. Could possibly be incorporated into the autoresponder. Note, however, that bouncing spam is usually not a good idea: the from address (both of them) are almost always fake, and sometimes end up in the mailbox(es) of innocent people. I have seen a lot of uucp nodes suffer under that kind of flooding. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=232489&group_id=103 From noreply at sourceforge.net Fri Jan 10 01:33:45 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Jan 10 04:31:56 2003 Subject: [Mailman-Developers] [ mailman-Patches-665569 ] make Postfix bounce detection work with newer postfix Message-ID: Patches item #665569, was opened at 2003-01-10 17:33 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=665569&group_id=103 Category: bounce processing Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: James Henstridge (jhenstridge) Assigned to: Nobody/Anonymous (nobody) Summary: make Postfix bounce detection work with newer postfix Initial Comment: Mailman does not recognise bounce messages from newer versions of Postfix. The content-type header on bounce messages looks like this: Content-Type: multipart/report; report-type=delivery-status; boundary="2892E4C0CF.1042189077/quoll.daa.com.au" Mailman only looks for bounce messages with type multipart/mixed, so skips them. The simple solution is to check for both content types (which should allow mailman to continue to work with old postfixes. The attached patch is against 2.0.x (haven't upgraded to MM2.1 yet), but the code is almost identical for 2.1 so the patch should be easy to apply. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=665569&group_id=103 From noreply at sourceforge.net Fri Jan 10 01:36:48 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Jan 10 04:35:08 2003 Subject: [Mailman-Developers] [ mailman-Patches-665569 ] make Postfix bounce detection work with newer postfix Message-ID: Patches item #665569, was opened at 2003-01-10 17:33 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=665569&group_id=103 Category: bounce processing Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: James Henstridge (jhenstridge) Assigned to: Nobody/Anonymous (nobody) Summary: make Postfix bounce detection work with newer postfix Initial Comment: Mailman does not recognise bounce messages from newer versions of Postfix. The content-type header on bounce messages looks like this: Content-Type: multipart/report; report-type=delivery-status; boundary="2892E4C0CF.1042189077/quoll.daa.com.au" Mailman only looks for bounce messages with type multipart/mixed, so skips them. The simple solution is to check for both content types (which should allow mailman to continue to work with old postfixes. The attached patch is against 2.0.x (haven't upgraded to MM2.1 yet), but the code is almost identical for 2.1 so the patch should be easy to apply. ---------------------------------------------------------------------- >Comment By: James Henstridge (jhenstridge) Date: 2003-01-10 17:36 Message: Logged In: YES user_id=146903 Hmm. It seems to have lost the attachment ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=665569&group_id=103 From noreply at sourceforge.net Fri Jan 10 06:05:35 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Jan 10 09:03:43 2003 Subject: [Mailman-Developers] [ mailman-Bugs-665732 ] List-Id should be one line. Message-ID: Bugs item #665732, was opened at 2003-01-10 15:05 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=665732&group_id=103 Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Bernhard Reiter (ber) Assigned to: Nobody/Anonymous (nobody) Summary: List-Id should be one line. Initial Comment: If the List-Id: header gets splitted into several lines, which I could observe on lists I'm on which switched to mailman 2.1 now, it is getting harder to filter the list based on the fixed part of the list id. Filtering would need to look at more than one line. So a procmail pattern (procmail uses egrep an basically work on one line) like :0: *^List-Id:.* $ kmail-incoming would not work anymore reliably when the description of the mailinglist is getting longer. Before mailman 2.1 the above pattern was save against the changes in the description. I know that headers longer than one line are allowed, still I consider is a design bug at mailman does not necessrily need to make filtering harder at this point. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=665732&group_id=103 From barry at python.org Fri Jan 10 09:08:14 2003 From: barry at python.org (Barry A. Warsaw) Date: Fri Jan 10 09:08:50 2003 Subject: [Mailman-Developers] Re: [Mailman-Users] What's wrong with the mailman-users archive? References: <3E1E10E7.6080606@is.kochi-u.ac.jp> <5.1.1.6.0.20030110090319.0430b500@pop3.demon.co.uk> Message-ID: <15902.54222.124426.905015@gargle.gargle.HOWL> We had some problems with mail delivery on python.org/zope.org. We now believe it was a SpamAssassin process that was hanging Exim delivery. We've got a stop gap measure in place which is getting mail flowing again. Looks like the hosage affected the archives. I'll attempt to rebuild them. -Barry From noreply at sourceforge.net Fri Jan 10 07:12:56 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Jan 10 10:11:12 2003 Subject: [Mailman-Developers] [ mailman-Bugs-665791 ] Hiding e-mail addresses breaks mbox archives Message-ID: Bugs item #665791, was opened at 2003-01-10 10:12 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: Open Resolution: None Priority: 5 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. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=665791&group_id=103 From noreply at sourceforge.net Sat Jan 11 04:19:15 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sat Jan 11 07:17:23 2003 Subject: [Mailman-Developers] [ mailman-Feature Requests-459227 ] remove user from all lists Message-ID: Feature Requests item #459227, was opened at 2001-09-06 11:29 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=459227&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: remove user from all lists Initial Comment: Have an automated way of finding the lists a user is on, and removing him from all of them. ---------------------------------------------------------------------- Comment By: David Gibbs (midrangeman) Date: 2003-01-11 06:19 Message: Logged In: YES user_id=86339 Try this script ... it's simple, but it works ... for LIST in `list_lists -b` do echo "Processing $LIST" /usr/local/mailman/bin/remove_members $LIST $* done ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=459227&group_id=103 From noreply at sourceforge.net Sat Jan 11 07:31:18 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sat Jan 11 10:29:25 2003 Subject: [Mailman-Developers] [ mailman-Bugs-666235 ] sync_members bugs (possible fixes included) Message-ID: Bugs item #666235, was opened at 2003-01-11 10:31 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=666235&group_id=103 Category: command line scripts Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Eric Ding (ericding) Assigned to: Nobody/Anonymous (nobody) Summary: sync_members bugs (possible fixes included) Initial Comment: While trying to run sync_members in MM 2.1, I get the following errors: Traceback (most recent call last): File "/home/mailman/bin/sync_members", line 286, in ? main() File "/home/mailman/bin/sync_members", line 258, in main s = email.Utils.formataddr((name, addr)).encode(enc, replace') UnboundLocalError: local variable 'enc' referenced before assignment I worked around this by adding enc = sys.getdefaultencoding() at line 258. But then the script throws an error while trying to remove members! Here's the traceback: File "/home/mailman/bin/sync_members", line 287, in ? main() File "/home/mailman/bin/sync_members", line 276, in main name = mlist.getMemberName(laddr) or '' File "/home/mailman/Mailman/OldStyleMemberships.py", line 128, in getMemberName self.__assertIsMember(member) File "/home/mailman/Mailman/OldStyleMemberships.py", line 113, in __assertIsMember raise Errors.NotAMemberError, member Mailman.Errors.NotAMemberError: xxxxx@hotmail.com If I change line 276 to just set name to '', then the script completes successfully. Is it possible it's trying to reference member name after the member has already been deleted from the list? Eric ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=666235&group_id=103 From noreply at sourceforge.net Sat Jan 11 07:36:10 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sat Jan 11 10:34:17 2003 Subject: [Mailman-Developers] [ mailman-Bugs-666235 ] sync_members bugs (possible fixes included) Message-ID: Bugs item #666235, was opened at 2003-01-11 10:31 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=666235&group_id=103 Category: command line scripts Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Eric Ding (ericding) Assigned to: Nobody/Anonymous (nobody) Summary: sync_members bugs (possible fixes included) Initial Comment: While trying to run sync_members in MM 2.1, I get the following errors: Traceback (most recent call last): File "/home/mailman/bin/sync_members", line 286, in ? main() File "/home/mailman/bin/sync_members", line 258, in main s = email.Utils.formataddr((name, addr)).encode(enc, replace') UnboundLocalError: local variable 'enc' referenced before assignment I worked around this by adding enc = sys.getdefaultencoding() at line 258. But then the script throws an error while trying to remove members! Here's the traceback: File "/home/mailman/bin/sync_members", line 287, in ? main() File "/home/mailman/bin/sync_members", line 276, in main name = mlist.getMemberName(laddr) or '' File "/home/mailman/Mailman/OldStyleMemberships.py", line 128, in getMemberName self.__assertIsMember(member) File "/home/mailman/Mailman/OldStyleMemberships.py", line 113, in __assertIsMember raise Errors.NotAMemberError, member Mailman.Errors.NotAMemberError: xxxxx@hotmail.com If I change line 276 to just set name to '', then the script completes successfully. Is it possible it's trying to reference member name after the member has already been deleted from the list? Eric ---------------------------------------------------------------------- >Comment By: Eric Ding (ericding) Date: 2003-01-11 10:36 Message: Logged In: YES user_id=302756 While I think my fix was sufficient, I think a more elegant one would be to move the offending line (i.e., mlist.getMemberName) further up in its clause, so that it's called before the address is deleted from the list. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=666235&group_id=103 From noreply at sourceforge.net Sun Jan 12 08:01:10 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sun Jan 12 10:59:25 2003 Subject: [Mailman-Developers] [ mailman-Patches-640518 ] SpamAssassin handler Message-ID: Patches item #640518, was opened at 2002-11-19 00:26 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=640518&group_id=103 Category: list administration Group: Mailman 2.2 / 3.0 Status: Open Resolution: None Priority: 5 Submitted By: Jon Parise (jparise) Assigned to: Nobody/Anonymous (nobody) Summary: SpamAssassin handler Initial Comment: I've updated the existing SpamAssassin patch (534577) for Mailman 2.1. ---------------------------------------------------------------------- >Comment By: Jon Parise (jparise) Date: 2003-01-12 11:01 Message: Logged In: YES user_id=485579 I've updated the SpamAssassin handler to report a more detailed reason when a DiscardMessage and HoldMessage exception is raised. ---------------------------------------------------------------------- Comment By: Jon Parise (jparise) Date: 2002-12-31 19:33 Message: Logged In: YES user_id=485579 The attached patch adds the SpamAssassin handler to Mailman's mail processing pipelines. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-11-27 11:13 Message: Logged In: YES user_id=12800 I'm only moving this to the MM2.2/3.0 group so I can concentrate on patches for 2.1. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=640518&group_id=103 From noreply at sourceforge.net Sun Jan 12 14:01:44 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sun Jan 12 16:59:35 2003 Subject: [Mailman-Developers] [ mailman-Bugs-666235 ] sync_members bugs (possible fixes included) Message-ID: Bugs item #666235, was opened at 2003-01-12 04:31 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=666235&group_id=103 Category: command line scripts Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Eric Ding (ericding) Assigned to: Nobody/Anonymous (nobody) Summary: sync_members bugs (possible fixes included) Initial Comment: While trying to run sync_members in MM 2.1, I get the following errors: Traceback (most recent call last): File "/home/mailman/bin/sync_members", line 286, in ? main() File "/home/mailman/bin/sync_members", line 258, in main s = email.Utils.formataddr((name, addr)).encode(enc, replace') UnboundLocalError: local variable 'enc' referenced before assignment I worked around this by adding enc = sys.getdefaultencoding() at line 258. But then the script throws an error while trying to remove members! Here's the traceback: File "/home/mailman/bin/sync_members", line 287, in ? main() File "/home/mailman/bin/sync_members", line 276, in main name = mlist.getMemberName(laddr) or '' File "/home/mailman/Mailman/OldStyleMemberships.py", line 128, in getMemberName self.__assertIsMember(member) File "/home/mailman/Mailman/OldStyleMemberships.py", line 113, in __assertIsMember raise Errors.NotAMemberError, member Mailman.Errors.NotAMemberError: xxxxx@hotmail.com If I change line 276 to just set name to '', then the script completes successfully. Is it possible it's trying to reference member name after the member has already been deleted from the list? Eric ---------------------------------------------------------------------- Comment By: Colin Palmer (tzs) Date: 2003-01-13 11:01 Message: Logged In: YES user_id=658762 Just ran into this one this morning too. Moving the call to mlist.getMemberName(laddr) up to line 266 solved it for me. ---------------------------------------------------------------------- Comment By: Eric Ding (ericding) Date: 2003-01-12 04:36 Message: Logged In: YES user_id=302756 While I think my fix was sufficient, I think a more elegant one would be to move the offending line (i.e., mlist.getMemberName) further up in its clause, so that it's called before the address is deleted from the list. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=666235&group_id=103 From noreply at sourceforge.net Sun Jan 12 22:00:28 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Jan 13 00:58:56 2003 Subject: [Mailman-Developers] [ mailman-Bugs-631186 ] Postfix msg.type Message-ID: Bugs item #631186, was opened at 2002-10-31 03:02 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=631186&group_id=103 Category: bounce detection Group: 2.0.x Status: Open Resolution: None Priority: 1 Submitted By: Gregory Karpinsky, TIV.NET Inc. (tivnet) Assigned to: Nobody/Anonymous (nobody) Summary: Postfix msg.type Initial Comment: In Postfix.py, I replaced 'multipart/mixed' with 'multipart/report' -- and now the bouncing works for me. I have: postfix-20011210_1 mailman-2.0.13 gregory at tiv.net ---------------------------------------------------------------------- Comment By: James Henstridge (jhenstridge) Date: 2003-01-13 14:00 Message: Logged In: YES user_id=146903 I created a patch for this bug in the following report: http://sourceforge.net/tracker/index.php?func=detail&aid=665569&group_id=103&atid=300103 It should work with older postfixes that used 'multipart/mixed' and current ones that use 'multipart/report'. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=631186&group_id=103 From noreply at sourceforge.net Sun Jan 12 23:42:53 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Jan 13 02:40:42 2003 Subject: [Mailman-Developers] [ mailman-Patches-667026 ] HyperArch.py unicode substitution Message-ID: Patches item #667026, was opened at 2003-01-13 07:42 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=667026&group_id=103 Category: Pipermail Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: HyperArch.py unicode substitution Initial Comment: bin/arch and HyperArch.py produced error when i18n characters are present in the message body. I suspect that the text is in unicode string. This patch tests if text is unicode and then make the substitute string unicode. File "/usr/home/mailman/mailman-21/Mailman/Archiver/pipermail.py", line 592, i n add_article temp = self.format_article(article) File "/usr/home/mailman/mailman-21/Mailman/Archiver/HyperArch.py", line 1192, in format_article self.__processbody_URLquote(lines) File "/usr/home/mailman/mailman-21/Mailman/Archiver/HyperArch.py", line 1131, in __processbody_URLquote text = re.sub('@', _(' at '), text) File "/usr/local/lib/python2.1/sre.py", line 63, in sub return _compile(pattern, 0).sub(repl, string, count) File "/usr/local/lib/python2.1/sre.py", line 164, in _sub return _subn(pattern, template, string, count)[0] File "/usr/local/lib/python2.1/sre.py", line 185, in _subn append(filter(m)) File "/usr/local/lib/python2.1/sre.py", line 173, in filter return sre_parse.expand_template(template, match) File "/usr/local/lib/python2.1/sre_parse.py", line 732, in expand_template return string.join(literals, sep) File "/usr/local/lib/python2.1/string.py", line 128, in join return sep.join(words) UnicodeError: ASCII decoding error: ordinal not in range(128) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=667026&group_id=103 From noreply at sourceforge.net Mon Jan 13 06:11:30 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Jan 13 09:09:14 2003 Subject: [Mailman-Developers] [ mailman-Bugs-667167 ] Non-digest options configuration help Message-ID: Bugs item #667167, was opened at 2003-01-13 09:11 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: Open Resolution: None Priority: 5 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 Mon Jan 13 08:20:01 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Jan 13 11:17:44 2003 Subject: [Mailman-Developers] [ mailman-Bugs-667232 ] Collapse CC: header Message-ID: Bugs item #667232, was opened at 2003-01-13 11:20 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: Open Resolution: None Priority: 5 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. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=667232&group_id=103 From noreply at sourceforge.net Mon Jan 13 09:14:20 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Jan 13 12:12:05 2003 Subject: [Mailman-Developers] [ mailman-Feature Requests-667266 ] clear out list archives Message-ID: Feature Requests item #667266, was opened at 2003-01-13 17:14 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=667266&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Jan Schaumann (jschauma) Assigned to: Nobody/Anonymous (nobody) Summary: clear out list archives Initial Comment: On occasion it may be desirable for a lists administrator to empty out the current list archives. For example, if a professor uses the same mailinglist (named after the course number) for one of her classes, she will want to clear out the list archives at the beginning of each semester or move them to a different location. While this is similar to creating a different archive-volume, it is a different functionality. It would be nice if this functionality was available through the list-administrators web-frontend. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=667266&group_id=103 From noreply at sourceforge.net Mon Jan 13 10:55:17 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Jan 13 13:52:57 2003 Subject: [Mailman-Developers] [ mailman-Bugs-665791 ] Hiding e-mail addresses breaks mbox archives Message-ID: Bugs item #665791, was opened at 2003-01-10 10:12 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: Open Resolution: None >Priority: 9 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. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=665791&group_id=103 From wheakory at isu.edu Mon Jan 13 15:32:23 2003 From: wheakory at isu.edu (Kory Wheatley) Date: Mon Jan 13 17:33:13 2003 Subject: [Mailman-Developers] Create mailing list on the web error Message-ID: <3E233E77.88303068@isu.edu> I received the below error when I tried to create a mailing list from the Mailman web interface page. It did add the list into the alias file, but it failed to run "postalias" probably because of permission issue's I'm guessing. I have my alias file in /var/mailman/mailman/data/aliases and the permissions are rw-rw---- mailman mailman aliases. I believe I need to change the permissons to rw-rw-rw- to get this to function properly, but this will leave a big security hole, is there a work around to getting this to function correctly on the web. Bug in Mailman version 2.1 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/mailman/scripts/driver", line 87, in run_main main() File "/var/mailman/mailman/Mailman/Cgi/create.py", line 55, in main process_request(doc, cgidata) File "/var/mailman/mailman/Mailman/Cgi/create.py", line 217, in process_request sys.modules[modname].create(mlist, cgi=1) File "/var/mailman/mailman/Mailman/MTA/Postfix.py", line 226, in create _update_maps() File "/var/mailman/mailman/Mailman/MTA/Postfix.py", line 47, in _update_maps raise RuntimeError, msg % (acmd, status, errstr) RuntimeError: command failed: /usr/sbin/postalias /var/mailman/mailman/data/aliases (status: 1, Operation not permitted) Python information: Variable Value sys.version 2.2.1 (#1, Aug 30 2002, 12:15:30) [GCC 3.2 20020822 (Red Hat Linux Rawhide 3.2-4)] sys.executable /usr/bin/python sys.prefix /usr sys.exec_prefix /usr sys.path /usr sys.platform linux2 Environment variables: Variable Value CONTENT_LENGTH 142 CONTENT_TYPE application/x-www-form-urlencoded HTTP_COOKIE ssogrp1-nda45=ux9.isu.edu-15c%253A3e231b6a%253Aa371957ae32d457c SCRIPT_FILENAME /var/mailman/mailman/cgi-bin/create PYTHONPATH /var/mailman/mailman SERVER_SOFTWARE Apache/2.0.40 (Red Hat Linux) SERVER_ADMIN root@localhost SCRIPT_NAME /mailman/create SERVER_SIGNATURE Apache/2.0.40 Server at kwlinux.isu.edu Port 80 REQUEST_METHOD POST HTTP_HOST kwlinux.isu.edu HTTP_KEEP_ALIVE 300 SERVER_PROTOCOL HTTP/1.1 QUERY_STRING REQUEST_URI /mailman/create 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 (Windows; U; Windows NT 5.1; en-US; rv:1.0.2) Gecko/20021120 Netscape/7.01 HTTP_CONNECTION keep-alive HTTP_REFERER http://kwlinux.isu.edu/mailman/create SERVER_NAME kwlinux.isu.edu REMOTE_ADDR 134.50.249.22 REMOTE_PORT 4423 HTTP_ACCEPT_LANGUAGE en-us, en;q=0.50 UNIQUE_ID Sl0jwoYy@TAAAERzLY0AAAAF SERVER_PORT 80 GATEWAY_INTERFACE CGI/1.1 HTTP_ACCEPT_ENCODING gzip, deflate, compress;q=0.9 SERVER_ADDR 134.50.249.48 DOCUMENT_ROOT /var/www/html -- Kory Wheatley Academic Computing Analyst Sr. Phone 282-3874 ######################################### Everything must point to him. From col.neeson at planetone-asia.com Tue Jan 14 14:12:17 2003 From: col.neeson at planetone-asia.com (Colin Neeson) Date: Mon Jan 13 22:11:12 2003 Subject: [Mailman-Developers] Create mailing list on the web error In-Reply-To: <3E233E77.88303068@isu.edu> Message-ID: I've confirmed it on my box as well - I'm wondering why we are trying to run postaliases - as mailman, we'll never have the correct permissions, no? -colin. > I received the below error when I tried to create a mailing list from > the Mailman web interface page. It did add the list into the alias file, > but it > failed to run "postalias" probably because of permission issue's I'm > guessing. > > I have my alias file in /var/mailman/mailman/data/aliases > and the permissions are rw-rw---- mailman mailman aliases. I > believe I need to change the permissons to rw-rw-rw- to get this to > function properly, but this will leave a big security hole, > is there a work around to getting this to function correctly on the web. > From col.neeson at planetone-asia.com Tue Jan 14 14:16:31 2003 From: col.neeson at planetone-asia.com (Colin Neeson) Date: Mon Jan 13 22:15:22 2003 Subject: [Mailman-Developers] Create mailing list on the web error In-Reply-To: Message-ID: Please ignore that incredibly stupid statement. :-) > I've confirmed it on my box as well - I'm wondering why we are trying to run > postaliases - as mailman, we'll never have the correct permissions, no? > > -colin. > > >> I received the below error when I tried to create a mailing list from >> the Mailman web interface page. It did add the list into the alias file, >> but it >> failed to run "postalias" probably because of permission issue's I'm >> guessing. >> >> I have my alias file in /var/mailman/mailman/data/aliases >> and the permissions are rw-rw---- mailman mailman aliases. I >> believe I need to change the permissons to rw-rw-rw- to get this to >> function properly, but this will leave a big security hole, >> is there a work around to getting this to function correctly on the web. >> > > > _______________________________________________ > Mailman-Developers mailing list > Mailman-Developers@python.org > http://mail.python.org/mailman/listinfo/mailman-developers From fil at rezo.net Tue Jan 14 11:55:26 2003 From: fil at rezo.net (Fil) Date: Tue Jan 14 05:55:36 2003 Subject: [Mailman-Developers] a stupid but useful backup script for Mailman Message-ID: <20030114105526.GF7496@rezo.net> Hello, every day at 11:00 I run this script on my Mailman lists, and receive a nicely formatted email showing who un/subscribed to what list, what did the list owners do (or try to do), and so on. And of course it stores gzipped copies of the list of subscribers and of the configurations in my /var/state/mailman/ folder. I've updated it a bit since I wrote it (version 0.13 was dated year 2000). Here's version 0.14 if it can be of any interest to anyone. It's quick and dirty, but I've been using it for more than two years without a glitch. -- Fil -------------- next part -------------- A non-text attachment was scrubbed... Name: mailman_save_lists.sh Type: application/x-sh Size: 2726 bytes Desc: not available Url : http://mail.python.org/pipermail/mailman-developers/attachments/20030114/0de77d7f/mailman_save_lists.sh From bryanf at samurai.com Tue Jan 14 15:49:56 2003 From: bryanf at samurai.com (Bryan Fullerton) Date: Tue Jan 14 15:50:00 2003 Subject: [Mailman-Developers] Create mailing list on the web error In-Reply-To: <3E233E77.88303068@isu.edu> Message-ID: On Monday, January 13, 2003, at 05:32 PM, Kory Wheatley wrote: > I received the below error when I tried to create a mailing list from > the Mailman web interface page. It did add the list into the alias > file, > but it > failed to run "postalias" probably because of permission issue's I'm > guessing. > > I have my alias file in /var/mailman/mailman/data/aliases > and the permissions are rw-rw---- mailman mailman aliases. Unfortunately, for some reason bin/check_perms doesn't check permissions on the aliases* files in the data directory - this should be fixed (I'll look at a patch in a bit). I suspect that the problem is similar to one I had - your aliases.db file is probably not group writable (or isn't owned by the mailman group). Because all the web scripts run setgid as the mailman group, all files accessed by the web need to be group writable as that group. Here are the permissions on mine (which I just tested): -rw-rw---- 1 root mailman 33256 Jan 14 15:44 aliases -rw-rw-r-- 1 mailman mailman 57344 Jan 14 15:44 aliases.db Thanks, Bryan From bryanf at samurai.com Tue Jan 14 16:03:59 2003 From: bryanf at samurai.com (Bryan Fullerton) Date: Tue Jan 14 16:04:03 2003 Subject: [Mailman-Developers] Create mailing list on the web error In-Reply-To: Message-ID: On Tuesday, January 14, 2003, at 03:49 PM, Bryan Fullerton wrote: > Unfortunately, for some reason bin/check_perms doesn't check > permissions on the aliases* files in the data directory - this should > be fixed (I'll look at a patch in a bit). Just looking at this, there's a comment in checkperms() in Mailman/MTA/Postfix.py as follows: # Make sure the corresponding .db files are owned by the Mailman user. # We don't need to check the group ownership of the file, since # check_perms checks this itself. Was this from an earlier version of 2.1 which checked permissions on */*.db? I don't see anything in check_perms which checks group permissions of data/aliases.db. Bryan From bryanf at samurai.com Tue Jan 14 16:12:04 2003 From: bryanf at samurai.com (Bryan Fullerton) Date: Tue Jan 14 16:12:09 2003 Subject: [Mailman-Developers] mm2.1 - DEFAULT_PLAIN_DIGEST_KEEP_HEADERS Message-ID: Howdy, Nobody seems to be answering questions in mailman-users (is Barry away?), so I'll try this one here. There's a setting in Defaults.py which seems to be just what my customers are looking for to limit the headers being shown in their plain digests - DEFAULT_PLAIN_DIGEST_KEEP_HEADERS. However, this setting appears nowhere in the actual Mailman code except Defaults.py. Was it supposed to be included somewhere? They're rather unhappy that their plain digests are showing things like Precedence and various MIME headers for each message. Thanks, Bryan From barry at python.org Tue Jan 14 16:25:56 2003 From: barry at python.org (Barry A. Warsaw) Date: Tue Jan 14 16:26:26 2003 Subject: [Mailman-Developers] mm2.1 - DEFAULT_PLAIN_DIGEST_KEEP_HEADERS References: Message-ID: <15908.32868.427643.590030@gargle.gargle.HOWL> >>>>> "BF" == Bryan Fullerton writes: BF> Nobody seems to be answering questions in mailman-users (is BF> Barry away?), so I'll try this one here. I've been swamped with Zope work, a upcoming studio project, and getting ready for the Spam conference. Trust me, I'm taking all these messages with me on my laptop. 6:30 hours each way on the train should give me plenty of time to catch up. :) BTW, if anybody else is going to be at the Spam conference, let me know. I'd love to have a chat about Mailman, spam and other stuffis. I'll be getting in Thursday night. -Barry From bryanf at samurai.com Tue Jan 14 16:34:01 2003 From: bryanf at samurai.com (Bryan Fullerton) Date: Tue Jan 14 16:34:05 2003 Subject: [Mailman-Developers] mm2.1 - DEFAULT_PLAIN_DIGEST_KEEP_HEADERS In-Reply-To: <15908.32868.427643.590030@gargle.gargle.HOWL> Message-ID: On Tuesday, January 14, 2003, at 04:25 PM, Barry A. Warsaw wrote: > I've been swamped with Zope work, a upcoming studio project, and > getting ready for the Spam conference. Trust me, I'm taking all these > messages with me on my laptop. 6:30 hours each way on the train > should give me plenty of time to catch up. :) Excellent, I'll keep sending mail and filing bug reports. ;) Bryan From philb at philb.us Tue Jan 14 21:32:39 2003 From: philb at philb.us (Phil Barnett) Date: Tue Jan 14 21:32:44 2003 Subject: [Mailman-Developers] mm2.1 - DEFAULT_PLAIN_DIGEST_KEEP_HEADERS In-Reply-To: <15908.32868.427643.590030@gargle.gargle.HOWL> References: <15908.32868.427643.590030@gargle.gargle.HOWL> Message-ID: <200301142132.39749.philb@philb.us> On Tuesday 14 January 2003 4:25 pm, Barry A. Warsaw wrote: > >>>>> "BF" == Bryan Fullerton writes: > > BF> Nobody seems to be answering questions in mailman-users (is > BF> Barry away?), so I'll try this one here. > > I've been swamped with Zope work, a upcoming studio project, and > getting ready for the Spam conference. Trust me, I'm taking all these > messages with me on my laptop. 6:30 hours each way on the train > should give me plenty of time to catch up. :) > > BTW, if anybody else is going to be at the Spam conference, let me > know. I'd love to have a chat about Mailman, spam and other stuffis. > I'll be getting in Thursday night. I'd love to see mailman get some spam recognition and some thresholds that we can set to deliberately get rid of the most obvious stuff. From noreply at sourceforge.net Tue Jan 14 19:26:32 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Jan 14 22:24:04 2003 Subject: [Mailman-Developers] [ mailman-Patches-645513 ] qmail VERP-enabled delivery handler Message-ID: Patches item #645513, was opened at 2002-11-28 18:58 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=645513&group_id=103 Category: mail delivery Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Colin Palmer (tzs) Assigned to: Nobody/Anonymous (nobody) Summary: qmail VERP-enabled delivery handler Initial Comment: This is based on Peter D. Gray's popen-avoiding Sendmail.py module, tweaked so it can use qmail-inject instead of sendmail and ask qmail to do VERP when the message is delivered, which is much faster than getting Mailman to do it at message injection time. You'll need the following in mm_cfg.py: DELIVERY_MODULE = 'Qmail' SENDMAIL_CMD = '/var/qmail/bin/qmail-inject' DO_QMAIL_VERP = 1 ---------------------------------------------------------------------- Comment By: Ed Lau (edlau) Date: 2003-01-14 19:26 Message: Logged In: YES user_id=675094 Everything works as documented for me right now. Might also need to include a step to make ~alias/.qmail--bounce-default. ---------------------------------------------------------------------- Comment By: Colin Palmer (tzs) Date: 2003-01-08 12:09 Message: Logged In: YES user_id=658762 Yes, python throws an exception if they (or any other config options) are undefined. Set them to 'None' if you don't want logging to happen. ---------------------------------------------------------------------- Comment By: Ed Lau (edlau) Date: 2003-01-08 01:49 Message: Logged In: YES user_id=675094 using the version released 2003-01-07 17:27, with DO_QMAIL_VERP = 0, any post to a list gets posted to all members properly, but also gets shunted. This happened because I didn't have QMAIL_LOG_EVERY_MESSAGE, QMAIL_LOG_SUCCESS, or QMAIL_LOG_FAILURE defined. Is the Email shunted, yet posted event supposed to happen? I'll be testing out VERP later on ---------------------------------------------------------------------- Comment By: Colin Palmer (tzs) Date: 2003-01-07 12:46 Message: Logged In: YES user_id=658762 Oops, should have been comparing it's function with 'SMTPDirect' as well as 'Sendmail'... this version should work a lot better. It doesn't support personalisation or mailman-generated VERP headers, but should do everything else now. Read the the comments at the top of the module for things that need to be in mm_cfg.py for it to work. ---------------------------------------------------------------------- Comment By: Ed Lau (edlau) Date: 2002-12-24 16:32 Message: Logged In: YES user_id=675094 Running as listed except DO_QMAIL_VERP = 0, messages don't appear to have the footer tacked on at the bottom. Everything else (header-wise) seems there. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=645513&group_id=103 From noreply at sourceforge.net Wed Jan 15 07:43:12 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Jan 15 10:40:36 2003 Subject: [Mailman-Developers] [ mailman-Bugs-667232 ] Collapse CC: header Message-ID: Bugs item #667232, was opened at 2003-01-13 11:20 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: Open Resolution: None >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. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=667232&group_id=103 From noreply at sourceforge.net Wed Jan 15 07:43:13 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Jan 15 10:40:40 2003 Subject: [Mailman-Developers] [ mailman-Bugs-666235 ] sync_members bugs (possible fixes included) Message-ID: Bugs item #666235, was opened at 2003-01-11 10:31 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=666235&group_id=103 Category: command line scripts Group: 2.1 (stable) Status: Open Resolution: None >Priority: 7 Submitted By: Eric Ding (ericding) Assigned to: Nobody/Anonymous (nobody) Summary: sync_members bugs (possible fixes included) Initial Comment: While trying to run sync_members in MM 2.1, I get the following errors: Traceback (most recent call last): File "/home/mailman/bin/sync_members", line 286, in ? main() File "/home/mailman/bin/sync_members", line 258, in main s = email.Utils.formataddr((name, addr)).encode(enc, replace') UnboundLocalError: local variable 'enc' referenced before assignment I worked around this by adding enc = sys.getdefaultencoding() at line 258. But then the script throws an error while trying to remove members! Here's the traceback: File "/home/mailman/bin/sync_members", line 287, in ? main() File "/home/mailman/bin/sync_members", line 276, in main name = mlist.getMemberName(laddr) or '' File "/home/mailman/Mailman/OldStyleMemberships.py", line 128, in getMemberName self.__assertIsMember(member) File "/home/mailman/Mailman/OldStyleMemberships.py", line 113, in __assertIsMember raise Errors.NotAMemberError, member Mailman.Errors.NotAMemberError: xxxxx@hotmail.com If I change line 276 to just set name to '', then the script completes successfully. Is it possible it's trying to reference member name after the member has already been deleted from the list? Eric ---------------------------------------------------------------------- Comment By: Colin Palmer (tzs) Date: 2003-01-12 17:01 Message: Logged In: YES user_id=658762 Just ran into this one this morning too. Moving the call to mlist.getMemberName(laddr) up to line 266 solved it for me. ---------------------------------------------------------------------- Comment By: Eric Ding (ericding) Date: 2003-01-11 10:36 Message: Logged In: YES user_id=302756 While I think my fix was sufficient, I think a more elegant one would be to move the offending line (i.e., mlist.getMemberName) further up in its clause, so that it's called before the address is deleted from the list. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=666235&group_id=103 From noreply at sourceforge.net Wed Jan 15 07:43:16 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Jan 15 10:40:46 2003 Subject: [Mailman-Developers] [ mailman-Bugs-664575 ] mailman 2.1 tarball permissions Message-ID: Bugs item #664575, was opened at 2003-01-08 14:24 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=664575&group_id=103 Category: configuring/installing Group: 2.1 (stable) Status: Open Resolution: None >Priority: 7 Submitted By: Barry A. Warsaw (bwarsaw) Assigned to: Nobody/Anonymous (nobody) Summary: mailman 2.1 tarball permissions Initial Comment: The tarball contains world writeable directories and files by default. This may be a problem on systems where users do not have a sane umask or safe directory permissions, allowing an attacker to modify source code that is later compiled (usually as root) and that is installed setuid/setgid (allowing for easy insertion of backdoors). kurt@seifried.org ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=664575&group_id=103 From noreply at sourceforge.net Wed Jan 15 07:43:15 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Jan 15 10:40:49 2003 Subject: [Mailman-Developers] [ mailman-Bugs-665791 ] Hiding e-mail addresses breaks mbox archives Message-ID: Bugs item #665791, was opened at 2003-01-10 10:12 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: Open Resolution: None >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. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=665791&group_id=103 From noreply at sourceforge.net Wed Jan 15 07:43:16 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Jan 15 10:40:51 2003 Subject: [Mailman-Developers] [ mailman-Bugs-665732 ] List-Id should be one line. Message-ID: Bugs item #665732, was opened at 2003-01-10 09:05 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=665732&group_id=103 Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None >Priority: 7 Submitted By: Bernhard Reiter (ber) Assigned to: Nobody/Anonymous (nobody) Summary: List-Id should be one line. Initial Comment: If the List-Id: header gets splitted into several lines, which I could observe on lists I'm on which switched to mailman 2.1 now, it is getting harder to filter the list based on the fixed part of the list id. Filtering would need to look at more than one line. So a procmail pattern (procmail uses egrep an basically work on one line) like :0: *^List-Id:.* $ kmail-incoming would not work anymore reliably when the description of the mailinglist is getting longer. Before mailman 2.1 the above pattern was save against the changes in the description. I know that headers longer than one line are allowed, still I consider is a design bug at mailman does not necessrily need to make filtering harder at this point. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=665732&group_id=103 From noreply at sourceforge.net Wed Jan 15 07:43:17 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Jan 15 10:40:54 2003 Subject: [Mailman-Developers] [ mailman-Bugs-664466 ] 2.0 cookies break 2.1 web auth Message-ID: Bugs item #664466, was opened at 2003-01-08 11:30 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=664466&group_id=103 Category: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None >Priority: 7 Submitted By: Bryan Fullerton (fehwalker) Assigned to: Nobody/Anonymous (nobody) Summary: 2.0 cookies break 2.1 web auth Initial Comment: (as discussed on mailman-users) If there are *any* mm2.0 cookies in the URI-space mm2.1 looks in, the following code will always raise a Cookie.CookieException and return 0. # Treat the cookie data as simple strings, and do application level # decoding as necessary. By using SimpleCookie, we prevent any kind # of security breach due to untrusted cookie data being unpickled # (which is quite unsafe). try: c = Cookie.SimpleCookie(cookiedata) except Cookie.CookieError: return 0 If python's Cookie code (or at least SimpleCookie) doesn't like cookies with :'s in them that'd explain it. This is rather a problem for anyone thinking they could run both mm2.0 and mm2.1 mapped into the same URI-space. Simply put, you can't (without re-auth'ing with every action in 2.1 lists), unless the mm2.1 code is rewritten to handle that exception better. Or unless you nuke all your cookies after every use of a 2.0 list (not just logout - in my testing that doesn't actually remove the cookie, just the cookie's contents). The good news is that this should be no problem once everything is moved to 2.1. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=664466&group_id=103 From noreply at sourceforge.net Wed Jan 15 07:43:17 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Jan 15 10:40:57 2003 Subject: [Mailman-Developers] [ mailman-Bugs-663675 ] Administrative interface vs. non-standard HTTP ports Message-ID: Bugs item #663675, was opened at 2003-01-07 08:02 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: Open Resolution: None >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? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=663675&group_id=103 From noreply at sourceforge.net Wed Jan 15 07:43:18 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Jan 15 10:40:59 2003 Subject: [Mailman-Developers] [ mailman-Bugs-663272 ] held message notice options Message-ID: Bugs item #663272, was opened at 2003-01-06 14:20 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=663272&group_id=103 Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None >Priority: 7 Submitted By: Bryan Fullerton (fehwalker) Assigned to: Nobody/Anonymous (nobody) Summary: held message notice options Initial Comment: I notice that in mm2.1 the "a message has been held" notices to list owners/moderators now include the content of the message. When spam is held, this can result as the notice itself being tagged as spam, which causes them to be thrown in my spam folder. Is there an option to use the smaller sized notices like in 2.0.x? If not, could there be one? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=663272&group_id=103 From noreply at sourceforge.net Wed Jan 15 07:43:18 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Jan 15 10:41:02 2003 Subject: [Mailman-Developers] [ mailman-Bugs-662504 ] Mailman Admin Notification Racing Message-ID: Bugs item #662504, was opened at 2003-01-05 02:41 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=662504&group_id=103 Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None >Priority: 7 Submitted By: Ian Wilson (tacgeek) Assigned to: Nobody/Anonymous (nobody) Summary: Mailman Admin Notification Racing Initial Comment: Hi folks; When a non-list member sends a message to a list, I start to receive emails in a race format...up to about 20 a minute in some instances. Here's how to replicate problem (for those who need to know, and please understand I'm not being a smartbutt, but someone who is just confused with this behavior). 1.) Create new list 2.) Add your email in list administrator's area 3.) Save 4.) Send an email to list from a non-subscribed list 5.) Watch the fireworks on your Admin Email I'm having to go in, stop qrunner, then delete the request.db file before starting qrunner before the race condition stops. Any help would be appreciated! Ian ian@dysfunctional-household.org ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=662504&group_id=103 From noreply at sourceforge.net Wed Jan 15 07:43:13 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Jan 15 10:41:05 2003 Subject: [Mailman-Developers] [ mailman-Bugs-667167 ] Non-digest options configuration help Message-ID: Bugs item #667167, was opened at 2003-01-13 09:11 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: Open Resolution: None >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 Wed Jan 15 07:43:21 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Jan 15 10:41:08 2003 Subject: [Mailman-Developers] [ mailman-Bugs-660733 ] pipermail date handling Message-ID: Bugs item #660733, was opened at 2003-01-01 12:29 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=660733&group_id=103 Category: Pipermail Group: 2.1 (stable) Status: Open Resolution: None >Priority: 7 Submitted By: Bryan Fullerton (fehwalker) Assigned to: Nobody/Anonymous (nobody) Summary: pipermail date handling Initial Comment: I moved my first list to mailman 2.1 and tried to re-generate the pipermail archives (just, ya know, to see how it'd work :), and got the following traceback. This is a list that's been around for a long time (archives back to 1995), and the .mbox file was generated from a majordomo/hypermail archive when it was moved to mailman 2.0 a couple of years ago. Here's a ls -l of the .mbox file: -rw-rw-r-- 1 mailman mailman 17741891 Jan 1 10:36 bryans-list.mbox Here's the traceback: Updating HTML for article 467 Updating HTML for article 468 Updating HTML for article 469 Updating HTML for article 473 Updating HTML for article 472 Pickling archive state into /home/mailman-2.1/archives/private/bryans-list/pipermail.pck Traceback (most recent call last): File "bin/arch", line 187, in ? main() File "bin/arch", line 175, in main archiver.processUnixMailbox(fp, start, end) File "/home/mailman-2.1/Mailman/Archiver/pipermail.py", line 544, in processUnixMailbox m = mbox.next() File "/usr/local/lib/python2.2/mailbox.py", line 34, in next return self.factory(_Subfile(self.fp, start, stop)) File "/home/mailman-2.1/Mailman/Mailbox.py", line 79, in scrubber return mailbox.scrub(msg) File "/home/mailman-2.1/Mailman/Mailbox.py", line 99, in scrub return self._scrubber(self._mlist, msg) File "/home/mailman-2.1/Mailman/Handlers/Scrubber.py", line 132, in process dir = calculate_attachments_dir(mlist, msg, msgdata) File "/home/mailman-2.1/Mailman/Handlers/Scrubber.py", line 93, in calculate_attachments_dir datedir = safe_strftime(fmt, now) File "/home/mailman-2.1/Mailman/Handlers/Scrubber.py", line 77, in safe_strftime return time.strftime(fmt, floatsecs) TypeError: argument must be 9-item sequence, not None I'm guessing it's a header problem in one of the messages, but I'm not sure what. Thanks, Bryan ---------------------------------------------------------------------- Comment By: Bryan Fullerton (fehwalker) Date: 2003-01-01 13:45 Message: Logged In: YES user_id=660772 After some investigation, the following (admittedly invalid) date headers cause tracebacks similar to the above. After reformatting them I'm able to generate the archive. Date: 25 Aug 95 18.00 Date: Thursday, 30 October 1997 3:02pm PT Date: Mon, 29 Nov 1999 Pacific Standard Time Note that these messages *didn't* cause bin/arch|pipermail in mailman 2.0.x to fail, though it probably didn't parse them properly. Perhaps trapping the error and/or skipping these messages might be more useful? It also appears that bin/arch is throwing all messages with dates it can't figure out (after the above were removed) into the current day. An example can be seen at http://lists.samurai.com/pipermail/bryans-list/2003-January/thread.html . I'm unsure if there's any way to better handle this, but just wanted to note it - I can create a separate bug report if it's important. Thanks, Bryan ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=660733&group_id=103 From noreply at sourceforge.net Wed Jan 15 07:43:23 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Jan 15 10:41:11 2003 Subject: [Mailman-Developers] [ mailman-Bugs-214205 ] e-mail&amp;lt;-&amp;gt; usenet gateway Reply-To header (PR#303) Message-ID: Bugs item #214205, was opened at 2000-09-11 16:25 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=214205&group_id=103 Category: nntp/news Group: 2.1 (stable) Status: Open Resolution: None Priority: 7 Submitted By: Nobody/Anonymous (nobody) Assigned to: Barry A. Warsaw (bwarsaw) >Summary: e-mail&amp;lt;-&amp;gt;usenet gateway Reply-To header (PR#303) Initial Comment: Jitterbug-Id: 303 Submitted-By: orion@tribble.dyndns.org Date: Mon, 24 Jul 2000 18:54:02 -0400 (EDT) Version: 2.0beta4 OS: Debian linux potato I'm running a plain e-mail<->usenet gateway. When someone replies to a usenet post through the list, his e-mail client sets an In-Reply-To: header instead of a Reply-To: header. This causes newsreaders to improperly thread messages. I inserted the following bit into Mailman/Handlers/ToUsenet.py at around line 82: # if the message is a reply to a previous post, change the header so # that newsreaders can thread it properly if msg.getheader('in-reply-to'): msg.headers.append('References: %s\n' % msg.getheader('in-reply-to')) del msg['in-reply-to'] I'm happy to say that this solved the problem. (before you laugh at me, take note that I never looked at python before.) ==================================================================== Audit trail: None ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-12-24 00:07 Message: Logged In: YES user_id=12800 Sigh. Very doubtful I'll get to look at the threading issues before MM2.1 final. I'll address this again after the release. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-08-23 18:38 Message: Logged In: YES user_id=12800 Changing the group to 2.1 beta because I want to look at threading issues for gated messages before 2.1 final is released. ---------------------------------------------------------------------- Comment By: Giovanni Lopedote (giuans) Date: 2002-05-01 08:34 Message: Logged In: YES user_id=531451 What a coincidence! I had the same problem and I looked into the code, then modified it to work properly. The coincidence is that my patch is *identical* to yours. So, for sure it works :-) ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2000-09-27 17:00 Message: RFC 2076 says nothing about using In-Reply-To for news, so it might not be a bad idea to copy In-Reply-To to References when gating a message from mail to news. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2000-09-19 12:48 Message: This sounds like the email client in question is broken. Mine for example, correctly inserts References: headers and the news readers properly thread the messages. I'm not inclined to cater to broken email or news clients. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=214205&group_id=103 From noreply at sourceforge.net Wed Jan 15 07:43:21 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Jan 15 10:41:16 2003 Subject: [Mailman-Developers] [ mailman-Bugs-659014 ] decoration problems with German lists Message-ID: Bugs item #659014, was opened at 2002-12-27 09:25 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=659014&group_id=103 Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None >Priority: 7 Submitted By: Jost Krieger (jkrieger) Assigned to: Nobody/Anonymous (nobody) Summary: decoration problems with German lists Initial Comment: 1. German is one of the languages where the mapping to a acharacter set is currently ambiguous: If you want a Euro sign, you have to use iso-8859-15, most people still have iso-8859-1 and some have iso-8859-2 (which also contains all German glyphs). 2. People hat getting there mails in three text/plain parts (partly due to the deficiencies of their mail readers). 3. List owners tend to put plain ASCII into their header and footer files, but this doesn't help, unfortunately, as Mailman still thinks it *must* be iso-8859-1. 4. MIME RFCs recommend taking the lowest compatible charset. This sometimes leads to Mailman messages consisting of three ASCII parts. One longtime solution would be to upgrade everything to Unicode and downgrade it later on as far as possible. This sounds expensive, though. Another, cheaper possibility might be to attach a character set to haeders and footers. Jost ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=659014&group_id=103 From noreply at sourceforge.net Wed Jan 15 07:43:21 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Jan 15 10:41:20 2003 Subject: [Mailman-Developers] [ mailman-Bugs-659011 ] add_members -c publishes member list Message-ID: Bugs item #659011, was opened at 2002-12-27 09:10 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: Open Resolution: None >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 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=659011&group_id=103 From noreply at sourceforge.net Wed Jan 15 07:43:22 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Jan 15 10:41:22 2003 Subject: [Mailman-Developers] [ mailman-Bugs-657443 ] Header and footer in multipart Message-ID: Bugs item #657443, was opened at 2002-12-22 03:08 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=657443&group_id=103 Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None >Priority: 7 Submitted By: Demeilliez Bruno (dive_bruno) Assigned to: Nobody/Anonymous (nobody) Summary: Header and footer in multipart Initial Comment: Hi, I have install mailman 2.1b6 on redhat 7.1. My mailling list is in french and when I received mail from the list with theBat, the header and the footer is in multipart (like at the end). I would like the bady and the footer was in the same message. Can you tell me if it's a bug or a configuration problem ? And how I can resolve it ? Thank's for your help. Bruno Example : .... From: Bruno Demeilliez X-Mailer: The Bat! (v1.62 Christmas Edition) Organization: Aquanaute.com X-Priority: 3 (Normal) Message-ID: <11916819925.20021222110418@aquanaute.com> To: test2@aquanaute.com MIME-Version: 1.0 Subject: Test X-BeenThere: test2@aquanaute.com X-Mailman-Version: 2.1b6 Precedence: list Reply-To: Bruno Demeilliez , test2@aquanaute.com List-Id: List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , Content-Type: multipart/mixed; boundary="===============2617006012765839==" Sender: test2-bounces@aquanaute.com Errors-To: test2-bounces@aquanaute.com --===============2617006012765839== Content-Transfer-Encoding: 8bit content-type: text/plain Bonjour test2, Amicalement, Bruno --- Pour l'équipe d'Aquanaute.com http://www.aquanaute.com SARL de presse Aquanaute.com 8 rue Duployé 38100 Grenoble France Tél et Fax : 04 76 99 93 77 --===============2617006012765839== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit _______________________________________________ Liste de discussion Test2 Liste hébergée et administrée gratuitement par Aquanaute.com Présentation de la liste, Abonnement / Désabonnement : http://www.aquanaute.com/mailman/listinfo/test2 Archives de la liste : http://aquanaute.com/listes/Test2/ --===============2617006012765839==-- ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=657443&group_id=103 From noreply at sourceforge.net Wed Jan 15 07:43:20 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Jan 15 10:41:25 2003 Subject: [Mailman-Developers] [ mailman-Bugs-662163 ] Autoreplies confirm subscription invitations Message-ID: Bugs item #662163, was opened at 2003-01-04 11:05 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=662163&group_id=103 Category: (un)subscribing Group: 2.1 (stable) Status: Open Resolution: None >Priority: 7 Submitted By: Stonewall Ballard (stoneyb) Assigned to: Nobody/Anonymous (nobody) Summary: Autoreplies confirm subscription invitations Initial Comment: I'm not sure of the exact circumstances (maybe personalization needs to be on), bu t i fyou "invite" people to join a mailing list, or, presumably, if someone sends a message to list-join, and there is an autoresponder at that address, the address is subscribed to the list without the subscriber being aware of it. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=662163&group_id=103 From noreply at sourceforge.net Wed Jan 15 07:43:19 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Jan 15 10:41:28 2003 Subject: [Mailman-Developers] [ mailman-Bugs-662490 ] not mimetype return Message-ID: Bugs item #662490, was opened at 2003-01-05 01:44 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: Open Resolution: None >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 Wed Jan 15 07:43:20 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Jan 15 10:41:31 2003 Subject: [Mailman-Developers] [ mailman-Bugs-662127 ] Race condition with summary modification screen Message-ID: Bugs item #662127, was opened at 2003-01-04 09:18 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=662127&group_id=103 Category: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None >Priority: 7 Submitted By: David Shaw (dmshaw) Assigned to: Nobody/Anonymous (nobody) Summary: Race condition with summary modification screen Initial Comment: I just upgraded to 2.1 and noticed an interesting race condition with the summary version of the moderation page. Take this timeline: 1) user@example.com sends 3 messages to the list 2) moderator visits summary moderation page and sees the 3 messages 3) user@example.com sends another message to the list 4) moderator clicks "discard" and submits The end result is that Mailman discards 4 messages, including the latest one that the moderator did not get to see. This does not happen with the old-style "details" version of the moderation page. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=662127&group_id=103 From noreply at sourceforge.net Wed Jan 15 07:43:19 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Jan 15 10:41:34 2003 Subject: [Mailman-Developers] [ mailman-Bugs-662472 ] scrubber arbitrary extension change for attachments Message-ID: Bugs item #662472, was opened at 2003-01-04 23:38 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: Open Resolution: None >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. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=662472&group_id=103 From noreply at sourceforge.net Wed Jan 15 08:57:39 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Jan 15 11:55:12 2003 Subject: [Mailman-Developers] [ mailman-Bugs-658261 ] transcheck error for double % Message-ID: Bugs item #658261, was opened at 2002-12-24 12:29 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=658261&group_id=103 Category: command line scripts >Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Simone Piunno (pioppo) Assigned to: Simone Piunno (pioppo) Summary: transcheck error for double % Initial Comment: As reported by Daniel Buchmann, transcheck doesn't detect correctly when a literal % is expressed as a double %, e.g. %%(<variabelnavn>)s is detected a variable reference to interpolate insted of a simple text. The fix would require a much more complex parser, which is not worth it now but could be in 2.2. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=658261&group_id=103 From noreply at sourceforge.net Wed Jan 15 08:58:33 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Jan 15 11:56:42 2003 Subject: [Mailman-Developers] [ mailman-Bugs-658892 ] traceback EOF read where object expected Message-ID: Bugs item #658892, was opened at 2002-12-27 01:23 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=658892&group_id=103 Category: None Group: 2.0.x >Status: Closed >Resolution: Out of Date Priority: 5 Submitted By: Ubaida Othman (sirdeath) Assigned to: Nobody/Anonymous (nobody) Summary: traceback EOF read where object expected Initial Comment: ive got loads of these errors ... any ideas ? Dec 27 14:20:02 2002 (21760) Delivery exception: EOF read where object expected Dec 27 14:20:02 2002 (21760) Traceback (most recent call last): File "/home/ml/mailman/Mailman/Handlers/HandlerAPI.py", line 82, in do_pipeline func(mlist, msg, msgdata) File "/home/ml/mailman/Mailman/Handlers/Hold.py", line 152, in process hold_for_approval(mlist, msg, msgdata, NonMemberPost) File "/home/ml/mailman/Mailman/Handlers/Hold.py", line 218, in hold_for_approval mlist.HoldMessage(msg, reason, msgdata) File "/home/ml/mailman/Mailman/ListAdmin.py", line 145, in HoldMessage self.__opendb() File "/home/ml/mailman/Mailman/ListAdmin.py", line 69, in __opendb self.__db = marshal.load(fp) EOFError: EOF read where object expected im running mailman 2.0.13 and python Python 2.2.2 ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-01-15 11:58 Message: Logged In: YES user_id=12800 Closing all non-security related 2.0 bugs. If this is still a problem in Mailman 2.1, please resubmit. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=658892&group_id=103 From noreply at sourceforge.net Wed Jan 15 08:59:50 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Jan 15 11:57:17 2003 Subject: [Mailman-Developers] [ mailman-Bugs-655827 ] names w/ .'s + accents held for approval Message-ID: Bugs item #655827, was opened at 2002-12-18 10:55 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=655827&group_id=103 Category: mail delivery Group: 2.0.x >Status: Closed >Resolution: Out of Date Priority: 5 Submitted By: Rob Ellis (robellis) Assigned to: Nobody/Anonymous (nobody) Summary: names w/ .'s + accents held for approval Initial Comment: people who use microsoft outlook (at least) and have accented characters and .'s in their names (e.g. "F. André") have their names encoded in the From: line as per RFC 2049, like =?Windows-1252?Q?F._Andr=E9?= the unescaped dots break Mailman's RFC822 parsing, so the user's messages are held for approval when member_posting_only=1, even if they're subscribed. one fix is to escape the unescaped dots -- patch for rfc822.py attached... - rob -- Rob Ellis System administrator, Web Networks ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-01-15 11:59 Message: Logged In: YES user_id=12800 I believe this has been fixed in MM2.1. If not, please resubmit. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=655827&group_id=103 From noreply at sourceforge.net Wed Jan 15 09:02:32 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Jan 15 11:59:50 2003 Subject: [Mailman-Developers] [ mailman-Bugs-611185 ] rmlist doesn't delete lock files Message-ID: Bugs item #611185, was opened at 2002-09-18 13:23 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=611185&group_id=103 Category: command line scripts >Group: 2.1 (stable) Status: Open Resolution: None >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 Wed Jan 15 09:03:34 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Jan 15 12:01:38 2003 Subject: [Mailman-Developers] [ mailman-Bugs-612784 ] feature-request : Use of Spamassassintag Message-ID: Bugs item #612784, was opened at 2002-09-22 06:20 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=612784&group_id=103 Category: mail delivery Group: 2.0.x >Status: Closed >Resolution: Invalid Priority: 1 Submitted By: Alexandre Dulaunoy (adulau) Assigned to: Nobody/Anonymous (nobody) Summary: feature-request : Use of Spamassassintag Initial Comment: Mail::SpamAssassin is adding a tag when He suspects to be a spam. Do you plan to add a test on it and not forward mail into the mailing if the tag is present ? It's also useful when the list is moderated. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-01-15 12:03 Message: Logged In: YES user_id=12800 Closing this as not-a-bug. I believe there's a patch to add such functionality, and I'm working on integrating other spam detection technology for the next version. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=612784&group_id=103 From noreply at sourceforge.net Wed Jan 15 11:05:11 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Jan 15 14:02:35 2003 Subject: [Mailman-Developers] [ mailman-Bugs-668664 ] ValueError processing held messages Message-ID: Bugs item #668664, was opened at 2003-01-15 14:05 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=668664&group_id=103 Category: None Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Bryan Fullerton (fehwalker) Assigned to: Nobody/Anonymous (nobody) Summary: ValueError processing held messages Initial Comment: I've seen this problem both with cron/checkdbs and now with the admindb CGI. I'm submitting this one because it has lots of detail. I've had some luck playing with try/except in checkdbs, but that just skips the entry that's having problems, doesn't actually deal with it. Jan 14 18:21:47 2003 admin(54023): @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ admin(54023): [----- Mailman Version: 2.1 -----] admin(54023): [----- Traceback ------] admin(54023): Traceback (most recent call last): admin(54023): File "/home/mailman-2.1/scripts/driver", line 87, in run_main admin(54023): main() admin(54023): File "/home/mailman-2.1/Mailman/Cgi/admindb.py", line 226, in main admin(54023): num = show_pending_subs(mlist, form) admin(54023): File "/home/mailman-2.1/Mailman/Cgi/admindb.py", line 287, in show_pending_subs admin(54023): time, addr, fullname, passwd, digest, lang = mlist.GetRecord(id) admin(54023): ValueError: unpack tuple of wrong size admin(54023): [----- Python Information -----] admin(54023): sys.version = 2.2.2 (#1, Dec 1 2002, 11:44:59) [GCC 2.95.3 20010315 (release) [FreeBSD]] admin(54023): sys.executable = /usr/local/bin/python admin(54023): sys.prefix = /usr/local admin(54023): sys.exec_prefix = /usr/local admin(54023): sys.path = /usr/local admin(54023): sys.platform = freebsd4 admin(54023): [----- Environment Variables -----] admin(54023): PATH_INFO: /wnet admin(54023): HTTP_ACCEPT: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, application/vnd.ms-powerpoint, application/vnd.ms-excel, application/msword, */* admin(54023): CONTENT_TYPE: application/x-www-form-urlencoded admin(54023): HTTP_REFERER: http://lists.samurai.com/mailman/admindb/wnet admin(54023): SERVER_SOFTWARE: Apache/1.3.27 (Unix) admin(54023): PYTHONPATH: /home/mailman-2.1 admin(54023): SCRIPT_FILENAME: /home/mailman-2.1/cgi-bin/admindb admin(54023): SERVER_ADMIN: webmaster@samurai.com admin(54023): SCRIPT_NAME: /mailman/admindb admin(54023): SCRIPT_URI: http://lists.samurai.com/mailman/admindb/wnet admin(54023): SERVER_SIGNATURE:
Apache/1.3.27 Server at lists.samurai.com Port 80
admin(54023): admin(54023): REQUEST_METHOD: POST admin(54023): HTTP_HOST: lists.samurai.com admin(54023): SCRIPT_URL: /mailman/admindb/wnet admin(54023): SERVER_PROTOCOL: HTTP/1.1 admin(54023): QUERY_STRING: admin(54023): HTTP_CACHE_CONTROL: no-cache admin(54023): REQUEST_URI: /mailman/admindb/wnet admin(54023): CONTENT_LENGTH: 18 admin(54023): PATH_TRANSLATED: /usr/local/www/data/wnet admin(54023): HTTP_USER_AGENT: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; Q312461) admin(54023): HTTP_CONNECTION: Keep-Alive admin(54023): SERVER_NAME: lists.samurai.com admin(54023): REMOTE_ADDR: 65.93.181.251 admin(54023): REMOTE_PORT: 4749 admin(54023): HTTP_ACCEPT_LANGUAGE: en-ca admin(54023): UNIQUE_ID: PiSbis3PHE8AAKK7eCk admin(54023): SERVER_PORT: 80 admin(54023): GATEWAY_INTERFACE: CGI/1.1 admin(54023): REMOTE_HOST: sherbrooke-hse-ppp3609836.sympatico.ca admin(54023): HTTP_ACCEPT_ENCODING: gzip, deflate admin(54023): SERVER_ADDR: 205.207.28.81 admin(54023): DOCUMENT_ROOT: /usr/local/www/data Bryan ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=668664&group_id=103 From noreply at sourceforge.net Wed Jan 15 11:35:46 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Jan 15 14:33:03 2003 Subject: [Mailman-Developers] [ mailman-Patches-668685 ] sys.exit handling by script/driver Message-ID: Patches item #668685, was opened at 2003-01-15 19:35 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: 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 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 < ../ ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=668685&group_id=103 From noreply at sourceforge.net Wed Jan 15 12:09:24 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Jan 15 15:08:31 2003 Subject: [Mailman-Developers] [ mailman-Patches-444884 ] Integration of Mailman & htdig for archi Message-ID: Patches item #444884, was opened at 2001-07-26 18:27 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=444884&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: 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-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 Jan 15 12:14:00 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Jan 15 15:11:47 2003 Subject: [Mailman-Developers] [ mailman-Patches-444884 ] Integration of Mailman & htdig for archi Message-ID: Patches item #444884, was opened at 2001-07-26 18:27 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=444884&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: 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-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 Jan 15 12:18:33 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Jan 15 15:19:56 2003 Subject: [Mailman-Developers] [ mailman-Patches-444884 ] Integration of Mailman & htdig for archi Message-ID: Patches item #444884, was opened at 2001-07-26 18:27 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=444884&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: 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-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 ayanic01 at cs.fiu.edu Wed Jan 15 16:35:32 2003 From: ayanic01 at cs.fiu.edu (Asher Yanich) Date: Wed Jan 15 16:35:39 2003 Subject: [Mailman-Developers] problem with CGI after upgrade Message-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I get: Mailman CGI error!!! The Mailman CGI wrapper encountered a fatal error. This entry is being stored in your syslog: No such file or directory Can someone please point me to the cause of this problem? I am stumped. THANKS, - -asher -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE+JdQmAvdNfNYuUt8RAtIhAJ9wYwbteJfAL3fYzF3xbWyNfgtH6QCfVWpM L54gZ4hM8rWFd7+VBOaPcTw= =RvGc -----END PGP SIGNATURE----- From donn at u.washington.edu Wed Jan 15 13:37:56 2003 From: donn at u.washington.edu (Donn Cave) Date: Wed Jan 15 16:38:31 2003 Subject: [Mailman-Developers] mm2.1 - DEFAULT_PLAIN_DIGEST_KEEP_HEADERS Message-ID: <200301152137.h0FLbuHh012172@mailhost1.u.washington.edu> Quoth Phil Barnett : | On Tuesday 14 January 2003 4:25 pm, Barry A. Warsaw wrote: ... |> BTW, if anybody else is going to be at the Spam conference, let me |> know. I'd love to have a chat about Mailman, spam and other stuffis. |> I'll be getting in Thursday night. | | I'd love to see mailman get some spam recognition and some thresholds that we | can set to deliberately get rid of the most obvious stuff. The statistical approach sounds very good to me for lists - I guess the spambayes project that some notable Python people have been working with falls in that category, I've been using something called "spamoracle", etc. In this case, though, before you start thinking about thresholds, you have to train the classifier for your list's traffic - furnish it with examples of good and bad mail. After a couple of batches, it's surprisingly accurate with my own mail, and since lists should normally follow a narrower range of subject matter it ought to do even better there. I haven't thought of a real good way to set up the training, though. You want to be able to select particular messages from the archives and feed them into the classifier intact (headers and everything.) That sounds like writing a new archive index from the ground up (which might be a good thing anyway, but I hope I'm wrong and that isn't necessary!) Donn Cave, donn@u.washington.edu From ayanic01 at cs.fiu.edu Wed Jan 15 17:20:32 2003 From: ayanic01 at cs.fiu.edu (Asher Yanich) Date: Wed Jan 15 17:20:38 2003 Subject: [Mailman-Developers] problem with CGI after upgrade In-Reply-To: References: Message-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 arg, mail server was running a different install of linux than our standard clone, python2.2 was installed. - -asher On Wed, 15 Jan 2003, Asher Yanich wrote: > --[PinePGP]--------------------------------------------------[begin]-- > > I get: > Mailman CGI error!!! > The Mailman CGI wrapper encountered a fatal error. This entry is being > stored in your syslog: > > No such file or directory > > > Can someone please point me to the cause of this problem? I am stumped. > > THANKS, > -asher > --[PinePGP]----------------------------------------------------------- > gpg: Signature made Wed 15 Jan 2003 04:35:34 PM EST using DSA key ID D62E52DF > gpg: Good signature from "Asher Yanich " > --[PinePGP]----------------------------------------------------[end]-- > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE+Jd6yAvdNfNYuUt8RAjqYAJ9eYBXCTcRImbDv+9cUrphRx1ZMYwCdG+CZ qt05PqXJ3c4Y/5UmbXbtXhk= =BiAg -----END PGP SIGNATURE----- From noreply at sourceforge.net Wed Jan 15 16:17:17 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Jan 15 19:14:32 2003 Subject: [Mailman-Developers] [ mailman-Patches-668819 ] improve plain-ness and i18n-ness of plain-text digest Message-ID: Patches item #668819, was opened at 2003-01-16 00:17 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=668819&group_id=103 Category: internationalization Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: improve plain-ness and i18n-ness of plain-text digest Initial Comment: When the mail charset and list charset are different like Japanese, plain text digests become mixture of these charsets and result in mojibake. This patch converts the message into list specific charset and deliver the digest with single charset. It also takes care of the message headers to retain in the digest according to the setting of mm_cfg.DEFAULT_PLAIN_DIGEST_KEEP_HEADERS. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=668819&group_id=103 From tkikuchi at is.kochi-u.ac.jp Thu Jan 16 09:24:30 2003 From: tkikuchi at is.kochi-u.ac.jp (Tokio Kikuchi) Date: Wed Jan 15 19:24:44 2003 Subject: [Mailman-Developers] mm2.1 - DEFAULT_PLAIN_DIGEST_KEEP_HEADERS References: Message-ID: <3E25FBBE.9070702@is.kochi-u.ac.jp> Hi, Please try this patch. https://sourceforge.net/tracker/index.php?func=detail&aid=668819&group_id=103&atid=300103 Bryan Fullerton wrote: > Howdy, > > Nobody seems to be answering questions in mailman-users (is Barry > away?), so I'll try this one here. > > There's a setting in Defaults.py which seems to be just what my > customers are looking for to limit the headers being shown in their > plain digests - DEFAULT_PLAIN_DIGEST_KEEP_HEADERS. However, this setting > appears nowhere in the actual Mailman code except Defaults.py. Was it > supposed to be included somewhere? They're rather unhappy that their > plain digests are showing things like Precedence and various MIME > headers for each message. > > Thanks, > > Bryan > > > _______________________________________________ > Mailman-Developers mailing list > Mailman-Developers@python.org > http://mail.python.org/mailman/listinfo/mailman-developers > > -- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ From noreply at sourceforge.net Wed Jan 15 20:21:54 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Jan 15 23:19:22 2003 Subject: [Mailman-Developers] [ mailman-Patches-573505 ] usenet threading improvements Message-ID: Patches item #573505, was opened at 2002-06-25 01:59 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=573505&group_id=103 Category: mail delivery Group: Mailman 2.0.x Status: Open Resolution: None Priority: 1 Submitted By: Mark Weaver (mdw21) Assigned to: Nobody/Anonymous (nobody) Summary: usenet threading improvements Initial Comment: Basically message-id munging for all messages. Might be better as an option? This helps with threading in usenet gating, as what happens is this: someone sends a mail with message- id foo@bar.com gating replaces the message-id with mailman.123.456.list@list.com list member replies via mail, "in-reply-to" header is set to the foo@bar.com now when the message is gated it can't thread because in-reply-to: (which is translated into references:) is wrong. Solution is to munge all message-ids. Doesn't really do any harm AFAICT. ---------------------------------------------------------------------- Comment By: Nicolas Marchildon (elecnix) Date: 2003-01-15 23:21 Message: Logged In: YES user_id=106549 The submitted patch does not do what it should to. The calls to time.time() will not return the same thing as in ToUsenet.py. I don't know much about the internals of Mailman, and not much either about Python, so I don't really know where to store the "correct" message ID so that it is generated once, and used in both places. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=573505&group_id=103 From tneff at bigfoot.com Wed Jan 15 23:27:45 2003 From: tneff at bigfoot.com (Tom Neff) Date: Wed Jan 15 23:25:46 2003 Subject: [Mailman-Developers] Sourceforge notifications considered harmful In-Reply-To: References: Message-ID: <945946531.1042673265@[192.168.254.79]> It completely sucks, and has completely sucked ever since the decision was made a few months ago, that Mailman-Developers gets Cc'd on every Sourceforge update. I'm sure Barry (or whoever) felt they were doing a service, but it has practically killed discussion here and cost us many, many kilobytes of repetitive cruft, since everytime anyone adds a "yeah me too" comment to the end of a bug, the ENTIRE thing has to be reposted here. If you don't actually want to have a Developers discussion list, then shut it down and let people submit stuff via Sourceforge only. If you do want one, let us have one. Sure, it seems legit to let the list know what bugs have been added/updated. So run a nightly script that prepares a one-line-per-bug summary of adds & updates, and let that be a single (very useful) message on the list. From noreply at sourceforge.net Wed Jan 15 20:29:43 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Jan 15 23:27:04 2003 Subject: [Mailman-Developers] [ mailman-Bugs-451475 ] header munging ruins threading Message-ID: Bugs item #451475, was opened at 2001-08-16 03:55 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=451475&group_id=103 Category: nntp/news Group: 2.1 (stable) Status: Open Resolution: None Priority: 7 Submitted By: CrackMonkey (monkeymaster) Assigned to: Barry A. Warsaw (bwarsaw) Summary: header munging ruins threading Initial Comment: The header hacking done by ToUsenet.py ruins threading in mail! It takes a perfectly good message ID, and throws it away! news replies to a mail message appear to be replies to the parent (since the news messag references contain the references of the parent + some crazy mailman message ID). This is bogus. At the very least, could you add the real message ID somewhere so that newsreaders will include it in the references headers? Some of us actually use threaded mailers, you know! ---------------------------------------------------------------------- Comment By: Nicolas Marchildon (elecnix) Date: 2003-01-15 23:29 Message: Logged In: YES user_id=106549 The solution is probably not to remove munging, but to munge both mail and usenet message IDs. See patch #573505 ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-04-12 12:16 Message: Logged In: YES user_id=12800 The problem is that many NNTP servers are really picky about message-id's; they won't allow duplicates, and they won't allow cross-postings with the same message-id. I suppose if the message had an id we could try to preserve it, attempt a post, and if that's rejected by the nntpd, we could try again with our own crafted message-id. I'm up for any suggestions that are rfc-compliant and work with the widest range of currently existing nntpds. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=451475&group_id=103 From bigdog at dogpound.vnet.net Wed Jan 15 23:59:28 2003 From: bigdog at dogpound.vnet.net (Matthew Davis) Date: Wed Jan 15 23:55:00 2003 Subject: [Mailman-Developers] Sourceforge notifications considered harmful In-Reply-To: <945946531.1042673265@[192.168.254.79]>; from tneff@bigfoot.com on Wed, Jan 15, 2003 at 11:27:45PM -0500 References: <945946531.1042673265@[192.168.254.79]> Message-ID: <20030115235928.A4644@dogpound.vnet.net> * Tom Neff (tneff@bigfoot.com) wrote: > If you don't actually want to have a Developers discussion list, then shut > it down and let people submit stuff via Sourceforge only. If you do want > one, let us have one. How about a mailman-developers and mailman-bugsandpatches list? ---------------------------------------------- | Matthew Davis /\ http://dogpound.vnet.net/ | |--------------------------------------------| | Wednesday, January 15, 2003 / 11:57PM | ---------------------------------------------- Definition of Terror: A female Klingon having a bad hair day. From noreply at sourceforge.net Wed Jan 15 21:11:00 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Jan 16 00:08:27 2003 Subject: [Mailman-Developers] [ mailman-Patches-573505 ] usenet threading improvements Message-ID: Patches item #573505, was opened at 2002-06-25 01:59 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=573505&group_id=103 Category: mail delivery Group: Mailman 2.0.x Status: Open Resolution: None Priority: 1 Submitted By: Mark Weaver (mdw21) Assigned to: Nobody/Anonymous (nobody) Summary: usenet threading improvements Initial Comment: Basically message-id munging for all messages. Might be better as an option? This helps with threading in usenet gating, as what happens is this: someone sends a mail with message- id foo@bar.com gating replaces the message-id with mailman.123.456.list@list.com list member replies via mail, "in-reply-to" header is set to the foo@bar.com now when the message is gated it can't thread because in-reply-to: (which is translated into references:) is wrong. Solution is to munge all message-ids. Doesn't really do any harm AFAICT. ---------------------------------------------------------------------- Comment By: Nicolas Marchildon (elecnix) Date: 2003-01-16 00:11 Message: Logged In: YES user_id=106549 I solved the problem by adding the munging code to DeliverToList, in HandlerAPI.py, right before the message is sent in the delivery pipeline, and removed it from ToUsenet.py and CookHeaders.py. This way, the Message-ID header is calculated only once, and used for all the steps of the pipeline. Nicolas Marchildon ---------------------------------------------------------------------- Comment By: Nicolas Marchildon (elecnix) Date: 2003-01-15 23:21 Message: Logged In: YES user_id=106549 The submitted patch does not do what it should to. The calls to time.time() will not return the same thing as in ToUsenet.py. I don't know much about the internals of Mailman, and not much either about Python, so I don't really know where to store the "correct" message ID so that it is generated once, and used in both places. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=573505&group_id=103 From barry at python.org Thu Jan 16 00:12:07 2003 From: barry at python.org (Barry A. Warsaw) Date: Thu Jan 16 00:12:34 2003 Subject: [Mailman-Developers] Sourceforge notifications considered harmful References: <945946531.1042673265@[192.168.254.79]> Message-ID: <15910.16167.93291.953083@gargle.gargle.HOWL> >>>>> "TN" == Tom Neff writes: TN> It completely sucks, and has completely sucked ever since the TN> decision was made a few months ago, that Mailman-Developers TN> gets Cc'd on every Sourceforge update. I'm sure Barry (or TN> whoever) felt they were doing a service, but it has TN> practically killed discussion here That's definitely the /last/ thing I wanted to do! I think it's worse now because 2.1 is out, people are finding it, playing with it, and are submitting bugs and patches against it. Here's a proposal: a. I create a mailman-coders@python.org list b. Send SF tracker messages to this list instead of mailman-developers c. Possibly (and I think optimally), retire mailman-checkins and send the cvs diffs to mailman-coders as well. Personally, I don't see the need for two different lists, but -checkins is more than this list would do. So vote by the -1/0/+1 rules against these options: 1. Do nothing, everything's fine just the way it is 2. Do a + b 3. Do a + b + c -Barry From CHALUB at fgv.br Fri Jan 3 15:09:54 2003 From: CHALUB at fgv.br (Fabricio Chalub) Date: Thu Jan 16 00:14:15 2003 Subject: [Mailman-Developers] GetScriptURL and "absolute=1" Message-ID: <3BE65222F383D611BE1E00D0B7B60A55B0F029@FGVRJ23> Hi, 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 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? If this is okay, I can provide a patch (although there are very few lines that need changing). Thanks, Fabricio Chalub From chuqui at plaidworks.com Tue Jan 14 07:25:11 2003 From: chuqui at plaidworks.com (Chuq Von Rospach) Date: Thu Jan 16 00:14:24 2003 Subject: [Mailman-Developers] update on: AOL dropping e-mail Message-ID: <5F26A28A-27D4-11D7-8B3B-0003934516A8@plaidworks.com> FYI for those that are interested, I've posted an update on my earlier note on AOL dropping e-mail. I wish I had good news, but... chuq -- Chuq Von Rospach, Architech chuqui@plaidworks.com -- http://www.plaidworks.com/chuqui/blog/ But I can hear the sound Of slamming doors and folding chairs And that's a sound they'll never know From dhesi at rahul.net Wed Jan 15 20:48:07 2003 From: dhesi at rahul.net (dhesi@rahul.net) Date: Thu Jan 16 00:14:46 2003 Subject: [Mailman-Developers] bug report : nntp connect failure does not specify host nameZ Message-ID: Hi, I'm sorry, I tried to submit a bug report via the SourceForge project page, but could not find any buttons or links on the 'bugs' and 'tracker' pages that would let me submit a new bug report. I am using Mailman 2.0.13 as included RedHat Linux 7.2. When mailman is unable to make an nntp connection to a News host, it returns an error of the form shown below. In this error message it does not specify to which host it was trying to connect. This seems like a minor thing. But in fact, due to this omission, I spent a lot of time debugging a connection failure problem. I did not realize that due to a DNS and /etc/hosts inconsistency, mailman was trying to connect to the wrong host. Rahul ---------- Forwarded message ---------- Date: Wed, 15 Jan 2003 20:05:36 -0800 (PST) From: Cron Daemon To: mailman@rahul.net Subject: Cron /usr/bin/python -S /var/mailman/cron/gate_news Traceback (innermost last): File "/var/mailman/cron/gate_news", line 222, in ? main() File "/var/mailman/cron/gate_news", line 203, in main process_lists(lock) File "/var/mailman/cron/gate_news", line 148, in process_lists conn, first, last = open_newsgroup(mlist) File "/var/mailman/cron/gate_news", line 75, in open_newsgroup password=mm_cfg.NNTP_PASSWORD) File "/var/mailman/Mailman/pythonlib/nntplib.py", line 111, in __init__ self.sock.connect((self.host, self.port)) socket.error: (113, 'No route to host') == END == From erik at eskimo.com Wed Jan 8 23:00:52 2003 From: erik at eskimo.com (Erik) Date: Thu Jan 16 00:15:14 2003 Subject: [Mailman-Developers] Hello folks, I just joined the list Message-ID: <0c9f01c2b7ac$d9e3fb50$0300a8c0@redmond.corp.microsoft.com> I'm in serious need.... I'm on a mailinglist run on (X-Mailman-Version: 2.0.8). This list is desperately in need of the "limit posts per day" feature. I see it on the wishlist at (http://www.list.org/todo.html): Add a limit on the number of posts from any one individual within a period of time (1 post per day, 10 per week, etc). Do you have an idea of how hard this would be to add? I've been around computers and programming for 30 years, starting with Fortran in high school on a CDC 3300, including assembler (Motorola 68K), C (Unix 4.1 BSD - 4.3 BSD, Solaris), C++, C# (NT, XP, etc), some scripting with sh and csh, perl, etc., but no Python (yet). I'm sure I could eventually figure it out. I'd like to volunteer to do the work, but I'd like to know what I'm up against first. I've downloaded the 2.0.8 sources but haven't had time to look through them carefully. Any words of wisdom (sure, it's easy ... forget it, it's hopeless)? Thanks, Erik From fred at bytesforall.org Tue Jan 14 02:19:53 2003 From: fred at bytesforall.org (FREDERICK NORONHA) Date: Thu Jan 16 00:15:46 2003 Subject: [Mailman-Developers] Re: [LO] Huge messages... a problem while moderating In-Reply-To: <15905.42861.373972.838280@gargle.gargle.HOWL> References: <15905.42861.373972.838280@gargle.gargle.HOWL> Message-ID: <0301140219530U.01752@news.goa.bytesforall.org> Just soem replies: (i) I worked on Majordomo earlier, and found it (despite its other shortcomings and lack-of-development for years) to be rather precise and easy-to-operate if one opted to send in commands via email. Perhaps Majordomo's strong dependence on email is based on the fact that it evolved largely in a pre-Web world. But we must remember that email is still the most affordable means of access for many, it is less time-consuming to use, and in parts of the globe where people like me live (India) it's sometimes not practical to expect to stay on the web for long (read, more than ten minutes). (ii) Easier URLs to remember the Mailman pages would help. Looks like every sysadm has his / her own way of setting up the URLs leading to the approve-page etc (iii) When on the Net, is it not possible to have one simple step to decide whether to subscribe someone in a digest mode or non-digest mode? As of now, I first need to subscribe that someone; then go back and locate his/her address rightly, and then change the mode to digest/non-digest as required. (iv) Re the ability to search for a member's address, in case he/she needs to be removed, this is what I meant. Imaging I have an 800 member list. The person who wants to be removed doesn't remember exactly which address he subscribed on. It could be one of many options, containing the word, say, *abilio*. Is it not possible for me to do a search in the entire database of subscribers, and just pull up all the *abilios* to see which might be the possible subscriber? This would help greatly, rather than having to search manually across the 800 member list. FN From jonah at urban.net Tue Jan 14 11:14:50 2003 From: jonah at urban.net (Jonah Crawford) Date: Thu Jan 16 00:17:30 2003 Subject: [Mailman-Developers] subscribing via email... Message-ID: <4EEFF287-27DB-11D7-BBD7-0003934273FA@urban.net> what parameter can I include in the email to override the default 'plain' so that MIMEs are included for the subscriber when receiving their daily newsletter? Many thanks! -j From r.g.steltenpool at student.utwente.nl Fri Jan 10 15:58:39 2003 From: r.g.steltenpool at student.utwente.nl (Ruud Steltenpool) Date: Thu Jan 16 00:18:00 2003 Subject: [Mailman-Developers] preventing double messages Message-ID: <003e01c2b8b8$c2d7a1c0$43e15982@kabel.utwente.nl> Hello, I'm on a few lists of 1 and the same mailman. It occurs that someone sends 1 e-mail to multiple of those lists. Then i get the same message more than once. This could be prevented: For every incoming mail: Not start sending to all members of all receiving lists right away, but hold a temp-list in memory of all receiving members for this particular message. Then when all lists are processed, remove doubles from the temp-list and THEN send. cheers. From terri.slater at washburn.edu Fri Jan 3 11:12:04 2003 From: terri.slater at washburn.edu (terri slater) Date: Thu Jan 16 00:19:05 2003 Subject: [Mailman-Developers] RE: Listserv Maximum Message-ID: Is there a listserv maximum number? ************************************************************************ * * "You grow up the day you have your first * * Terri Slater real laugh - at yourself. * * Web Programmer Ethel Barrymore * * Washburn University * * 785-231-1010 ext 2302 * ************************************************************************** From spacey-mailman at lenin.nu Wed Jan 15 21:19:54 2003 From: spacey-mailman at lenin.nu (Peter C. Norton) Date: Thu Jan 16 00:19:57 2003 Subject: [Mailman-Developers] Hello folks, I just joined the list In-Reply-To: <0c9f01c2b7ac$d9e3fb50$0300a8c0@redmond.corp.microsoft.com> References: <0c9f01c2b7ac$d9e3fb50$0300a8c0@redmond.corp.microsoft.com> Message-ID: <20030116051954.GH14875@lenin.nu> Its probably not too hard. In my experience (I wrote a patch that I posted here to prevent mailman 2.0.x from allowing posts from non-subscribers since I didn't want to deal with manually dropping all the spam) you could auto-reject above a certian number by adding a check against a python dictionary (essentially an associative array) that contains an email address as the key and the last [n] posts - each one with a timestamp or something like that. You can check the patch I posted a while ago, or if you want I can send you my patch since I think you'd want to reject posts in the same part of Hold.py. -Peter On Wed, Jan 08, 2003 at 11:00:52PM -0800, Erik wrote: > I'm in serious need.... > > I'm on a mailinglist run on (X-Mailman-Version: 2.0.8). This list is desperately in need of the "limit posts per day" feature. I see it on the wishlist at (http://www.list.org/todo.html): > > Add a limit on the number of posts from any one individual within a period of time (1 post per day, 10 per week, etc). > > Do you have an idea of how hard this would be to add? I've been around computers and programming for 30 years, starting with Fortran in high school on a CDC 3300, including assembler (Motorola 68K), C (Unix 4.1 BSD - 4.3 BSD, Solaris), C++, C# (NT, XP, etc), some scripting with sh and csh, perl, etc., but no Python (yet). I'm sure I could eventually figure it out. I'd like to volunteer to do the work, but I'd like to know what I'm up against first. I've downloaded the 2.0.8 sources but haven't had time to look through them carefully. > > Any words of wisdom (sure, it's easy ... forget it, it's hopeless)? > > Thanks, > Erik > _______________________________________________ > Mailman-Developers mailing list > Mailman-Developers@python.org > http://mail.python.org/mailman/listinfo/mailman-developers -- The 5 year plan: In five years we'll make up another plan. Or just re-use this one. From tneff at bigfoot.com Thu Jan 16 00:22:42 2003 From: tneff at bigfoot.com (Tom Neff) Date: Thu Jan 16 00:20:45 2003 Subject: [Mailman-Developers] Sourceforge notifications considered harmful In-Reply-To: <15910.16167.93291.953083@gargle.gargle.HOWL> References: <945946531.1042673265@[192.168.254.79]> <15910.16167.93291.953083@gargle.gargle.HOWL> Message-ID: <949243375.1042676562@[192.168.254.79]> Barry wrote: > That's definitely the /last/ thing I wanted to do! I think it's worse > now because 2.1 is out, people are finding it, playing with it, and > are submitting bugs and patches against it. ... I hope I didn't sound too ungrateful or anything. I don't know whether or how my suggested solution fits into Barry's a/b/c -1/0/+1 thing. I just think that mailman-developers should go on as it was (akin to the -developers list for so many other open source projects) but that the Sourceforge bug dump messages should be replaced by a single daily summary message saying which SF bugs were updated, with a one line subject for each. From jon at csh.rit.edu Thu Jan 16 00:16:38 2003 From: jon at csh.rit.edu (Jon Parise) Date: Thu Jan 16 00:23:52 2003 Subject: [Mailman-Developers] Sourceforge notifications considered harmful In-Reply-To: <15910.16167.93291.953083@gargle.gargle.HOWL> References: <945946531.1042673265@[192.168.254.79]> <15910.16167.93291.953083@gargle.gargle.HOWL> Message-ID: <20030116051638.GA12145@csh.rit.edu> On Thu, Jan 16, 2003 at 12:12:07AM -0500, Barry A. Warsaw wrote: > a. I create a mailman-coders@python.org list > > b. Send SF tracker messages to this list instead of mailman-developers > > c. Possibly (and I think optimally), retire mailman-checkins and send > the cvs diffs to mailman-coders as well. Personally, I don't see > the need for two different lists, but -checkins is more than this > list would do. > > So vote by the -1/0/+1 rules against these options: > > 1. Do nothing, everything's fine just the way it is 0 > 2. Do a + b +1 > 3. Do a + b + c +0 -- Jon Parise (jon@csh.rit.edu) :: http://www.csh.rit.edu/~jon/ From jam at jamux.com Thu Jan 16 01:10:16 2003 From: jam at jamux.com (John A. Martin) Date: Thu Jan 16 08:27:37 2003 Subject: [Mailman-Developers] Sourceforge notifications considered harmful In-Reply-To: <15910.16167.93291.953083@gargle.gargle.HOWL> (barry@python.org's message of "Thu, 16 Jan 2003 00:12:07 -0500") References: <945946531.1042673265@[192.168.254.79]> <15910.16167.93291.953083@gargle.gargle.HOWL> Message-ID: <87y95ltyk7.fsf@athene.jamux.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 >>>>> "BAW" == Barry A Warsaw >>>>> "Re: [Mailman-Developers] Sourceforge notifications considered harmful" >>>>> Thu, 16 Jan 2003 00:12:07 -0500 BAW> So vote by the -1/0/+1 rules against these options: BAW> 1. Do nothing, everything's fine just the way it is -1 BAW> 2. Do a + b +1 BAW> 3. Do a + b + c 0 jam -----BEGIN PGP SIGNATURE----- iD8DBQE+Jky5UEvv1b/iXy8RAlw5AJ0ZX9QCEoUgvItCFhkNZ6Up0R15NgCeKJT6 ICtzONTXgDk0H9FUKgl0VMg= =EQzo -----END PGP SIGNATURE----- From noreply at sourceforge.net Thu Jan 16 06:13:00 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Jan 16 09:10:14 2003 Subject: [Mailman-Developers] [ mailman-Feature Requests-669056 ] Archive URL in Email Message-ID: Feature Requests item #669056, was opened at 2003-01-16 06:12 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=669056&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Grant Bowman (grantbow) Assigned to: Nobody/Anonymous (nobody) Summary: Archive URL in Email Initial Comment: When an email goes out, it should have the assigned URL in the header. This requires you to know what it is as you send it out which can be tricky. I don't know if Mailman is designed to handle such a feature. I hope it is! ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=669056&group_id=103 From bryanf at samurai.com Thu Jan 16 09:41:28 2003 From: bryanf at samurai.com (Bryan Fullerton) Date: Thu Jan 16 09:41:33 2003 Subject: [Mailman-Developers] Sourceforge notifications considered harmful In-Reply-To: <15910.16167.93291.953083@gargle.gargle.HOWL> Message-ID: <989FE13C-2960-11D7-ADA4-0003936377F0@samurai.com> On Thursday, January 16, 2003, at 12:12 AM, Barry A. Warsaw wrote: > 3. Do a + b + c I don't entirely understand this -1/0/+1 thing, but option 3 would be my preference. Bryan From noreply at sourceforge.net Thu Jan 16 06:46:06 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Jan 16 09:43:16 2003 Subject: [Mailman-Developers] [ mailman-Bugs-669081 ] Major attachment handling bug! Message-ID: Bugs item #669081, was opened at 2003-01-16 15:46 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=669081&group_id=103 Category: Pipermail Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Daniel Buchmann (avalon) Assigned to: Nobody/Anonymous (nobody) Summary: Major attachment handling bug! Initial Comment: Attachments are not handled correctly. Attached to this bug report is an example email in a mbox file. How to reproduce: 1. create a list called "clasohlson" 2. copy this mbox file to the archive mbox file 3. run bin/arch for the list 4. look at the resulting archive I will post a followup which will contain the resulting html file I got when doing this. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=669081&group_id=103 From barry at python.org Thu Jan 16 10:03:19 2003 From: barry at python.org (Barry A. Warsaw) Date: Thu Jan 16 10:04:00 2003 Subject: [Mailman-Developers] Sourceforge notifications considered harmful References: <15910.16167.93291.953083@gargle.gargle.HOWL> <989FE13C-2960-11D7-ADA4-0003936377F0@samurai.com> Message-ID: <15910.51639.356970.636152@gargle.gargle.HOWL> >>>>> "BF" == Bryan Fullerton writes: BF> I don't entirely understand this -1/0/+1 thing, but option 3 BF> would be my preference. http://www.python.org/peps/pep-0010.html -Barry From noreply at sourceforge.net Thu Jan 16 07:07:14 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Jan 16 10:05:54 2003 Subject: [Mailman-Developers] [ mailman-Bugs-669081 ] Major attachment handling bug! Message-ID: Bugs item #669081, was opened at 2003-01-16 09:46 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=669081&group_id=103 Category: Pipermail Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Daniel Buchmann (avalon) Assigned to: Nobody/Anonymous (nobody) Summary: Major attachment handling bug! Initial Comment: Attachments are not handled correctly. Attached to this bug report is an example email in a mbox file. How to reproduce: 1. create a list called "clasohlson" 2. copy this mbox file to the archive mbox file 3. run bin/arch for the list 4. look at the resulting archive I will post a followup which will contain the resulting html file I got when doing this. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-01-16 10:07 Message: Logged In: YES user_id=12800 There was no attachment, are you sure you clicked the checkbox? :( ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=669081&group_id=103 From noreply at sourceforge.net Thu Jan 16 07:26:53 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Jan 16 10:24:10 2003 Subject: [Mailman-Developers] [ mailman-Bugs-669081 ] Major attachment handling bug! Message-ID: Bugs item #669081, was opened at 2003-01-16 15:46 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=669081&group_id=103 Category: Pipermail Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Daniel Buchmann (avalon) Assigned to: Nobody/Anonymous (nobody) Summary: Major attachment handling bug! Initial Comment: Attachments are not handled correctly. Attached to this bug report is an example email in a mbox file. How to reproduce: 1. create a list called "clasohlson" 2. copy this mbox file to the archive mbox file 3. run bin/arch for the list 4. look at the resulting archive I will post a followup which will contain the resulting html file I got when doing this. ---------------------------------------------------------------------- >Comment By: Daniel Buchmann (avalon) Date: 2003-01-16 16:26 Message: Logged In: YES user_id=184577 Sorry, my web browser hung after submitting the bug, and I had to go offfline in a hurry. Trying again.... :) ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-01-16 16:07 Message: Logged In: YES user_id=12800 There was no attachment, are you sure you clicked the checkbox? :( ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=669081&group_id=103 From noreply at sourceforge.net Thu Jan 16 07:28:18 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Jan 16 10:25:34 2003 Subject: [Mailman-Developers] [ mailman-Bugs-669081 ] Major attachment handling bug! Message-ID: Bugs item #669081, was opened at 2003-01-16 15:46 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=669081&group_id=103 Category: Pipermail Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Daniel Buchmann (avalon) Assigned to: Nobody/Anonymous (nobody) Summary: Major attachment handling bug! Initial Comment: Attachments are not handled correctly. Attached to this bug report is an example email in a mbox file. How to reproduce: 1. create a list called "clasohlson" 2. copy this mbox file to the archive mbox file 3. run bin/arch for the list 4. look at the resulting archive I will post a followup which will contain the resulting html file I got when doing this. ---------------------------------------------------------------------- >Comment By: Daniel Buchmann (avalon) Date: 2003-01-16 16:28 Message: Logged In: YES user_id=184577 Here is the generated html page for the email, if list language is set to norwegian. ---------------------------------------------------------------------- Comment By: Daniel Buchmann (avalon) Date: 2003-01-16 16:26 Message: Logged In: YES user_id=184577 Sorry, my web browser hung after submitting the bug, and I had to go offfline in a hurry. Trying again.... :) ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-01-16 16:07 Message: Logged In: YES user_id=12800 There was no attachment, are you sure you clicked the checkbox? :( ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=669081&group_id=103 From wheakory at isu.edu Thu Jan 16 08:27:17 2003 From: wheakory at isu.edu (Kory Wheatley) Date: Thu Jan 16 10:27:32 2003 Subject: [Mailman-Developers] spam filter Message-ID: <3E26CF4C.45A77E8C@isu.edu> Hi, I would like to discard any email that comes from the from address "big@boss.com". I know you can put a filter value in the mm_cfg.py and that will filter mail to be held for moderation; for example, "from: .big@boss.com", but I would rather have it be automatically discarded, so there is no need to manually discard these emails when they are held for approval. I would need this for mailman 2.0.13 and mailman 2.1 -- Kory Wheatley Academic Computing Analyst Sr. Phone 282-3874 ######################################### Everything must point to him. From noreply at sourceforge.net Thu Jan 16 07:30:48 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Jan 16 10:28:03 2003 Subject: [Mailman-Developers] [ mailman-Patches-644810 ] Sendmail mailer in Python Message-ID: Patches item #644810, was opened at 2002-11-27 16:27 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-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 Thu Jan 16 07:31:01 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Jan 16 10:28:18 2003 Subject: [Mailman-Developers] [ mailman-Bugs-669081 ] Major attachment handling bug! Message-ID: Bugs item #669081, was opened at 2003-01-16 15:46 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=669081&group_id=103 Category: Pipermail Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Daniel Buchmann (avalon) Assigned to: Nobody/Anonymous (nobody) Summary: Major attachment handling bug! Initial Comment: Attachments are not handled correctly. Attached to this bug report is an example email in a mbox file. How to reproduce: 1. create a list called "clasohlson" 2. copy this mbox file to the archive mbox file 3. run bin/arch for the list 4. look at the resulting archive I will post a followup which will contain the resulting html file I got when doing this. ---------------------------------------------------------------------- >Comment By: Daniel Buchmann (avalon) Date: 2003-01-16 16:31 Message: Logged In: YES user_id=184577 And here is the html file in english. Notice the difference. Lots of garbage (also called mojibake?) ;) ---------------------------------------------------------------------- Comment By: Daniel Buchmann (avalon) Date: 2003-01-16 16:28 Message: Logged In: YES user_id=184577 Here is the generated html page for the email, if list language is set to norwegian. ---------------------------------------------------------------------- Comment By: Daniel Buchmann (avalon) Date: 2003-01-16 16:26 Message: Logged In: YES user_id=184577 Sorry, my web browser hung after submitting the bug, and I had to go offfline in a hurry. Trying again.... :) ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-01-16 16:07 Message: Logged In: YES user_id=12800 There was no attachment, are you sure you clicked the checkbox? :( ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=669081&group_id=103 From noreply at sourceforge.net Thu Jan 16 07:46:11 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Jan 16 10:43:29 2003 Subject: [Mailman-Developers] [ mailman-Bugs-669111 ] Tiny mistake on the remove a list webpage Message-ID: Bugs item #669111, was opened at 2003-01-16 15:46 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=669111&group_id=103 Category: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Szilard Vizi (szilardv) Assigned to: Nobody/Anonymous (nobody) Summary: Tiny mistake on the remove a list webpage Initial Comment: On the remove mailing list webpage in the titlebar of the webbrowser the listname is between and , the browsers don't use HTML tag here. The problem is in Mailman/Cgi/rmlist.py line 188, where the title gets the same value as the first line of the document. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=669111&group_id=103 From noreply at sourceforge.net Thu Jan 16 07:54:20 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Jan 16 10:52:03 2003 Subject: [Mailman-Developers] [ mailman-Bugs-660675 ] special characters in realnames Message-ID: Bugs item #660675, was opened at 2003-01-01 15: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: Open Resolution: None >Priority: 8 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: Peer Heinlein (pheinlein) Date: 2003-01-16 16: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 23: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 23: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 Jan 16 08:29:19 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Jan 16 11:26:46 2003 Subject: [Mailman-Developers] [ mailman-Bugs-669081 ] Major attachment handling bug! Message-ID: Bugs item #669081, was opened at 2003-01-16 15:46 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=669081&group_id=103 Category: Pipermail Group: 2.1 (stable) Status: Open Resolution: None >Priority: 9 Submitted By: Daniel Buchmann (avalon) >Assigned to: Barry A. Warsaw (bwarsaw) Summary: Major attachment handling bug! Initial Comment: Attachments are not handled correctly. Attached to this bug report is an example email in a mbox file. How to reproduce: 1. create a list called "clasohlson" 2. copy this mbox file to the archive mbox file 3. run bin/arch for the list 4. look at the resulting archive I will post a followup which will contain the resulting html file I got when doing this. ---------------------------------------------------------------------- >Comment By: Daniel Buchmann (avalon) Date: 2003-01-16 17:29 Message: Logged In: YES user_id=184577 -changing priority and assignment- ---------------------------------------------------------------------- Comment By: Daniel Buchmann (avalon) Date: 2003-01-16 16:31 Message: Logged In: YES user_id=184577 And here is the html file in english. Notice the difference. Lots of garbage (also called mojibake?) ;) ---------------------------------------------------------------------- Comment By: Daniel Buchmann (avalon) Date: 2003-01-16 16:28 Message: Logged In: YES user_id=184577 Here is the generated html page for the email, if list language is set to norwegian. ---------------------------------------------------------------------- Comment By: Daniel Buchmann (avalon) Date: 2003-01-16 16:26 Message: Logged In: YES user_id=184577 Sorry, my web browser hung after submitting the bug, and I had to go offfline in a hurry. Trying again.... :) ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-01-16 16:07 Message: Logged In: YES user_id=12800 There was no attachment, are you sure you clicked the checkbox? :( ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=669081&group_id=103 From noreply at sourceforge.net Thu Jan 16 10:16:14 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Jan 16 13:13:21 2003 Subject: [Mailman-Developers] [ mailman-Bugs-669197 ] lock timeouts need to be reported Message-ID: Bugs item #669197, was opened at 2003-01-16 13:16 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=669197&group_id=103 Category: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: jared mauch (jaredmauch) Assigned to: Nobody/Anonymous (nobody) Summary: lock timeouts need to be reported Initial Comment: when accessing the admindb/ cgi, if the system is unable to obtain the list lock, it continually retries to get the lock. the cgi needs to time out after a specified amount of time (30 seconds perhaps?) and write a message saying "something is amiss, could not get list lock". this caused much puzzlement to me today trying to debug one of my lists. (the system was not cleanly restarted earlier today). ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=669197&group_id=103 From noreply at sourceforge.net Thu Jan 16 10:20:27 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Jan 16 13:17:48 2003 Subject: [Mailman-Developers] [ mailman-Bugs-669200 ] need ability to block mail from a specific machine Message-ID: Bugs item #669200, was opened at 2003-01-16 13:20 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=669200&group_id=103 Category: security/privacy Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: jared mauch (jaredmauch) Assigned to: Nobody/Anonymous (nobody) Summary: need ability to block mail from a specific machine Initial Comment: spammers use a variety of techniques to hide their true identiy. I have a remote MX host that they periodically relay their spam through and due to its configuration they periodically have messages that come through with a From: spammer@MX.HOST I'd like the ability to mark for discard any mail that is @MX.HOST without having to guess the explicit addresses they will be sending from. If this functionality exists, please ignore my ignorance. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=669200&group_id=103 From noreply at sourceforge.net Thu Jan 16 10:22:49 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Jan 16 13:19:56 2003 Subject: [Mailman-Developers] [ mailman-Bugs-669201 ] feature: unified membership allow post list. Message-ID: Bugs item #669201, was opened at 2003-01-16 13:22 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=669201&group_id=103 Category: security/privacy Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: jared mauch (jaredmauch) Assigned to: Nobody/Anonymous (nobody) Summary: feature: unified membership allow post list. Initial Comment: i host a variety of lists that obtain posts from members and non-members alike. they also have times where the email address they send from changes. i'd like the ability to create a global list of people that are allowed to post to lists and have it be enabled/disabled on a per-list basis. eg: list1 - use list members, extra people and GLOBAL_allow_list list2 - use list members, extra people only. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=669201&group_id=103 From noreply at sourceforge.net Thu Jan 16 11:54:19 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Jan 16 14:51:36 2003 Subject: [Mailman-Developers] [ mailman-Bugs-669200 ] need ability to block mail from a specific machine Message-ID: Bugs item #669200, was opened at 2003-01-16 19:20 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=669200&group_id=103 Category: security/privacy Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: jared mauch (jaredmauch) Assigned to: Nobody/Anonymous (nobody) Summary: need ability to block mail from a specific machine Initial Comment: spammers use a variety of techniques to hide their true identiy. I have a remote MX host that they periodically relay their spam through and due to its configuration they periodically have messages that come through with a From: spammer@MX.HOST I'd like the ability to mark for discard any mail that is @MX.HOST without having to guess the explicit addresses they will be sending from. If this functionality exists, please ignore my ignorance. ---------------------------------------------------------------------- Comment By: Daniel Buchmann (avalon) Date: 2003-01-16 20:54 Message: Logged In: YES user_id=184577 Yes, this functionality exists. It is possible to use python regexps in the Sender Filters (Privacy Options->Sender Filters->Non-member filters). Example: ^.*@MX\.HOST$ ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=669200&group_id=103 From noreply at sourceforge.net Thu Jan 16 11:59:44 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Jan 16 15:04:33 2003 Subject: [Mailman-Developers] [ mailman-Bugs-669200 ] need ability to block mail from a specific machine Message-ID: Bugs item #669200, was opened at 2003-01-16 13:20 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=669200&group_id=103 Category: security/privacy Group: 2.1 (stable) >Status: Closed Resolution: None Priority: 5 Submitted By: jared mauch (jaredmauch) Assigned to: Nobody/Anonymous (nobody) Summary: need ability to block mail from a specific machine Initial Comment: spammers use a variety of techniques to hide their true identiy. I have a remote MX host that they periodically relay their spam through and due to its configuration they periodically have messages that come through with a From: spammer@MX.HOST I'd like the ability to mark for discard any mail that is @MX.HOST without having to guess the explicit addresses they will be sending from. If this functionality exists, please ignore my ignorance. ---------------------------------------------------------------------- >Comment By: jared mauch (jaredmauch) Date: 2003-01-16 14:59 Message: Logged In: YES user_id=131445 i assume this is for discard_these_nonmembers thanks. ---------------------------------------------------------------------- Comment By: Daniel Buchmann (avalon) Date: 2003-01-16 14:54 Message: Logged In: YES user_id=184577 Yes, this functionality exists. It is possible to use python regexps in the Sender Filters (Privacy Options->Sender Filters->Non-member filters). Example: ^.*@MX\.HOST$ ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=669200&group_id=103 From noreply at sourceforge.net Thu Jan 16 13:16:06 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Jan 16 16:13:12 2003 Subject: [Mailman-Developers] [ mailman-Bugs-669296 ] rmlist and held messages Message-ID: Bugs item #669296, was opened at 2003-01-16 22:16 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=669296&group_id=103 Category: command line scripts Group: 2.1 (stable) Status: Open Resolution: None Priority: 2 Submitted By: Peer Heinlein (pheinlein) Assigned to: Nobody/Anonymous (nobody) Summary: rmlist and held messages Initial Comment: rmlist removes the mailinglist and listarchiv, but held messages are left in /var/spool/mailman/data! ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=669296&group_id=103 From bigdog at dogpound.vnet.net Thu Jan 16 17:57:21 2003 From: bigdog at dogpound.vnet.net (Matthew Davis) Date: Thu Jan 16 17:53:03 2003 Subject: [Mailman-Developers] Re: [Mailman-Users] spam filter In-Reply-To: <3E26CF4C.45A77E8C@isu.edu> References: <3E26CF4C.45A77E8C@isu.edu> Message-ID: <1042757841.3e2738d1e4c6b@dogpound.vnet.net> Quoting Kory Wheatley : > I would like to discard any email that comes from the from address > "big@boss.com". I know you can put a filter value in the mm_cfg.py and > that will filter mail to be held for moderation; for example, "from: > .big@boss.com", but I would rather have it be automatically discarded, > so there is no need to manually discard these emails when they are held > for approval. > > I would need this for mailman 2.0.13 and mailman 2.1 It would be smarter to put that ban in at the mailserver level. Putting a line in your /etc/mail/access (if its sendmail) would be nice. That way no processing of the message, less CPU consumption. But if cannot modify the mailserver and your using mailman 2.1, putting an entry in reject_these_nonmembers under Privacy Options -> Sender filters will auto reject that address. I don't think that mm2.0 has this auto-reject feature. ------------------------------------------------- This mail sent through IMP: http://horde.org/imp/ From marilyn at deliberate.com Thu Jan 16 15:45:46 2003 From: marilyn at deliberate.com (Marilyn Davis) Date: Thu Jan 16 18:45:52 2003 Subject: [Mailman-Developers] Sourceforge notifications considered harmful In-Reply-To: <15910.16167.93291.953083@gargle.gargle.HOWL> Message-ID: > 1. Do nothing, everything's fine just the way it is +0 > 2. Do a + b +1 > 3. Do a + b + c +1 Gee, eVote could help here. I'm dawdling with the install process and documentation, but soon. On an eVoted list, for this poll, you'd send a message to the list address that says: eVote poll public visible group 1. Do nothing [-1,1] 2. Do a + b [-1,1] 3. Do a + b + c [-1,1] message: Here's a proposal: a. I create a mailman-coders@python.org list b. Send SF tracker messages to this list instead of mailman-developers c. Possibly (and I think optimally), retire mailman-checkins and send the cvs diffs to mailman-coders as well. Personally, I don't see the need for two different lists, but -checkins is more than this list would do. --- end of message -- Then the list would get detailed poll instructions, and then I'd reply-to the list addresses saying: eVote 1. 0 2. 1 3. 1 --- end of message -- I hope people will find it handy sometimes. Marilyn From terri at zone12.com Thu Jan 16 17:21:22 2003 From: terri at zone12.com (Terri Oda) Date: Thu Jan 16 18:59:12 2003 Subject: [Mailman-Developers] Sourceforge notifications considered harmful In-Reply-To: <15910.16167.93291.953083@gargle.gargle.HOWL> References: <945946531.1042673265@[192.168.254.79]> <15910.16167.93291.953083@gargle.gargle.HOWL> Message-ID: <20030116222122.GA4349@ostraya.zone12.com> > 1. Do nothing, everything's fine just the way it is 0 > 2. Do a + b +1 > 3. Do a + b + c 0 4. do a + b + post summaries to mailman-developers +1 I don't mind getting the SF messages, even on those "my poor laptop's on dialup" days, but to be honest, they get procmailed to another folder and I tend to forget about them most of the time, so they're not really serving their purpose. I *really* like the idea of this list getting summaries as suggested in the original mail because I know I'd take the time to scan a summary. (After all, I scan the summary of stuff caught in my spam filter every day, and it's way less interesting.) Sure, plenty of people will ignore it, but at least the volume won't be so large that it'll drive people and discussions away, and it just might better serve the original purpose of having all the SF stuff send to this list. Terri (who *wishes* she were going to the spam conference) From dan.mick at sun.com Thu Jan 16 16:36:21 2003 From: dan.mick at sun.com (Dan Mick) Date: Thu Jan 16 19:37:07 2003 Subject: [Mailman-Developers] Sourceforge notifications considered harmful In-Reply-To: <15910.16167.93291.953083@gargle.gargle.HOWL> References: <945946531.1042673265@[192.168.254.79]> <15910.16167.93291.953083@gargle.gargle.HOWL> Message-ID: <3E275005.7080405@sun.com> Barry A. Warsaw wrote: > a. I create a mailman-coders@python.org list > > b. Send SF tracker messages to this list instead of mailman-developers > > c. Possibly (and I think optimally), retire mailman-checkins and send > the cvs diffs to mailman-coders as well. Personally, I don't see > the need for two different lists, but -checkins is more than this > list would do > > So vote by the -1/0/+1 rules against these options: > > 1. Do nothing, everything's fine just the way it is -1 > 2. Do a + b +1 > 3. Do a + b + c -1 (I'm very interested in checkins; I'm not very interested in "I tried to install Mailman and it didn't work, can you help?" buried in pounds of Sourceforge crap. Those notifications from SF's bugtracking *suck*, is a large part of the problem; if they just had delta text, or even changebars, or something, they'd suck a lot less.) From bryanf at samurai.com Thu Jan 16 21:06:05 2003 From: bryanf at samurai.com (Bryan Fullerton) Date: Thu Jan 16 21:06:05 2003 Subject: [Mailman-Developers] mm2.1 - DEFAULT_PLAIN_DIGEST_KEEP_HEADERS In-Reply-To: <3E25FBBE.9070702@is.kochi-u.ac.jp> Message-ID: <3CAA18B2-29C0-11D7-8715-000393013B04@samurai.com> On Wednesday, January 15, 2003, at 07:24 PM, Tokio Kikuchi wrote: > Please try this patch. > https://sourceforge.net/tracker/ > index.php?func=detail&aid=668819&group_id=103&atid=300103 This looks good. I've applied it - will let you know how digests look when they go out (midnight). Thanks! Bryan From bigdog at dogpound.vnet.net Thu Jan 16 21:39:26 2003 From: bigdog at dogpound.vnet.net (Matthew Davis) Date: Thu Jan 16 21:35:02 2003 Subject: [Mailman-Developers] Sourceforge notifications considered harmful In-Reply-To: <15910.16167.93291.953083@gargle.gargle.HOWL>; from barry@python.org on Thu, Jan 16, 2003 at 12:12:07AM -0500 References: <945946531.1042673265@[192.168.254.79]> <15910.16167.93291.953083@gargle.gargle.HOWL> Message-ID: <20030116213926.B9552@dogpound.vnet.net> * Barry A. Warsaw (barry@python.org) wrote: > 1. Do nothing, everything's fine just the way it is -1 > 2. Do a + b +1 > 3. Do a + b + c 0 ---------------------------------------------- | Matthew Davis /\ http://dogpound.vnet.net/ | |--------------------------------------------| | Thursday, January 16, 2003 / 09:38PM | ---------------------------------------------- My karma ran over my dogma From noreply at sourceforge.net Fri Jan 17 02:29:30 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Jan 17 05:26:47 2003 Subject: [Mailman-Developers] [ mailman-Bugs-598844 ] BASE64 attachments barfing Message-ID: Bugs item #598844, was opened at 2002-08-22 15:52 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=598844&group_id=103 Category: Pipermail Group: 2.1 beta Status: Closed Resolution: Fixed Priority: 5 Submitted By: Patrick Finnerty (finnertyp) Assigned to: Nobody/Anonymous (nobody) Summary: BASE64 attachments barfing Initial Comment: When testing MIME attachments I get the following error which occurs using arch to convert a mailbox or when posting to the archive: Pickling archive state into /usr/local/mailman/archives/private/opsarchtest/pipermail.pck Traceback (most recent call last): File "bin/arch", line 160, in ? main() File "bin/arch", line 148, in main archiver.processUnixMailbox(fp, Article, start, end) File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 545, in processUnixMailbox m = mbox.next() File "/usr/local/lib/python2.2/mailbox.py", line 34, in next return self.factory(_Subfile(self.fp, start, stop)) File "/usr/local/mailman/Mailman/Mailbox.py", line 69, in scrubber return mailbox.scrub(msg) File "/usr/local/mailman/Mailman/Mailbox.py", line 89, in scrub return self._scrubber(self._mlist, msg) File "/usr/local/mailman/Mailman/Handlers/Scrubber.py", line 114, in process url = save_attachment(mlist, part, filter_html=0) File "/usr/local/mailman/Mailman/Handlers/Scrubber.py", line 217, in save_attachment decodedpayload = msg.get_payload(decode=1) File "/usr/local/mailman/pythonlib/email/Message.py", line 177, in get_payload return Utils._bdecode(payload) File "/usr/local/mailman/pythonlib/email/Utils.py", line 71, in _bdecode value = base64.decodestring(s) File "/usr/local/lib/python2.2/base64.py", line 44, in decodestring return binascii.a2b_base64(s) binascii.Error: Incorrect padding I've narrowed this down to HTML attachments that include tables. I've attached a mbox that will give this error when used with arch. This only happens when base64 is used. I've also found that even when messages with HTML attachments are archived, clicking on the attachment doesn't display the page but the source instead. Or in some cases it can be garbage. I can supply more info on this if you wish. ---------------------------------------------------------------------- Comment By: Samuel Nicolary (nicolary) Date: 2003-01-17 10:29 Message: Logged In: YES user_id=27555 When I monitored what strings were causing this to barf I found that there were two scenarios - one when the mailman generated html descibing the file was being sent to this function (I have no idea why it is doing this) Ex. A non-text attachment was scrubbed... The second scenario that was truly a padding issue I got around by doing the following in the _bdecode funtion: value = base64.decodestring(s+'=========') let me know if you want a full patch of my trashy hack. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-08-22 19:09 Message: Logged In: YES user_id=12800 Thanks for the report and the mbox file, this was indeed a bug, which will be fixed in beta4. As for you second question, what you're seeing could be caused by this bug, but it's more likely just the behavior specified by ARCHIVE_HTML_SANTIZER in Defaults.py/mm_cfg.py. To prohibit evil stuff like cross-site scripting, or web bugs and virus from affecting your archive readers, html is typically santized to be harmless. ---------------------------------------------------------------------- Comment By: Patrick Finnerty (finnertyp) Date: 2002-08-22 15:58 Message: Logged In: YES user_id=594846 Whoops. Attached the html file which was used as attachment instead of the mbox file.... ...which I'm gonna upload now. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=598844&group_id=103 From mss at mawhrin.net Fri Jan 17 10:30:49 2003 From: mss at mawhrin.net (Mikhail Sobolev) Date: Fri Jan 17 05:30:55 2003 Subject: [Mailman-Developers] Sourceforge notifications considered harmful In-Reply-To: <15910.16167.93291.953083@gargle.gargle.HOWL> References: <945946531.1042673265@[192.168.254.79]> <15910.16167.93291.953083@gargle.gargle.HOWL> Message-ID: <20030117103049.GA19995@mawhrin.net> > 1. Do nothing, everything's fine just the way it is -1 > 2. Do a + b +1 > 3. Do a + b + c 0 And, separately, to use summaries instead of full messages for bugs/patches/etc. +1 -- Misha -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available Url : http://mail.python.org/pipermail/mailman-developers/attachments/20030117/f5b5f613/attachment.bin From bryanf at samurai.com Fri Jan 17 09:29:43 2003 From: bryanf at samurai.com (Bryan Fullerton) Date: Fri Jan 17 09:30:11 2003 Subject: [Mailman-Developers] mm2.1 - DEFAULT_PLAIN_DIGEST_KEEP_HEADERS In-Reply-To: <3CAA18B2-29C0-11D7-8715-000393013B04@samurai.com> Message-ID: <1ECD143A-2A28-11D7-85FB-000393013B04@samurai.com> On Thursday, January 16, 2003, at 09:06 PM, Bryan Fullerton wrote: > On Wednesday, January 15, 2003, at 07:24 PM, Tokio Kikuchi wrote: > >> Please try this patch. >> https://sourceforge.net/tracker/ >> index.php?func=detail&aid=668819&group_id=103&atid=300103 > > This looks good. I've applied it - will let you know how digests look > when they go out (midnight). Aaand... it worked great! My customers are happy! Please merge this patch into CVS (or something equivalent). Thanks, Bryan From lrosa at mail.hypertrek.info Fri Jan 17 15:49:23 2003 From: lrosa at mail.hypertrek.info (Luigi Rosa) Date: Fri Jan 17 09:49:59 2003 Subject: [Mailman-Developers] mailmanctl and syslog Message-ID: <11620114359.20030117154923@mail.hypertrek.info> Hello, wouldn't be a good idea to log the start and stop of mailmanctl in the syslog? Something like "Mailman $version services started successfuly" and "Mailman $version services stopped successfuly". Just to leave a trace of the activity in the system log. -- Best regards, Luigi mailto:lrosa@mail.hypertrek.info From bryanf at samurai.com Fri Jan 17 09:59:26 2003 From: bryanf at samurai.com (Bryan Fullerton) Date: Fri Jan 17 09:59:54 2003 Subject: [Mailman-Developers] mailmanctl and syslog In-Reply-To: <11620114359.20030117154923@mail.hypertrek.info> Message-ID: <45A0060B-2A2C-11D7-85FB-000393013B04@samurai.com> On Friday, January 17, 2003, at 09:49 AM, Luigi Rosa wrote: > wouldn't be a good idea to log the start and stop of mailmanctl in the > syslog? This information is effectively logged in logs/qrunner, as seen below, though it might be nice to have a single log-line entry indicating the commands passed to mailmanctl. Jan 15 13:25:37 2003 (67350) Master watcher caught SIGTERM. Exiting. Jan 15 13:25:37 2003 (67350) Master qrunner detected subprocess exit (pid: 67356, sig: None, sts: 15, class: OutgoingRunner, slice: 1/1) Jan 15 13:25:37 2003 (67350) Master qrunner detected subprocess exit (pid: 67355, sig: None, sts: 15, class: NewsRunner, slice: 1/1) Jan 15 13:25:37 2003 (67350) Master qrunner detected subprocess exit (pid: 67354, sig: None, sts: 15, class: IncomingRunner, slice: 1/1) Jan 15 13:25:37 2003 (67350) Master qrunner detected subprocess exit (pid: 67353, sig: None, sts: 15, class: CommandRunner, slice: 1/1) Jan 15 13:25:37 2003 (67350) Master qrunner detected subprocess exit (pid: 67352, sig: None, sts: 15, class: BounceRunner, slice: 1/1) Jan 15 13:25:37 2003 (67350) Master qrunner detected subprocess exit (pid: 67351, sig: None, sts: 15, class: ArchRunner, slice: 1/1) Jan 15 13:25:37 2003 (67350) Master qrunner detected subprocess exit (pid: 67357, sig: None, sts: 15, class: VirginRunner, slice: 1/1) Jan 15 13:25:41 2003 (67471) OutgoingRunner qrunner started. Jan 15 13:25:41 2003 (67468) CommandRunner qrunner started. Jan 15 13:25:41 2003 (67467) BounceRunner qrunner started. Jan 15 13:25:41 2003 (67472) VirginRunner qrunner started. Jan 15 13:25:41 2003 (67469) IncomingRunner qrunner started. Jan 15 13:25:41 2003 (67470) NewsRunner qrunner started. Jan 15 13:25:41 2003 (67466) ArchRunner qrunner started. Bryan From lrosa at mail.hypertrek.info Fri Jan 17 16:05:18 2003 From: lrosa at mail.hypertrek.info (Luigi Rosa) Date: Fri Jan 17 10:05:51 2003 Subject: [Mailman-Developers] mailmanctl and syslog In-Reply-To: <45A0060B-2A2C-11D7-85FB-000393013B04@samurai.com> References: <45A0060B-2A2C-11D7-85FB-000393013B04@samurai.com> Message-ID: <3221069234.20030117160518@mail.hypertrek.info> Hello Bryan, Friday, January 17, 2003, 3:59:26 PM, you wrote: >> wouldn't be a good idea to log the start and stop of mailmanctl in the >> syslog? BF> This information is effectively logged in logs/qrunner, as seen below, BF> though it might be nice to have a single log-line entry indicating the BF> commands passed to mailmanctl. Mybe I should rephrase my question. Would'nt it be better if mailman can log either in a logfile or in a user configurable SysLog facility? I mean, for each logfile that mm creates, could it be possible to specify a filename or a syslog target? -- Best regards, Luigi mailto:lrosa@mail.hypertrek.info From bryanf at samurai.com Fri Jan 17 12:59:00 2003 From: bryanf at samurai.com (Bryan Fullerton) Date: Fri Jan 17 12:59:29 2003 Subject: [Mailman-Developers] mailmanctl and syslog In-Reply-To: <3221069234.20030117160518@mail.hypertrek.info> Message-ID: <5B44D658-2A45-11D7-85FB-000393013B04@samurai.com> On Friday, January 17, 2003, at 10:05 AM, Luigi Rosa wrote: > Mybe I should rephrase my question. > > Would'nt it be better if mailman can log either in a logfile or in a > user > configurable SysLog facility? > > I mean, for each logfile that mm creates, could it be possible to > specify a > filename or a syslog target? Aah. :) I probably wouldn't use that (or change from defaults), but I can see how it'd be useful for the logging to be more configurable. Bryan From noreply at sourceforge.net Fri Jan 17 10:24:28 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Jan 17 13:21:31 2003 Subject: [Mailman-Developers] [ mailman-Bugs-669874 ] partial string.lower() in Address Matching Message-ID: Bugs item #669874, was opened at 2003-01-17 18:24 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=669874&group_id=103 Category: configuring/installing Group: 2.0.x Status: Open Resolution: None Priority: 5 Submitted By: Jasper van Beusekom (jvbeusek) Assigned to: Nobody/Anonymous (nobody) Summary: partial string.lower() in Address Matching Initial Comment: FindMatchingAddresses of Utils.py (mailman 2.0.13) compares the given 'name' variable to the given dictionary, for example privacy/forbidden_posters. In this comparison, 'name' is converted to lower case (both if SMART_ADDRESS_MATCH is true or false). Unfortunately this dictionary that is being compared to is not converted to lower case. As a result, addresses that should be matched aren't. Additionally, the configuration web-interface doesn't encourage the list owner to only use lowercase. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=669874&group_id=103 From noreply at sourceforge.net Fri Jan 17 11:47:29 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Jan 17 14:44:32 2003 Subject: [Mailman-Developers] [ mailman-Feature Requests-669922 ] list creation without password Message-ID: Feature Requests item #669922, was opened at 2003-01-17 11:47 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=669922&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Calvin Leung (cleung) Assigned to: Nobody/Anonymous (nobody) Summary: list creation without password Initial Comment: There should be an option which allow list creation without password but treated as a pending request by the site admin. The site admin can approve the list creation (like the moderation process) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=669922&group_id=103 From noreply at sourceforge.net Fri Jan 17 16:30:20 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Jan 17 19:27:28 2003 Subject: [Mailman-Developers] [ mailman-Patches-670080 ] list_lists selection based on archive category Message-ID: Patches item #670080, was opened at 2003-01-17 18:30 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=670080&group_id=103 Category: command line scripts Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: David Gibbs (midrangeman) Assigned to: Nobody/Anonymous (nobody) Summary: list_lists selection based on archive category Initial Comment: This patch adds two new command line parms to the list_lists script. -r / --private-archives, which causes only lists with private archives to be displayed -u / --public-archives, which causes only lists with public archives to be displayed. I wanted to control the creation of htpasswd files for only private archives, so this modification was born. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=670080&group_id=103 From noreply at sourceforge.net Fri Jan 17 20:28:58 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Jan 17 23:25:51 2003 Subject: [Mailman-Developers] [ mailman-Patches-670142 ] Generate .htaccess from subscriber list Message-ID: Patches item #670142, was opened at 2003-01-17 22:28 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=670142&group_id=103 Category: command line scripts Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: David Gibbs (midrangeman) Assigned to: Nobody/Anonymous (nobody) Summary: Generate .htaccess from subscriber list Initial Comment: This is a version of the 2.0.x script, that generates htaccess files based on list subscribers, adapted for MM 2.1 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=670142&group_id=103 From noreply at sourceforge.net Fri Jan 17 21:58:37 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sat Jan 18 00:55:38 2003 Subject: [Mailman-Developers] [ mailman-Patches-670167 ] fix i18n attachment description in archive Message-ID: Patches item #670167, was opened at 2003-01-18 05:58 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: None Priority: 5 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. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=670167&group_id=103 From noreply at sourceforge.net Fri Jan 17 22:03:34 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sat Jan 18 01:00:46 2003 Subject: [Mailman-Developers] [ mailman-Bugs-669081 ] Major attachment handling bug! Message-ID: Bugs item #669081, was opened at 2003-01-16 14:46 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=669081&group_id=103 Category: Pipermail Group: 2.1 (stable) Status: Open Resolution: None Priority: 9 Submitted By: Daniel Buchmann (avalon) Assigned to: Barry A. Warsaw (bwarsaw) Summary: Major attachment handling bug! Initial Comment: Attachments are not handled correctly. Attached to this bug report is an example email in a mbox file. How to reproduce: 1. create a list called "clasohlson" 2. copy this mbox file to the archive mbox file 3. run bin/arch for the list 4. look at the resulting archive I will post a followup which will contain the resulting html file I got when doing this. ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-01-18 06:03 Message: Logged In: YES user_id=67709 Please try this patch. https://sourceforge.net/tracker/?func=detail&atid=300103&aid=670167&group_id=103 (Patch ID 670167) ---------------------------------------------------------------------- Comment By: Daniel Buchmann (avalon) Date: 2003-01-16 16:29 Message: Logged In: YES user_id=184577 -changing priority and assignment- ---------------------------------------------------------------------- Comment By: Daniel Buchmann (avalon) Date: 2003-01-16 15:31 Message: Logged In: YES user_id=184577 And here is the html file in english. Notice the difference. Lots of garbage (also called mojibake?) ;) ---------------------------------------------------------------------- Comment By: Daniel Buchmann (avalon) Date: 2003-01-16 15:28 Message: Logged In: YES user_id=184577 Here is the generated html page for the email, if list language is set to norwegian. ---------------------------------------------------------------------- Comment By: Daniel Buchmann (avalon) Date: 2003-01-16 15:26 Message: Logged In: YES user_id=184577 Sorry, my web browser hung after submitting the bug, and I had to go offfline in a hurry. Trying again.... :) ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-01-16 15:07 Message: Logged In: YES user_id=12800 There was no attachment, are you sure you clicked the checkbox? :( ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=669081&group_id=103 From noreply at sourceforge.net Fri Jan 17 22:28:21 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sat Jan 18 01:25:14 2003 Subject: [Mailman-Developers] [ mailman-Feature Requests-670171 ] Adding [label] tag to HTML pages Message-ID: Feature Requests item #670171, was opened at 2003-01-18 07:28 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=670171&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Benjamin Sonntag (benjaminsonntag) Assigned to: Nobody/Anonymous (nobody) Summary: Adding [label] tag to HTML pages Initial Comment: The