Mailman 3 November 2001 - Mailman-Developers

Re: [Mailman-Developers] clobber_date bug
by Dan Mick 09 Nov '01

09 Nov '01

> On Thu, Nov 08, 2001 at 02:23:58PM -0800, Dan Mick wrote: > > > > > So it looks like my options are to use asctime(gmtime(time)) or write a > > > routine that parses time.timezone into "-0600". > > > > Luckily 'altzone' is defined in time, so > > > > "+%02d%02d" % (time.altzone / 3600, time.altzone % 3600) > > Well, that's not totally right either. It doesn't look as though 'time' > has a function to tell us if we're in the DST timezone or the non-DST > timezone, so there's no way to tell if we're supposed to use 'timezone' > or 'altzone'. Well, there's the ninth return value of localtime(). But I'm too lazy to write the code to use it (as you can surely tell by the fact that I'm too lazy to tell the difference between altzone and timezone.. ;) > So it looks to me like using 'gmtime' is the only way to > get the right info under all circumstances. > > To be totally RFC 822/2822 compliant, you could convert to GMT (using > gmtime) and then blindly append "+0000". But since (in 2.0.6) this only > happens to messages on the way to being archived, it doesn't seem > terribly likely that message will ever be resent again. So as long as > the archiver is happy I'm not too concerned. > > Ugh. I just noticed that RFC 2822 requires day-month-year-time order, > while ctime and asctime produce month-day-time year order. So looks to > me like this is most correct: > > time.strftime("%a, %d %b %Y %H:%M:%S +0000", time.gmtime(time.time()))

1 0

Re: [Mailman-Developers] clobber_date bug
by Dan Mick 09 Nov '01

09 Nov '01

> > While clobber_date doesn't process the existing date, it > > seems to replace it by the local date (namely > > the output of ctime(time()). That seems correct to me. > > Are you certain your local TZ is set properly? > > Using python 1.5.2, ctime() is giving local time without timezone info. Good point. It's the correct time, but it's not fully-qualified. I get it. > If I use asctime(gmtime(time)) I seem to get the correct result. > > [eds@ike eds]$ python > Python 1.5.2 (#1, Dec 21 2000, 15:29:08) [GCC egcs-2.91.66 > 19990314/Linux (egcs- on linux-i386 > Copyright 1991-1995 Stichting Mathematisch Centrum, Amsterdam > >>> time.ctime(time.time()) > 'Thu Nov 8 16:01:44 2001' > >>> time.tzname > ('CST', 'CDT') > >>> time.timezone /3600 > 6 > >>> time.asctime(time.gmtime(time.time())) > 'Thu Nov 8 22:06:05 2001' Well, sorta. You really want that TZ information appended. > So it looks like my options are to use asctime(gmtime(time)) or write a > routine that parses time.timezone into "-0600". Luckily 'altzone' is defined in time, so "+%02d%02d" % (time.altzone / 3600, time.altzone % 3600) seems to do it. But it sure looks like a bug to me.

2 1

Re: [Mailman-Developers] clobber_date bug
by Dan Mick 09 Nov '01

09 Nov '01

> Hello nice Mailman folks, thanks for the great software. I've been > using it for over a year to run a handful of small mailing lists and > I've always been impressed with the quality. > > I just noticed a small bug. On an active list, I turned on the > clobber_date setting (to apply the "resent" time to messages stored in > the archives), and I noticed that it messed up the order of a bunch of > messages in the archive. > > The reason is that clobber_date doesn't put the timezone information in > the Date: field. So it looks as though the messages are dated GMT > instead of GMT-6, and the messages from this morning appear after those > from the afternoon. > > Example message without clobber_date: > Date: Thu, 8 Nov 2001 10:48:20 -0600 > > Example message with clobber_date: > Date: Thu Nov 8 13:33:00 2001 > X-Original-Date: Thu, 08 Nov 2001 13:31:30 -0600 While clobber_date doesn't process the existing date, it seems to replace it by the local date (namely the output of ctime(time()). That seems correct to me. Are you certain your local TZ is set properly?

2 1

Re: [Mailman-Users] threaded view on archive does not work
by J C Lawrence 09 Nov '01

09 Nov '01

CC'ed to -developers to note that pipermail's threading seems either broken/fragile, and to note that the mbox archives for the -users list are borked (early apparency is that Pipermail is excessively restrictive on In-Reply-To header field formats). On Mon, 05 Nov 2001 08:18:55 +0100 Lucas Hofman <lucas.hofman(a)pgs.com> wrote: > On Friday 02 November 2001 09:53, J C Lawrence wrote: >> On Fri, 02 Nov 2001 10:42:33 +0100 >> exmh. Quoting the headers from this very message: >> >> In-Reply-To: Message from Lucas Hofman <lucas.hofman(a)pgs.com> of >> "Fri, 02 Nov 2001 10:42:33 +0100." >> <0111021004.AA1004693972(a)lysntsmail.oslo.pgs.com> References: >> <0111021004.AA1004693972(a)lysntsmail.oslo.pgs.com> > There are gone when the message arrives at my workstation (at > least, kmail 'show all headers' does not reveal them). Neither in > the copy received from your not the one sent by the list. Which is then a problem with your mail setup, and is not specific to either the mail I send, or the mailman lists at Python.Org. Quoting the full headers from another message I sent to this forum: --<cut>>-- X-envelope-from: mailman-users-admin(a)python.org Tue Nov 06 12:46:03 2001 Return-path: <mailman-users-admin(a)python.org> Envelope-to: claw@localhost Delivery-date: Tue, 06 Nov 2001 12:46:03 -0800 Received: from localhost [127.0.0.1] by dingo.home.kanga.nu with esmtp (Exim 3.32 #1 (Debian)) id 161D6h-0001ns-00; Tue, 06 Nov 2001 12:46:03 -0800 Delivered-to: claw(a)kanga.nu Received: from kanga.nu [157.22.12.214] by localhost with IMAP (fetchmail-5.9.3) for claw@localhost (single-drop); Tue, 06 Nov 2001 12:46:03 -0800 (PST) Received: from mail.python.org (mail.python.org [63.102.49.29]) by bush.kanga.nu (Postfix) with ESMTP id 4DCEE12E27 for <claw(a)kanga.nu>; Tue, 6 Nov 2001 12:44:44 -0800 (PST) Received: from localhost.localdomain ([127.0.0.1] helo=mail.python.org) by mail.python.org with esmtp (Exim 3.21 #1) id 161D30-0000fp-00; Tue, 06 Nov 2001 15:42:14 -0500 Received: from [63.203.253.2] (helo=localhost) by mail.python.org with esmtp (Exim 3.21 #1) id 161D2h-0000bB-00 for mailman-users(a)python.org; Tue, 06 Nov 2001 15:41:55 -0500 Received: from 2wire.com (localhost [127.0.0.1]) by localhost (Postfix) with ESMTP id 4338E129A; Tue, 6 Nov 2001 12:41:25 -0800 (PST) In-reply-to: Message from "Leonard Jacobs" <ljacobs(a)shambhala.com> of "Tue, 06 Nov 2001 13:27:57 EST." <3BE7E55D.13726.2154F0A@localhost> References: <3BE7E55D.13726.2154F0A@localhost> X-message-flag: Are you sure that Microsoft Outlook is good enough for you to use? X-accepted-file-formats: text/plain preferred, Postscript and PDF accepted - *NO* Micosoft Office files please. X-face: ?<YUs-cNP1\Oc-H>^_yw@fA`CEX&}--=*&XqXbF-oePvxaT4(kyt\nwM9]{]N!>b^K}-Mb9 YH%saz^>nq5usBlD"s{(.h'_w|U^3ldUq7wVZz$`u>MB(-4$f\a6Eu8.e=Pf\ X-image-url: http://www.kanga.nu/~claw/kanga.face.tiff X-url: http://www.kanga.nu/~claw/ Message-id: <12753.1005079285(a)2wire.com> Sender: mailman-users-admin(a)python.org Errors-to: mailman-users-admin(a)python.org X-beenthere: mailman-users(a)python.org X-mailman-version: 2.0.6 (101270) Precedence: bulk List-help: <mailto:mailman-users-request@python.org?subject=help> List-post: <mailto:mailman-users@python.org> List-subscribe: <http://mail.python.org/mailman/listinfo/mailman-users>, <mailto:mailman-users-request@python.org?subject=subscribe> List-id: Mailman mailing list management users <mailman-users.python.org> List-unsubscribe: <http://mail.python.org/mailman/listinfo/mailman-users>, <mailto:mailman-users-request@python.org?subject=unsubscribe> List-archive: <http://mail.python.org/pipermail/mailman-users/> Subject: Re: [Mailman-Users] resolving qfiles stuck in the queue From: J C Lawrence <claw(a)2wire.com> Date: Tue, 06 Nov 2001 12:41:25 -0800 To: Ljacobs(a)shambhala.com Cc: mailman-users(a)python.org --<cut>>-- Unfortunately the mbox files for the archives at python.org are borked, but checking other posts of mine there universally show correct in-Reply-To: and References: headers. eg: --<cut>>-- >From claw(a)kanga.nu Thu Nov 1 18:00:37 2001 From: claw(a)kanga.nu (J C Lawrence) Date: Thu, 01 Nov 2001 10:00:37 -0800 Subject: [Mailman-Users] threaded view on archive does not work In-Reply-To: Message from Lucas Hofman <lucas.hofman(a)pgs.com> of "Thu, 01 Nov 2001 11:30:22 +0100." <0111011004.AA1004610438(a)lysntsmail.oslo.pgs.com> References: <0111011004.AA1004610438(a)lysntsmail.oslo.pgs.com> Message-ID: <29859.1004637637(a)kanga.nu> --<cut>>-- > Do you have any any why your messages do not hread in the mailman > user maillist archive? No. > In other words, could it be that the mail > system at python.org does not see those headers too? No. This would appear to be another Pipermail bug. As you can see here: http://www.kanga.nu/archives/MUD-Dev-L/2001Q4/thread.php#00434 my messages thread properly under MHonArc (a tool I know handles thread headers properly). -- J C Lawrence ---------(*) Satan, oscillate my metallic sonatas. claw(a)kanga.nu He lived as a devil, eh? http://www.kanga.nu/~claw/ Evil is a name of a foeman, as I live.

3 2

Problem with mailman and postfix
by Hanno Liem 08 Nov '01

08 Nov '01

Hi, I have consulted all the online docs, but haven't been able to find anything relating to my problem. I hope someone here can help me. For some reason, mailman is unable to send outgoing email to any mailing lists. In /var/log/maillog postfix logs: Nov 8 13:47:01 shane postfix/master[24382]: warning: process /usr/local/libexec /postfix/local pid 61748 exit status 1 Nov 8 13:47:01 shane postfix/master[24382]: warning: /usr/local/libexec/postfix /local: bad command startup -- throttling Normal mail can be sent out by shane. Only mail from postfix hangs somewhere... Any hints would be much appreciated. kind regards, Hanno Liem Your Choice

1 0

Re: [Mailman-Developers] Software Development �10 per hour!
by Phillip Smith 08 Nov '01

08 Nov '01

Greetings. Can anyone explain to me why this spam E-mail made it to the list? I see a lot of spam being sent to this list, but in this particular case, one of the mailing lists I run also received the same identical message.. which I find odd. Did they intentionally target mailman powered lists? I find it more odd that for both mailman-developers and my list, subscription/confirmation is required, but I find no trace of any addresses with the header domains or From: address, which would indicate to me there is some way around the subscription process, or that they came up with a scheme to go through the sub/confirm and then unsubscribe. Seems like a lot of trouble just to send spam though... Am I missing something here? -phillip

1 0

SimpleMatch.py problem
by Bob Puff＠NLE 08 Nov '01

08 Nov '01

Hi Barry & gang, I finally figured out why my few additions to SimpleMatch.py bounce messages weren't working. It turns out that if one of the lines in one of the previous cases matches, but the other ones don't, the search is aborted immediately, instead of testing the other patterns. I'm sure this is a simple fix, but I'm not fluent enough in Python (yet) to take a stab at this. The offending code is: state = 0 while 1: line = msg.fp.readline() if not line: break if state == 0: for scre, ecre, acre in patterns: if scre.search(line): state = 1 break elif state == 1: mo = acre.search(line) if mo: addrs[mo.group('addr')] = 1 elif ecre.search(line): break return addrs.keys() or None Bob

1 0

WWW.LIST.ORG
by Vanessa Lintner 08 Nov '01

08 Nov '01

Hello, I have visited www.list.org and noticed that your website is not listed on some search engines. I am sure that through our service the number of people who visit your website will definitely increase. SeekerCenter is a unique technology that instantly submits your website to over 500,000 search engines and directories -- a really low-cost and effective way to advertise your site. For more details please go to SeekerCenter.net. Give your web site maximum exposure today! I am looking forward to hearing from you. Best Regards, Vanessa Lintner Sales & Marketing www.SeekerCenter.net

1 0

Re: [Mailman-Developers] List CGI
by J C Lawrence 07 Nov '01

07 Nov '01

On Sat, 6 Oct 2001 11:39:05 -0500 Allan Baker <allan(a)caldera.com.mx> wrote: > As a job assignment I'm required to make a script (its highly > likely it will be with a CGI script) so that mailman mailing lists > can be created using a web page. However my idea is not to > reinvent the wheel. Is there anything like it or do I have to > start coding? Already done for 2.1 -- J C Lawrence ---------(*) Satan, oscillate my metallic sonatas. claw(a)kanga.nu He lived as a devil, eh? http://www.kanga.nu/~claw/ Evil is a name of a foeman, as I live.

2 1

Re: [Mailman-Users] Upgrading from 2.0b5 to 2.1a2
by barry＠zope.com 07 Nov '01

07 Nov '01

[Note: I'm moving this discussion to malman-developers. -baw] >>>>> "JAA" == Jose A Accino <jaccino(a)ieev.uma.es> writes: JAA> Is there any clean way to make a smooth upgrade from 2.0b5 to JAA> lates 2.1a2? (I'm making that just to check the upgrade JAA> process, using a spare machine and a copy of the actual JAA> lists). JAA> Making a 2.1a2 fresh installation (without lists) runs fine. JAA> However, I've been unable to upgrade the old lists. Here are JAA> the main points: There's two ways to upgrade, neither of which has gotten a lot of testing. Based on you're message I tried the first way, and I'm about to check in a bunch of patches to make that go smoother. I'll try the second way soon. 1) Install a fresh virgin MM2.1 in /usr/local/mailman and then move lists from /home/mailman (MM2.0.x) to /usr/local/mailman. This way lets you migrate lists one at a time, gaining confidence in the new system in measured increments. I will probably upgrade {python,zope}.org this way. 2) Install MM2.1 overtop an existing MM2.0.x installation and have everything just magically work. I'll probably upgrade wooz.org's production lists this way. Both ought to work, and ought to be easy. After the checkins, here's a recipe that makes #1 easy: - Do a fresh install of MM2.1 in /usr/local/mailman according to the instructions. - Copy or move `mylist' by first moving /home/mailman/lists/mylist to /usr/local/mailman/lists/mylist and /home/mailman/archives/private/mylist.mbox to /usr/local/mailman/archives/private BTW, I used rsync for this, just cause it's a cool tool and I can actually remember how to invoke it with the right options. :) That's it. Everything else should just work, except for possibly two minor complications. - If your web server is going to support both installations, it's possible you'll have two different base urls, one for your MM2.0.x installation and one for your MM2.1 installation. If so, you'll need to manually change each moved list's web_page_url attribute. Fortunately, I'm about to add a script called `fix_url' which will reset a list's web_page_url to mm_cfg.DEFAULT_URL. So if you configure mm_cfg.py correctly, then run fix_url, you should be golden. I.e. % bin/withlist -l -r fix_url mylist - Same dealie with your MTA, i.e. your wrapper aliases may point to two different directories. Here, because I use Postfix and glued them together as described in README.POSTFIX, all I needed to do was run bin/genaliases and the new list aliases got installed. I'm sure that if you use Exim and glued them together as per README.EXIM, you probably don't need to do anything. (I'm still waiting on contributions for better gluing instructions for Sendmail, qmail, and any others.) -Barry

4 5