From tneff at bigfoot.com Thu May 1 10:43:42 2003 From: tneff at bigfoot.com (Tom Neff) Date: Thu May 1 09:44:14 2003 Subject: [Mailman-Developers] Ignoring "mail." in domain names In-Reply-To: References: Message-ID: <89881531.1051782221@tomdual2> Another way we could really reduce moderator headaches would be to teach Mailman to try removing a leading "mail." in the domain part of the address if a member lookup fails. I get a lot of people who join lists as JSmith@splonk.edu and end up posting (immediately or six months later) as JSmith@mail.splonk.edu. If I had per-member aliases I could add them as needed, but this one case is so pervasive that it might make more sense to do it list-wide or even hard code it. From edc at proadmin.com Thu May 1 16:58:05 2003 From: edc at proadmin.com (Eric D. Christensen) Date: Thu May 1 11:58:06 2003 Subject: [Mailman-Developers] Re: monthly notification error In-Reply-To: References: Message-ID: <1051804652.26686.91.camel@o3> > I'm running debian/testing and just upgraded mailman to the version > in unstable (2.1.1-5). Last night the cron job to send out the monthly > password reminders failed with this error: > > Traceback (most recent call last): > File "/usr/lib/mailman/cron/mailpasswds", line 218, in ? > main() > File "/usr/lib/mailman/cron/mailpasswds", line 145, in main > password = mlist.getMemberPassword(member) > File "/var/lib/mailman/Mailman/OldStyleMemberships.py", line 102, in > getMemberPassword > raise Errors.NotAMemberError, member > Mailman.Errors.NotAMemberError: rick@niof.net > > Is there some upgrade configuring I need to do? I did create the > 'mailman' mailing list. Do I need to add myself as a subscriber? > Should I send a bugreport to the debian maintainer? It's not just Debian... I'm running 2.1.1 on Linux and had the same problem. Probably worth filing a bug report against mailman since there are at least two of us seeing the same problems on different platforms now. I've also see this when running the cron/disabled script. It always seems to be with one specific user, which makes me suspect something that didn't translate correctly in the database. Attached below are the details I reported earlier. Barry - if it would be helpful, I'd be happy to give you access to the mailman account on my server so you can poke around. -- Eric D. Christensen Proadmin, Inc. --- Attached Message Follows --- I'm getting an error when running cron/disabled after updating from 2.0 to 2.1.1. I suspect this is due to something that got corrupted / confused / boggled in the upgrade process, but I'm not finding any clues. Just wondering if anyone else had run into this before I devote time tracking it down (which could take awhile with my miserable python skills). This is from a list that has existing for several years and has survived though several mailman upgrades. I'm concerned that there my be rubbish in one of the pickled db files that might be causing other problems that I'm not aware of yet.... Traceback (most recent call last): File "../cron/disabled", line 209, in ? main() File "../cron/disabled", line 168, in main mlist.disableBouncingMember(member, info, msg) File "/home/mailman/Mailman/Bouncer.py", line 163, in disableBouncingMember self.sendNextNotification(member) File "/home/mailman/Mailman/Bouncer.py", line 243, in sendNextNotification {'listname' : self.real_name, File "/home/mailman/Mailman/OldStyleMemberships.py", line 102, in getMemberPassword raise Errors.NotAMemberError, member Mailman.Errors.NotAMemberError: mosterbrink@saturnee.com The address in question IS a member, and interestingly enough, doesn't show as disabled form the admin interface or when running list_members --nomail. I also find in the error log: Apr 18 18:07:05 2003 (29034) Uncaught runner exception: mosterbrink@saturnee.comApr 18 18:07:05 2003 (29034) Traceback (most recent call last): File "/home/mailman/Mailman/Queue/Runner.py", line 105, in _oneloop self._onefile(msg, msgdata) File "/home/mailman/Mailman/Queue/Runner.py", line 155, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/home/mailman/Mailman/Queue/BounceRunner.py", line 126, in _dispose mlist.registerBounce(addr, msg) File "/home/mailman/Mailman/Bouncer.py", line 155, in registerBounce self.disableBouncingMember(member, info, msg) File "/home/mailman/Mailman/Bouncer.py", line 163, in disableBouncingMember self.sendNextNotification(member) File "/home/mailman/Mailman/Bouncer.py", line 243, in sendNextNotification {'listname' : self.real_name, File "/home/mailman/Mailman/OldStyleMemberships.py", line 102, in getMemberPassword raise Errors.NotAMemberError, member NotAMemberError: mosterbrink@saturnee.com Apr 18 18:07:05 2003 (29034) SHUNTING: 1050714405.7204649+8f6a162efa552e48101820d5a680dba33c29e4c5 Anyone have any ideas? From admin at chirolists.com Thu May 1 10:03:58 2003 From: admin at chirolists.com (admin@chirolists.com) Date: Thu May 1 12:02:04 2003 Subject: [Mailman-Developers] Ignoring "mail." in domain names In-Reply-To: <89881531.1051782221@tomdual2> References: Message-ID: <5.2.0.9.0.20030501085710.00a946b8@jbod.calchiro.com> Tom, Hotmail also does the same thing, or at least they used to. I used to run into the issue more frequently when I was running Majordomo. It would seem to me that rather than hard-coding a string ("mail"), that one could see if there was more than one "." after the "@", if so parse out the domain (splonk.edu) and see if there is a match with JSmith@some_mail_server.splonk.edu.... Just a thot.... Brian At 09:43 AM 5/1/2003 -0400, Tom Neff wrote: >Another way we could really reduce moderator headaches would be to teach >Mailman to try removing a leading "mail." in the domain part of the address >if a member lookup fails. I get a lot of people who join lists as >JSmith@splonk.edu and end up posting (immediately or six months later) as >JSmith@mail.splonk.edu. If I had per-member aliases I could add them as >needed, but this one case is so pervasive that it might make more sense to do >it list-wide or even hard code it. > >_______________________________________________ >Mailman-Developers mailing list >Mailman-Developers@python.org >http://mail.python.org/mailman/listinfo/mailman-developers From jon at latchkey.com Thu May 1 12:08:19 2003 From: jon at latchkey.com (Jon Scott Stevens) Date: Thu May 1 14:08:28 2003 Subject: [Mailman-Developers] Feature request Message-ID: Wouldn't it be really cool if someone responds to a moderated posting asking to be removed from the list and it gets put into the moderation queue, that there is an option to remove that user from the list instead of having to go into the list admin interface (or command line) to remove the user? -jon From charlie at begeistert.org Thu May 1 23:12:33 2003 From: charlie at begeistert.org (Charlie Clark) Date: Thu May 1 16:12:10 2003 Subject: [Mailman-Developers] Re: Mailman-Developers External user database In-Reply-To: References: Message-ID: <20030501221233.896.4@wonderland.1051813410.fake> On 2003-04-30 at 23:32:02 [+0200], mailman-developers-request@python.org wrote: > > 1) External user database. I'm sure you're all aware of the desire of > > some > > folks to have this. I found a Wiki document somewhere on the zope.org > > site that had discussions on this but I believe it was somewhat dated. > > Have any conclusions been reached with respect to the direction here? I > > think I read talk of a Zope-specific solution. I'm wondering if this > > means that we're likely never to see a Mailman that can talk to a MySQL > > database. I believe this one feature alone would elevate Mailman > > significantly. How hgh of a priority is this to the development team > > and what is the status? Are there current discussions on this somewhere > > other than the list (wiki boards, chats, what-have-you) , and if so, > > may I take part? > > See MemberAdapter in Mailman 2.1.x. As it happens, I'm currently writing > an advanced LDAP backend [ yes, I've see the other one :-) ]. We are currently using a generic RDBMS adapter which is available (commercially) from the developer; I assume there are others out there. This is a non-trivial piece of work so I think it may be a while before it is part of core mailman. I cannot recommend using MySQL for this because it will not enforce data integrity which is one of the key reasons for using an RDBMS in my view another being size: our lists are due to get very, very big (100.000 + users) I think Mailman's data store gets pretty bloated on such lists. Charlie From kmccann at bellanet.org Thu May 1 17:30:36 2003 From: kmccann at bellanet.org (Kevin McCann) Date: Thu May 1 16:31:03 2003 Subject: [Mailman-Developers] Re: Mailman-Developers External user database In-Reply-To: <20030501221233.896.4@wonderland.1051813410.fake> References: Message-ID: <5.0.0.25.2.20030501161623.031e1d60@mail.idrc.ca> I think having a choice would be good. Sympa allows the use of a MySQL user database. And while I don't want to get into a Sympa vs. Mailman debate I have to say that the feature is attractive because it presents opportunities for those who want their MLM to be an integrated part of a bigger tool. There is a need for collaborative tools that go beyond the mailing list but I believe the mailing list is the foundation, the glue. And being able to easily integrate a proven MLM such as Mailman into a variety of scenarios would be a Good Thing. Zope / Plone + Mailman PHP/MySQL tools (eg Postnuke) + Mailman whatever-your-heart-desires + Mailman Cheers, Kevin At 10:12 PM 01/05/03 +0200, Charlie Clark wrote: >We are currently using a generic RDBMS adapter which is available >(commercially) from the developer; I assume there are others out there. >This is a non-trivial piece of work so I think it may be a while before it >is part of core mailman. I cannot recommend using MySQL for this because it >will not enforce data integrity which is one of the key reasons for using >an RDBMS in my view another being size: our lists are due to get very, very >big (100.000 + users) I think Mailman's data store gets pretty bloated on >such lists. > >Charlie From barry at python.org Thu May 1 21:58:57 2003 From: barry at python.org (Barry Warsaw) Date: Thu May 1 16:58:57 2003 Subject: [Mailman-Developers] Priority/status of moderated-edit and external user DB In-Reply-To: <009b01c30ac8$b8c82fd0$0501a8c0@kevinduron> References: <009b01c30ac8$b8c82fd0$0501a8c0@kevinduron> Message-ID: <1051822703.24341.95.camel@barry> On Thu, 2003-04-24 at 21:19, Kevin McCann wrote: > 1) External user database. I'm sure you're all aware of the desire of some > folks to have this. I found a Wiki document somewhere on the zope.org site > that had discussions on this but I believe it was somewhat dated. Have any > conclusions been reached with respect to the direction here? I think I read > talk of a Zope-specific solution. I'm wondering if this means that we're > likely never to see a Mailman that can talk to a MySQL database. I believe > this one feature alone would elevate Mailman significantly. How hgh of a > priority is this to the development team and what is the status? Are there > current discussions on this somewhere other than the list (wiki boards, > chats, what-have-you) , and if so, may I take part? This mailing list is the best place to discuss such things. Wiki gardening takes too much time. ;} As Jeff Waugh mentions, Mailman 2.1 provides an interface through which it does all its user access, and a MailList extension mechanism you can use to substitute other MemberAdaptor implementations for the default legacy one. While the 2.1 approach is a step in the right direction (I have an experimental BerkeleyDB-based backend checked into the cvs head), there are a few problems with it: - It is a pretty inefficient interface for some tasks, most notably the admin membership management u/i. To build this u/i it has to load the entire user database into memory, even to display just a chunk of 30 addresses. - The design is still list-centric. While I believe you could implement a backend that unifies the user database (e.g. barry@zope.com on list1 has the same user profile as barry@zope.com on list2), I want to make this much more evident in the interface designs. I want to invert the focus of Mailman from being list-centric to being user-centric. > 2) Moderated-edit. I'm running Mailman on a couple of boxes but I also have > a few hundred lists on a box running Lyris. I want to move them but one of > the deal breakers at the moment is moderated-edit - the ability of a > moderator to edit a message before it goes out. I personally don't use this > feature for the lists I am the admin of but this seems to be a very > important feature to some. An absolute must, in fact. I'm wonderig if this > is in the cards, is it high on the priority list, should we expect to see it > soon? There is kludgey support for this now, that most people are probably not aware of: in the admindb interface, you forward the message to yourself. Then you use whatever tools you want to edit the message and resend it back to the list with the Approved header. Then you delete the message from the admindb. Not exactly the most efficient workflow. ;) The thing that's always held me back here is designing a useable u/i to such a feature. Actually doing the editing probably isn't difficult, but I'm far from a web u/i expert. Doing it in a way that won't get clobbered by huge messages, be vulnerable to cross-site scripting or other security issues, and that provides a natural editing interface, is a big task. I wish there was some free tool we could just bolt on to do this -- I'm wondering if something like SquirrelMail could be appropriated for the task? > I understand this is a non-paying gig for Barry and others, and I understand > there are likely a ton of other items to deal with. But knowing what the > priority and status of these two items are would give me a realistic idea of > when I might be able to drop the oh-so-commercial Lyris. Hopefully the above gives some indication of the direction. I don't have much to say at the moment about ETA for any of this stuff, except that I'm beginning to experiment and write interfaces. > Finally, I'm not a Python programmer (yet), mostly Perl and PHP. But if I > can help the cause in non-Python coding ways let me know. I'm sure Python will be easy for you to pick up . I wonder if we can start talking about how to get the community to take over more of the maintenance of the 2.1 branch so that I can start concentrating on the 3.0 work? Trying to do both in my spare time is difficult. -Barry From barry at python.org Thu May 1 22:03:23 2003 From: barry at python.org (Barry Warsaw) Date: Thu May 1 17:03:24 2003 Subject: [Mailman-Developers] Re: Mailman-Developers External user database In-Reply-To: <20030501221233.896.4@wonderland.1051813410.fake> References: <20030501221233.896.4@wonderland.1051813410.fake> Message-ID: <1051822967.24341.98.camel@barry> On Thu, 2003-05-01 at 16:12, Charlie Clark wrote: > We are currently using a generic RDBMS adapter which is available > (commercially) from the developer; I assume there are others out there. > This is a non-trivial piece of work so I think it may be a while before it > is part of core mailman. I cannot recommend using MySQL for this because it > will not enforce data integrity which is one of the key reasons for using > an RDBMS in my view another being size: our lists are due to get very, very > big (100.000 + users) I think Mailman's data store gets pretty bloated on > such lists. Yep, see my previous posting about the bloat issue. Mailman has to load the entire user database into memory to act on it and this sucks. The other issue is that updates to the list data and by extension the user data should be transactionally protected. This is possible in Mailman 2.1.2 although it may not be completely obvious. The BerkeleyDB adaptor in cvs utilizes this. -Barry From barry at python.org Thu May 1 22:04:24 2003 From: barry at python.org (Barry Warsaw) Date: Thu May 1 17:04:25 2003 Subject: [Mailman-Developers] Re: Mailman-Developers External user database In-Reply-To: <5.0.0.25.2.20030501161623.031e1d60@mail.idrc.ca> References: <5.0.0.25.2.20030501161623.031e1d60@mail.idrc.ca> Message-ID: <1051823032.24341.100.camel@barry> On Thu, 2003-05-01 at 16:30, Kevin McCann wrote: > And being able to easily integrate a proven MLM such as Mailman into a > variety of scenarios would be a Good Thing. > > Zope / Plone + Mailman > > PHP/MySQL tools (eg Postnuke) + Mailman > > whatever-your-heart-desires + Mailman You've been peeking in on my dreams, huh? :) okay-so-they're-boring-ly y'rs, -Barry From admin at chirolists.com Thu May 1 16:10:50 2003 From: admin at chirolists.com (admin@chirolists.com) Date: Thu May 1 18:08:52 2003 Subject: [Mailman-Developers] Priority/status of moderated-edit and external user DB In-Reply-To: <1051822703.24341.95.camel@barry> References: <009b01c30ac8$b8c82fd0$0501a8c0@kevinduron> <009b01c30ac8$b8c82fd0$0501a8c0@kevinduron> Message-ID: <5.2.0.9.0.20030501150716.027080b0@jbod.calchiro.com> Barry, You are right about Python. Fun and not too tough to learn. What kind of help are you looking for? I've been programming for a while...I started on a Trash 80 back in the day. Mostly been doing 'web/db stuff the past few years. I've started playing around with some of the admindb stuff, working on getting the interface to look a bit more purdy. I was planning to poke around and see if I could set up a way to allow an admin to more easily add a logo to all pages, etc. Brian At 04:58 PM 5/1/2003 -0400, Barry Warsaw wrote: >On Thu, 2003-04-24 at 21:19, Kevin McCann wrote: > > > 1) External user database. I'm sure you're all aware of the desire of some > > folks to have this. I found a Wiki document somewhere on the zope.org site > > that had discussions on this but I believe it was somewhat dated. Have any > > conclusions been reached with respect to the direction here? I think I read > > talk of a Zope-specific solution. I'm wondering if this means that we're > > likely never to see a Mailman that can talk to a MySQL database. I believe > > this one feature alone would elevate Mailman significantly. How hgh of a > > priority is this to the development team and what is the status? Are there > > current discussions on this somewhere other than the list (wiki boards, > > chats, what-have-you) , and if so, may I take part? > >This mailing list is the best place to discuss such things. Wiki >gardening takes too much time. ;} > >As Jeff Waugh mentions, Mailman 2.1 provides an interface through which >it does all its user access, and a MailList extension mechanism you can >use to substitute other MemberAdaptor implementations for the default >legacy one. > >While the 2.1 approach is a step in the right direction (I have an >experimental BerkeleyDB-based backend checked into the cvs head), there >are a few problems with it: > >- It is a pretty inefficient interface for some tasks, most notably the >admin membership management u/i. To build this u/i it has to load the >entire user database into memory, even to display just a chunk of 30 >addresses. > >- The design is still list-centric. While I believe you could implement >a backend that unifies the user database (e.g. barry@zope.com on list1 >has the same user profile as barry@zope.com on list2), I want to make >this much more evident in the interface designs. I want to invert the >focus of Mailman from being list-centric to being user-centric. > > > 2) Moderated-edit. I'm running Mailman on a couple of boxes but I also have > > a few hundred lists on a box running Lyris. I want to move them but one of > > the deal breakers at the moment is moderated-edit - the ability of a > > moderator to edit a message before it goes out. I personally don't use this > > feature for the lists I am the admin of but this seems to be a very > > important feature to some. An absolute must, in fact. I'm wonderig if this > > is in the cards, is it high on the priority list, should we expect to > see it > > soon? > >There is kludgey support for this now, that most people are probably not >aware of: in the admindb interface, you forward the message to yourself. >Then you use whatever tools you want to edit the message and resend it >back to the list with the Approved header. Then you delete the message >from the admindb. Not exactly the most efficient workflow. ;) > >The thing that's always held me back here is designing a useable u/i to >such a feature. Actually doing the editing probably isn't difficult, >but I'm far from a web u/i expert. Doing it in a way that won't get >clobbered by huge messages, be vulnerable to cross-site scripting or >other security issues, and that provides a natural editing interface, is >a big task. I wish there was some free tool we could just bolt on to do >this -- I'm wondering if something like SquirrelMail could be >appropriated for the task? > > > I understand this is a non-paying gig for Barry and others, and I > understand > > there are likely a ton of other items to deal with. But knowing what the > > priority and status of these two items are would give me a realistic > idea of > > when I might be able to drop the oh-so-commercial Lyris. > >Hopefully the above gives some indication of the direction. I don't have >much to say at the moment about ETA for any of this stuff, except that >I'm beginning to experiment and write interfaces. > > > Finally, I'm not a Python programmer (yet), mostly Perl and PHP. But if I > > can help the cause in non-Python coding ways let me know. > >I'm sure Python will be easy for you to pick up . > >I wonder if we can start talking about how to get the community to take >over more of the maintenance of the 2.1 branch so that I can start >concentrating on the 3.0 work? Trying to do both in my spare time is >difficult. > >-Barry > > > >_______________________________________________ >Mailman-Developers mailing list >Mailman-Developers@python.org >http://mail.python.org/mailman/listinfo/mailman-developers Thanks, The admin staff admin@chirolists.com From colinp at waikato.ac.nz Fri May 2 15:00:10 2003 From: colinp at waikato.ac.nz (Colin Palmer) Date: Thu May 1 22:00:48 2003 Subject: [Mailman-Developers] Subject: MTA assisted VERP (Postfix/Qmail) Message-ID: Just making my own announcment about these patches since tracker messages don't get posted to this list anymore. Firstly, the latest, I-think-it-actually-works-now release of the Qmail.py delivery handler: http://sourceforge.net/tracker/?func=detail&aid=645513&group_id=103&atid=300103 And, due to an enforced switch from Qmail to Postfix at work, here's a patch to SMTPDirect.py that does VERP in Postfix: http://sourceforge.net/tracker/?func=detail&aid=731100&group_id=103&atid=300103 Both have been tested in production and work for me. -- ** Colin Palmer, Systems and Development Group, University of Waikato, NZ ** From barry at python.org Fri May 2 04:16:20 2003 From: barry at python.org (Barry Warsaw) Date: Thu May 1 23:16:23 2003 Subject: [Mailman-Developers] Re: monthly notification error In-Reply-To: <1051804652.26686.91.camel@o3> References: <1051804652.26686.91.camel@o3> Message-ID: <1051845350.1655.33.camel@geddy> On Thu, 2003-05-01 at 11:57, Eric D. Christensen wrote: > > I'm running debian/testing and just upgraded mailman to the version > > in unstable (2.1.1-5). Last night the cron job to send out the monthly > > password reminders failed with this error: > > > > Traceback (most recent call last): > > File "/usr/lib/mailman/cron/mailpasswds", line 218, in ? > > main() > > File "/usr/lib/mailman/cron/mailpasswds", line 145, in main > > password = mlist.getMemberPassword(member) > > File "/var/lib/mailman/Mailman/OldStyleMemberships.py", line 102, in > > getMemberPassword > > raise Errors.NotAMemberError, member > > Mailman.Errors.NotAMemberError: rick@niof.net > > > > Is there some upgrade configuring I need to do? I did create the > > 'mailman' mailing list. Do I need to add myself as a subscriber? > > Should I send a bugreport to the debian maintainer? > > It's not just Debian... I'm running 2.1.1 on Linux and had the same > problem. Probably worth filing a bug report against mailman since there > are at least two of us seeing the same problems on different platforms > now. > > I've also see this when running the cron/disabled script. It always > seems to be with one specific user, which makes me suspect something > that didn't translate correctly in the database. Attached below are the > details I reported earlier. > > Barry - if it would be helpful, I'd be happy to give you access to the > mailman account on my server so you can poke around. I'd generally not like to have access unless there's no other way. But I think the only way this can happen is if you've got an address that for some reason never got a password assigned to them. You can try the attached bin/withlist script to see if there are any password-less members in your database. Save this to bin/verify.py. I think there were situations in older versions where a member could get subscribed w/o a password. I think Mailman should just auto-assign one in that case. -Barry def verify(mlist): members = {} for m in mlist.members.keys(): members[m] = None for m in mlist.digest_members.keys(): members[m] = None for m, p in mlist.passwords.items(): if not members.has_key(m): print 'password for non-member:', m else: members[m] = p for m, p in members.items(): if p is None: print 'no password for member:', m print 'done' From barry at python.org Fri May 2 04:47:28 2003 From: barry at python.org (Barry Warsaw) Date: Thu May 1 23:47:29 2003 Subject: [Mailman-Developers] Re: monthly notification error In-Reply-To: <1051845350.1655.33.camel@geddy> References: <1051804652.26686.91.camel@o3> <1051845350.1655.33.camel@geddy> Message-ID: <1051847221.1655.37.camel@geddy> On Thu, 2003-05-01 at 23:15, Barry Warsaw wrote: > I think the only way this can happen is if you've got an address that > for some reason never got a password assigned to them. I just checked in a patch to make mailpasswds a little more robust in this case. It'll log the password-less address and continue. -Barry From barry at python.org Fri May 2 04:51:20 2003 From: barry at python.org (Barry Warsaw) Date: Thu May 1 23:51:21 2003 Subject: [Mailman-Developers] Ignoring "mail." in domain names In-Reply-To: <89881531.1051782221@tomdual2> References: <89881531.1051782221@tomdual2> Message-ID: <1051847448.1655.41.camel@geddy> On Thu, 2003-05-01 at 09:43, Tom Neff wrote: > Another way we could really reduce moderator headaches would be to teach > Mailman to try removing a leading "mail." in the domain part of the address > if a member lookup fails. I get a lot of people who join lists as > JSmith@splonk.edu and end up posting (immediately or six months later) as > JSmith@mail.splonk.edu. If I had per-member aliases I could add them as > needed, but this one case is so pervasive that it might make more sense to do > it list-wide or even hard code it. Mailman used to do stuff like this, but it was pretty error-prone. I think the best long-term solution is to allow members to specify posting aliases. -Barry From barry at python.org Fri May 2 05:03:09 2003 From: barry at python.org (Barry Warsaw) Date: Fri May 2 00:03:10 2003 Subject: [Mailman-Developers] Hacking at MM In-Reply-To: <5.2.0.9.0.20030430124630.026f9888@jbod.calchiro.com> References: <5.2.0.9.0.20030430124630.026f9888@jbod.calchiro.com> Message-ID: <1051848164.1655.45.camel@geddy> On Wed, 2003-04-30 at 15:48, admin@chirolists.com wrote: > I've been doing a bit of hacking on MM the past couple of weeks, mainly > HTML related formatting (straight and in python)...I was kinda curious how > someone got involved in the project.... The best thing to do is to start posting patches to SourceForge. I've been way behind on processing them, but as 2.1 gets more stable, it will be time to start thinking about the next version. -Barry From barry at python.org Fri May 2 05:44:02 2003 From: barry at python.org (Barry Warsaw) Date: Fri May 2 00:44:03 2003 Subject: [Mailman-Developers] Mails get lost with different 2.1.x mailmans, including today's CVS In-Reply-To: <1051534792.14541.67.camel@linux.local> References: <1051534792.14541.67.camel@linux.local> Message-ID: <1051850618.12896.1.camel@geddy> On Mon, 2003-04-28 at 08:59, Tonu Samuel wrote: > New to this list but checked FAQ. Was not able to find solution. I am > using mailman from CVS and this bug seems to be unfixed. > Original mail subject line in raw data: > > Subject: =?windows-1257?Q?FW:_=E4=E4test_kustutage_=E4ra?= Hmm, I just send such a message through my test list and it came through just fine. What version of Python are you using? It would help to see the logs/error message and if possible, a copy of the message that's getting shunted. -Barry From tneff at bigfoot.com Fri May 2 01:54:46 2003 From: tneff at bigfoot.com (Tom Neff) Date: Fri May 2 00:54:49 2003 Subject: [Mailman-Developers] Ignoring "mail." in domain names In-Reply-To: <1051847448.1655.41.camel@geddy> References: <89881531.1051782221@tomdual2> <1051847448.1655.41.camel@geddy> Message-ID: <144545937.1051836886@tomdual2> --On Thursday, May 01, 2003 11:50 PM -0400 Barry Warsaw wrote: > On Thu, 2003-05-01 at 09:43, Tom Neff wrote: >> Another way we could really reduce moderator headaches would be to teach >> Mailman to try removing a leading "mail." in the domain part of the address >> if a member lookup fails. I get a lot of people who join lists as >> JSmith@splonk.edu and end up posting (immediately or six months later) as >> JSmith@mail.splonk.edu. If I had per-member aliases I could add them as >> needed, but this one case is so pervasive that it might make more sense to >> do it list-wide or even hard code it. > > Mailman used to do stuff like this, but it was pretty error-prone. I > think the best long-term solution is to allow members to specify posting > aliases. I'll take it! I'll take it! :) From jdub at perkypants.org Fri May 2 16:15:30 2003 From: jdub at perkypants.org (Jeff Waugh) Date: Fri May 2 01:34:08 2003 Subject: [Mailman-Developers] Priority/status of moderated-edit and external user DB In-Reply-To: <1051822703.24341.95.camel@barry> References: <009b01c30ac8$b8c82fd0$0501a8c0@kevinduron> <1051822703.24341.95.camel@barry> Message-ID: <20030502051530.GX31770@lazarus> > While the 2.1 approach is a step in the right direction (I have an > experimental BerkeleyDB-based backend checked into the cvs head), there > are a few problems with it: > > - It is a pretty inefficient interface for some tasks, most notably the > admin membership management u/i. To build this u/i it has to load the > entire user database into memory, even to display just a chunk of 30 > addresses. I sort of suspected this when I first started hacking on it, but wanted to get my hands dirty before saying anything about it. Would you want backends to provide iterators? I guess it's a moot point considering what you say next: > - The design is still list-centric. While I believe you could implement > a backend that unifies the user database (e.g. barry@zope.com on list1 > has the same user profile as barry@zope.com on list2), I want to make > this much more evident in the interface designs. I want to invert the > focus of Mailman from being list-centric to being user-centric. *yes!* :-) That would provide so many plusses both for users and the code. It would be a really good change, one I've been thinking about here and there whilst doing the LDAP backend. It would definitely make integration with different backends easier. One thing I'm working on at the moment is list abstraction, so you can store all of the list information in different formats (I'm primarily interested in LDAP at the moment. With a few changes, there is the potential for dynamic membership too (ie. "the members of this list are found via this LDAP query"). I can't do all of this within the scope of my current contract, so if anyone's interested in LDAP integration, seriously scalable backends, or paying someone to help with the changes Barry describes above, please get in touch. :-) > I wonder if we can start talking about how to get the community to take > over more of the maintenance of the 2.1 branch so that I can start > concentrating on the 3.0 work? Trying to do both in my spare time is > difficult. That's possibly a good entry point for me, though I'm not too familiar with the rest of the codebase (beyond lists/members, backends, etc). I'm also pretty swamped with GNOME stuff too. But we'll see. :-) Thanks, - Jeff -- linux.conf.au 2004: Adelaide, Australia http://lca2004.linux.org.au/ "When you're running, you want to run as far as you can, and you can't run further than Australia." - Jacek Koman From edc at proadmin.com Fri May 2 17:53:52 2003 From: edc at proadmin.com (Eric D. Christensen) Date: Fri May 2 12:53:54 2003 Subject: [Mailman-Developers] Re: monthly notification error In-Reply-To: <1051845350.1655.33.camel@geddy> References: <1051804652.26686.91.camel@o3> <1051845350.1655.33.camel@geddy> Message-ID: <1051894396.25213.5.camel@o3> On Thu, 2003-05-01 at 20:15, Barry Warsaw wrote: > > I think the only way this can happen is if you've got an address that > for some reason never got a password assigned to them. Thanks Barry! Indeed, the problem user who didn't have a password. I set one for him and things seem to be working nicely now. > I think there were situations in older versions where a member could get > subscribed w/o a password. I think Mailman should just auto-assign one > in that case. That's what I gut for letting users hang around for years. I guess I should boot the old users off the lists once they've hung around for 4 or 5 years! :-) Thanks again for the support Barry! -- Eric D. Christensen Proadmin, Inc. From boettiger at pobox.com Fri May 2 11:24:42 2003 From: boettiger at pobox.com (Adam Boettiger) Date: Fri May 2 13:25:18 2003 Subject: [Mailman-Developers] Developer help In-Reply-To: <20030427160242.GL11992@lazarus> Message-ID: I'd like to hire someone to help walk me through an upgrade install of mailman. I wanted to install the patch that allows you to modify held posts, but the documentation said that after installing the patch I must regenerate all of the lists. Is this true? Do you really have to regenerate all of your lists each time you install a patch or upgrade? It seems to me that this would be a real detriment to upgrading or installing new patches and quite time consuming. Is there a developer on this list that I could pay to walk me through the new upgrade install and ask a few newbie questions to? Thx AB From mch at cix.compulink.co.uk Fri May 2 22:48:00 2003 From: mch at cix.compulink.co.uk (Mike Holderness) Date: Fri May 2 16:49:00 2003 Subject: [Mailman-Developers] Moderated-edit Message-ID: Barry Warsaw wrote, inter alia: > > 2) Moderated-edit. I'm running Mailman on a couple of boxes but I > > There is kludgey support for this now, that most people are probably not > aware of: in the admindb interface, you forward the message to yourself. > Then you use whatever tools you want to edit the message and resend it > back to the list with the Approved header. Then you delete the message > from the admindb. Not exactly the most efficient workflow. ;) Ah, that's it. And what is the Approved header like? Can't find it in the www.lists.org documentation. Currently waiting to see whether List-Approved: works. Well, it wasn't a *bad* guess... but it was wrong, in that the message still came up requiring moderation. > The thing that's always held me back here is designing a useable u/i to > such a feature. Actually doing the editing probably isn't difficult, > but I'm far from a web u/i expert. Doing it in a way that won't get > clobbered by huge messages, be vulnerable to cross-site scripting or > other security issues, and that provides a natural editing interface, is > a big task. I wish there was some free tool we could just bolt on to do > this -- I'm wondering if something like SquirrelMail could be > appropriated for the task? Wouldn't it be enough to offer editing in the standard TEXTAREA, having first checked that the message isn't stupidly large? Then users who sent stupidly large messages that needed editing, or non-plain-text attachments that needed editing, would simply get them bounced. And then they might get to grasp the virtues of plain text and brevity. Which would be a Good Thing. (List I moderate have a max message size of 10k and no attachments. More than that is too much to be skimming.) I've briefly tried and failed to think of an exploit that works in a TEXTAREA. Someone will be along in a moment to correct me. Mike From Daniel.Buchmann at bibsys.no Fri May 2 23:01:16 2003 From: Daniel.Buchmann at bibsys.no (Daniel Buchmann) Date: Fri May 2 18:01:17 2003 Subject: [Mailman-Developers] Moderated-edit In-Reply-To: References: Message-ID: <1051912571.2747.9.camel@fornax.hjemme.bibsys.no> On Fri, 2003-05-02 at 22:48, Mike Holderness wrote: > Ah, that's it. And what is the Approved header like? I believe it was: Approved: > Can't find it in the www.lists.org documentation. See http:////admindb/?details=instructions (or ~mailman/templates/en/admindbdetails.html) :) -Daniel -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 232 bytes Desc: This is a digitally signed message part Url : http://mail.python.org/pipermail/mailman-developers/attachments/20030502/54da5552/attachment.bin From colin at mackinlay.demon.co.uk Sat May 3 10:49:21 2003 From: colin at mackinlay.demon.co.uk (Colin Mackinlay) Date: Sat May 3 04:53:00 2003 Subject: [Mailman-Developers] Multiple bounces in 1 reply Message-ID: I have started to receive bounce messages grouped together and mailman can't recognise them. Is this an unusual bounce format not worth the effort or is it worth adding to the "to do" list? The bounce contents are: This is the mail delivery agent at messagelabs.com. I was not able to deliver your message to the following addresses. : 65.54.253.99 does not like recipient. Remote host said: 550 Requested action not taken: mailbox unavailable : 194.73.73.118 does not like recipient. Remote host said: 550 Unknown local part xxx in : 205.158.62.33 does not like recipient. Remote host said: 550 : inactive user This is the mail delivery agent at messagelabs.com. --- Below this line is a copy of the message. -- Colin Mackinlay From terri at zone12.com Mon May 5 03:22:45 2003 From: terri at zone12.com (Terri Oda) Date: Mon May 5 02:21:06 2003 Subject: [Mailman-Developers] Members' documentation for 2.1 Message-ID: <20030505062245.GA1602@ostraya.zone12.com> I've checked in member (subscriber, user) documentation for 2.1. It's available in cvs or on my website. CVS gives only the tex source, and since I imagine people would rather read the final output, I've also uploaded some generated copies to my website in various formats. Some proofreading's been done by people who are list users (but aren't list maintainers), but I'm sure more comments would make for a better document, so feel free to make suggestions or point out missed typos! Link for the web cvs: http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/mailman/mailman/doc/mailman-member.tex Link for the generated copies on my website: http://terri.zone12.com/doc/ Terri From a.carter at cordis.lu Mon May 5 11:56:51 2003 From: a.carter at cordis.lu (CARTER Anthony) Date: Mon May 5 04:56:58 2003 Subject: [Mailman-Developers] public and private archives problem In-Reply-To: <3EB0156B.4020204@isu.edu> References: <3EB013FD.7090506@isu.edu> <3EB0156B.4020204@isu.edu> Message-ID: <200305051056.51942.a.carter@intrasoft.lu> How did you fix this? I am getting this too. Thanks, Anthony On Wednesday 30 April 2003 20:26, Kory Wheatley wrote: > Never Miind I fixed the problem. > > Kory Wheatley wrote: > > I'm getting this below error when an user tries to open up there > > archives. I've run check_perms and all the permissions are correct. > > When I change the archive options on this list to public I get this > > below error when I change it back to private I can view the threaded > > archives fine, is there a solution to this. I've tested this with my > > other lists and it does the same thing. There most be something that > > I've got configured wrong that a list can't be setup to view the > > archives in the (public) setting. > > > > > > ACCESS DENIED ! > > > > You don't have permission to access the requested directory. There > > is either no index document or the directory is read-protected. > > > > If you think this is a server error, please contact the webmaster > > > > ERROR 403 > > > > mm.isu.edu > > Wed Apr 30 11:47:13 2003 > > Apache/2.0.40 (Red Hat Linux) From maechler at stat.math.ethz.ch Mon May 5 12:28:16 2003 From: maechler at stat.math.ethz.ch (Martin Maechler) Date: Mon May 5 05:28:27 2003 Subject: [Mailman-Developers] 2.1.2 -- still "Uncaught runner exception: unknown encoding" Message-ID: <16054.11952.441927.867305@gargle.gargle.HOWL> Dear Barry and co-developers, thanks a lot for 2.1.2 and all the bugs you've fixed! With 2.1.1 (installed early March here), I had started to allow for some mailing lists all available different languages, including Japanese, e.g. and I see that some users gladly chose them. Maybe that's the reason for things like the following {cut&paste}ed from the data/logs/error file Regards, Martin Maechler http://stat.ethz.ch/~maechler/ Seminar fuer Statistik, ETH-Zentrum LEO C16 Leonhardstr. 27 ETH (Federal Inst. Technology) 8092 Zurich SWITZERLAND phone: x-41-1-632-3408 fax: ...-1228 <>< -------- cut from data/logs/error ----------------------------- May 05 09:52:37 2003 (23520) SHUNTING: 1052121156.282855+3ec8467f1fdc497d2189844244854948fc4c7c6b May 05 09:52:40 2003 (23520) Uncaught runner exception: unknown encoding May 05 09:52:40 2003 (23520) Traceback (most recent call last): File "/usr/local/app/mailman-sfs/2.1.2/Mailman/Queue/Runner.py", line 105, in _oneloop self._onefile(msg, msgdata) File "/usr/local/app/mailman-sfs/2.1.2/Mailman/Queue/Runner.py", line 155, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/local/app/mailman-sfs/2.1.2/Mailman/Queue/CommandRunner.py", line 218, in _dispose res = Results(mlist, msg, msgdata) File "/usr/local/app/mailman-sfs/2.1.2/Mailman/Queue/CommandRunner.py", line 75, in __init__ subj = make_header(decode_header(subj)).__unicode__() File "/usr/local/app/mailman-sfs/2.1.2/pythonlib/email/Header.py", line 144, in make_header h.append(s, charset) File "/usr/local/app/mailman-sfs/2.1.2/pythonlib/email/Header.py", line 272, in append ustr = unicode(s, incodec, errors) LookupError: unknown encoding May 05 09:52:40 2003 (23520) SHUNTING: 1052121160.428594+dd539dae2deaafc3ecd67c30e303dfaac826f882 May 05 09:52:47 2003 (23520) Uncaught runner exception: unknown encoding May 05 09:52:47 2003 (23520) Traceback (most recent call last): File "/usr/local/app/mailman-sfs/2.1.2/Mailman/Queue/Runner.py", line 105, in _oneloop self._onefile(msg, msgdata) File "/usr/local/app/mailman-sfs/2.1.2/Mailman/Queue/Runner.py", line 155, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/local/app/mailman-sfs/2.1.2/Mailman/Queue/CommandRunner.py", line 218, in _dispose res = Results(mlist, msg, msgdata) File "/usr/local/app/mailman-sfs/2.1.2/Mailman/Queue/CommandRunner.py", line 75, in __init__ subj = make_header(decode_header(subj)).__unicode__() File "/usr/local/app/mailman-sfs/2.1.2/pythonlib/email/Header.py", line 144, in make_header h.append(s, charset) File "/usr/local/app/mailman-sfs/2.1.2/pythonlib/email/Header.py", line 272, in append ustr = unicode(s, incodec, errors) LookupError: unknown encoding May 05 09:52:47 2003 (23520) SHUNTING: 1052121167.541289+1866a13cdc22d889275125bb124ecb58ae5fceb9 From barry at python.org Mon May 5 16:00:41 2003 From: barry at python.org (Barry Warsaw) Date: Mon May 5 11:00:43 2003 Subject: [Mailman-Developers] Members' documentation for 2.1 In-Reply-To: <20030505062245.GA1602@ostraya.zone12.com> References: <20030505062245.GA1602@ostraya.zone12.com> Message-ID: <1052146808.21413.20.camel@barry> On Mon, 2003-05-05 at 02:22, Terri Oda wrote: > I've checked in member (subscriber, user) documentation for 2.1. It's > available in cvs or on my website. CVS gives only the tex source, and > since I imagine people would rather read the final output, I've also > uploaded some generated copies to my website in various formats. > > Some proofreading's been done by people who are list users (but aren't list > maintainers), but I'm sure more comments would make for a better document, > so feel free to make suggestions or point out missed typos! > > Link for the web cvs: > http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/mailman/mailman/doc/mailman-member.tex > > Link for the generated copies on my website: > http://terri.zone12.com/doc/ Awesome Terri! I'm giving you a standing ovation right now. :) I'm going to print out a copy and read it during lunch. I skimmed it a bit and it looked pretty good, but I have an easier time reading stuff like this on dead tree carcasses. -Barry From maechler at stat.math.ethz.ch Mon May 5 18:03:32 2003 From: maechler at stat.math.ethz.ch (Martin Maechler) Date: Mon May 5 11:03:42 2003 Subject: [Mailman-Developers] Uncaught bounce ... still in mailman 2.1.2 Message-ID: <16054.32068.347446.515739@gargle.gargle.HOWL> Dear developers here's an example of an "uncaught bounce notification" where I believe mailman *should* catch. Regards, Martin -------------- next part -------------- An embedded message was scrubbed... From: mailman-bounces@stat.math.ethz.ch Subject: Uncaught bounce notification Date: Mon, 05 May 2003 11:40:03 +0200 Size: 5583 Url: http://mail.python.org/pipermail/mailman-developers/attachments/20030505/c75e7257/attachment.eml From dag at sonsorol.org Tue May 6 17:38:24 2003 From: dag at sonsorol.org (Chris Dagdigian) Date: Tue May 6 16:38:32 2003 Subject: [Mailman-Developers] advice needed: shunt problems with MM2.1 and 2.1.2 only on one list out of many Message-ID: <3EB81D40.5060504@sonsorol.org> Hello, {First off thanks for a fantastic package...we've been using MM for several years on bioperl.org} I've got one list out of many on our MM server that has not processed a new email since May 1st. The messages are apparently all in the shunt/ dir and running bin/unshunt just repeats the same traceback errors. Tried googling, tried the archives and tried upgrading from 2.1 to 2.1.2 but I'm still having a serious problem with the bioperl-l@bioperl.org mailing list. It also happens to be our biggest and most active list so I'm starting to get a bit stressed. Google searching on "shunt errors" and "TypeError: iterable argument required" brought me to a page where it was suggested that there was a unicode parsing bug that triggers when subscribers have 8-bit encoded chars. I did find one subscriber who had funky chars in his "name" field and deleted it via the web admin. Running "list_list" verified that the subscriber list looks OK otherwise. Sent a test message to the list and it still got shunted with a traceback error message. The message.pck file is attached. I'll happily supply the .db file if it would be useful. The actual traceback is this: > May 06 16:31:39 2003 (14914) Uncaught runner exception: iterable argument required > May 06 16:31:39 2003 (14914) Traceback (most recent call last): > File "/home/mailman/Mailman/Queue/Runner.py", line 105, in _oneloop > self._onefile(msg, msgdata) > File "/home/mailman/Mailman/Queue/Runner.py", line 155, in _onefile > keepqueued = self._dispose(mlist, msg, msgdata) > File "/home/mailman/Mailman/Queue/IncomingRunner.py", line 130, in _dispose > more = self._dopipeline(mlist, msg, msgdata, pipeline) > File "/home/mailman/Mailman/Queue/IncomingRunner.py", line 153, in _dopipeline > sys.modules[modname].process(mlist, msg, msgdata) > File "/home/mailman/Mailman/Handlers/ToDigest.py", line 89, in process > send_digests(mlist, mboxfp) > File "/home/mailman/Mailman/Handlers/ToDigest.py", line 130, in send_digests > send_i18n_digests(mlist, mboxfp) > File "/home/mailman/Mailman/Handlers/ToDigest.py", line 303, in send_i18n_digests > msg = scrubber(mlist, msg) > File "/home/mailman/Mailman/Handlers/Scrubber.py", line 257, in process > url = save_attachment(mlist, part, dir) > File "/home/mailman/Mailman/Handlers/Scrubber.py", line 349, in save_attachment > ext = guess_extension(ctype, fnext) > File "/home/mailman/Mailman/Handlers/Scrubber.py", line 80, in guess_extension > if ext in all: > TypeError: iterable argument required > > May 06 16:31:39 2003 (14914) SHUNTING: 1052253095.709591+38e71a4dd22ea87b3961d1aa1c14d08e16d2683c Any advice or pointers would be deeply appreciated. Regards, Chris open-bio.org list admin -- Chris Dagdigian, BioTeam Inc. - Independent Bio-IT & Informatics consulting Office: 617-666-6454, Mobile: 617-877-5498, Fax: 425-699-0193 PGP KeyID: 83D4310E Yahoo IM: craffi Web: http://bioteam.net -------------- next part -------------- A non-text attachment was scrubbed... Name: shunted-msg.pck Type: application/octet-stream Size: 2592 bytes Desc: not available Url : http://mail.python.org/pipermail/mailman-developers/attachments/20030506/765a40d4/shunted-msg.obj From donn at u.washington.edu Tue May 6 15:39:06 2003 From: donn at u.washington.edu (Donn Cave) Date: Tue May 6 17:39:10 2003 Subject: [Mailman-Developers] message data storage Message-ID: <200305062139.h46Ld6u6025778@mailhost1.u.washington.edu> I'm breathing easier this week, now that a new month has started. At the end of April, one of our new lists was up to 6500 archived messages for the month. It takes close to 4 minutes CPU time to archive a message in a situation like that. The average delivery rate to achieve 6500 messages in 30 days is 1 per 6 minutes, so the system obviously cannot work. I intervened and threw away a couple hundred of them (it's drivel) to break the logjam and get everyone else going. We have only a fraction of our expected population so far, we're just beginning to migrate in earnest from listproc, so it looks like we're in some trouble. Most of the work appears to be in the 68Mb database, as in database/2003-April-article. It can take up to a minute to get this through marshal.load(), almost all of it disk I/O. It takes nearly 3 minutes CPU time to get all the values through cPickle.loads(), and I believe the archiver does in fact load every single one. Working with the current system (as opposed to the Next Generation archiver), I'm tempted to think about a semi-permanent per-archive archiver and queue. The archiver would exit when its queue has been empty for some short interval, but any extra messages that arrive during that time get the database for free. I'd be interested in any other ideas. thanks, Donn Cave, donn@u.washington.edu From pioppo at ferrara.linux.it Wed May 7 00:53:10 2003 From: pioppo at ferrara.linux.it (Simone Piunno) Date: Tue May 6 17:55:22 2003 Subject: [Mailman-Developers] message data storage In-Reply-To: <200305062139.h46Ld6u6025778@mailhost1.u.washington.edu> References: <200305062139.h46Ld6u6025778@mailhost1.u.washington.edu> Message-ID: <200305062353.10785.pioppo@ferrara.linux.it> On Tuesday 06 May 2003 23:39, Donn Cave wrote: > At the end of April, one of our new lists was up to 6500 archived > messages for the month. It takes close to 4 minutes CPU time to > archive a message in a situation like that. The average delivery > rate to achieve 6500 messages in 30 days is 1 per 6 minutes, so > the system obviously cannot work. Why don't you just change the archiving period to "weekly"? -- Adde parvum parvo magnus acervus erit -- Ovidio _________________________________________________________________ Il servizio Postemail sottopone tutti i documenti a una scansione automatica antivirus con i programmi TREND MICRO. From donn at u.washington.edu Tue May 6 16:52:02 2003 From: donn at u.washington.edu (Donn Cave) Date: Tue May 6 18:52:15 2003 Subject: [Mailman-Developers] message data storage Message-ID: <200305062252.h46Mq2u6009914@mailhost1.u.washington.edu> Quoth Simone Piunno : | On Tuesday 06 May 2003 23:39, Donn Cave wrote: | | > At the end of April, one of our new lists was up to 6500 archived | > messages for the month. It takes close to 4 minutes CPU time to | > archive a message in a situation like that. The average delivery | > rate to achieve 6500 messages in 30 days is 1 per 6 minutes, so | > the system obviously cannot work. | | Why don't you just change the archiving period to "weekly"? Good question. Maybe because I spend to much time rewriting Mailman and not enough time using it. But I'm not sure that's really solving the problem, though it would alleviate it in this case. If I understand the archive volume thing, it's a user-visible change. We could have a talk with the list owner, and he'd probably be happy to do this - or for that matter, would probably be happy to dispense with archives altogether, which would be even better! But we have several thousand lists. 1500 already in Mailman, 3 times that many yet to be converted from listproc. The present problem is new to me partly because it's an unusually active list, but also because up to now the relatively light load on our host has allowed this kind of problem to pass unnoticed. This summer when we have twice the population, will we have only twice as many problem lists - or will we have 20 times as many, because the higher overall load has lowered the threshhold? Do we want to try to manage this problem, or solve it? I'm hoping for something more like a solution. thanks, Donn Cave, donn@u.washington.edu From tkikuchi at is.kochi-u.ac.jp Wed May 7 10:27:16 2003 From: tkikuchi at is.kochi-u.ac.jp (Tokio Kikuchi) Date: Tue May 6 20:27:39 2003 Subject: [Mailman-Developers] Re: [Mailman-Users] Problem with Date:-headers References: <5.1.1.6.0.20030506222216.00b115d0@pop3.demon.co.uk> <1052265785.3331.27.camel@anncons> Message-ID: <3EB852E4.2030602@is.kochi-u.ac.jp> Hi, Jon and Richard. I am with Richard. Following patch fix this and I really don't understand why this else close is required. Tokio --- /home/mailman/src/mailman-2.1.2/misc/email-2.5.1/email/_parseaddr.py Mon Mar 31 05:21:29 2003 +++ _parseaddr.py Fri May 2 08:45:34 2003 @@ -52,11 +52,11 @@ if data[0].endswith(',') or data[0].lower() in _daynames: # There's a dayname here. Skip it del data[0] - else: - i = data[0].rfind(',') - if i < 0: - return None - data[0] = data[0][i+1:] + #else: + # i = data[0].rfind(',') + # if i < 0: + # return None + # data[0] = data[0][i+1:] if len(data) == 3: # RFC 850 date, deprecated stuff = data[0].split('-') if len(stuff) == 3: Jon Carnes wrote: > Thanks Richard, > > I hate to say this, but I'm not seeing the same results as you. I > duplicated your test and got the same answer for both tests. > > Here is my test with the "import paths": > > [jonc@anncons /usr/local/mailman/bin]$ python > Python 2.2.2 (#2, Feb 5 2003, 10:40:08) > [GCC 3.2.1 (Mandrake Linux 9.1 3.2.1-5mdk)] on linux-i386 > Type "help", "copyright", "credits" or "license" for more information. > >>>>import paths >>>>from email.Utils import parsedate_tz, mktime_tz >>>>d1 = '22 Mar 2002 13:26:16 +0100' >>>>p1 = parsedate_tz(d1) >>>>print p1 >>> > (2002, 3, 22, 13, 26, 16, 0, 0, 0, 3600) > > > Thanks - Jon > > On Tue, 2003-05-06 at 17:26, Richard Barrett wrote: > >>Jon >> >>I sent this earlier to Stig petterso@online.no but managed to screw up >>putting you and mailman-users on the Cc >> >>Richard >> >>I said to Stig: >> >>Stig >> >>In response to your original query, I think there may be an issue with the >>version of email,Utils.parsedate_tz() function that is shipped with Mailman. >> >>Mailman ships with the email module version 2.5.1 and MM uses that in >>preference to any version of the email module that is installed with your >>Python version. >> >>The first form of date you cited is not parsed successfully and pipermail >>reverts to other alternatives, ultimately using now if all else fails. >> >>This looks to be a problem with a standard library module rather than a >>pipermail problem per se. Whether this is a bug or a feature in email-2.5.1 >>I have yet to determine. >> >>The following results are from running Python on a terminal using Python >>2.2.2 and you can see the difference in parsing the date between the >>version of email that shipped with Python 2.2.2 and the alternative version >>(which is loaded instead as a result of the import paths statement) which >>shipped with MM 2.1.2 >> >> >>mailman@mailman2:/mailman/run/bin> python >>Python 2.2.2 (#3, Feb 11 2003, 16:57:53) >>[GCC 2.95.3 20010315 (SuSE)] on linux2 >>Type "help", "copyright", "credits" or "license" for more information. >> >>> from email.Utils import parsedate_tz, mktime_tz >> >>> d1 = '22 Mar 2002 13:26:16 +0100' >> >>> p1 = parsedate_tz(d1) >> >>> print p1 >>(2002, 3, 22, 13, 26, 16, 0, 0, 0, 3600) >> >>> >>mailman@mailman2:/mailman/run/bin> python >>Python 2.2.2 (#3, Feb 11 2003, 16:57:53) >>[GCC 2.95.3 20010315 (SuSE)] on linux2 >>Type "help", "copyright", "credits" or "license" for more information. >> >>> import paths >> >>> from email.Utils import parsedate_tz, mktime_tz >> >>> d1 = '22 Mar 2002 13:26:16 +0100' >> >>> p1 = parsedate_tz(d1) >> >>> print p1 >>None >> >>> >>mailman@mailman2:/mailman/run/bin> >> >>I will take a look at the email.Utils source code and see if I can sort out >>some sort of patch for this. If I cannot see a solution, I will send Barry >>Warsaw, who I believe also 'owns' the email module, a problem report. >> >>Regards >> >>Richard >> >> >>In http://mail.python.org/pipermail/mailman-users/2003-May/028679.html >> >>Stig said; >> >>I just upgraded to Mailman 2.1.2 and regenerated my archives. >> >>After the process was finished, some messages was given todays date, and >>was therefor misplaced in the archive hierarcy. >> >>It seems to me that Mailman/Pipermail does not understand this kind of >>date-header: >> >> Date: 22 Mar 2002 13:26:16 +0100 >> >>while this one is ok: >> >> Date: Fri, 22 Mar 2002 13:08:56 +0100 >> >>The first mail is posted using GNUS/Emacs, while the second is posted using >>Outlook Express. >> >>Am I right? >> >>Is this a known bug, or is it supposed to be like this? Kind regards, >> >>Stig >> > From dag at sonsorol.org Wed May 7 16:02:41 2003 From: dag at sonsorol.org (Chris Dagdigian) Date: Wed May 7 15:02:56 2003 Subject: [Mailman-Developers] re: advice needed: shunt problems with MM2.1 and 2.1.2 only on one list out of many Message-ID: <3EB95851.1020308@sonsorol.org> Hello, I'm following up my own message because we seem to have resolved our issue with MM2.1.2 shunting messages with a "TypeError: iterable argument required" traceback. We re-created our list and got email flowing again which was our main concern. Andrew Dalke then had the time to check out the traceback errors and the messages that remaind in the shunt/ directory. He is suggesting a patch or a possible fix so I'm enclosing his entire message here: Our server is an ancient Alpha box running RedHat Linux 6.2 with a clean build of python 2.3. Mailman is 2.1.2 but since we've been using MM for years and upgrade-installing into the same directory I can't promise that our problems were not caused entirely by old cruft laying around.... -Chris Here are the notes from Andrew: > Actually, I didn't get your email about the shunt problem, I got it > about the archive problem. So I'm sending this to you to let > you forward to mailman developers in the proper context > > Here's the traceback > > Traceback (most recent call last): > File "/home/mailman/Mailman/Queue/Runner.py", line 105, in _oneloop > self._onefile(msg, msgdata) > File "/home/mailman/Mailman/Queue/Runner.py", line 155, in _onefile > keepqueued = self._dispose(mlist, msg, msgdata) > File "/home/mailman/Mailman/Queue/IncomingRunner.py", line 130, in _dispose > more = self._dopipeline(mlist, msg, msgdata, pipeline) > File "/home/mailman/Mailman/Queue/IncomingRunner.py", line 153, in _dopipeline > sys.modules[modname].process(mlist, msg, msgdata) > File "/home/mailman/Mailman/Handlers/ToDigest.py", line 89, in process > send_digests(mlist, mboxfp) > File "/home/mailman/Mailman/Handlers/ToDigest.py", line 130, in send_digests > send_i18n_digests(mlist, mboxfp) > File "/home/mailman/Mailman/Handlers/ToDigest.py", line 303, in send_i18n_digests > msg = scrubber(mlist, msg) > File "/home/mailman/Mailman/Handlers/Scrubber.py", line 257, in process > url = save_attachment(mlist, part, dir) > File "/home/mailman/Mailman/Handlers/Scrubber.py", line 349, in save_attachment > ext = guess_extension(ctype, fnext) > File "/home/mailman/Mailman/Handlers/Scrubber.py", line 80, in guess_extension > if ext in all: > TypeError: iterable argument required > > It occurs when Scrubber.guess_extension . The code does > > all = guess_all_extensions(ctype, strict=0) > if ext in all: > return ext > return all and all[0] > > The function 'guess_all_extensions' comes from the top of the > files from the section > > try: > from mimetypes import guess_all_extensions > except ImportError: > import mimetypes > def guess_all_extensions(ctype, strict=1): > # BAW: sigh, guess_all_extensions() is new in Python 2.3 > > We're running Python 2.3, which means we're using the > one from mimetypes. That function's docstring says > > guess_type(). If no extension can be guessed for `type', None > is returned. > > So if no extension can be guessed, then Scrubber.guess_extension > try to iterate over None, which fails > > Our fix to get things working again is > > all = guess_all_extensions(ctype, strict=0) > if all is None: all = [] > if ext in all: > return ext > return all and all[0] > > However, another possibility is that the guess_all_extensions > in Python 2.3's mimetypes should return [] when it cannot > guess, rather than a None. I would be happier with that > solution than this patch, but will leave it up to the Mailman > and Python people to decide on the appropriate solution. > > Andrew Dalke > dalke@dalkescientific.com From jarrell at vt.edu Wed May 7 17:40:38 2003 From: jarrell at vt.edu (Ron Jarrell) Date: Wed May 7 16:43:18 2003 Subject: [Mailman-Developers] message data storage In-Reply-To: <200305062139.h46Ld6u6025778@mailhost1.u.washington.edu> Message-ID: <5.2.1.1.2.20030507163930.04382830@lennier.cc.vt.edu> At 02:39 PM 5/6/03 -0700, Donn Cave wrote: >I'm breathing easier this week, now that a new month has started. > >At the end of April, one of our new lists was up to 6500 archived >messages for the month. It takes close to 4 minutes CPU time to Do you really need a monthly archive? For my extremely light lists I'll set archiving all the way up to quarterly. But busy lists will get weekly or even daily archiving. I know I don't want to have to look at an index page that indexes 6500 messages... From wheakory at isu.edu Wed May 7 17:33:41 2003 From: wheakory at isu.edu (Kory Wheatley) Date: Wed May 7 18:33:49 2003 Subject: [Mailman-Developers] Problem with Administrative requests functions Message-ID: <3EB989C5.9080907@isu.edu> I receive this below error when I go into the Administrative Interface and check "Preserve messsages for the site administrator" and then I check the discard option. Once I click submit this is what I receive below. BUG in Mailman version 2.1.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 "/home/mailman/scripts/driver", line 87, in run_main main() File "/home/mailman/Mailman/Cgi/admindb.py", line 163, in main process_form(mlist, doc, cgidata) File "/home/mailman/Mailman/Cgi/admindb.py", line 681, in process_form forward, forwardaddr) File "/home/mailman/Mailman/ListAdmin.py", line 184, in HandleRequest forward, addr) File "/home/mailman/Mailman/ListAdmin.py", line 262, in __handlepost msg = cPickle.load(fp) ValueError: could not convert string to float -- Kory Wheatley Academic Computing Analyst Sr. Phone 282-3874 ######################################### Everything must point to him. From barry at python.org Thu May 8 04:28:07 2003 From: barry at python.org (Barry Warsaw) Date: Wed May 7 23:28:09 2003 Subject: [Mailman-Developers] Re: [Mailman-Users] Problem with Date:-headers In-Reply-To: <3EB852E4.2030602@is.kochi-u.ac.jp> References: <5.1.1.6.0.20030506222216.00b115d0@pop3.demon.co.uk> <1052265785.3331.27.camel@anncons> <3EB852E4.2030602@is.kochi-u.ac.jp> Message-ID: <1052364453.1156.9.camel@geddy> On Tue, 2003-05-06 at 20:27, Tokio Kikuchi wrote: > I am with Richard. Following patch fix this and I really don't > understand why this else close is required. The else clause is there to handle formats like: Wed, 3 Apr 2002 14:58:26 +0800 Notice the single digit in the day field. So commenting out the else clause causes a regression in the test suite. Here's the patch I'm going to check in (along with some test cases). I'll tag email 2.5.2 and check it into Mailman's cvs. Thanks and sorry for the delay, -Barry -------------- next part -------------- A non-text attachment was scrubbed... Name: email-patch.txt Type: text/x-patch Size: 634 bytes Desc: not available Url : http://mail.python.org/pipermail/mailman-developers/attachments/20030508/7aa267e8/email-patch.bin From chuqui at plaidworks.com Wed May 7 21:46:24 2003 From: chuqui at plaidworks.com (Chuq Von Rospach) Date: Wed May 7 23:47:19 2003 Subject: [Mailman-Developers] mailman 2.1.2 upgrade warning on OS X. Message-ID: barry: FYI: while trying to update from CVS tonight, I got errors during the make. "msgmerge -U" was erroring out as an unknown option. turns out (a) msgmerge (and gettext) aren't installed on OS X as part of the disto. I'd previously installed them through fink -- but fink is distributing a really old version (0.10.something instead of 0.11.5). So this change to the gettext stuff is going to break OS X installations as they try to upgrade, and they're going to have to track down and install the current gettext to make things work again (I'm in process now, it's unclear that's all I'll find....) perhaps the README should be updated for this? From barry at python.org Thu May 8 04:59:55 2003 From: barry at python.org (Barry Warsaw) Date: Wed May 7 23:59:57 2003 Subject: [Mailman-Developers] mailman 2.1.2 upgrade warning on OS X. In-Reply-To: References: Message-ID: <1052366361.1156.20.camel@geddy> On Wed, 2003-05-07 at 23:46, Chuq Von Rospach wrote: > barry: > > FYI: while trying to update from CVS tonight, I got errors during the > make. "msgmerge -U" was erroring out as an unknown option. I think this is just a buglet in the Makefile.in on the cvs trunk. I thought I checked in a fix for this but 1) maybe I didn't (will check shortly), or 2) you didn't pick it up because you need to re-run configure or config.status to regen the Makefile. You guys (end users installing from source) should never have to run msgmerge. You /will/ have to run msgfmt but that's why I include a pure-Python version in bin (which I think you have to re-run configure also to get). -Barry From chuqui at plaidworks.com Wed May 7 22:17:09 2003 From: chuqui at plaidworks.com (Chuq Von Rospach) Date: Thu May 8 00:18:18 2003 Subject: [Mailman-Developers] mailman 2.1.2 upgrade warning on OS X. In-Reply-To: <1052366361.1156.20.camel@geddy> Message-ID: On Wednesday, May 7, 2003, at 08:59 PM, Barry Warsaw wrote: > I think this is just a buglet in the Makefile.in on the cvs trunk. I > thought I checked in a fix for this but 1) maybe I didn't (will check > shortly), or 2) you didn't pick it up because you need to re-run > configure or config.status to regen the Makefile. > did that. updated from CVS and got the makefile.in update... % make clean % config.status % make /usr/bin/python ../build/bin/msgfmt.py -o nl/LC_MESSAGES/mailman.mo nl/LC_MESSAGES/mailman.po /usr/bin/python ../build/bin/msgfmt.py -o no/LC_MESSAGES/mailman.mo no/LC_MESSAGES/mailman.po Merging new template file with existing translations msgmerge -U pl/LC_MESSAGES/mailman.po mailman.pot msgmerge: invalid option -- U Try `msgmerge --help' for more information. make[1]: *** [pl/LC_MESSAGES/mailman.po] Error 1 make[1]: Nothing to be done for `all'. still failing. From chuqui at plaidworks.com Wed May 7 22:24:09 2003 From: chuqui at plaidworks.com (Chuq Von Rospach) Date: Thu May 8 00:25:19 2003 Subject: [Mailman-Developers] mailman 2.1.2 upgrade warning on OS X. In-Reply-To: Message-ID: nope. make distclean, configure, make still fails: /usr/bin/python ../build/bin/msgfmt.py -o ko/LC_MESSAGES/mailman.mo ko/LC_MESSAGES/mailman.po /usr/bin/python ../build/bin/msgfmt.py -o lt/LC_MESSAGES/mailman.mo lt/LC_MESSAGES/mailman.po /usr/bin/python ../build/bin/msgfmt.py -o nl/LC_MESSAGES/mailman.mo nl/LC_MESSAGES/mailman.po /usr/bin/python ../build/bin/msgfmt.py -o no/LC_MESSAGES/mailman.mo no/LC_MESSAGES/mailman.po Merging new template file with existing translations msgmerge -U pl/LC_MESSAGES/mailman.po mailman.pot msgmerge: invalid option -- U Try `msgmerge --help' for more information. make[1]: *** [pl/LC_MESSAGES/mailman.po] Error 1 make[1]: Nothing to be done for `all'. 37.950u 19.490s 1:01.09 94.0% 0+0k 0+55io 0pf+0w On Wednesday, May 7, 2003, at 09:17 PM, Chuq Von Rospach wrote: > > On Wednesday, May 7, 2003, at 08:59 PM, Barry Warsaw wrote: > >> I think this is just a buglet in the Makefile.in on the cvs trunk. I >> thought I checked in a fix for this but 1) maybe I didn't (will check >> shortly), or 2) you didn't pick it up because you need to re-run >> configure or config.status to regen the Makefile. >> > > did that. updated from CVS and got the makefile.in update... > > % make clean > % config.status > % make > > /usr/bin/python ../build/bin/msgfmt.py -o nl/LC_MESSAGES/mailman.mo > nl/LC_MESSAGES/mailman.po > /usr/bin/python ../build/bin/msgfmt.py -o no/LC_MESSAGES/mailman.mo > no/LC_MESSAGES/mailman.po > Merging new template file with existing translations > msgmerge -U pl/LC_MESSAGES/mailman.po mailman.pot > msgmerge: invalid option -- U > Try `msgmerge --help' for more information. > make[1]: *** [pl/LC_MESSAGES/mailman.po] Error 1 > make[1]: Nothing to be done for `all'. > > > still failing. > > > _______________________________________________ > Mailman-Developers mailing list > Mailman-Developers@python.org > http://mail.python.org/mailman/listinfo/mailman-developers From chuqui at plaidworks.com Thu May 8 00:04:26 2003 From: chuqui at plaidworks.com (Chuq Von Rospach) Date: Thu May 8 02:05:25 2003 Subject: [Mailman-Developers] mailman 2.1.2 upgrade warning on OS X. In-Reply-To: Message-ID: On Wednesday, May 7, 2003, at 09:24 PM, Chuq Von Rospach wrote: > nope. make distclean, configure, make still fails: > yippee! that last set of changes seems to have fixed it. From chuqui at plaidworks.com Thu May 8 00:23:42 2003 From: chuqui at plaidworks.com (Chuq Von Rospach) Date: Thu May 8 02:24:25 2003 Subject: [Mailman-Developers] mailman 2.1.2 upgrade warning on OS X. In-Reply-To: Message-ID: <9D75FD84-811D-11D7-BD0D-0003934516A8@plaidworks.com> On Wednesday, May 7, 2003, at 11:04 PM, Chuq Von Rospach wrote: > yippee! > > that last set of changes seems to have fixed it. > new problem. started up 2.1.2+, and... File "/usr/local/mailman/bin/qrunner", line 270, in ? main() File "/usr/local/mailman/bin/qrunner", line 230, in main qrunner.run() File "/usr/local/mailman/Mailman/Queue/Runner.py", line 76, in run self._snooze(filecnt) File "/usr/local/mailman/Mailman/Queue/RetryRunner.py", line 44, in _snooze time.sleep(self.SLEEPTIME) NameError: global name 'time' is not defined it actually seems to be delivering, though.. *** /Users/mailman/logs/smtp *** May 07 23:21:45 2003 (6938) <000f01c3151e$57b381d0$0a02a8c0@budjens.org> smtp for 211 recips, completed in 38.212 seconds *** /Users/mailman/logs/post *** May 07 23:21:45 2003 (6938) post to sharks from jimbudler@earthlink.net, size=2029, message-id=<000f01c3151e$57b381d0$0a02a8c0@budjens.org>, success From chuqui at plaidworks.com Thu May 8 00:29:12 2003 From: chuqui at plaidworks.com (Chuq Von Rospach) Date: Thu May 8 02:30:25 2003 Subject: [Mailman-Developers] mailman 2.1.2 upgrade warning on OS X. In-Reply-To: <9D75FD84-811D-11D7-BD0D-0003934516A8@plaidworks.com> Message-ID: <622C3F3A-811E-11D7-BD0D-0003934516A8@plaidworks.com> adding import time to the RetryRunner.py file fixes this. I seem to be up on 2.1.2+ On Wednesday, May 7, 2003, at 11:23 PM, Chuq Von Rospach wrote: > File "/usr/local/mailman/Mailman/Queue/RetryRunner.py", line 44, in > _snooze > time.sleep(self.SLEEPTIME) > NameError: global name 'time' is not defined From charlie at begeistert.org Thu May 8 14:46:28 2003 From: charlie at begeistert.org (Charlie Clark) Date: Thu May 8 07:45:53 2003 Subject: [Mailman-Developers] message data storage In-Reply-To: References: Message-ID: <20030508134628.883.6@wonderland.1052391746.fake> Hi Donn, nice to see you on this list! > At the end of April, one of our new lists was up to 6500 archived > messages for the month. It takes close to 4 minutes CPU time to archive > a message in a situation like that. The average delivery rate to achieve > 6500 messages in 30 days is 1 per 6 minutes, so the system obviously > cannot work. wow, that is a lot of traffic and a sluggish system. But I don't see how 6500 mails can generate a 68 MB unless there are a lot of attachments. > Working with the current system (as opposed to the Next Generation > archiver), I'm tempted to think about a semi-permanent per-archive > archiver and queue. The archiver would exit when its queue has been > empty for some short interval, but any extra messages that arrive during > that time get the database for free. I'd be interested in any other > ideas. As someone else has noted apart from the performance issue there is also one of usability: searching 6500 messages is a proverbial needle in a haystack. I don't know what the Next Generation archiver is but I guess it's a move towards a more sophisticated persistance system which might allow things like full-text searches. If I understand you correctly you want to archive mails directly as they come in and keep the archiver / db-connection open pretty much all the time. This would seem about the best solution in the short term. Anything else sounds like: database to pass the memory issue to something which is designed to handle it. Our own experience with lists with a large member base is that Mailman isn't that efficient at dealing with them which is why we're using an RDBMS adapter and letting the RDBMS be the muscle while Mailman remains the brains. Novice question? How easy would it be just to dump to a database rather than using Python storage? Charlie From barry at python.org Thu May 8 09:21:18 2003 From: barry at python.org (Barry Warsaw) Date: Thu May 8 08:21:52 2003 Subject: [Mailman-Developers] mailman 2.1.2 upgrade warning on OS X. In-Reply-To: Message-ID: <9221695E-814F-11D7-ABFF-003065EEFAC8@python.org> On Thursday, May 8, 2003, at 02:04 AM, Chuq Von Rospach wrote: > > On Wednesday, May 7, 2003, at 09:24 PM, Chuq Von Rospach wrote: > >> nope. make distclean, configure, make still fails: >> > yippee! > > that last set of changes seems to have fixed it. Yay! -Barry From barry at python.org Thu May 8 09:54:33 2003 From: barry at python.org (Barry Warsaw) Date: Thu May 8 08:58:45 2003 Subject: [Mailman-Developers] mailman 2.1.2 upgrade warning on OS X. In-Reply-To: <622C3F3A-811E-11D7-BD0D-0003934516A8@plaidworks.com> Message-ID: <372B10BE-8154-11D7-ABFF-003065EEFAC8@python.org> On Thursday, May 8, 2003, at 02:29 AM, Chuq Von Rospach wrote: > adding > > import time > > to the RetryRunner.py file fixes this. I seem to be up on 2.1.2+ Fixed in cvs (on the trunk). Thanks. BTW, RetryRunner will be (mostly) no-op if you never get temporary failures from your MTA. If you know it can never happen, you can disable the RetryRunner in your mm_cfg.py file. -Barry From tkikuchi at is.kochi-u.ac.jp Fri May 9 10:49:59 2003 From: tkikuchi at is.kochi-u.ac.jp (Tokio Kikuchi) Date: Thu May 8 20:52:14 2003 Subject: [Mailman-Developers] Re: [Mailman-Users] Problem with Date:-headers References: <5.1.1.6.0.20030506222216.00b115d0@pop3.demon.co.uk> <1052265785.3331.27.camel@anncons> <3EB852E4.2030602@is.kochi-u.ac.jp> <1052364453.1156.9.camel@geddy> Message-ID: <3EBAFB37.6020900@is.kochi-u.ac.jp> Barry, Sorry for my slow response. Barry Warsaw wrote: > On Tue, 2003-05-06 at 20:27, Tokio Kikuchi wrote: > >>I am with Richard. Following patch fix this and I really don't >>understand why this else close is required. > > > The else clause is there to handle formats like: > > Wed, 3 Apr 2002 14:58:26 +0800 This passed my test without else close. May be this pattern ? > Wed,3 Apr 2002 14:58:26 +0800 If you stick to the BNF, you should not insert space between the comma and date. :-< In RFC2822, date-time = [ day-of-week "," ] date FWS time [CFWS] Anyway, thank you for the fix. Cheers, -- Tokio From barry at python.org Fri May 9 01:43:02 2003 From: barry at python.org (Barry Warsaw) Date: Fri May 9 00:43:38 2003 Subject: [Mailman-Developers] Re: [Mailman-Users] Problem with Date:-headers In-Reply-To: <3EBAFB37.6020900@is.kochi-u.ac.jp> Message-ID: On Thursday, May 8, 2003, at 08:49 PM, Tokio Kikuchi wrote: >> The else clause is there to handle formats like: >> >> Wed, 3 Apr 2002 14:58:26 +0800 > > This passed my test without else close. > > May be this pattern ? > >> Wed,3 Apr 2002 14:58:26 +0800 You're right. The regression was in test_parsedate_compact() which indeed tests the string you mention. > If you stick to the BNF, you should not insert space between > the comma and date. :-< Liberal in what you accept, strict in what you produce. :) In any event, I think we're good on this one. Thanks, -Barry From Mark.Martinec at ijs.si Fri May 9 13:15:26 2003 From: Mark.Martinec at ijs.si (Mark Martinec) Date: Fri May 9 06:15:36 2003 Subject: [Mailman-Developers] Re: [Mailman-Users] Problem with Date:-headers Message-ID: <01KVOR4CYLPI0012TH@CATHY.IJS.SI> >> Wed,3 Apr 2002 14:58:26 +0800 > If you stick to the BNF, you should not insert space between > the comma and date. :-< This is not true. rfc2822: date-time = [ day-of-week "," ] date FWS time [CFWS] date = day month year day = ([FWS] 1*2DIGIT) / obs-day ^^^^ ^^^^ it is allowed Mark From tkikuchi at is.kochi-u.ac.jp Fri May 9 21:13:16 2003 From: tkikuchi at is.kochi-u.ac.jp (Tokio Kikuchi) Date: Fri May 9 07:13:28 2003 Subject: [Mailman-Developers] Re: [Mailman-Users] Problem with Date:-headers References: <01KVOR4CYLPI0012TH@CATHY.IJS.SI> Message-ID: <3EBB8D4C.7020407@is.kochi-u.ac.jp> Oops! Sorry for the confusing remark. -- Tokio Mark Martinec wrote: >>>Wed,3 Apr 2002 14:58:26 +0800 >> >>If you stick to the BNF, you should not insert space between >>the comma and date. :-< > > > This is not true. > > rfc2822: > > date-time = [ day-of-week "," ] date FWS time [CFWS] > date = day month year > day = ([FWS] 1*2DIGIT) / obs-day > ^^^^ > ^^^^ it is allowed > > Mark From Bryan.Bradsby at capnet.state.tx.us Fri May 2 17:15:53 2003 From: Bryan.Bradsby at capnet.state.tx.us (Bryan Bradsby) Date: Mon May 12 08:46:37 2003 Subject: [Mailman-Developers] Moderated-edit In-Reply-To: References: Message-ID: <20030502160857.N83953@lark.capnet.state.tx.us> > > > 2) Moderated-edit. I'm running Mailman on a couple of boxes but I > > > > There is kludgey support for this now, that most people are probably not > > aware of: in the admindb interface, you forward the message to yourself. How do I forward a message to myself in the admindb "Moderater menu" ? > > Then you use whatever tools you want to edit the message and resend it > > back to the list with the Approved header. Then you delete the message > > from the admindb. Not exactly the most efficient workflow. ;) > > [...] And what is the Approved header like? Inquiring minds... (ditto) > > The thing that's always held me back here is designing a useable u/i to > > such a feature. Actually doing the editing probably isn't difficult, > > but I'm far from a web u/i expert. Doing it in a way that won't get > > clobbered by huge messages, be vulnerable to cross-site scripting or > > other security issues, and that provides a natural editing interface, is > > a big task. I would be happy if I could VIEW the body of the message from the Moderator menu. Then I would have a better idea if I wanted to delete it, or release it to the list. Thank you, -bryan bradsby Texas State Government Net NOC: 512-475-2432 877-472-4848 From edwin at qscomputers.com Wed May 7 18:11:34 2003 From: edwin at qscomputers.com (Edwin Sevrence) Date: Mon May 12 08:46:56 2003 Subject: [Mailman-Developers] Questions Quesions In-Reply-To: <3EB989C5.9080907@isu.edu> Message-ID: 1. Where can I find the latest version of mailman to Download? 2. Can I install mailman if I am not SU? And what DIR does it go into if I can? I am hosted on a computer out of state by a hosting service, the hosting service owner is a friend of mine and might be able to help if I cannot but I need all the feedback I can get on this issue. I am not the only person with a list server being hosted on this server so I don't know if anything I do will effect the whole system or not. From gbb at dcs.st-and.ac.uk Thu May 1 15:20:18 2003 From: gbb at dcs.st-and.ac.uk (Graeme Bell) Date: Mon May 12 08:47:25 2003 Subject: [Mailman-Developers] virus infection? Message-ID: Hi, a file in the mailman-2.1.1.tgz archive from http://ftp.gnu.org/gnu/mailman/ is infected with the Nimda virus according to antivir (www.free-av.com) Can I suggest removing this archive and checking other archives available on ftp.gnu.org/gnu/mailman and it's mirrors. Can someone mail me back to acknowledge this problem has been recognised. Cheers Graeme. From grant at libertyrms.info Mon May 5 17:10:42 2003 From: grant at libertyrms.info (Grant Cullen) Date: Mon May 12 08:47:35 2003 Subject: [Mailman-Developers] Converting from MM1.1 to MM2.1.1 Message-ID: <1052151055.23405.12.camel@sysadmin.int.libertyrms.com> Yes I am making that big a jump. MM1.1 is running currently, we are replacing the server and in the process upgrading all of our software. The problem is: New lists created on the new system show up when the listinfo page is displayed. Lists which are copied over from the old system do no appear on the listinfo page, but are accessible. Obviously the configuration files are different, but mailman seems to be able to handle that. Running the config_list command on new list and a copied over list produce similar output. Suggestions would be appreciated. -- Grant Cullen Liberty RMS From grant at libertyrms.info Tue May 6 16:57:19 2003 From: grant at libertyrms.info (Grant Cullen) Date: Mon May 12 08:47:38 2003 Subject: [Mailman-Developers] Converting from MM1.1 to MM2.1.1 Message-ID: <1052236651.24759.1.camel@sysadmin.int.libertyrms.com> Yes I am making that big a jump. MM1.1 is running currently, we are replacing the server and in the process upgrading all of our software. The problem is: New lists created on the new system show up when the listinfo page is displayed. Lists which are copied over from the old system do no appear on the listinfo page, but are accessible. Obviously the configuration files are different, but mailman seems to be able to handle that. Running the config_list command on new list and a copied over list produce similar output. Suggestions would be appreciated. -- Grant Cullen Liberty RMS From hfastjava at yahoo.com Thu May 8 14:17:00 2003 From: hfastjava at yahoo.com (Hunter Peress) Date: Mon May 12 08:47:54 2003 Subject: [Mailman-Developers] adding list url to sent out message Message-ID: <20030508201700.55321.qmail@web41307.mail.yahoo.com> For each email, I want to include it's web address in the archives. I've looked at the code, and im really not familiar. I went to mailman-2.1.1/Mailman/Archiver and poked around. Maybe the GetBaseArchiveURL is part of what I need. anyway, could someone assist in pointing out the places in the code i'll need to change to accomplish this. i did a: hperes@HillCountryPeress:[~/mailman-2.1.2/Mailman]%grep -r GetBase * Archiver/Archiver.py: def GetBaseArchiveURL(self): Cgi/admin.py: otherlinks.AddItem(Link(mlist.GetBaseArchiveURL(), HTMLFormatter.py: return '' % self.GetBaseArchiveURL() Handlers/CookHeaders.py: archiveurl = mlist.GetBaseArchiveURL() Handlers/Scrubber.py: baseurl = mlist.GetBaseArchiveURL() so given that its all over the place i have no idea where to start. __________________________________ Do you Yahoo!? The New Yahoo! Search - Faster. Easier. Bingo. http://search.yahoo.com From hfastjava at yahoo.com Thu May 8 14:35:17 2003 From: hfastjava at yahoo.com (Hunter Peress) Date: Mon May 12 08:47:56 2003 Subject: [Mailman-Developers] adding list url to sent out message Message-ID: <20030508203517.38479.qmail@web41315.mail.yahoo.com> For each email, I want to include it's web address in the archives. I've looked at the code, and im really not familiar. I went to mailman-2.1.1/Mailman/Archiver and poked around. Maybe the GetBaseArchiveURL is part of what I need. anyway, could someone assist in pointing out the places in the code i'll need to change to accomplish this. i did a: hperes@HillCountryPeress:[~/mailman-2.1.2/Mailman]%grep -r GetBase * Archiver/Archiver.py: def GetBaseArchiveURL(self): Cgi/admin.py: otherlinks.AddItem(Link(mlist.GetBaseArchiveURL(), HTMLFormatter.py: return '' % self.GetBaseArchiveURL() Handlers/CookHeaders.py: archiveurl = mlist.GetBaseArchiveURL() Handlers/Scrubber.py: baseurl = mlist.GetBaseArchiveURL() so given that its all over the place i have no idea where to star __________________________________ Do you Yahoo!? The New Yahoo! Search - Faster. Easier. Bingo. http://search.yahoo.com From larva at linux.ucla.edu Thu May 1 18:33:31 2003 From: larva at linux.ucla.edu (Matt Helsley) Date: Mon May 12 08:48:11 2003 Subject: [Mailman-Developers] A Helper Script In-Reply-To: <20030425160124.GN24554@merlins.org> Message-ID: Just thought I'd let folks know I wrote a small helper script for list administrators. I've tested it on my own lists and it seems to work. I'd appreciate any bug reports and other feedback. Send them to mhelsley _at_ linux _dot_ you see L A _dot_ eee dee you. Description: This is a command line helper script which allows a list administrator to quickly handle a large queue of messages pending approval on a given list. Messages are matched using a regular expression applied to either the subject field, from field, or both. Subject and From fields must match in the case of both regular expressions being provided. To do an 'or' operation execute the script twice -- once with each regular expression applied appropriately. When a message is found that matches the description provided, it can either be approved, rejected, or discarded. Usage: list_handle_pending [-s |-f |--subject=| --from=] (-a|-r|-d|--approve|--reject|--discard) Here's a link to the script: http://linux.ucla.edu/~larva/projects/list_handle_pending I found it necessary to write this script when a list I managed received 300 copies of nearly identical messages in the pending queue. The list in question was the destination of some cron-triggered script-generated error reports intended for a group of system administrators. Manually scrolling through the pending queue page and discarding the messages would have been much too tedious. Hopefully this might be of use to other mailman (list) administrators. Regards, -Matt Helsley From marisa at stat.umn.edu Tue May 6 17:36:07 2003 From: marisa at stat.umn.edu (Marisa Riviere) Date: Mon May 12 08:49:04 2003 Subject: [Mailman-Developers] domain definition syntax Message-ID: <20030506213607.F15E92286@muskrat.stat.umn.edu> I would like to permit everyone from my site (stat.umn.edu) to write to some mailing lists wihout moderator's approval. I tested several expressions on the "Addresses of members accepted for posting to this list without implicit approval requirement" but so far I only got individual addresses such as "marisa@stat.umn.edu" working. I may be using the wrong syntax. I did several tests using "*@stat\.umn\.edu" or "^.*@stat.umn.edu" and other combinations in that field but no one worked. Can you please help me with the syntax or tell me what else I may be doing wrong? Or how to get around with this, like, for example, if it makes sense to place everyone on my site in the "Addresses of members accepted for posting to this list without implicit approval requirement"? -- Seems drastic but it may work! We are running Mailman version 2.0.8. Thank you. -- Marisa Riviere U of M - Statistics marisa@stat.umn.edu 612-624-5859 From marty at heavyreckoning.com Thu May 1 02:51:41 2003 From: marty at heavyreckoning.com (Marty Galyean) Date: Mon May 12 08:49:22 2003 Subject: [Mailman-Developers] Request update of list information page In-Reply-To: <3EAD14D6.1020807@pobox.com> References: <3EAD14D6.1020807@pobox.com> Message-ID: <1051753653.1730.79.camel@localhost.localdomain> Tony, This is easy to handle! Just create a directory in ../lists/// if it doesn't exist. In my case this was ../lists/glocklist/en Copy ../templates/en/listinfo.html into the directory above and modify to your heart's content! Be aware the listinfo.html interacts with the list information you enter in through the admin interface so you will likely have to edit both. Marty On Mon, 2003-04-28 at 05:47, Anthony E. Greene wrote: > I've been a list owner for several years, using several different list mgt > packages. I've also managed web sites and done some help desk work. I'm > not a Mailman developer, but the Sourceforge page for bug submission > suggested that the developers be notified directly of bug submissions, so > here goes. > > ******************************************************************** > Bug# 728122: Unsub instructions difficult to find > > The default Mailman info page for the list could stand some improvements. > I've noticed it over and over and finally decided to contribute to a > solution instead of griping about the problem. ;-) > > I recommend these two changes: > > 1. Move the administrative "$listname Subscribers" section to the bottom > of the page. Admins will know where to look and subscribers should not > have to read through admin info to get to the section that concerns > them (changing subscription options). > > 2. Add a standard colored section header titled "Change Options or > Unsubscribe". The original format for this section did not clearly > indicate that this is the section for unsubscribing. Users have to > read the fine print. Reading the fine print is fine for detailed > instructions, but the users should have some idea that the unsub > instructions are there just by looking at the section header. > ********************************************************************* > > A sample HTML page is attached to the Bug record. > > Tony > -- > Anthony E. Greene > OpenPGP Key: 0x6C94239D/7B3D BD7D 7D91 1B44 BA26 C484 A42A 60DD 6C94 239D > AOL/Yahoo Chat: TonyG05 HomePage: > Linux. The choice of a GNU generation. > > > _______________________________________________ > Mailman-Developers mailing list > Mailman-Developers@python.org > http://mail.python.org/mailman/listinfo/mailman-developers From pst at pst.org Tue May 6 02:07:28 2003 From: pst at pst.org (Paul Traina) Date: Mon May 12 08:50:32 2003 Subject: [Mailman-Developers] English (USA) Message-ID: <3EB76D40.7060208@pst.org> Not to beat a dead horse, but ... > So far, I've only noticed one, the spelling of "internationalisation", and that only appears on an admin page. Look at a British English dictionary and you'll note that the 'ize' form is actually primary, although not common usage. Can't we just all get along? It seems ridiculous to have an en_US and en_GB for such triviality. Anything that differs can probably be rewritten to be proper in both dialects. Yours for "English" as opposed to "English (...)" From sgsax at ksu.edu Thu May 1 21:08:01 2003 From: sgsax at ksu.edu (Seth Galitzer) Date: Mon May 12 08:50:47 2003 Subject: [Mailman-Developers] where is this bounce message coming from Message-ID: <1051819833.11821.68.camel@sgsax-th4022c> Greetings, A member of one of many lists I help manage recently got this rejection message: The message's content type was not explicitly allowed I do have content-filtering enabled on this list and have the following items in the pass_mime_types list: multipart/mixed multipart/alternative text/plain I do not have any items in the filter_mime_types list, convert_to_plaintext is set to Yes, and the filter_action is set to Reject. I had the user send me a copy of the message he tried to send. Reading the source of the message, it contained the following in the Content-Type header: multipart/related; type="multipart/alternative"; And then in subsequent mime sections it had parts with the following Content-Types: multipart/alternative text/plain text/html image/gif Now, it is my understanding, that with my current configuration, if any part has a mime-type that is not listed in the whitelist, that part is just dropped. Is that correct? Since the whole message was typed as multipart/related, did that cause the filters to behave differently? >From the docs: "Note this action is not taken if after filtering the message still contains content. In that case the message is always forwarded on to the list membership." Since there was at least one text/plain part and since I have also enabled plaintext conversion, shouldn't the message have gone on to the list anyway? I guess I'm just confused as to why this one got bounced. This is the first time a message has been bounced due to content filtering since we enabled the feature a month or so ago. On a related note, if I set the filter_action to Preserver instead of Reject, will the message go into the pending moderator request queue, or into a different queue? Just trying to sort things out. Seth -- Seth Galitzer sgsax@ksu.edu Computing Specialist http://puma.agron.ksu.edu/~sgsax Dept. of Plant Pathology Kansas State University From pioppo at ferrara.linux.it Mon May 12 16:02:11 2003 From: pioppo at ferrara.linux.it (Simone Piunno) Date: Mon May 12 08:53:57 2003 Subject: [Mailman-Developers] virus infection? In-Reply-To: References: Message-ID: <20030512130211.GB4457@pioppo.wired> gioved?, 01 maggio 2003 alle 14:20:18, Graeme Bell ha scritto: > a file in the mailman-2.1.1.tgz archive from > > http://ftp.gnu.org/gnu/mailman/ > > is infected with the Nimda virus according to antivir (www.free-av.com) Which file exactly? -- This signature intentionally left blank From barry at python.org Mon May 12 10:00:30 2003 From: barry at python.org (Barry Warsaw) Date: Mon May 12 09:01:05 2003 Subject: [Mailman-Developers] virus infection? In-Reply-To: Message-ID: On Thursday, May 1, 2003, at 09:20 AM, Graeme Bell wrote: > a file in the mailman-2.1.1.tgz archive from > > http://ftp.gnu.org/gnu/mailman/ > > is infected with the Nimda virus according to antivir (www.free-av.com) > > Can I suggest removing this archive and checking other archives > available > on ftp.gnu.org/gnu/mailman and it's mirrors. > > Can someone mail me back to acknowledge this problem has been > recognised. No, there is no virus in the tarfile. One of the test case data files has a neutered email message where the virus has been removed but the telltale headers are still there. That's what's tripping up your antivir. There is absolutely nothing to worry about. -Barry From donn at u.washington.edu Mon May 12 11:20:41 2003 From: donn at u.washington.edu (Donn Cave) Date: Mon May 12 13:20:58 2003 Subject: [Mailman-Developers] message data storage Message-ID: <200305121720.h4CHKfu6001875@mailhost1.u.washington.edu> Quoth Charlie Clark : ... | wow, that is a lot of traffic and a sluggish system. But I don't see how | 6500 mails can generate a 68 MB unless there are a lot of attachments. Even with attachments it takes some doing. The articles database actually tends to be double the size of the .txt archive for the same month. Not only this particular list. | As someone else has noted apart from the performance issue there is also | one of usability: searching 6500 messages is a proverbial needle in a | haystack. I don't know what the Next Generation archiver is but I guess | it's a move towards a more sophisticated persistance system which might | allow things like full-text searches. If I understand you correctly you | want to archive mails directly as they come in and keep the archiver / | db-connection open pretty much all the time. This would seem about the best | solution in the short term. Anything else sounds like: database to pass the | memory issue to something which is designed to handle it. Our own | experience with lists with a large member base is that Mailman isn't that | efficient at dealing with them which is why we're using an RDBMS adapter | and letting the RDBMS be the muscle while Mailman remains the brains. | | Novice question? How easy would it be just to dump to a database rather | than using Python storage? I don't know if anyone has a clear picture of this next generation system, it's just the subject of a dormant mailing list http://rogue.amk.ca/mailman/listinfo/ng-arch An external database might be a part of that picture, for all I know. I would expect that if a database really would pay off, it would take some rewriting anyway. It would be trivial to use a database for storage, but that would only slow things down. Really need to find a way to use the database more inside the threading algorithm. Donn Cave, donn@u.washington.edu From terri at zone12.com Mon May 12 14:36:26 2003 From: terri at zone12.com (Terri Oda) Date: Mon May 12 13:33:17 2003 Subject: [Mailman-Developers] Converting from MM1.1 to MM2.1.1 In-Reply-To: <1052236651.24759.1.camel@sysadmin.int.libertyrms.com> References: <1052236651.24759.1.camel@sysadmin.int.libertyrms.com> Message-ID: <20030512173626.GC495@ostraya.zone12.com> On Tue, May 06, 2003 at 11:57:31AM -0400, Grant Cullen wrote: > New lists created on the new system show up when the listinfo page is > displayed. Lists which are copied over from the old system do no appear > on the listinfo page, but are accessible. You've tried setting the "Advertise this list" bit for all those lists? It's under "privacy" in the admin interface, and the option is DEFAULT_LIST_ADVERTISED if you're editing config files. Terri From wheakory at isu.edu Mon May 12 13:13:38 2003 From: wheakory at isu.edu (Kory Wheatley) Date: Mon May 12 14:13:45 2003 Subject: [Mailman-Developers] Problem with Administrative Requests functions Message-ID: <3EBFE452.8080609@isu.edu> I receive this below error when I go into the Administrative Interface and check "Preserve messsages for the site administrator" and then I check the discard option. Once I click submit this is what I receive below. BUG in Mailman version 2.1.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 "/home/mailman/scripts/driver", line 87, in run_main main() File "/home/mailman/Mailman/Cgi/admindb.py", line 163, in main process_form(mlist, doc, cgidata) File "/home/mailman/Mailman/Cgi/admindb.py", line 681, in process_form forward, forwardaddr) File "/home/mailman/Mailman/ListAdmin.py", line 184, in HandleRequest forward, addr) File "/home/mailman/Mailman/ListAdmin.py", line 262, in __handlepost msg = cPickle.load(fp) ValueError: could not convert string to float -- Kory Wheatley Academic Computing Analyst Sr. Phone 282-3874 ######################################### Everything must point to him. From mburton at jo.birdsense.com Mon May 12 13:50:49 2003 From: mburton at jo.birdsense.com (Mike Burton) Date: Mon May 12 17:26:25 2003 Subject: [Mailman-Developers] mailmanctl Message-ID: <2003512125049.334679@alfa> When I try to upgrade from 2.1.1 to 2.1.2, I get the following error when trying to start mailmanctl... Traceback (most recent call last) File "/usr/local/mailman/bin/qrunner", line 77, in ? from Mailman.i18n import _ File "/usr/local/mailman/Mailman/i18n.py", line 19, in ? import gettext File "/usr/local/lib/python2.2/gettext.py", line 49, in ? from errno import ENOENT Import Error: No module named errno I get several of these on startup. Python was installed from source code. Any ideas? Thanks, Mike From dan.mick at sun.com Mon May 12 15:32:12 2003 From: dan.mick at sun.com (Dan Mick) Date: Mon May 12 17:33:16 2003 Subject: [Mailman-Developers] mailmanctl In-Reply-To: <2003512125049.334679@alfa> References: <2003512125049.334679@alfa> Message-ID: <3EC012DC.8050600@sun.com> Mike Burton wrote: > When I try to upgrade from 2.1.1 to 2.1.2, I get the following error when > trying to start mailmanctl... > > Traceback (most recent call last) > File "/usr/local/mailman/bin/qrunner", line 77, in ? > from Mailman.i18n import _ > File "/usr/local/mailman/Mailman/i18n.py", line 19, in ? > import gettext > File "/usr/local/lib/python2.2/gettext.py", line 49, in ? > from errno import ENOENT > Import Error: No module named errno > > I get several of these on startup. > > Python was installed from source code. > > Any ideas? So, this may sound like the world's stupidest question, but: do you have a module named errno, and can you import it outside Mailman? From barry at python.org Mon May 12 22:55:27 2003 From: barry at python.org (Barry Warsaw) Date: Mon May 12 17:55:28 2003 Subject: [Mailman-Developers] mailmanctl In-Reply-To: <2003512125049.334679@alfa> References: <2003512125049.334679@alfa> Message-ID: <1052776487.27220.5.camel@barry> On Mon, 2003-05-12 at 15:50, Mike Burton wrote: > When I try to upgrade from 2.1.1 to 2.1.2, I get the following error when > trying to start mailmanctl... > > Traceback (most recent call last) > File "/usr/local/mailman/bin/qrunner", line 77, in ? > from Mailman.i18n import _ > File "/usr/local/mailman/Mailman/i18n.py", line 19, in ? > import gettext > File "/usr/local/lib/python2.2/gettext.py", line 49, in ? > from errno import ENOENT > Import Error: No module named errno > > I get several of these on startup. > > Python was installed from source code. > > Any ideas? Try % cd /usr/local/mailman % bin/withlist mylist [stuff] >>> import errno >>> errno what happens? then try: % python [stuff] >>> import errno >>> errno what happens then? -Barry From Daniel.Buchmann at bibsys.no Mon May 12 23:32:25 2003 From: Daniel.Buchmann at bibsys.no (Daniel Buchmann) Date: Mon May 12 18:32:26 2003 Subject: [Mailman-Developers] domain definition syntax In-Reply-To: <20030506213607.F15E92286@muskrat.stat.umn.edu> References: <20030506213607.F15E92286@muskrat.stat.umn.edu> Message-ID: <1052778706.2129.6.camel@FORNAX.bibsys.no> Hi Marisa, I think you need to upgrade to Mailman 2.1.2 to be able to use regexps in the accept-these-nonmembers filter... :) On Tue, 2003-05-06 at 23:36, Marisa Riviere wrote: > I would like to permit everyone from my site > (stat.umn.edu) to write to some mailing lists > wihout moderator's approval. > > I tested several expressions on the "Addresses of > members accepted for posting to this list without > implicit approval requirement" but so far I only got > individual addresses such as "marisa@stat.umn.edu" > working. > > I may be using the wrong syntax. I did several tests > using "*@stat\.umn\.edu" or "^.*@stat.umn.edu" > and other combinations in that field but no one worked. > > Can you please help me with the syntax or tell me > what else I may be doing wrong? Or how to get around > with this, like, for example, if it makes sense to > place everyone on my site in the "Addresses of > members accepted for posting to this list without > implicit approval requirement"? -- Seems drastic > but it may work! > > We are running Mailman version 2.0.8. > > Thank you. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 232 bytes Desc: This is a digitally signed message part Url : http://mail.python.org/pipermail/mailman-developers/attachments/20030512/4c44a701/attachment.bin From charlie at begeistert.org Tue May 13 14:12:37 2003 From: charlie at begeistert.org (Charlie Clark) Date: Tue May 13 07:11:40 2003 Subject: [Mailman-Developers] message data storage In-Reply-To: <200305121720.h4CHKfu6001875@mailhost1.u.washington.edu> References: <200305121720.h4CHKfu6001875@mailhost1.u.washington.edu> Message-ID: <20030513131237.1973.16@wonderland.1052807987.fake> On 2003-05-12 at 19:20:41 [+0200], you wrote: > Even with attachments it takes some doing. The articles database > actually tends to be double the size of the .txt archive for the same > month. Not only this particular list. > | Novice question? How easy would it be just to dump to a database rather > | than using Python storage? > > I don't know if anyone has a clear picture of this next generation > system, it's just the subject of a dormant mailing list > http://rogue.amk.ca/mailman/listinfo/ng-arch mm, I've just read this and there is some interesting stuff. I'm not much of a programmer but I always miss references to "use" in requirements descriptions. In an internet world we can do away with zipped versions of the archive at least in "monthly" or similar time-based versions. It makes much more sense to be able to download a whole thread or topic independent of which time barriers it crosses. The comparison with NNTP is good as it would be good to learn from the way Newsnet does it: e-mail and news aren't really that different as a friend of mine insists on reminding me. On his Amiga they've always been same... > An external database might be a part of that picture, for all I know. I > would expect that if a database really would pay off, it would take some > rewriting anyway. It would be trivial to use a database for storage, but > that would only slow things down. Really need to find a way to use the > database more inside the threading algorithm. mm, I don't like the file system storage suggestions. It would be alright if more people used BFS so we could use fsquery: no problems with lots of files and ATTRIBUTES :-)! but we're in a minority. The Bethon list is up by the way: bethon-request@mail.nexon.de But the main reason for a database would be scalability and resilience which seem absolutely essential for your current situation. Performance bottle necks can be alleviated through continuous archiving as opposed to cron-based CPU-killers. Put some kind of search system on top of it for full-text searching. I think it is very important to define the APIs so that storage type independance is in from the beginning. When I think of things, I think XML should be the way of structuring the mails but then I think "performance" so maybe not XML. But maybe it could help with modelling things and defining the interface? Charlie From Oliver.Egginger at dvz.fh-giessen.de Wed May 14 13:15:07 2003 From: Oliver.Egginger at dvz.fh-giessen.de (Oliver Egginger) Date: Wed May 14 08:15:09 2003 Subject: [Mailman-Developers] semantic error in mailmanctl line 255 (Mailman 2.1.2) Message-ID: <1052914469.8648.55.camel@chaos.dvz.fh-giessen.de> Hello, this was originally: Mandrake 9.1 / ImportError As a result of a suggestion from Luca Olivetti (Mandrake list member) I think now that you are maybe wrong with that line 255 in maimanctl. The original line is > os.execl(mm_cfg.PYTHON, 'qrunner', exe, rswitch, '-s') But this is a semantic error we think. The first parameter is arg0 no arg1, so you should be using something like os.execl(mm_cfg.PYTHON, '' , exe, rswitch, '-s') Here is the diff for a patch: 255c255 < os.execl(mm_cfg.PYTHON, '' , exe, rswitch, '-s') --- > os.execl(mm_cfg.PYTHON, 'qrunner', exe, rswitch, '-s') This bug breaks several python installations. It don't work for my Mandrake system for example. It is possible to correct this in future releases? What do you think? - oliver -- Oliver Egginger Fachochschule Giessen-Friedberg From fil at rezo.net Wed May 14 16:45:02 2003 From: fil at rezo.net (Fil) Date: Wed May 14 09:45:09 2003 Subject: [Mailman-Developers] a traceback Message-ID: <20030514134501.GD19836@rezo.net> When I "confirm" by email a spam received on a list (I want to discard it, of course, but Mailman writes "confirm", which is a biut weird, but thats' not my point today), I get this error in the log. And in fact the mail is not discarded. ==> /var/local/mailman/logs/error <== May 14 15:42:42 2003 (767) Uncaught runner exception: ASCII decoding error: ordinal not in range(128) May 14 15:42:42 2003 (767) Traceback (most recent call last): File "/usr/local/mailman/Mailman/Queue/Runner.py", line 105, in _oneloop self._onefile(msg, msgdata) File "/usr/local/mailman/Mailman/Queue/Runner.py", line 155, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/local/mailman/Mailman/Queue/CommandRunner.py", line 232, in _dispose res.process() File "/usr/local/mailman/Mailman/Queue/CommandRunner.py", line 105, in process stop = self.do_command(cmd, args) File "/usr/local/mailman/Mailman/Queue/CommandRunner.py", line 130, in do_command return self.do_command(cmd, args) File "/usr/local/mailman/Mailman/Queue/CommandRunner.py", line 132, in do_command return handler.process(self, args) File "/usr/local/mailman/Mailman/Commands/cmd_confirm.py", line 83, in process if line.lstrip() == match: UnicodeError: ASCII decoding error: ordinal not in range(128) May 14 15:42:42 2003 (767) SHUNTING: 1052919760.819023+d6d1f526383cb09df38958ab27e1c2cf00ef988b ==> /var/local/mailman/logs/vette <== May 14 15:42:42 2003 (767) spip-ann: Discarded posting: From: webdevelope1r@zipmail.com.br Subject: Faca de seu penis um P?NIS -- Fil From barry at python.org Wed May 14 17:21:08 2003 From: barry at python.org (Barry Warsaw) Date: Wed May 14 12:21:09 2003 Subject: [Mailman-Developers] Looking at performance again Message-ID: <1052929235.5006.36.camel@barry> I've been doing some (limited) performance testing lately, and I wanted to share some numbers and get some feedback. I've also been having fun re-reading some old mm-dev threads related to performance. :) I'm specifically looking for places to improve Mailman's raw throughput. I understand that MTA tuning can have a huge impact on the system, but I think that subject's been hashed out quite well in the past. On the table are anything from low-hanging fruit hacks to mm3-level redesigns. What I actually can implement all depends. :) I've been testing the following set up: - Postfix 2.0.9 configured with a special test transport such that all email @example.com gets dd'd to /dev/null - Postfix running on the same machine as Mailman 2.1.2+ and a second test with Postfix (similarly configured) on a separate, very unloaded, but less beefy machine sitting next to me on a 100Mb ethernet. - RH9 2.4.20-9 kernel, 863Mhz Dell PIII, 512MB (1723 bogomips), ext3, a WDC IDE drive of some 2 y.o. vintage. - Python 2.2.2 built from source My list consists of 8000 members like abcdefg@example.com where the localpart varies randomly. I've tried deliveries of 10KB, 50KB, 220KB, 1MB of text/plain and a 220KB multipart/related snapshot of a web page [1]. I have VERP and personalization both turned on. I started looking at memory usage, but I'm not so concerned about that now. It may be something to address later but I think it's "reasonable". First the (approximate) numbers. All deliveries are to 8000 members, each with their own personalized copy. SMTP_MAX_RCPTS is 500 unless otherwise specified (minimal impact seemingly). msgsz type time msg/hour ----- ---- ---- -------- 10k plain/text 6min 80k/hr 50k p/t 9.5min 50k/hr (SMTP_MAX_RCPTS=5) 220k p/t 24m 20k/hr 1MB p/t 105m 4500/hr 220k m/related 44m 10k/hr 220k m/related 41m 11k/hr (SMTP_MAX_RCPTS=5) 220k m/related 46m 10k/hr (remote MTA) A few high-level bits: - Disk i/o probably isn't much of an issue. Once the message hits the out qrunner, it's only two files and all the personalization weaving happens in memory just before the message goes out on the socket. Since using a remote MTA was actually slightly slower, I'm guessing that MTA overhead in the /dev/null pipe is actually minimal (the remote machine is a 500MHz, 128 KB, 999 bogomips, mostly idle). - email.Generator.Generator (and email.Parser.Parser) are good candidates for optimization. You can see that with the 220KB messages, the fact that one has structure and the other doesn't, affects performance significantly. That doesn't surprise me. ;) - Even so, a factor of 100 in message size has a 20x hit on performance. Part of that may be the way the personalization weaving gets done. Right now, we make a copy.deepcopy() of the original message object model, then poke in the personalization parts in the headers and such, then do all the complex stuff in Decorate.py (footers, headers, etc.), then generate the flat text. Maybe we can speed things up by converting the message to flat text as early as possible and just doing string substitution at the point of weaving. - What kind of a hit does the memberdb-in-a-pickle take? Would things go faster if we stored the member data in a Berkeley, MySQL, or other real database? I'd like to do some testing with my BDB member code and I'm wondering if the folks working on other member adapters have any performance feedback. - XVERP might be interesting, but it seems useless for personalization. - Do we win or lose with the process model, as compared to say, a threading model? I've been wondering if our fears of the Python GIL are unfounded. We could certainly reduce memory overhead by multi-threading, and we might be able to leverage something like Twisted, which is still in the back of my mind as a very cool way to get multi-protocol support into Mailman. - Does our "NFS-safe" locks impose too much complexity and overhead to be worth it? Does anybody actually /use/ Mailman over NFS? Don't we sorta suspect the LockFile implementation anyway? Would we be better off using kernel file locks, or thread locks if we go to a MT model? Okay, now I'm rambling. What is the lowest hanging fruit that we might be able to attack? I'm up for any other ideas people have. -Barry [1] wget -E -H -k -p -nH -nd -Pdownload followed by a little Python script to multipart/related it From mal at lemburg.com Wed May 14 19:41:09 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Wed May 14 12:41:46 2003 Subject: [Mailman-Developers] Looking at performance again In-Reply-To: <1052929235.5006.36.camel@barry> References: <1052929235.5006.36.camel@barry> Message-ID: <3EC271A5.9040808@lemburg.com> Barry Warsaw wrote: > - What kind of a hit does the memberdb-in-a-pickle take? Would things > go faster if we stored the member data in a Berkeley, MySQL, or > other real database? I'd like to do some testing with my BDB member > code and I'm wondering if the folks working on other member adapters > have any performance feedback. Apart from the fact that you'll have tough times when loading 100k members into memory, the use of a real database is a tradeoff: Mailman has lots of code which is built in a way that assumes membership data access is fast. With a few 1000 members, things can still fit nicely into memory, so that's a valid assumption. However, with a few 100k members you really want to be more careful and only load data in chunks into memory. Mailman needs to be redesigned in a couple of places for that to work. One example is the membership admin interface, another is personalization. So, no, you don't gain performance by putting small lists into a database and, yes, if your list size grows beyond certain limits, there's simply no alternative. Once your machine starts swapping, the database + chunking approach is faster. > - Do we win or lose with the process model, as compared to say, a > threading model? I've been wondering if our fears of the Python GIL > are unfounded. We could certainly reduce memory overhead by > multi-threading, and we might be able to leverage something like > Twisted, which is still in the back of my mind as a very cool way to > get multi-protocol support into Mailman. I don't think that multi-threading would gain any performance. It would make more sense to have Mailman use multiple SMTP backends for delivery (MTA clustering). BTW, is Mailman thread-safe ? > - Does our "NFS-safe" locks impose too much complexity and overhead to > be worth it? Does anybody actually /use/ Mailman over NFS? Don't > we sorta suspect the LockFile implementation anyway? Would we be > better off using kernel file locks, or thread locks if we go to a MT > model? You may want to have a look at mx.Misc.FileLock (in egenix-mx-base). That's a portable file locking mechanism which is not the fastest, but fast enough for most cases. > Okay, now I'm rambling. What is the lowest hanging fruit that we might > be able to attack? I'm up for any other ideas people have. MTA clustering support. Basically just do round-robin delivery to a list of SMTP hosts. -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, May 14 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ EuroPython 2003, Charleroi, Belgium: 41 days left From barry at python.org Wed May 14 18:09:36 2003 From: barry at python.org (Barry Warsaw) Date: Wed May 14 13:09:38 2003 Subject: [Mailman-Developers] Looking at performance again In-Reply-To: <3EC271A5.9040808@lemburg.com> References: <1052929235.5006.36.camel@barry> <3EC271A5.9040808@lemburg.com> Message-ID: <1052932143.5006.59.camel@barry> On Wed, 2003-05-14 at 12:41, M.-A. Lemburg wrote: > Apart from the fact that you'll have tough times when loading > 100k members into memory, the use of a real database is a > tradeoff: > > Mailman has lots of code which is built in a way that assumes > membership data access is fast. With a few 1000 members, things > can still fit nicely into memory, so that's a valid assumption. > However, with a few 100k members you really want to be more > careful and only load data in chunks into memory. > > Mailman needs to be redesigned in a couple of places for that > to work. One example is the membership admin interface, another > is personalization. I totally agree. I've been fleshing out some api's for mm3 that attempt to address these exact issues. I'm not ready to show them to the world yet, but I'm thinking exactly along these lines. > I don't think that multi-threading would gain any performance. > It would make more sense to have Mailman use multiple SMTP > backends for delivery (MTA clustering). Here's one place where it would help: with multiple threads, we won't need to keep multiple copies of the databases in memory. Maybe chunking and caching can help with this instead of moving to a threading model. > BTW, is Mailman thread-safe ? Depends. If we use one thread per qrunner, then I think so. > > - Does our "NFS-safe" locks impose too much complexity and overhead to > > be worth it? Does anybody actually /use/ Mailman over NFS? Don't > > we sorta suspect the LockFile implementation anyway? Would we be > > better off using kernel file locks, or thread locks if we go to a MT > > model? > > You may want to have a look at mx.Misc.FileLock (in egenix-mx-base). > That's a portable file locking mechanism which is not the > fastest, but fast enough for most cases. I'll look: in the meantime, how does it do locking? > > Okay, now I'm rambling. What is the lowest hanging fruit that we might > > be able to attack? I'm up for any other ideas people have. > > MTA clustering support. Basically just do round-robin > delivery to a list of SMTP hosts. I'm pretty sure there are folks on this list that are doing this. We may want to make it easier to configure though. -Barry From barry at python.org Wed May 14 18:10:48 2003 From: barry at python.org (Barry Warsaw) Date: Wed May 14 13:10:50 2003 Subject: [Mailman-Developers] Looking at performance again In-Reply-To: <5.1.1.6.0.20030514173849.0450ad30@ext-proxy.ftel.co.uk> References: <5.1.1.6.0.20030514173849.0450ad30@ext-proxy.ftel.co.uk> Message-ID: <1052932216.5006.61.camel@barry> On Wed, 2003-05-14 at 12:47, Richard Barrett wrote: > Mailman runs entirely out of NFS file space on my major client's site. It > is central to the backup and resilience (backup server) strategy for that > site. I would want to retain NFS locking as an option. Thanks for the data point. -Barry From Mark at Rauterkus.com Mon May 12 12:17:34 2003 From: Mark at Rauterkus.com (Mark Rauterkus) Date: Wed May 14 13:29:30 2003 Subject: [Mailman-Developers] Re: A Helper Script Message-ID: <200305121524.h4CFOYDK001484@rauterkus.com> > Subject: [Mailman-Developers] A Helper Script ... > Here's a link to the script: > http://linux.ucla.edu/~larva/projects/list_handle_pending Wow. Great script to have. If it works, I hope it becomes part of the /bin utilities. Having a handto get out of hot water is always nice. Having that hand always available and at the ready is even nicer. Ta. Mark Rauterkus mark@Rauterkus.com http://Rauterkus.com From r.barrett at openinfo.co.uk Wed May 14 18:47:00 2003 From: r.barrett at openinfo.co.uk (Richard Barrett) Date: Wed May 14 13:29:32 2003 Subject: [Mailman-Developers] Looking at performance again In-Reply-To: <1052929235.5006.36.camel@barry> Message-ID: <5.1.1.6.0.20030514173849.0450ad30@ext-proxy.ftel.co.uk> At 17:20 14/05/2003, Barry Warsaw wrote: big snip, because I am still thinking about the bulk of your post >- Does our "NFS-safe" locks impose too much complexity and overhead to > be worth it? Does anybody actually /use/ Mailman over NFS? Don't > we sorta suspect the LockFile implementation anyway? Would we be > better off using kernel file locks, or thread locks if we go to a MT > model? Mailman runs entirely out of NFS file space on my major client's site. It is central to the backup and resilience (backup server) strategy for that site. I would want to retain NFS locking as an option. >Okay, now I'm rambling. What is the lowest hanging fruit that we might >be able to attack? I'm up for any other ideas people have. > >-Barry > >[1] wget -E -H -k -p -nH -nd -Pdownload > followed by a little Python script to multipart/related it > > > > >_______________________________________________ >Mailman-Developers mailing list >Mailman-Developers@python.org >http://mail.python.org/mailman/listinfo/mailman-developers ------------------------------------------------------------------------------ Richard Barrett http://www.openinfo.co.uk From donn at u.washington.edu Wed May 14 11:39:02 2003 From: donn at u.washington.edu (Donn Cave) Date: Wed May 14 13:39:09 2003 Subject: [Mailman-Developers] Looking at performance again Message-ID: <200305141739.h4EHd2QN019814@mailhost2.u.washington.edu> Our disk I/O problems will come up towards the end of the month, with database/2003-May-article 2x the size of 2003-May.txt. Don't know if this counts in raw throughput, but it sure has an impact. Archiving looks to me like the bulk of our system CPU and disk load. Even less in the raw throughput department, we generate a static main listinfo page rather than poke through thousands of config.pcks every time someone wants to see the page. - In principle threading looks like a can of worms to me. Still incomplete support across platforms, problems with things like signal delivery, increase in complexity and decrease in robustness. It does depend on the application, but you have to be desperate. - We don't use NFS, but it's easy to see why someone would want to - run the web interface and mailman on separate hosts, etc. - I'm not sure I understand the multiple SMTP backends. MAL says "for delivery", which I take to mean incoming. Our listproc setup delivers to a single host but sends from multiple hosts - that's time consuming work that can easily be parallelized. We'll do it with Mailman too, have just been procrastinating. The SMTP inbound traffic seems relatively trivial to me. Donn Cave, donn@u.washington.edu From barry at python.org Wed May 14 19:07:19 2003 From: barry at python.org (Barry Warsaw) Date: Wed May 14 14:07:20 2003 Subject: [Mailman-Developers] Looking at performance again In-Reply-To: <200305141739.h4EHd2QN019814@mailhost2.u.washington.edu> References: <200305141739.h4EHd2QN019814@mailhost2.u.washington.edu> Message-ID: <1052935606.5006.79.camel@barry> On Wed, 2003-05-14 at 13:39, Donn Cave wrote: > Our disk I/O problems will come up towards the end of the month, > with database/2003-May-article 2x the size of 2003-May.txt. Don't > know if this counts in raw throughput, but it sure has an impact. > Archiving looks to me like the bulk of our system CPU and disk load. Archiving is a whole 'nuther can of worms, which could use a serious reworking. But I'm not concerned with that here given that there are at least two other abortive attempts at addressing archiver issues. > Even less in the raw throughput department, we generate a static > main listinfo page rather than poke through thousands of config.pcks > every time someone wants to see the page. That makes sense. > In principle threading looks like a can of worms to me. Still > incomplete support across platforms, problems with things like > signal delivery, increase in complexity and decrease in robustness. > It does depend on the application, but you have to be desperate. It's a lot to think/worry about. :) Thanks, -Barry From barry at python.org Wed May 14 19:13:15 2003 From: barry at python.org (Barry Warsaw) Date: Wed May 14 14:13:17 2003 Subject: [Mailman-Developers] Re: A Helper Script In-Reply-To: <200305121524.h4CFOYDK001484@rauterkus.com> References: <200305121524.h4CFOYDK001484@rauterkus.com> Message-ID: <1052935963.5006.83.camel@barry> On Mon, 2003-05-12 at 12:17, Mark Rauterkus wrote: > > Subject: [Mailman-Developers] A Helper Script > ... > > Here's a link to the script: > > http://linux.ucla.edu/~larva/projects/list_handle_pending > > Wow. Great script to have. If it works, I hope it becomes part of the /bin > utilities. Having a handto get out of hot water is always nice. Having that > hand always available and at the ready is even nicer. Indeed, seems really cool. Matt Helsley, would you be willing to assign this to the FSF? -Barry From mburton at jo.birdsense.com Wed May 14 13:10:22 2003 From: mburton at jo.birdsense.com (Mike Burton) Date: Wed May 14 15:10:30 2003 Subject: [Mailman-Developers] Another Traceback Message-ID: <2003514121022.740285@alfa> Barry got me steered in the right direction on my last problem (mixed python versions on this machine), and I appreciate that a bunch. All seemed to be well until this morning when I attempted to unsubscribe somebody from one of the lists. I tested a bit further and I get the same traceback. Again, any clues will be greatly appreciated. I'm not great at python - sorry. Traceback (most recent call last): File "/usr/local/mailman/scripts/driver", line 87, in run_main main() File "/usr/local/mailman/Mailman/Cgi/admin.py", line 169, in main change_options(mlist, category, subcat, cgidata, doc) File "/usr/local/mailman/Mailman/Cgi/admin.py", line 1354, in change_options mlist.ApprovedDeleteMember(user) File "/usr/local/mailman/Mailman/MailList.py", line 944, in ApprovedDeleteMember self.SendUnsubscribeAck(emailaddr, userlang) File "/usr/local/mailman/Mailman/Deliverer.py", line 87, in SendUnsubscribeAck Utils.wrap(self.goodbye_msg), lang) File "/usr/local/mailman/Mailman/Message.py", line 206, in __init__ errors='replace') TypeError: __init__() got an unexpected keyword argument 'errors' Take care, Mike From larva at linux.ucla.edu Wed May 14 17:06:07 2003 From: larva at linux.ucla.edu (Matt Helsley) Date: Wed May 14 19:06:42 2003 Subject: [Mailman-Developers] Re: A Helper Script In-Reply-To: <1052935963.5006.83.camel@barry> Message-ID: Sure! I'm not sure what I need to do for that though (sign papers? Or is this email sufficient?). Cheers, -Matt Helsley On 14 May 2003, Barry Warsaw wrote: > On Mon, 2003-05-12 at 12:17, Mark Rauterkus wrote: > > > Subject: [Mailman-Developers] A Helper Script > > ... > > > Here's a link to the script: > > > http://linux.ucla.edu/~larva/projects/list_handle_pending > > > > Wow. Great script to have. If it works, I hope it becomes part of the /bin > > utilities. Having a handto get out of hot water is always nice. Having that > > hand always available and at the ready is even nicer. > > Indeed, seems really cool. Matt Helsley, would you be willing to assign > this to the FSF? > > -Barry From barry at python.org Thu May 15 00:01:03 2003 From: barry at python.org (Barry Warsaw) Date: Wed May 14 23:01:37 2003 Subject: [Mailman-Developers] semantic error in mailmanctl line 255 (Mailman 2.1.2) In-Reply-To: <1052914469.8648.55.camel@chaos.dvz.fh-giessen.de> Message-ID: <7719FDA6-8681-11D7-A437-003065EEFAC8@python.org> On Wednesday, May 14, 2003, at 08:14 AM, Oliver Egginger wrote: > The original line is >> os.execl(mm_cfg.PYTHON, 'qrunner', exe, rswitch, '-s') > > But this is a semantic error we think. > The first parameter is arg0 no arg1, so you should be > using something like > > os.execl(mm_cfg.PYTHON, '' , exe, rswitch, '-s') > > Here is the diff for a patch: > 255c255 > < os.execl(mm_cfg.PYTHON, '' , exe, rswitch, '-s') > --- >> os.execl(mm_cfg.PYTHON, 'qrunner', exe, rswitch, '-s') > > > This bug breaks several python installations. > It don't work for my Mandrake system for example. I'd like to understand better what exactly breaks on Mandrake. Certainly, I've never had a problem on various Redhati. AFAIK, that argument is mostly for process listings, e.g. ps and doesn't have any semantic value. > It is possible to correct this in future releases? > What do you think? As you can tell by the comment just preceding these lines, I've thought about different values for argv0 and settled on 'qrunner' because it looks the best to me when I do a ps listing. On my RH9 system, if I use the empty string, then it eats arg1. So I'd consider using mm_cfg.PYTHON, but then the command line gets pretty long. 'qrunner' just looks the best so I'm disinclined to change that unless it fixes a real bug. -Barry From Oliver.Egginger at dvz.fh-giessen.de Thu May 15 09:29:51 2003 From: Oliver.Egginger at dvz.fh-giessen.de (Oliver Egginger) Date: Thu May 15 04:29:52 2003 Subject: [Mailman-Developers] semantic error in mailmanctl line 255(Mailman 2.1.2) In-Reply-To: <7719FDA6-8681-11D7-A437-003065EEFAC8@python.org> References: <7719FDA6-8681-11D7-A437-003065EEFAC8@python.org> Message-ID: <1052987342.26247.77.camel@chaos.dvz.fh-giessen.de> > > > > Here is the diff for a patch: > > 255c255 > > < os.execl(mm_cfg.PYTHON, '' , exe, rswitch, '-s') > > --- > >> os.execl(mm_cfg.PYTHON, 'qrunner', exe, rswitch, '-s') > > > > > > This bug breaks several python installations. > > It don't work for my Mandrake system for example. > > I'd like to understand better what exactly breaks on Mandrake. > Certainly, I've never had a problem on various Redhati. AFAIK, that > argument is mostly for process listings, e.g. ps and doesn't have any > semantic value. >From my understanding the first argument (argv[0]) of a program, which gets called by os.execl, should always yield the name of this programm. For example: os.execl(mm_cfg.PYTHON, mm_cfg.PYTHON , exe, rswitch, '-s') os.execl(mm_cfg.PYTHON, 'python' , exe, rswitch, '-s') or os.execl(exe , exe, rswitch, '-s') should work. The corresponding C systemcalls gets normally used this way. Furthermore the first suggestion os.execl(mm_cfg.PYTHON, '' , exe, rswitch, '-s') should work too but in the meantime I would prefer one of the three versions above. > > > It is possible to correct this in future releases? > > What do you think? > > As you can tell by the comment just preceding these lines, I've thought > about different values for argv0 and settled on 'qrunner' because it > looks the best to me when I do a ps listing. On my RH9 system, if I > use the empty string, then it eats arg1. So I'd consider using > mm_cfg.PYTHON, but then the command line gets pretty long. 'qrunner' > just looks the best so I'm disinclined to change that unless it fixes a > real bug. > os.execl(mm_cfg.PYTHON, 'qrunner', exe, rswitch, '-s') crashs on my system with: Could not find platform independent libraries Could not find platform dependent libraries Then it breaks with the error message: ImportError: No module named getopt File "/home/mailman/bin/qrunner", line 72, in ? import getopt ImportError: No module named getopt The messages gets repreatet several times then it breaks completely. The suggested modification solve this problem. The Qrunners starts up and everything seems to work normal. The only eye-catching thing is that I receive some error messages in the verbose mode during the qrunners starting up. I think this is another problem but maybe it gives you a hint. Here is one of them: # clear __builtin__._ Logging error: Traceback (most recent call last): File "/home/mailman/Mailman/Logging/MultiLogger.py", line 43, in write logger.write(msg) File "/home/mailman/Mailman/Logging/StampedLogger.py", line 73, in write Logger.write(self, "%s %s" % (prefix, msg)) File "/home/mailman/Mailman/Logging/Logger.py", line 88, in write msg = unicode(msg, self.__encoding) SystemError: codec module not properly initialized Original log message: # clear __builtin__._ Nevertheless Mailman seems to work normal. - oliver From carson at taltos.org Thu May 15 09:42:04 2003 From: carson at taltos.org (Carson Gaspar) Date: Thu May 15 08:41:53 2003 Subject: [Mailman-Developers] semantic error in mailmanctl line 255(Mailman 2.1.2) In-Reply-To: <1052987342.26247.77.camel@chaos.dvz.fh-giessen.de> References: <7719FDA6-8681-11D7-A437-003065EEFAC8@python.org> <1052987342.26247.77.camel@chaos.dvz.fh-giessen.de> Message-ID: <211214531.1052988124@[192.168.20.2]> --On Thursday, May 15, 2003 10:29 AM +0200 Oliver Egginger wrote: >> From my understanding the first argument (argv[0]) of a program, which > gets called by os.execl, should always yield the name of this programm. > For example: ARGV[0] can be absolutely any null terminated string your heart desires. Many pieces of software do "interesting" things based on what ARGV[0] is set to (such as shells, which are "login" shells if ARGV[0][0] is '-'). Anything that assumes ARGV[0] actually exists in the filesystem is deluded. -- Carson From Dale at Newfield.org Thu May 15 10:24:19 2003 From: Dale at Newfield.org (Dale Newfield) Date: Thu May 15 09:24:54 2003 Subject: [Mailman-Developers] semantic error in mailmanctl line 255(Mailman 2.1.2) In-Reply-To: <1052987342.26247.77.camel@chaos.dvz.fh-giessen.de> References: <7719FDA6-8681-11D7-A437-003065EEFAC8@python.org> <1052987342.26247.77.camel@chaos.dvz.fh-giessen.de> Message-ID: On Thu, 15 May 2003, Oliver Egginger wrote: > > > This bug breaks several python installations. > > > It don't work for my Mandrake system for example. Could you post the chunk of the execl manpage from Mandrake describing execl? > From my understanding the first argument (argv[0]) of a program, which > gets called by os.execl, should always yield the name of this programm. > For example: Not quite sure if the file name or the full path is called for by the manpage snippet below... Swapping in "exe" would leave the string "qrunner" there but add the rest of the path to qrunner as well... ...which might be beneficial for people running more than one installation on a box (independent of whether or not that is possible or a good idea :-)... "The const char *arg and subsequent ellipses in the execl(), execlp(), and execle() functions can be thought of as arg0, arg1, ..., argn. Together they describe a list of one or more pointers to null-terminated strings that represent the argument list available to the executed program. The first argument, by convention, should point to the file name associated with the file being executed." > os.execl(mm_cfg.PYTHON, 'qrunner', exe, rswitch, '-s') > > crashs on my system with: Just out of curiosity, are either qrunner or python in your path? --- Dale Newfield From Oliver.Egginger at dvz.fh-giessen.de Thu May 15 14:46:27 2003 From: Oliver.Egginger at dvz.fh-giessen.de (Oliver Egginger) Date: Thu May 15 09:46:28 2003 Subject: [Mailman-Developers] semantic error inmailmanctlline 255(Mailman 2.1.2) In-Reply-To: <211214531.1052988124@[192.168.20.2]> References: <7719FDA6-8681-11D7-A437-003065EEFAC8@python.org> <1052987342.26247.77.camel@chaos.dvz.fh-giessen.de> <211214531.1052988124@[192.168.20.2]> Message-ID: <1053006366.28889.129.camel@chaos.dvz.fh-giessen.de> Am Don, 2003-05-15 um 14.42 schrieb Carson Gaspar: > --On Thursday, May 15, 2003 10:29 AM +0200 Oliver Egginger > wrote: > > >> From my understanding the first argument (argv[0]) of a program, which > > gets called by os.execl, should always yield the name of this programm. > > For example: > > ARGV[0] can be absolutely any null terminated string your heart desires. > Many pieces of software do "interesting" things based on what ARGV[0] is > set to (such as shells, which are "login" shells if ARGV[0][0] is '-'). > > Anything that assumes ARGV[0] actually exists in the filesystem is deluded. As far as I am concerned but it is the common practice to set ARGV[0] to the program name. Last but not least every shell calls other programs this way and python gets started from shell a million times every day all over the world. It depends on the current program, in this case python 2.2.2, how ARGV[0]is treated. In this case it will not work if you break the common practice described above. Maybe this is only true for a few (maybe broken) Mandrake python installations. But are you completely sure that ARGV[0] is of no relevance for every python interpreter? I'am far away of being a python specialist. - oliver From Oliver.Egginger at dvz.fh-giessen.de Thu May 15 15:30:29 2003 From: Oliver.Egginger at dvz.fh-giessen.de (Oliver Egginger) Date: Thu May 15 10:30:31 2003 Subject: [Mailman-Developers] semantic error in mailmanctl ... @Dale In-Reply-To: References: <7719FDA6-8681-11D7-A437-003065EEFAC8@python.org> <1052987342.26247.77.camel@chaos.dvz.fh-giessen.de> Message-ID: <1053009005.28889.166.camel@chaos.dvz.fh-giessen.de> > Could you post the chunk of the execl manpage from Mandrake describing > execl? The execl isn't the problem. It works according to the rules. > > Just out of curiosity, are either qrunner or python in your path? At the moment I am relatively sure, that the python 2.2.2 binary on my Mandrake 9.1 system exspects itself on ARGV[0]. If ARGV[0] yields a different value than 'python', 'python2.2', '/usr/bin/python' or '/usr/bin/python2.2' the described import errors occurs. My python binary expects a executable python binary on ARGV[0] or it don't run with imports. I don't know why. - oliver From barry at python.org Thu May 15 16:02:06 2003 From: barry at python.org (Barry Warsaw) Date: Thu May 15 11:02:07 2003 Subject: [Mailman-Developers] semantic error in mailmanctl ... @Dale In-Reply-To: <1053009005.28889.166.camel@chaos.dvz.fh-giessen.de> References: <7719FDA6-8681-11D7-A437-003065EEFAC8@python.org> <1052987342.26247.77.camel@chaos.dvz.fh-giessen.de> <1053009005.28889.166.camel@chaos.dvz.fh-giessen.de> Message-ID: <1053010893.21562.20.camel@barry> On Thu, 2003-05-15 at 10:30, Oliver Egginger wrote: > > Could you post the chunk of the execl manpage from Mandrake describing > > execl? > > The execl isn't the problem. > It works according to the rules. > > > > > Just out of curiosity, are either qrunner or python in your path? > > At the moment I am relatively sure, that the python 2.2.2 binary on my Mandrake 9.1 > system exspects itself on ARGV[0]. > If ARGV[0] yields a different value than 'python', 'python2.2', '/usr/bin/python' or > '/usr/bin/python2.2' the described import errors occurs. > > My python binary expects a executable python binary on ARGV[0] or it don't run > with imports. > > I don't know why. Ok, I know what's going on, and it's not Mandrake specific, although the interaction between the default Python installation on the system, and your $PATH is probably causing you to see the bug where most people might not. I'd forgotten that the Python interpreter uses argv[0] to calculate the path to its libraries. I don't have time to tease out all the subtle interactions between $PATH, argv[0], your Python installations, --prefix, and --exec-prefix, but see Python's getpath.c mega-comment for details. Suffice to say, the full absolute path to Python (i.e. mm_cfg.PYTHON) should be passed to argv[0] in the os.execl() call for everything to work correctly. Alternatively, I could set $PYTHONHOME, but I think that's a bit more fragile. I'll commit the fix. -Barry From Oliver.Egginger at dvz.fh-giessen.de Thu May 15 16:34:35 2003 From: Oliver.Egginger at dvz.fh-giessen.de (Oliver Egginger) Date: Thu May 15 11:34:36 2003 Subject: [Mailman-Developers] semantic error in mailmanctl ... @Dale In-Reply-To: <1053010893.21562.20.camel@barry> References: <7719FDA6-8681-11D7-A437-003065EEFAC8@python.org> <1052987342.26247.77.camel@chaos.dvz.fh-giessen.de> <1053009005.28889.166.camel@chaos.dvz.fh-giessen.de> <1053010893.21562.20.camel@barry> Message-ID: <1053012858.26253.188.camel@chaos.dvz.fh-giessen.de> > I'll commit the fix. Thank you! And thank you very much for throwing light on this. - oliver Am Don, 2003-05-15 um 17.01 schrieb Barry Warsaw: > On Thu, 2003-05-15 at 10:30, Oliver Egginger wrote: > > > Could you post the chunk of the execl manpage from Mandrake describing > > > execl? > > > > The execl isn't the problem. > > It works according to the rules. > > > > > > > > Just out of curiosity, are either qrunner or python in your path? > > > > At the moment I am relatively sure, that the python 2.2.2 binary on my Mandrake 9.1 > > system exspects itself on ARGV[0]. > > If ARGV[0] yields a different value than 'python', 'python2.2', '/usr/bin/python' or > > '/usr/bin/python2.2' the described import errors occurs. > > > > My python binary expects a executable python binary on ARGV[0] or it don't run > > with imports. > > > > I don't know why. > > Ok, I know what's going on, and it's not Mandrake specific, although the > interaction between the default Python installation on the system, and > your $PATH is probably causing you to see the bug where most people > might not. > > I'd forgotten that the Python interpreter uses argv[0] to calculate the > path to its libraries. I don't have time to tease out all the subtle > interactions between $PATH, argv[0], your Python installations, > --prefix, and --exec-prefix, but see Python's getpath.c mega-comment for > details. > > Suffice to say, the full absolute path to Python (i.e. mm_cfg.PYTHON) > should be passed to argv[0] in the os.execl() call for everything to > work correctly. Alternatively, I could set $PYTHONHOME, but I think > that's a bit more fragile. > > I'll commit the fix. > -Barry > > > > _______________________________________________ > Mailman-Developers mailing list > Mailman-Developers@python.org > http://mail.python.org/mailman/listinfo/mailman-developers From charlie at begeistert.org Thu May 15 18:49:50 2003 From: charlie at begeistert.org (Charlie Clark) Date: Thu May 15 11:48:29 2003 Subject: [Mailman-Developers] Re: Looking at performance again In-Reply-To: References: Message-ID: <20030515174950.32194.17@wonderland.1052981285.fake> On 2003-05-14 at 21:11:38 [+0200], mailman-developers-request@python.org wrote: > > I'm not sure I understand the multiple SMTP backends. MAL says "for > delivery", which I take to mean incoming. Our listproc setup delivers to > a single host but sends from multiple hosts - that's time consuming work > that can easily be parallelized. We'll do it with Mailman too, have just > been procrastinating. The SMTP inbound traffic seems relatively trivial > to me. No, it is outbound "delivery of payload" - our application is large volume outgoing with negligible incoming. Using delivery makes sense for us in the overall sense and we use multiple SMTPs to make this as efficient as possible. Charlie From barry at python.org Thu May 15 17:07:18 2003 From: barry at python.org (Barry Warsaw) Date: Thu May 15 12:07:19 2003 Subject: [Mailman-Developers] Re: Looking at performance again In-Reply-To: <20030515174950.32194.17@wonderland.1052981285.fake> References: <20030515174950.32194.17@wonderland.1052981285.fake> Message-ID: <1053014805.21562.51.camel@barry> On Thu, 2003-05-15 at 11:49, Charlie Clark wrote: > No, it is outbound "delivery of payload" - our application is large volume > outgoing with negligible incoming. Using delivery makes sense for us in the > overall sense and we use multiple SMTPs to make this as efficient as > possible. What do you do about bounce processing? What's your bounce back ratio? I would think that with deliveries skewed heavily toward outbound traffic, incoming bounces will be a fairly large headache, especially as lists need to be locked to register bounce scores. -Barry From charlie at begeistert.org Thu May 15 19:31:17 2003 From: charlie at begeistert.org (Charlie Clark) Date: Thu May 15 12:29:56 2003 Subject: [Mailman-Developers] Re: Looking at performance again In-Reply-To: <1053014805.21562.51.camel@barry> References: <20030515174950.32194.17@wonderland.1052981285.fake> <1053014805.21562.51.camel@barry> Message-ID: <20030515183117.32665.19@wonderland.1052981285.fake> On 2003-05-15 at 18:06:45 [+0200], you wrote: > On Thu, 2003-05-15 at 11:49, Charlie Clark wrote: > > > No, it is outbound "delivery of payload" - our application is large > > volume outgoing with negligible incoming. Using delivery makes sense > > for us in the overall sense and we use multiple SMTPs to make this as > > efficient as possible. > > What do you do about bounce processing? What's your bounce back ratio? I > would think that with deliveries skewed heavily toward outbound traffic, > incoming bounces will be a fairly large headache, especially as lists > need to be locked to register bounce scores. Without going into implementation details - MAL is better at that and it's his code - we check addresses a lot better as we don't even have double opt-in and we have a low bounce threshold. We uncluttered the management interface and reduced the number of members per page and provide useful feedback to the admin when checking addresses including a bit of Javascript to highlight changes or proposed deletes. Using an RDBMS backend allows us to use CONSTRAINTS to catch duplicates and other invalidities. We recently did the import and caught nearly 2.000 from 25.000 and put them all straight on bounce. As the migration was recent and we don't often we don't expect to have reliable info on bounces before the summer. IMHO using an RDBMS for members offers lots of benefits: data integrity and less memory for Mailman as MAL has already explained. Mailman has been a great basis for this work - it provides the brains for user management and we've been able to extend it to run SMS (text messaging) and other services - but we had to do a lot more than initially intended to achieve this. It's very much "organic" but, hey, it's Python so we can live with that! ;-) Charlie From Oliver.Egginger at dvz.fh-giessen.de Fri May 16 08:44:52 2003 From: Oliver.Egginger at dvz.fh-giessen.de (Oliver Egginger) Date: Fri May 16 03:44:53 2003 Subject: [Mailman-Developers] Mailman 2.1.2 - Logging error messages during start and stop Message-ID: <1053071046.12428.42.camel@chaos.dvz.fh-giessen.de> Hello, I run Mailman 2.1.2. I can create lists, subscribe / unsubscribe and send messages to my lists. Also everything else (which I have tested) seems to work fine. But in verbose mode I receive during the startup (mailmanctl start) and during a mailmanctl stop messages like the following: # clear __builtin__._ Logging error: Traceback (most recent call last): File "/home/mailman/Mailman/Logging/MultiLogger.py", line 43, in write logger.write(msg) File "/home/mailman/Mailman/Logging/StampedLogger.py", line 73, in write Logger.write(self, "%s %s" % (prefix, msg)) File "/home/mailman/Mailman/Logging/Logger.py", line 88, in write msg = unicode(msg, self.__encoding) SystemError: codec module not properly initialized Original log message: # clear __builtin__._ Only the lines 43, 73 and 88 of MultiLogger.py are affected, nothing else. Augur this "Loggin errors" something bad? The loggin seems to work well anyway. I receive this messages only in verbose mode. There are no straying entries in /home/mailman/locks. I wondering, if I should bring this mailman installation into production? - oliver From hfastjava at yahoo.com Fri May 16 08:06:06 2003 From: hfastjava at yahoo.com (Hunter Peress) Date: Fri May 16 10:06:41 2003 Subject: [Mailman-Developers] appending archive url to sent out message Message-ID: <20030516140606.58720.qmail@web41304.mail.yahoo.com> For each email that mailman sends out, I want it to include the web address of that email in the archives. I've looked at the code, and im really not familiar. I went to mailman-2.1.1/Mailman/Archiver and poked around. Maybe the GetBaseArchiveURL is part of what I need. anyway, could someone assist in pointing out the places in the code i'll need to change to accomplish this. i did a: hperes@HillCountryPeress:[~/mailman-2.1.2/Mailman]%grep -r GetBase * Archiver/Archiver.py: def GetBaseArchiveURL(self): Cgi/admin.py: otherlinks.AddItem(Link(mlist.GetBaseArchiveURL(), HTMLFormatter.py: return '' % self.GetBaseArchiveURL() Handlers/CookHeaders.py: archiveurl = mlist.GetBaseArchiveURL() Handlers/Scrubber.py: baseurl = mlist.GetBaseArchiveURL() so given that its all over the place i have no idea where to star __________________________________ Do you Yahoo!? The New Yahoo! Search - Faster. Easier. Bingo. http://search.yahoo.com From barry at python.org Fri May 16 16:12:29 2003 From: barry at python.org (Barry Warsaw) Date: Fri May 16 11:12:31 2003 Subject: [Mailman-Developers] semantic error in mailmanctl line 255(Mailman 2.1.2) In-Reply-To: <1052987342.26247.77.camel@chaos.dvz.fh-giessen.de> References: <7719FDA6-8681-11D7-A437-003065EEFAC8@python.org> <1052987342.26247.77.camel@chaos.dvz.fh-giessen.de> Message-ID: <1053097915.1849.29.camel@barry> On Thu, 2003-05-15 at 04:29, Oliver Egginger wrote: > # clear __builtin__._ > Logging error: > Traceback (most recent call last): > File "/home/mailman/Mailman/Logging/MultiLogger.py", line 43, in write > logger.write(msg) > File "/home/mailman/Mailman/Logging/StampedLogger.py", line 73, in write > Logger.write(self, "%s %s" % (prefix, msg)) > File "/home/mailman/Mailman/Logging/Logger.py", line 88, in write > msg = unicode(msg, self.__encoding) > SystemError: codec module not properly initialized > Original log message: > # clear __builtin__._ What does the following give you: % python Python 2.2.2 (#1, Apr 28 2003, 12:01:50) [GCC 3.2.2 20030222 (Red Hat Linux 3.2.2-5)] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> import sys >>> sys.getdefaultencoding() 'ascii' ? -Barry From david at midrange.com Fri May 16 11:01:04 2003 From: david at midrange.com (David Gibbs) Date: Fri May 16 11:14:33 2003 Subject: [Mailman-Developers] MM 2.1.1 -> 2.1.2 patch? References: Message-ID: Is there going to be a patch available to move from 2.1.1 to 2.1.2? From barry at python.org Fri May 16 16:35:51 2003 From: barry at python.org (Barry Warsaw) Date: Fri May 16 11:35:53 2003 Subject: [Mailman-Developers] MM 2.1.1 -> 2.1.2 patch? In-Reply-To: References: Message-ID: <1053099317.1849.47.camel@barry> On Fri, 2003-05-16 at 11:01, David Gibbs wrote: > Is there going to be a patch available to move from 2.1.1 to 2.1.2? I kind of doubt it. The problem is all the binary files in cvs which make it impossible to patch critical parts, like the email package. -Barry From wheakory at isu.edu Fri May 16 23:12:26 2003 From: wheakory at isu.edu (Kory Wheatley) Date: Sat May 17 00:12:37 2003 Subject: [Mailman-Developers] PROBLEM with Administrative Requests Message-ID: <3EC5B6AA.60708@isu.edu> I've sent this email twice and no one has responded to this problem, I would really appreciate a response. I receive this below error when I go into the Administrative Interface and check "Preserve messsages for the site administrator" and then I check the discard option. Once I click submit this is what I receive below. BUG in Mailman version 2.1.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 "/home/mailman/scripts/driver", line 87, in run_main main() File "/home/mailman/Mailman/Cgi/admindb.py", line 163, in main process_form(mlist, doc, cgidata) File "/home/mailman/Mailman/Cgi/admindb.py", line 681, in process_form forward, forwardaddr) File "/home/mailman/Mailman/ListAdmin.py", line 184, in HandleRequest forward, addr) File "/home/mailman/Mailman/ListAdmin.py", line 262, in __handlepost msg = cPickle.load(fp) ValueError: could not convert string to float Kory Wheatley From wheakory at isu.edu Fri May 16 23:34:06 2003 From: wheakory at isu.edu (Kory Wheatley) Date: Sat May 17 00:34:15 2003 Subject: [Mailman-Developers] SLOW Mailmans delivery Message-ID: <3EC5BBBE.3070107@isu.edu> Is there a way to slow down the delivery of Mailman to the subscribers of all my Mailing lists? We have one list that has 16,000 subscribers to one domain, all these accounts are on our mail server. Every time a message is sent out from this list, it really causes the load on our mail server to be high. Currently our Mail server is on a powerful 3 processor HPUX 11 NClass server with 2GB of RAM. Mailman 2.1.1 is on a Red Hat 8 Pentium 600mhz, using Postfix as the MTA. I have Postfix setup to do slow delivery to this domain (isu.edu), but that doesn't seem to help. I also lowered the SMTP_MAX_RCPTS = to 3, thinking that might help. Postfix is setup as: In Main.cf transport_maps = hash:/etc/postfix/transport slow_destination_concurrency_limit = 1 In Master.cf slow unix - - y - - smtp In Transport isu.edu slow: Any Suggestions like causing the smtp process to pause after sending out a boat load of messages and then resume again. Kory Wheatley From maechler at stat.math.ethz.ch Sat May 17 17:53:52 2003 From: maechler at stat.math.ethz.ch (Martin Maechler) Date: Sat May 17 10:54:16 2003 Subject: [Mailman-Developers] Mass subscription failed / R-sig-QA mailing list In-Reply-To: References: Message-ID: <16070.19712.507731.680268@gargle.gargle.HOWL> >>>>> "Jim" == Jim Garrett >>>>> on Fri, 16 May 2003 16:34:00 -0400 writes: Jim> Hi Martin, Seeing the message below, I had the Jim> impression that I was subscribed to the mailing list, Jim> when perhaps I wasn't. At least, I sent a message to Jim> the list and didn't receive it, so I thought I wasn't Jim> signed up (maybe the list is intelligent enough not to Jim> send me my own messages...). So I subscribed, and all Jim> seems well. no, not from here. If I look at the members list, I only see the 6 people that have been subscribed for many many months, but not all the new ones I subscribed on May 7 -- nor your new subscription as of May 15. I'm very much startled and even shocked about such a problem -- that I haven't seen in the past for the many other mailman lists we manage here successfully. If I read the "subscribe" log file (of mailman) which tells me about the subscription it `did' : May 07 09:16:30 2003 (23390) r-sig-qa: new "Jim_Garrett@bd.com" <> May 07 09:16:30 2003 (23390) r-sig-qa: new "Rob.Balshaw@syreon.com" <> May 07 09:16:30 2003 (23390) r-sig-qa: new "barker@medtap.com" <> May 07 09:16:30 2003 (23390) r-sig-qa: new "fharrell@virginia.edu" <> May 07 09:16:31 2003 (23390) r-sig-qa: new "gregory_r_warnes@groton.pfizer.com" <> May 07 09:16:31 2003 (23390) r-sig-qa: new "luke@inpharmatica.co.uk" <> May 07 09:16:31 2003 (23390) r-sig-qa: new "maechler@stat.math.ethz.ch" <> May 07 09:16:31 2003 (23390) r-sig-qa: new "p.murrell@auckland.ac.nz" <> May 07 09:16:31 2003 (23390) r-sig-qa: new "partha_bagchi@hgsi.com" <> May 07 09:16:32 2003 (23390) r-sig-qa: new "rossini@blindglobe.net" <> May 07 09:16:32 2003 (23390) r-sig-qa: new "rreeve@liposcience.com" <> May 07 09:16:32 2003 (23390) r-sig-qa: new "tura@centroin.com.br" <> May 07 09:16:32 2003 (23390) r-sig-qa: new "v_bill_pikounis@merck.com" <> May 07 09:16:32 2003 (23390) r-sig-qa: new "werner_engl@baxter.com" <> May 15 22:05:38 2003 (20223) r-sig-qa: pending Jim Garrett 198.232.248.8 May 15 22:13:52 2003 (20630) r-sig-qa: new "jim_garrett@bd.com" everything looks fine, but when I then look at the members lists, nobody new one is there.... Jim> I wonder if it's possible that some people think they Jim> are subscribed when in fact they are not. Could you Jim> please verify how many are subscribed? I tried to Jim> check the subscriber list but wasn't allowed (even Jim> after giving my password). as you see, I did subscribe you and all these by a so-called "mass subscription" and you did get the corresponding welcome e-mail (that you had appended here). I just tried again (needs a tiny bit longer when working from home), and it didn't work again -- when I tried to "upload a file" of new member addresses. However when I tried (the old way of) pasting the new members e-mails in to the web-interface form -- it did work. This is clearly a bug with mailman (2.1.2) or our setup of mailman (the web server doesn't have the same files mounted, the file I used is only available on the client and the machine where mailman runs, but not on the machine where httpd runs). For this reason, I forward this answer to quite a few other people. Anyway, the new subscription are now up. Probably you should send a new short mail mentioning that everyone can use the list archives to read your last posting and Kurt Hornik's reply to it, via the usual web interface, or very directly going to https://www.stat.math.ethz.ch/pipermail/r-sig-qa/2003-May/thread.html Please apologize the problem! Martin Maechler http://stat.ethz.ch/~maechler/ Seminar fuer Statistik, ETH-Zentrum LEO C16 Leonhardstr. 27 ETH (Federal Inst. Technology) 8092 Zurich SWITZERLAND phone: x-41-1-632-3408 fax: ...-1228 <>< From Tom at ESEstudios.com Sat May 17 18:58:47 2003 From: Tom at ESEstudios.com (Tom Eagle) Date: Sun May 18 23:09:21 2003 Subject: [Mailman-Developers] BSD 4.6 GID Problems Message-ID: <010001c31cc7$e370dc80$6401a8c0@ESEstudios.com> Call someone make suggestion for correcting my BSD4.6 GID Problems. I don't want to break something while trying to fix mailman. I would be happy to call to discuss the problems. Thanks, Tom Eagle From steve at fractalus.com Sun May 18 13:15:45 2003 From: steve at fractalus.com (SteveC) Date: Sun May 18 23:09:24 2003 Subject: [Mailman-Developers] gpg again Message-ID: <20030518111545.GC19785@fractalus.com> Hello Please don't flame if I'm out of place, I'll go rtfm/etc but I googled for mailman+gpg and it came up with a bunch of old stuff on this list. from what I can see periodically someone would come along and say 'we want gpg support' but things don't happen. So, if anyone has a second I'd like to know why? Because it would be very cool. gpg would of course not be used by most lists, because most lists are public so theres no point. Then the private lists - most people on those don't care. But I'm on a couple of lists that are private and consist exclusively of people with gpg-enabled mutt or pgp-enabled outlook and we'd *very much* like a gpg-only inline or MIME (pgp for windows can't handle mime yet I'm told, but I only use linux so...). Then of course I should be able to say 'use this key server, or accept uploaded keys' and so on. Now as a student and a volunteer on other projects I have sod all time and only a little money so I can't just add it myself (which I respect as a response) but hey - I'd bet if there was a paypal pot or whatever for people to donate to get this feature written it'd get money. So at the very least - here I am and I ask for this feature if anyone feels like writing it. have fun, SteveC steve@fractalus.com http://www.fractalus.com/steve/ From Oliver.Egginger at dvz.fh-giessen.de Mon May 19 08:24:56 2003 From: Oliver.Egginger at dvz.fh-giessen.de (Oliver Egginger) Date: Mon May 19 03:24:58 2003 Subject: [Mailman-Developers] semantic error in mailmanctlline255(Mailman 2.1.2) In-Reply-To: <1053097915.1849.29.camel@barry> References: <7719FDA6-8681-11D7-A437-003065EEFAC8@python.org> <1052987342.26247.77.camel@chaos.dvz.fh-giessen.de> <1053097915.1849.29.camel@barry> Message-ID: <1053329070.5387.17.camel@chaos.dvz.fh-giessen.de> > What does the following give you: ~$ python Python 2.2.2 (#2, Feb 5 2003, 10:40:08) [GCC 3.2.1 (Mandrake Linux 9.1 3.2.1-5mdk)] on linux-i386 Type "help", "copyright", "credits" or "license" for more information. >>> import sys >>> sys.getdefaultencoding() 'ascii' Much the same thing. Compared with your output, I would say. Could these error messages somehow or other have serious consequences? - oliver Am Fre, 2003-05-16 um 17.11 schrieb Barry Warsaw: > On Thu, 2003-05-15 at 04:29, Oliver Egginger wrote: > > > # clear __builtin__._ > > Logging error: > > Traceback (most recent call last): > > File "/home/mailman/Mailman/Logging/MultiLogger.py", line 43, in write > > logger.write(msg) > > File "/home/mailman/Mailman/Logging/StampedLogger.py", line 73, in write > > Logger.write(self, "%s %s" % (prefix, msg)) > > File "/home/mailman/Mailman/Logging/Logger.py", line 88, in write > > msg = unicode(msg, self.__encoding) > > SystemError: codec module not properly initialized > > Original log message: > > # clear __builtin__._ > > What does the following give you: > > % python > Python 2.2.2 (#1, Apr 28 2003, 12:01:50) > [GCC 3.2.2 20030222 (Red Hat Linux 3.2.2-5)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>> import sys > >>> sys.getdefaultencoding() > 'ascii' > > ? > -Barry From rommel at suse.de Mon May 19 11:56:55 2003 From: rommel at suse.de (Heiko Rommel) Date: Mon May 19 04:56:26 2003 Subject: [Mailman-Developers] SLOW Mailmans delivery In-Reply-To: <3EC5BBBE.3070107@isu.edu> References: <3EC5BBBE.3070107@isu.edu> Message-ID: On Fri, 16 May 2003, Kory Wheatley wrote: > Is there a way to slow down the delivery of Mailman to the subscribers > of all my Mailing lists? We have one list that has 16,000 subscribers to > one domain, all these accounts are on our mail server. Every time a > message is sent out from this list, it really causes the load on our > mail server to be high. Currently our Mail server is on a powerful 3 > processor HPUX 11 NClass server with 2GB of RAM. Mailman 2.1.1 is on a > Red Hat 8 Pentium 600mhz, using Postfix as the MTA. > > I have Postfix setup to do slow delivery to this domain (isu.edu), but > that doesn't seem to help. I also lowered the SMTP_MAX_RCPTS = to 3, > thinking that might help. > > Postfix is setup as: > In Main.cf > transport_maps = hash:/etc/postfix/transport > slow_destination_concurrency_limit = 1 > Even if the HP machine is loaded, your Red Hat Box may still think it's fast enough. Therefore, the slow_destination citeria might not apply. Instead, try using the nqmgr instead of the qmgr and set default_delivery_slot_cost to something big (e.g. 20). For further details, see man nqmgr. Heiko Rommel phone +49-911-740 53 696 SuSE Linux AG fax +49-911-741 77 55 Deutschherrnstr. 15-19 mail rommel@suse.de 90429 Nuernberg www http://www.suse.de/ Germany From barry at python.org Mon May 19 20:16:46 2003 From: barry at python.org (Barry Warsaw) Date: Mon May 19 15:16:47 2003 Subject: [Mailman-Developers] semantic error in mailmanctlline255(Mailman 2.1.2) In-Reply-To: <1053329070.5387.17.camel@chaos.dvz.fh-giessen.de> References: <7719FDA6-8681-11D7-A437-003065EEFAC8@python.org> <1052987342.26247.77.camel@chaos.dvz.fh-giessen.de> <1053097915.1849.29.camel@barry> <1053329070.5387.17.camel@chaos.dvz.fh-giessen.de> Message-ID: <1053371773.22001.10.camel@barry> On Mon, 2003-05-19 at 03:24, Oliver Egginger wrote: > > What does the following give you: > > ~$ python > Python 2.2.2 (#2, Feb 5 2003, 10:40:08) > [GCC 3.2.1 (Mandrake Linux 9.1 3.2.1-5mdk)] on linux-i386 > Type "help", "copyright", "credits" or "license" for more information. > >>> import sys > >>> sys.getdefaultencoding() > 'ascii' > > > Much the same thing. > Compared with your output, I would say. > > Could these error messages somehow or other have serious consequences? What does >>> unicode('foo', 'ascii') give you? If you get the same SystemError, then there's something screwy with your Python installation. If not, then double check that when you applied the mailmanctl patch, you are really using it. This means, stop the original mailmanctl, re-run configure (or config.status), re-install and then re-start mailmanctl. -Barry From Oliver.Egginger at dvz.fh-giessen.de Tue May 20 09:25:20 2003 From: Oliver.Egginger at dvz.fh-giessen.de (Oliver Egginger) Date: Tue May 20 04:25:21 2003 Subject: [Mailman-Developers] semantic errorinmailmanctlline255(Mailman 2.1.2) In-Reply-To: <1053371773.22001.10.camel@barry> References: <7719FDA6-8681-11D7-A437-003065EEFAC8@python.org> <1052987342.26247.77.camel@chaos.dvz.fh-giessen.de> <1053097915.1849.29.camel@barry> <1053329070.5387.17.camel@chaos.dvz.fh-giessen.de> <1053371773.22001.10.camel@barry> Message-ID: <1053418986.23343.72.camel@chaos.dvz.fh-giessen.de> > What does > > >>> unicode('foo', 'ascii') > > give you? > u'foo' > If you get the same SystemError, then there's something screwy with your > Python installation. If not, then double check that when you applied > the mailmanctl patch, you are really using it. This means, stop the > original mailmanctl, re-run configure (or config.status), re-install and > then re-start mailmanctl. > I did it. No change. Also Mailman doesn't start up on my system without the patch, so I have to use it. Independent from this error messages during the start and stop phase mailman seems to work well. There are no irregularities. But further particulars: when I comment out the line 126 in mailmanctl the error messages go away. Here is the line LogStdErr('error', 'mailmanctl', manual_reprime=0) I execute this function call with python -v on command line via: >>> import paths >>> from Mailman.Logging.Utils import LogStdErr >>> LogStdErr('error', 'mailmanctl', manual_reprime=0) and receive: without error messages. So it seems to work. But when I terminate the python session by typing CTRL-D (end of input) I receive the same error messages as I get from mailmanctl during the start and stop phase. I have trailed them at the end of this message. Also it seems as if the error messages came from Mailman.Logging.Utils import LogStdErr. Maybe by destroying the objects which gets created by LogStdErr('error', 'mailmanctl', manual_reprime=0). The function seems to work, none the less the shutdown of the corresponding objects seems to fail. But I'am no python expert. Here are the error messages from: python -v >>> import paths >>> from Mailman.Logging.Utils import LogStdErr >>> LogStdErr('error', 'mailmanctl', manual_reprime=0) **** and then I typing CTRL-D and got this: # clear __builtin__._ Logging error: Traceback (most recent call last): File "/home/mailman/Mailman/Logging/MultiLogger.py", line 43, in write logger.write(msg) File "/home/mailman/Mailman/Logging/StampedLogger.py", line 73, in write Logger.write(self, "%s %s" % (prefix, msg)) File "/home/mailman/Mailman/Logging/Logger.py", line 88, in write msg = unicode(msg, self.__encoding) SystemError: codec module not properly initialized Original log message: # clear __builtin__._ # clear sys.path Logging error: Traceback (most recent call last): File "/home/mailman/Mailman/Logging/MultiLogger.py", line 43, in write logger.write(msg) File "/home/mailman/Mailman/Logging/StampedLogger.py", line 73, in write Logger.write(self, "%s %s" % (prefix, msg)) File "/home/mailman/Mailman/Logging/Logger.py", line 88, in write msg = unicode(msg, self.__encoding) SystemError: codec module not properly initialized Original log message: # clear sys.path # clear sys.argv Logging error: Traceback (most recent call last): File "/home/mailman/Mailman/Logging/MultiLogger.py", line 43, in write logger.write(msg) File "/home/mailman/Mailman/Logging/StampedLogger.py", line 73, in write Logger.write(self, "%s %s" % (prefix, msg)) File "/home/mailman/Mailman/Logging/Logger.py", line 88, in write msg = unicode(msg, self.__encoding) SystemError: codec module not properly initialized Original log message: # clear sys.argv # clear sys.ps1 Logging error: Traceback (most recent call last): File "/home/mailman/Mailman/Logging/MultiLogger.py", line 43, in write logger.write(msg) File "/home/mailman/Mailman/Logging/StampedLogger.py", line 73, in write Logger.write(self, "%s %s" % (prefix, msg)) File "/home/mailman/Mailman/Logging/Logger.py", line 88, in write msg = unicode(msg, self.__encoding) SystemError: codec module not properly initialized Original log message: # clear sys.ps1 # clear sys.ps2 Logging error: Traceback (most recent call last): File "/home/mailman/Mailman/Logging/MultiLogger.py", line 43, in write logger.write(msg) File "/home/mailman/Mailman/Logging/StampedLogger.py", line 73, in write Logger.write(self, "%s %s" % (prefix, msg)) File "/home/mailman/Mailman/Logging/Logger.py", line 88, in write msg = unicode(msg, self.__encoding) SystemError: codec module not properly initialized Original log message: # clear sys.ps2 # clear sys.exitfunc Logging error: Traceback (most recent call last): File "/home/mailman/Mailman/Logging/MultiLogger.py", line 43, in write logger.write(msg) File "/home/mailman/Mailman/Logging/StampedLogger.py", line 73, in write Logger.write(self, "%s %s" % (prefix, msg)) File "/home/mailman/Mailman/Logging/Logger.py", line 88, in write msg = unicode(msg, self.__encoding) SystemError: codec module not properly initialized Original log message: # clear sys.exitfunc # clear sys.exc_type Logging error: Traceback (most recent call last): File "/home/mailman/Mailman/Logging/MultiLogger.py", line 43, in write logger.write(msg) File "/home/mailman/Mailman/Logging/StampedLogger.py", line 73, in write Logger.write(self, "%s %s" % (prefix, msg)) File "/home/mailman/Mailman/Logging/Logger.py", line 88, in write msg = unicode(msg, self.__encoding) SystemError: codec module not properly initialized Original log message: # clear sys.exc_type # clear sys.exc_value Logging error: Traceback (most recent call last): File "/home/mailman/Mailman/Logging/MultiLogger.py", line 43, in write logger.write(msg) File "/home/mailman/Mailman/Logging/StampedLogger.py", line 73, in write Logger.write(self, "%s %s" % (prefix, msg)) File "/home/mailman/Mailman/Logging/Logger.py", line 88, in write msg = unicode(msg, self.__encoding) SystemError: codec module not properly initialized Original log message: # clear sys.exc_value # clear sys.exc_traceback Logging error: Traceback (most recent call last): File "/home/mailman/Mailman/Logging/MultiLogger.py", line 43, in write logger.write(msg) File "/home/mailman/Mailman/Logging/StampedLogger.py", line 73, in write Logger.write(self, "%s %s" % (prefix, msg)) File "/home/mailman/Mailman/Logging/Logger.py", line 88, in write msg = unicode(msg, self.__encoding) SystemError: codec module not properly initialized Original log message: # clear sys.exc_traceback # clear sys.last_type Logging error: Traceback (most recent call last): File "/home/mailman/Mailman/Logging/MultiLogger.py", line 43, in write logger.write(msg) File "/home/mailman/Mailman/Logging/StampedLogger.py", line 73, in write Logger.write(self, "%s %s" % (prefix, msg)) File "/home/mailman/Mailman/Logging/Logger.py", line 88, in write msg = unicode(msg, self.__encoding) SystemError: codec module not properly initialized Original log message: # clear sys.last_type # clear sys.last_value Logging error: Traceback (most recent call last): File "/home/mailman/Mailman/Logging/MultiLogger.py", line 43, in write logger.write(msg) File "/home/mailman/Mailman/Logging/StampedLogger.py", line 73, in write Logger.write(self, "%s %s" % (prefix, msg)) File "/home/mailman/Mailman/Logging/Logger.py", line 88, in write msg = unicode(msg, self.__encoding) SystemError: codec module not properly initialized Original log message: # clear sys.last_value # clear sys.last_traceback Logging error: Traceback (most recent call last): File "/home/mailman/Mailman/Logging/MultiLogger.py", line 43, in write logger.write(msg) File "/home/mailman/Mailman/Logging/StampedLogger.py", line 73, in write Logger.write(self, "%s %s" % (prefix, msg)) File "/home/mailman/Mailman/Logging/Logger.py", line 88, in write msg = unicode(msg, self.__encoding) SystemError: codec module not properly initialized Original log message: # clear sys.last_traceback # restore sys.stdin Logging error: Traceback (most recent call last): File "/home/mailman/Mailman/Logging/MultiLogger.py", line 43, in write logger.write(msg) File "/home/mailman/Mailman/Logging/StampedLogger.py", line 73, in write Logger.write(self, "%s %s" % (prefix, msg)) File "/home/mailman/Mailman/Logging/Logger.py", line 88, in write msg = unicode(msg, self.__encoding) SystemError: codec module not properly initialized Original log message: # restore sys.stdin # restore sys.stdout Logging error: Traceback (most recent call last): File "/home/mailman/Mailman/Logging/MultiLogger.py", line 43, in write logger.write(msg) File "/home/mailman/Mailman/Logging/StampedLogger.py", line 73, in write Logger.write(self, "%s %s" % (prefix, msg)) File "/home/mailman/Mailman/Logging/Logger.py", line 88, in write msg = unicode(msg, self.__encoding) SystemError: codec module not properly initialized Original log message: # restore sys.stdout # restore sys.stderr Logging error: Traceback (most recent call last): File "/home/mailman/Mailman/Logging/MultiLogger.py", line 43, in write logger.write(msg) File "/home/mailman/Mailman/Logging/StampedLogger.py", line 73, in write Logger.write(self, "%s %s" % (prefix, msg)) File "/home/mailman/Mailman/Logging/Logger.py", line 88, in write msg = unicode(msg, self.__encoding) SystemError: codec module not properly initialized Original log message: # restore sys.stderr # cleanup __main__ # cleanup[1] __future__ # cleanup[1] site # cleanup[1] Mailman # cleanup[1] paths # cleanup[1] strop # cleanup[1] _codecs # cleanup[1] korean # cleanup[1] string # cleanup[1] japanese # cleanup[1] readline # cleanup[1] korean.aliases # cleanup[1] Mailman.Version # cleanup[1] signal # cleanup[1] posix # cleanup[1] japanese.aliases # cleanup[1] encodings # cleanup[1] Mailman.Defaults # cleanup[1] Mailman.Logging # cleanup[1] Mailman.Logging.Utils # cleanup[1] Mailman.Logging.Logger # cleanup[1] encodings.latin_1 # cleanup[1] codecs # cleanup[1] traceback # cleanup[1] linecache # cleanup[1] encodings.aliases # cleanup[1] exceptions # cleanup[1] Mailman.mm_cfg # cleanup[1] Mailman.Logging.MultiLogger # cleanup[1] Mailman.Logging.StampedLogger # cleanup[1] struct # cleanup[1] types # cleanup[1] time # cleanup[2] copy_reg # cleanup[2] os.path # cleanup[2] stat # cleanup[2] UserDict # cleanup[2] posixpath # cleanup[2] os # cleanup sys # cleanup __builtin__ # cleanup ints: 5 unfreed ints in 1 out of 5 blocks # cleanup floats - oliver From fil at rezo.net Tue May 20 11:31:15 2003 From: fil at rezo.net (Fil) Date: Tue May 20 04:31:22 2003 Subject: [Mailman-Developers] still encoding problems Message-ID: <20030520083115.GB14608@rezo.net> Hi, I'm with this morning's CVS, and installed the email-2.5.2 package correctly (I think). But I still get those errors: ==> logs/error <== May 20 10:28:25 2003 (8945) Uncaught runner exception: unknown encoding May 20 10:28:25 2003 (8945) Traceback (most recent call last): File "/usr/local/mailman/Mailman/Queue/Runner.py", line 110, in _oneloop self._onefile(msg, msgdata) File "/usr/local/mailman/Mailman/Queue/Runner.py", line 160, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/local/mailman/Mailman/Queue/IncomingRunner.py", line 130, in _dispose more = self._dopipeline(mlist, msg, msgdata, pipeline) File "/usr/local/mailman/Mailman/Queue/IncomingRunner.py", line 153, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File "/usr/local/mailman/Mailman/Handlers/CookHeaders.py", line 75, in process prefix_subject(mlist, msg, msgdata) File "/usr/local/mailman/Mailman/Handlers/CookHeaders.py", line 262, in prefix_subject h.append(s, c) File "/usr/local/mailman/pythonlib/email/Header.py", line 285, in append s = s.encode(outcodec, errors) LookupError: unknown encoding May 20 10:28:25 2003 (8945) SHUNTING: 1053419304.694351+978ad1e0b03b3e44f82eb885f530cd366a12efac -- Fil From Oliver.Egginger at dvz.fh-giessen.de Tue May 20 10:23:04 2003 From: Oliver.Egginger at dvz.fh-giessen.de (Oliver Egginger) Date: Tue May 20 05:23:07 2003 Subject: [Mailman-Developers] semantic error ... correction In-Reply-To: <1053418986.23343.72.camel@chaos.dvz.fh-giessen.de> References: <7719FDA6-8681-11D7-A437-003065EEFAC8@python.org> <1052987342.26247.77.camel@chaos.dvz.fh-giessen.de> <1053097915.1849.29.camel@barry> <1053329070.5387.17.camel@chaos.dvz.fh-giessen.de> <1053371773.22001.10.camel@barry> <1053418986.23343.72.camel@chaos.dvz.fh-giessen.de> Message-ID: <1053420530.23345.82.camel@chaos.dvz.fh-giessen.de> I wrote: > Also it seems as if the error messages came from > Mailman.Logging.Utils import LogStdErr. Sorry I meant to say 'Thus' not 'Also'. - oliver From tkikuchi at is.kochi-u.ac.jp Tue May 20 20:36:53 2003 From: tkikuchi at is.kochi-u.ac.jp (Tokio Kikuchi) Date: Tue May 20 06:37:04 2003 Subject: [Mailman-Developers] still encoding problems References: <20030520083115.GB14608@rezo.net> Message-ID: <3ECA0545.50505@is.kochi-u.ac.jp> Fil, I wonder if my patch to CookHeaders.py may solve your problem. http://sourceforge.net/tracker/?func=detail&aid=601117&group_id=103&atid=300103 It is intended for adding sequential number in the header but because I live in non-ascii world it is robust to encoding errors. Good Luck. Fil wrote: > Hi, > > I'm with this morning's CVS, and installed the email-2.5.2 package correctly > (I think). But I still get those errors: > > ==> logs/error <== > May 20 10:28:25 2003 (8945) Uncaught runner exception: unknown encoding > May 20 10:28:25 2003 (8945) Traceback (most recent call last): > File "/usr/local/mailman/Mailman/Queue/Runner.py", line 110, in _oneloop > self._onefile(msg, msgdata) > File "/usr/local/mailman/Mailman/Queue/Runner.py", line 160, in _onefile > keepqueued = self._dispose(mlist, msg, msgdata) > File "/usr/local/mailman/Mailman/Queue/IncomingRunner.py", line 130, in > _dispose > more = self._dopipeline(mlist, msg, msgdata, pipeline) > File "/usr/local/mailman/Mailman/Queue/IncomingRunner.py", line 153, in > _dopipeline > sys.modules[modname].process(mlist, msg, msgdata) > File "/usr/local/mailman/Mailman/Handlers/CookHeaders.py", line 75, in > process > prefix_subject(mlist, msg, msgdata) > File "/usr/local/mailman/Mailman/Handlers/CookHeaders.py", line 262, in > prefix_subject > h.append(s, c) > File "/usr/local/mailman/pythonlib/email/Header.py", line 285, in append > s = s.encode(outcodec, errors) > LookupError: unknown encoding > > May 20 10:28:25 2003 (8945) SHUNTING: > 1053419304.694351+978ad1e0b03b3e44f82eb885f530cd366a12efac > > > > -- Fil > -- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ From barry at python.org Tue May 20 09:59:55 2003 From: barry at python.org (Barry Warsaw) Date: Tue May 20 09:00:29 2003 Subject: [Mailman-Developers] Anyone planning on attending Freenix 2003? Message-ID: If you're planning on attending Freenix 2003, June 9-14 in San Antonio TX, and would be willing to present a paper on Mailman I18N, please contact me. I have a paper that's been accepted but am unable to attend the conference. Thanks, -Barry From barry at python.org Tue May 20 10:13:16 2003 From: barry at python.org (Barry Warsaw) Date: Tue May 20 09:13:53 2003 Subject: [Mailman-Developers] still encoding problems In-Reply-To: <20030520083115.GB14608@rezo.net> Message-ID: On Tuesday, May 20, 2003, at 04:31 AM, Fil wrote: > Hi, > > I'm with this morning's CVS, and installed the email-2.5.2 package > correctly > (I think). But I still get those errors: > > ==> logs/error <== > May 20 10:28:25 2003 (8945) Uncaught runner exception: unknown encoding > May 20 10:28:25 2003 (8945) Traceback (most recent call last): > File "/usr/local/mailman/Mailman/Queue/Runner.py", line 110, in > _oneloop > self._onefile(msg, msgdata) > File "/usr/local/mailman/Mailman/Queue/Runner.py", line 160, in > _onefile > keepqueued = self._dispose(mlist, msg, msgdata) > File "/usr/local/mailman/Mailman/Queue/IncomingRunner.py", line 130, > in > _dispose > more = self._dopipeline(mlist, msg, msgdata, pipeline) > File "/usr/local/mailman/Mailman/Queue/IncomingRunner.py", line 153, > in > _dopipeline > sys.modules[modname].process(mlist, msg, msgdata) > File "/usr/local/mailman/Mailman/Handlers/CookHeaders.py", line 75, > in > process > prefix_subject(mlist, msg, msgdata) > File "/usr/local/mailman/Mailman/Handlers/CookHeaders.py", line 262, > in > prefix_subject > h.append(s, c) > File "/usr/local/mailman/pythonlib/email/Header.py", line 285, in > append > s = s.encode(outcodec, errors) > LookupError: unknown encoding > > May 20 10:28:25 2003 (8945) SHUNTING: > 1053419304.694351+978ad1e0b03b3e44f82eb885f530cd366a12efac Can you submit a bug report and upload a message that causes this crash? -Barry From fil at rezo.net Tue May 20 16:40:20 2003 From: fil at rezo.net (Fil) Date: Tue May 20 09:40:24 2003 Subject: [Mailman-Developers] still encoding problems In-Reply-To: References: <20030520083115.GB14608@rezo.net> Message-ID: <20030520134020.GN13815@rezo.net> > >I'm with this morning's CVS, and installed the email-2.5.2 package > >correctly (I think). But I still get those errors: > .../... > Can you submit a bug report and upload a message that causes this crash? > > -Barry Done. In fact I could spot 3 different errors, and submitted a report for each one. -- Fil From Dan.Mick at sun.com Tue May 20 13:56:00 2003 From: Dan.Mick at sun.com (Dan Mick) Date: Tue May 20 15:57:01 2003 Subject: [Mailman-Developers] semantic errorinmailmanctlline255(Mailman 2.1.2) In-Reply-To: <1053418986.23343.72.camel@chaos.dvz.fh-giessen.de> References: <7719FDA6-8681-11D7-A437-003065EEFAC8@python.org> <1052987342.26247.77.camel@chaos.dvz.fh-giessen.de> <1053097915.1849.29.camel@barry> <1053329070.5387.17.camel@chaos.dvz.fh-giessen.de> <1053371773.22001.10.camel@barry> <1053418986.23343.72.camel@chaos.dvz.fh-giessen.de> Message-ID: <3ECA8850.7050204@sun.com> Oliver Egginger wrote: >>What does >> >>>>>unicode('foo', 'ascii') >> >>give you? >> > > u'foo' hey now, no reason to be insulting! :) :) (yes Oliver I'm joking) From xullo at inetware.com Wed May 21 09:57:00 2003 From: xullo at inetware.com (OXullo Intersecans) Date: Wed May 21 08:38:18 2003 Subject: [Mailman-Developers] Share list passwords with a php script Message-ID: <3ECB233C.6020309@inetware.com> Greetings, I'm advancing excuses if this topic has been treated yet but I found no clues even in this mailing list. I would find a way to let a php script running under www-data user permission to test an authentication providing email and password (I have to test if a particular user has or not access to the list) I achieved this executing 'withlist' on the script running a python piece of code: -------------- code snippet --------------------- from Mailman.Errors import NotAMemberError def getmemberpw(mlist, addr): try: pw = mlist.getMemberPassword(addr) print pw except NotAMemberError: print 'ENOPW' -------------------------------------------------- This however works well if config.pck belongs to www-data, which obviously creates a security hole I thought to find a way using a wrapper, stronging security giving the couple email,pwd to the program and get a positive or a negative response. But I know very little of python and now I'm asking if are there some other ways. Thank you very much for your kind attention Marco Fagiolini From Tom at ESEstudios.com Wed May 21 15:16:47 2003 From: Tom at ESEstudios.com (Tom Eagle) Date: Wed May 21 15:18:24 2003 Subject: [Mailman-Developers] Auto-responder Message-ID: <008201c31fcd$8a075940$6401a8c0@ESEstudios.com> I have two items about Auto-responder 1) Can there be a option to but a "real name" (either variable or fixed) in the from: header which would be less confusing that test-bounces@lsmo.us? 2) Can we use more internal strings in the body, i.e. %(description)s ? Tom Eagle From xullo at inetware.com Thu May 22 10:20:28 2003 From: xullo at inetware.com (OXullo Intersecans) Date: Thu May 22 03:21:04 2003 Subject: [Mailman-Developers] Share list passwords with a php script: a possible solution Message-ID: <3ECC7A3C.9020201@inetware.com> Greetings, I'm here again to share my solution with the list I solved my fuss with the following perl-suid script: -------------- code snippet --------------------- #!/usr/bin/perl $ENV{PATH} = ''; if ($ARGV[0] =~ /(\w{1}\w*)/) { $list = $1; } else { nok(); } if ($ARGV[1] =~ /(\w{1}[\w-.]*)\@([\w-.]+)/) { $email = "$1\@$2"; } else { nok(); } $pass = $ARGV[2]; $o = `/usr/local/mailman/bin/withlist -q -r getmemberpw $list $email`; chomp($o); if ($pass eq $o) { print "OK\n"; } else { nok(); } sub nok() { print "NOK"; exit(); } -------------------------------------------------- Cleaning up the eventual taint on the arguments, I call this script with exec() function in PHP, getting the output as a return code. The script is setuid to mailman. Thanks for your attention Marco Fagiolini From maechler at stat.math.ethz.ch Thu May 22 13:25:10 2003 From: maechler at stat.math.ethz.ch (Martin Maechler) Date: Thu May 22 06:26:25 2003 Subject: [Mailman-Developers] Mailman problem: Unable to unsubscribe {via web} In-Reply-To: References: Message-ID: <16076.42374.909602.12332@gargle.gargle.HOWL> >>>>> "JeffG" == Jeff Gentry >>>>> on Wed, 21 May 2003 16:34:02 -0400 (EDT) writes: JeffG> Martin ... I went in as the administrator and even JeffG> tried to manually unsub him and he was still on the JeffG> list. Any ideas as to what might be going on here? JeffG> ---------- Forwarded message ---------- Date: Wed, 21 JeffG> May 2003 12:54:03 -0700 (PDT) From: Lance Parsons JeffG> To: JeffG> bioconductor-owner@stat.math.ethz.ch Subject: Unable JeffG> to unsubscribe JeffG> I have un-subscribed three times from the JeffG> Bioconductor list, but I still receive email JeffG> messages. Each time I have gotten this confirmation, JeffG> but I still seem to be on the list. Can you help? JeffG> Note: forwarded message attached. JeffG> ===== Lance Parsons ------ lparsons@yahoo.com And I looked into the mailman log file {.../data/logs/subscribe} and it also showed several unsubscriptions of Lance and the one by you.. >> May 13 05:39:11 2003 (26065) bioconductor: deleted lparsons@yahoo.com; web confirmation >> May 16 05:56:25 2003 (9423) bioconductor: deleted lparsons@yahoo.com; web confirmation >> May 21 00:35:46 2003 (13519) bioconductor: deleted lparsons@yahoo.com; web confirmation >> May 21 22:22:08 2003 (9983) bioconductor: deleted lparsons@yahoo.com >> May 22 09:39:16 2003 (8466) bioconductor: deleted lparsons@yahoo.com I have now done the same (logged in as administrator) and when I unsubscribed him it worked {{the last line in the above excerpt}}. This seems like a bug/problem with the web -> mailman interface (which are on different servers). I don't understand ---> hence forwarding to people who might help. Regards, Martin Maechler http://stat.ethz.ch/~maechler/ Seminar fuer Statistik, ETH-Zentrum LEO C16 Leonhardstr. 27 ETH (Federal Inst. Technology) 8092 Zurich SWITZERLAND phone: x-41-1-632-3408 fax: ...-1228 <>< From Oliver.Egginger at dvz.fh-giessen.de Thu May 22 12:20:21 2003 From: Oliver.Egginger at dvz.fh-giessen.de (Oliver Egginger) Date: Thu May 22 07:20:22 2003 Subject: [Mailman-Developers] Re: [Mailman-Users] mailmanctl DOESN'T start In-Reply-To: <3ECCA0A7.7080005@cedex.es> References: <3ECCA0A7.7080005@cedex.es> Message-ID: <1053601427.3736.73.camel@chaos.dvz.fh-giessen.de> You maybe have to patch bin/mailmanctl. Here is the diff for a patch: 255c255 os.execl(mm_cfg.PYTHON, mm_cfg.PYTHON , exe, rswitch, '-s') --- os.execl(mm_cfg.PYTHON, 'qrunner', exe, rswitch, '-s') The last line namely os.execl(mm_cfg.PYTHON, 'qrunner', exe, rswitch, '-s') is the original line from the 2.1.2 mailman distribution. It cause maybe the errors on your system. Barry told us, that os.execl uses the second parameter to calculate the library path enviroment for the called python interpreter. So the original line may break your python interpreter. There exists no official patch yet, so you have to fix this manually. Let us now whether or not this patch works for you. I'am using Mandrake 9.1 and it works for me. - oliver Am Don, 2003-05-22 um 12.04 schrieb javier: > Please, i've installed glibc because i thought it was the problem... > Somebody fought with a similar problem? > > :-( :-( :-( :-( > > Hello, i've installed mailman 2.1.2 in Mandrake 9.0 (sources)with python 2.2.2, > all looks to be good, but i can't start daemon. > I can create a list, and admin it, but the list doesn't send. > sendmail is working fine (after smrsh problem solved) > here is the reply of the system... thanks > > [root@pc6426 mailman]# bin/mailmanctl start > Arrancando el qrunner maestro de Mailman > [root@pc6426 mailman]# Traceback (most recent call last): > File "/usr/local/mailman/bin/qrunner", line 77, in ? > from Mailman.i18n import _ > File "/usr/local/mailman/Mailman/i18n.py", line 19, in ? > import gettext > File "/usr/local/lib/python2.2/gettext.py", line 49, in ? > from errno import ENOENT > ImportError: No module named errno [] > Traceback (most recent call last): > File "/usr/local/mailman/bin/qrunner", line 77, in ? > from Mailman.i18n import _ > File "/usr/local/mailman/Mailman/i18n.py", line 19, in ? > import gettext > File "/usr/local/lib/python2.2/gettext.py", line 49, in ? > from errno import ENOENT > ImportError: No module named errno > Traceback (most recent call last): > File "/usr/local/mailman/bin/qrunner", line 77, in ? > from Mailman.i18n import _ > File "/usr/local/mailman/Mailman/i18n.py", line 19, in ? > import gettext > File "/usr/local/lib/python2.2/gettext.py", line 49, in ? > from errno import ENOENT > ImportError: No module named errno > > -- > Javier Romero Casado > tel.913357274 > Dep. Comunicaciones > CEDEX > > > > ------------------------------------------------------ > Mailman-Users mailing list > Mailman-Users@python.org > http://mail.python.org/mailman/listinfo/mailman-users > Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py > Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ > > This message was sent to: javier.romero@cedex.es > Unsubscribe or change your options at > http://mail.python.org/mailman/options/mailman-users/javier.romero%40cedex.es > From Oliver.Egginger at dvz.fh-giessen.de Thu May 22 12:35:54 2003 From: Oliver.Egginger at dvz.fh-giessen.de (Oliver Egginger) Date: Thu May 22 07:35:55 2003 Subject: [Mailman-Developers] Re: [Mailman-Users] mailmanctl DOESN'T start In-Reply-To: <3ECCA0A7.7080005@cedex.es> References: <3ECCA0A7.7080005@cedex.es> Message-ID: <1053601427.3736.73.camel@chaos.dvz.fh-giessen.de> You maybe have to patch bin/mailmanctl. Here is the diff for a patch: 255c255 os.execl(mm_cfg.PYTHON, mm_cfg.PYTHON , exe, rswitch, '-s') --- os.execl(mm_cfg.PYTHON, 'qrunner', exe, rswitch, '-s') The last line namely os.execl(mm_cfg.PYTHON, 'qrunner', exe, rswitch, '-s') is the original line from the 2.1.2 mailman distribution. It cause maybe the errors on your system. Barry told us, that os.execl uses the second parameter to calculate the library path enviroment for the called python interpreter. So the original line may break your python interpreter. There exists no official patch yet, so you have to fix this manually. Let us now whether or not this patch works for you. I'am using Mandrake 9.1 and it works for me. - oliver Am Don, 2003-05-22 um 12.04 schrieb javier: > Please, i've installed glibc because i thought it was the problem... > Somebody fought with a similar problem? > > :-( :-( :-( :-( > > Hello, i've installed mailman 2.1.2 in Mandrake 9.0 (sources)with python 2.2.2, > all looks to be good, but i can't start daemon. > I can create a list, and admin it, but the list doesn't send. > sendmail is working fine (after smrsh problem solved) > here is the reply of the system... thanks > > [root@pc6426 mailman]# bin/mailmanctl start > Arrancando el qrunner maestro de Mailman > [root@pc6426 mailman]# Traceback (most recent call last): > File "/usr/local/mailman/bin/qrunner", line 77, in ? > from Mailman.i18n import _ > File "/usr/local/mailman/Mailman/i18n.py", line 19, in ? > import gettext > File "/usr/local/lib/python2.2/gettext.py", line 49, in ? > from errno import ENOENT > ImportError: No module named errno [] > Traceback (most recent call last): > File "/usr/local/mailman/bin/qrunner", line 77, in ? > from Mailman.i18n import _ > File "/usr/local/mailman/Mailman/i18n.py", line 19, in ? > import gettext > File "/usr/local/lib/python2.2/gettext.py", line 49, in ? > from errno import ENOENT > ImportError: No module named errno > Traceback (most recent call last): > File "/usr/local/mailman/bin/qrunner", line 77, in ? > from Mailman.i18n import _ > File "/usr/local/mailman/Mailman/i18n.py", line 19, in ? > import gettext > File "/usr/local/lib/python2.2/gettext.py", line 49, in ? > from errno import ENOENT > ImportError: No module named errno > > -- > Javier Romero Casado > tel.913357274 > Dep. Comunicaciones > CEDEX > > > > ------------------------------------------------------ > Mailman-Users mailing list > Mailman-Users@python.org > http://mail.python.org/mailman/listinfo/mailman-users > Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py > Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ > > This message was sent to: javier.romero@cedex.es > Unsubscribe or change your options at > http://mail.python.org/mailman/options/mailman-users/javier.romero%40cedex.es > From Oliver.Egginger at dvz.fh-giessen.de Thu May 22 12:51:23 2003 From: Oliver.Egginger at dvz.fh-giessen.de (Oliver Egginger) Date: Thu May 22 07:51:24 2003 Subject: [Mailman-Developers] Re: [Mailman-Users] mailmanctl DOESN'T start In-Reply-To: <3ECCA0A7.7080005@cedex.es> References: <3ECCA0A7.7080005@cedex.es> Message-ID: <1053601427.3736.73.camel@chaos.dvz.fh-giessen.de> You maybe have to patch bin/mailmanctl. Here is the diff for a patch: 255c255 os.execl(mm_cfg.PYTHON, mm_cfg.PYTHON , exe, rswitch, '-s') --- os.execl(mm_cfg.PYTHON, 'qrunner', exe, rswitch, '-s') The last line namely os.execl(mm_cfg.PYTHON, 'qrunner', exe, rswitch, '-s') is the original line from the 2.1.2 mailman distribution. It cause maybe the errors on your system. Barry told us, that os.execl uses the second parameter to calculate the library path enviroment for the called python interpreter. So the original line may break your python interpreter. There exists no official patch yet, so you have to fix this manually. Let us now whether or not this patch works for you. I'am using Mandrake 9.1 and it works for me. - oliver Am Don, 2003-05-22 um 12.04 schrieb javier: > Please, i've installed glibc because i thought it was the problem... > Somebody fought with a similar problem? > > :-( :-( :-( :-( > > Hello, i've installed mailman 2.1.2 in Mandrake 9.0 (sources)with python 2.2.2, > all looks to be good, but i can't start daemon. > I can create a list, and admin it, but the list doesn't send. > sendmail is working fine (after smrsh problem solved) > here is the reply of the system... thanks > > [root@pc6426 mailman]# bin/mailmanctl start > Arrancando el qrunner maestro de Mailman > [root@pc6426 mailman]# Traceback (most recent call last): > File "/usr/local/mailman/bin/qrunner", line 77, in ? > from Mailman.i18n import _ > File "/usr/local/mailman/Mailman/i18n.py", line 19, in ? > import gettext > File "/usr/local/lib/python2.2/gettext.py", line 49, in ? > from errno import ENOENT > ImportError: No module named errno [] > Traceback (most recent call last): > File "/usr/local/mailman/bin/qrunner", line 77, in ? > from Mailman.i18n import _ > File "/usr/local/mailman/Mailman/i18n.py", line 19, in ? > import gettext > File "/usr/local/lib/python2.2/gettext.py", line 49, in ? > from errno import ENOENT > ImportError: No module named errno > Traceback (most recent call last): > File "/usr/local/mailman/bin/qrunner", line 77, in ? > from Mailman.i18n import _ > File "/usr/local/mailman/Mailman/i18n.py", line 19, in ? > import gettext > File "/usr/local/lib/python2.2/gettext.py", line 49, in ? > from errno import ENOENT > ImportError: No module named errno > > -- > Javier Romero Casado > tel.913357274 > Dep. Comunicaciones > CEDEX > > > > ------------------------------------------------------ > Mailman-Users mailing list > Mailman-Users@python.org > http://mail.python.org/mailman/listinfo/mailman-users > Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py > Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ > > This message was sent to: javier.romero@cedex.es > Unsubscribe or change your options at > http://mail.python.org/mailman/options/mailman-users/javier.romero%40cedex.es > From Oliver.Egginger at dvz.fh-giessen.de Thu May 22 13:07:15 2003 From: Oliver.Egginger at dvz.fh-giessen.de (Oliver Egginger) Date: Thu May 22 08:07:16 2003 Subject: [Mailman-Developers] Re: [Mailman-Users] mailmanctl DOESN'T start In-Reply-To: <3ECCA0A7.7080005@cedex.es> References: <3ECCA0A7.7080005@cedex.es> Message-ID: <1053601427.3736.73.camel@chaos.dvz.fh-giessen.de> You maybe have to patch bin/mailmanctl. Here is the diff for a patch: 255c255 os.execl(mm_cfg.PYTHON, mm_cfg.PYTHON , exe, rswitch, '-s') --- os.execl(mm_cfg.PYTHON, 'qrunner', exe, rswitch, '-s') The last line namely os.execl(mm_cfg.PYTHON, 'qrunner', exe, rswitch, '-s') is the original line from the 2.1.2 mailman distribution. It cause maybe the errors on your system. Barry told us, that os.execl uses the second parameter to calculate the library path enviroment for the called python interpreter. So the original line may break your python interpreter. There exists no official patch yet, so you have to fix this manually. Let us now whether or not this patch works for you. I'am using Mandrake 9.1 and it works for me. - oliver Am Don, 2003-05-22 um 12.04 schrieb javier: > Please, i've installed glibc because i thought it was the problem... > Somebody fought with a similar problem? > > :-( :-( :-( :-( > > Hello, i've installed mailman 2.1.2 in Mandrake 9.0 (sources)with python 2.2.2, > all looks to be good, but i can't start daemon. > I can create a list, and admin it, but the list doesn't send. > sendmail is working fine (after smrsh problem solved) > here is the reply of the system... thanks > > [root@pc6426 mailman]# bin/mailmanctl start > Arrancando el qrunner maestro de Mailman > [root@pc6426 mailman]# Traceback (most recent call last): > File "/usr/local/mailman/bin/qrunner", line 77, in ? > from Mailman.i18n import _ > File "/usr/local/mailman/Mailman/i18n.py", line 19, in ? > import gettext > File "/usr/local/lib/python2.2/gettext.py", line 49, in ? > from errno import ENOENT > ImportError: No module named errno [] > Traceback (most recent call last): > File "/usr/local/mailman/bin/qrunner", line 77, in ? > from Mailman.i18n import _ > File "/usr/local/mailman/Mailman/i18n.py", line 19, in ? > import gettext > File "/usr/local/lib/python2.2/gettext.py", line 49, in ? > from errno import ENOENT > ImportError: No module named errno > Traceback (most recent call last): > File "/usr/local/mailman/bin/qrunner", line 77, in ? > from Mailman.i18n import _ > File "/usr/local/mailman/Mailman/i18n.py", line 19, in ? > import gettext > File "/usr/local/lib/python2.2/gettext.py", line 49, in ? > from errno import ENOENT > ImportError: No module named errno > > -- > Javier Romero Casado > tel.913357274 > Dep. Comunicaciones > CEDEX > > > > ------------------------------------------------------ > Mailman-Users mailing list > Mailman-Users@python.org > http://mail.python.org/mailman/listinfo/mailman-users > Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py > Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ > > This message was sent to: javier.romero@cedex.es > Unsubscribe or change your options at > http://mail.python.org/mailman/options/mailman-users/javier.romero%40cedex.es > From Oliver.Egginger at dvz.fh-giessen.de Thu May 22 13:22:45 2003 From: Oliver.Egginger at dvz.fh-giessen.de (Oliver Egginger) Date: Thu May 22 08:22:47 2003 Subject: [Mailman-Developers] Re: [Mailman-Users] mailmanctl DOESN'T start In-Reply-To: <3ECCA0A7.7080005@cedex.es> References: <3ECCA0A7.7080005@cedex.es> Message-ID: <1053601427.3736.73.camel@chaos.dvz.fh-giessen.de> You maybe have to patch bin/mailmanctl. Here is the diff for a patch: 255c255 os.execl(mm_cfg.PYTHON, mm_cfg.PYTHON , exe, rswitch, '-s') --- os.execl(mm_cfg.PYTHON, 'qrunner', exe, rswitch, '-s') The last line namely os.execl(mm_cfg.PYTHON, 'qrunner', exe, rswitch, '-s') is the original line from the 2.1.2 mailman distribution. It cause maybe the errors on your system. Barry told us, that os.execl uses the second parameter to calculate the library path enviroment for the called python interpreter. So the original line may break your python interpreter. There exists no official patch yet, so you have to fix this manually. Let us now whether or not this patch works for you. I'am using Mandrake 9.1 and it works for me. - oliver Am Don, 2003-05-22 um 12.04 schrieb javier: > Please, i've installed glibc because i thought it was the problem... > Somebody fought with a similar problem? > > :-( :-( :-( :-( > > Hello, i've installed mailman 2.1.2 in Mandrake 9.0 (sources)with python 2.2.2, > all looks to be good, but i can't start daemon. > I can create a list, and admin it, but the list doesn't send. > sendmail is working fine (after smrsh problem solved) > here is the reply of the system... thanks > > [root@pc6426 mailman]# bin/mailmanctl start > Arrancando el qrunner maestro de Mailman > [root@pc6426 mailman]# Traceback (most recent call last): > File "/usr/local/mailman/bin/qrunner", line 77, in ? > from Mailman.i18n import _ > File "/usr/local/mailman/Mailman/i18n.py", line 19, in ? > import gettext > File "/usr/local/lib/python2.2/gettext.py", line 49, in ? > from errno import ENOENT > ImportError: No module named errno [] > Traceback (most recent call last): > File "/usr/local/mailman/bin/qrunner", line 77, in ? > from Mailman.i18n import _ > File "/usr/local/mailman/Mailman/i18n.py", line 19, in ? > import gettext > File "/usr/local/lib/python2.2/gettext.py", line 49, in ? > from errno import ENOENT > ImportError: No module named errno > Traceback (most recent call last): > File "/usr/local/mailman/bin/qrunner", line 77, in ? > from Mailman.i18n import _ > File "/usr/local/mailman/Mailman/i18n.py", line 19, in ? > import gettext > File "/usr/local/lib/python2.2/gettext.py", line 49, in ? > from errno import ENOENT > ImportError: No module named errno > > -- > Javier Romero Casado > tel.913357274 > Dep. Comunicaciones > CEDEX > > > > ------------------------------------------------------ > Mailman-Users mailing list > Mailman-Users@python.org > http://mail.python.org/mailman/listinfo/mailman-users > Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py > Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ > > This message was sent to: javier.romero@cedex.es > Unsubscribe or change your options at > http://mail.python.org/mailman/options/mailman-users/javier.romero%40cedex.es > From Oliver.Egginger at dvz.fh-giessen.de Thu May 22 13:38:17 2003 From: Oliver.Egginger at dvz.fh-giessen.de (Oliver Egginger) Date: Thu May 22 08:38:19 2003 Subject: [Mailman-Developers] Re: [Mailman-Users] mailmanctl DOESN'T start In-Reply-To: <3ECCA0A7.7080005@cedex.es> References: <3ECCA0A7.7080005@cedex.es> Message-ID: <1053601427.3736.73.camel@chaos.dvz.fh-giessen.de> You maybe have to patch bin/mailmanctl. Here is the diff for a patch: 255c255 os.execl(mm_cfg.PYTHON, mm_cfg.PYTHON , exe, rswitch, '-s') --- os.execl(mm_cfg.PYTHON, 'qrunner', exe, rswitch, '-s') The last line namely os.execl(mm_cfg.PYTHON, 'qrunner', exe, rswitch, '-s') is the original line from the 2.1.2 mailman distribution. It cause maybe the errors on your system. Barry told us, that os.execl uses the second parameter to calculate the library path enviroment for the called python interpreter. So the original line may break your python interpreter. There exists no official patch yet, so you have to fix this manually. Let us now whether or not this patch works for you. I'am using Mandrake 9.1 and it works for me. - oliver Am Don, 2003-05-22 um 12.04 schrieb javier: > Please, i've installed glibc because i thought it was the problem... > Somebody fought with a similar problem? > > :-( :-( :-( :-( > > Hello, i've installed mailman 2.1.2 in Mandrake 9.0 (sources)with python 2.2.2, > all looks to be good, but i can't start daemon. > I can create a list, and admin it, but the list doesn't send. > sendmail is working fine (after smrsh problem solved) > here is the reply of the system... thanks > > [root@pc6426 mailman]# bin/mailmanctl start > Arrancando el qrunner maestro de Mailman > [root@pc6426 mailman]# Traceback (most recent call last): > File "/usr/local/mailman/bin/qrunner", line 77, in ? > from Mailman.i18n import _ > File "/usr/local/mailman/Mailman/i18n.py", line 19, in ? > import gettext > File "/usr/local/lib/python2.2/gettext.py", line 49, in ? > from errno import ENOENT > ImportError: No module named errno [] > Traceback (most recent call last): > File "/usr/local/mailman/bin/qrunner", line 77, in ? > from Mailman.i18n import _ > File "/usr/local/mailman/Mailman/i18n.py", line 19, in ? > import gettext > File "/usr/local/lib/python2.2/gettext.py", line 49, in ? > from errno import ENOENT > ImportError: No module named errno > Traceback (most recent call last): > File "/usr/local/mailman/bin/qrunner", line 77, in ? > from Mailman.i18n import _ > File "/usr/local/mailman/Mailman/i18n.py", line 19, in ? > import gettext > File "/usr/local/lib/python2.2/gettext.py", line 49, in ? > from errno import ENOENT > ImportError: No module named errno > > -- > Javier Romero Casado > tel.913357274 > Dep. Comunicaciones > CEDEX > > > > ------------------------------------------------------ > Mailman-Users mailing list > Mailman-Users@python.org > http://mail.python.org/mailman/listinfo/mailman-users > Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py > Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ > > This message was sent to: javier.romero@cedex.es > Unsubscribe or change your options at > http://mail.python.org/mailman/options/mailman-users/javier.romero%40cedex.es > From Oliver.Egginger at dvz.fh-giessen.de Thu May 22 14:09:17 2003 From: Oliver.Egginger at dvz.fh-giessen.de (Oliver Egginger) Date: Thu May 22 09:09:18 2003 Subject: [Mailman-Developers] Re: [Mailman-Users] mailmanctl DOESN'T start In-Reply-To: <3ECCA0A7.7080005@cedex.es> References: <3ECCA0A7.7080005@cedex.es> Message-ID: <1053601427.3736.73.camel@chaos.dvz.fh-giessen.de> You maybe have to patch bin/mailmanctl. Here is the diff for a patch: 255c255 os.execl(mm_cfg.PYTHON, mm_cfg.PYTHON , exe, rswitch, '-s') --- os.execl(mm_cfg.PYTHON, 'qrunner', exe, rswitch, '-s') The last line namely os.execl(mm_cfg.PYTHON, 'qrunner', exe, rswitch, '-s') is the original line from the 2.1.2 mailman distribution. It cause maybe the errors on your system. Barry told us, that os.execl uses the second parameter to calculate the library path enviroment for the called python interpreter. So the original line may break your python interpreter. There exists no official patch yet, so you have to fix this manually. Let us now whether or not this patch works for you. I'am using Mandrake 9.1 and it works for me. - oliver Am Don, 2003-05-22 um 12.04 schrieb javier: > Please, i've installed glibc because i thought it was the problem... > Somebody fought with a similar problem? > > :-( :-( :-( :-( > > Hello, i've installed mailman 2.1.2 in Mandrake 9.0 (sources)with python 2.2.2, > all looks to be good, but i can't start daemon. > I can create a list, and admin it, but the list doesn't send. > sendmail is working fine (after smrsh problem solved) > here is the reply of the system... thanks > > [root@pc6426 mailman]# bin/mailmanctl start > Arrancando el qrunner maestro de Mailman > [root@pc6426 mailman]# Traceback (most recent call last): > File "/usr/local/mailman/bin/qrunner", line 77, in ? > from Mailman.i18n import _ > File "/usr/local/mailman/Mailman/i18n.py", line 19, in ? > import gettext > File "/usr/local/lib/python2.2/gettext.py", line 49, in ? > from errno import ENOENT > ImportError: No module named errno [] > Traceback (most recent call last): > File "/usr/local/mailman/bin/qrunner", line 77, in ? > from Mailman.i18n import _ > File "/usr/local/mailman/Mailman/i18n.py", line 19, in ? > import gettext > File "/usr/local/lib/python2.2/gettext.py", line 49, in ? > from errno import ENOENT > ImportError: No module named errno > Traceback (most recent call last): > File "/usr/local/mailman/bin/qrunner", line 77, in ? > from Mailman.i18n import _ > File "/usr/local/mailman/Mailman/i18n.py", line 19, in ? > import gettext > File "/usr/local/lib/python2.2/gettext.py", line 49, in ? > from errno import ENOENT > ImportError: No module named errno > > -- > Javier Romero Casado > tel.913357274 > Dep. Comunicaciones > CEDEX > > > > ------------------------------------------------------ > Mailman-Users mailing list > Mailman-Users@python.org > http://mail.python.org/mailman/listinfo/mailman-users > Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py > Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ > > This message was sent to: javier.romero@cedex.es > Unsubscribe or change your options at > http://mail.python.org/mailman/options/mailman-users/javier.romero%40cedex.es > From javier.romero at cedex.es Thu May 22 14:37:25 2003 From: javier.romero at cedex.es (javier) Date: Thu May 22 09:16:26 2003 Subject: [Mailman-Developers] Re: [Mailman-Users] mailmanctl DO start !!!! References: <3ECCA0A7.7080005@cedex.es> <1053601427.3736.73.camel@chaos.dvz.fh-giessen.de> Message-ID: <3ECCB675.8080703@cedex.es> I kiss where you are walking...Oliver. lot of thanks! solution: os.execl(mm_cfg.PYTHON,mm_cfg.PYTHON , exe, rswitch, '-s') :-D :-D :-D :-D fixed manually Did you have to patch mailmctl for mandrake 91??? i have my own machine with 9.1, and it contains the folders /lists and /archives, and i'm trying to install in 2 differents machines (both with mandrake90) the mailman program, mounting with nfs the 9.1 machines folders, because we want to use the DNS round-robin option (high hability :-[ ) .Now we are only testing, but next week we are planing to work with two sunfire(netra&solaris8) and folders /lists and /archives in a networkappliant by nfs, we thought that we can only save the lists configuration and archives once but we can execute in two diferent machines with the same dns name.... wath do you think? [root@pc6426 mailman]# bin/mailmanctl start Arrancando el qrunner maestro de Mailman [root@pc6426 mailman]# Oliver Egginger wrote: >You maybe have to patch bin/mailmanctl. > >Here is the diff for a patch: >255c255 > os.execl(mm_cfg.PYTHON, mm_cfg.PYTHON , exe, rswitch, '-s') >--- > os.execl(mm_cfg.PYTHON, 'qrunner', exe, rswitch, '-s') > >The last line namely >os.execl(mm_cfg.PYTHON, 'qrunner', exe, rswitch, '-s') >is the original line from the 2.1.2 mailman distribution. >It cause maybe the errors on your system. > >Barry told us, that os.execl uses the second parameter to calculate the >library path enviroment for the called python interpreter. >So the original line may break your python interpreter. > >There exists no official patch yet, so you have to >fix this manually. > >Let us now whether or not this patch works for you. >I'am using Mandrake 9.1 and it works for me. > >- oliver > > >Am Don, 2003-05-22 um 12.04 schrieb javier: > > >> Please, i've installed glibc because i thought it was the problem... >>Somebody fought with a similar problem? >> >>:-( :-( :-( :-( >> >>Hello, i've installed mailman 2.1.2 in Mandrake 9.0 (sources)with python 2.2.2, >>all looks to be good, but i can't start daemon. >>I can create a list, and admin it, but the list doesn't send. >>sendmail is working fine (after smrsh problem solved) >>here is the reply of the system... thanks >> >>[root@pc6426 mailman]# bin/mailmanctl start >>Arrancando el qrunner maestro de Mailman >>[root@pc6426 mailman]# Traceback (most recent call last): >> File "/usr/local/mailman/bin/qrunner", line 77, in ? >> from Mailman.i18n import _ >> File "/usr/local/mailman/Mailman/i18n.py", line 19, in ? >> import gettext >> File "/usr/local/lib/python2.2/gettext.py", line 49, in ? >> from errno import ENOENT >>ImportError: No module named errno [] >>Traceback (most recent call last): >> File "/usr/local/mailman/bin/qrunner", line 77, in ? >> from Mailman.i18n import _ >> File "/usr/local/mailman/Mailman/i18n.py", line 19, in ? >> import gettext >> File "/usr/local/lib/python2.2/gettext.py", line 49, in ? >> from errno import ENOENT >>ImportError: No module named errno >>Traceback (most recent call last): >> File "/usr/local/mailman/bin/qrunner", line 77, in ? >> from Mailman.i18n import _ >> File "/usr/local/mailman/Mailman/i18n.py", line 19, in ? >> import gettext >> File "/usr/local/lib/python2.2/gettext.py", line 49, in ? >> from errno import ENOENT >>ImportError: No module named errno >> >>-- >>Javier Romero Casado >> tel.913357274 >>Dep. Comunicaciones >> CEDEX >> >> >> >>------------------------------------------------------ >>Mailman-Users mailing list >>Mailman-Users@python.org >>http://mail.python.org/mailman/listinfo/mailman-users >>Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py >>Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ >> >>This message was sent to: javier.romero@cedex.es >>Unsubscribe or change your options at >>http://mail.python.org/mailman/options/mailman-users/javier.romero%40cedex.es >> >> >> > > > > > > -- Javier Romero Casado tel.913357274 Dep. Comunicaciones CEDEX From Oliver.Egginger at dvz.fh-giessen.de Thu May 22 14:29:18 2003 From: Oliver.Egginger at dvz.fh-giessen.de (Oliver Egginger) Date: Thu May 22 09:29:19 2003 Subject: [Mailman-Developers] Re: [Mailman-Users] mailmanctl DOESN'T start In-Reply-To: <3ECCA0A7.7080005@cedex.es> References: <3ECCA0A7.7080005@cedex.es> Message-ID: <1053601427.3736.73.camel@chaos.dvz.fh-giessen.de> You maybe have to patch bin/mailmanctl. Here is the diff for a patch: 255c255 os.execl(mm_cfg.PYTHON, mm_cfg.PYTHON , exe, rswitch, '-s') --- os.execl(mm_cfg.PYTHON, 'qrunner', exe, rswitch, '-s') The last line namely os.execl(mm_cfg.PYTHON, 'qrunner', exe, rswitch, '-s') is the original line from the 2.1.2 mailman distribution. It cause maybe the errors on your system. Barry told us, that os.execl uses the second parameter to calculate the library path enviroment for the called python interpreter. So the original line may break your python interpreter. There exists no official patch yet, so you have to fix this manually. Let us now whether or not this patch works for you. I'am using Mandrake 9.1 and it works for me. - oliver Am Don, 2003-05-22 um 12.04 schrieb javier: > Please, i've installed glibc because i thought it was the problem... > Somebody fought with a similar problem? > > :-( :-( :-( :-( > > Hello, i've installed mailman 2.1.2 in Mandrake 9.0 (sources)with python 2.2.2, > all looks to be good, but i can't start daemon. > I can create a list, and admin it, but the list doesn't send. > sendmail is working fine (after smrsh problem solved) > here is the reply of the system... thanks > > [root@pc6426 mailman]# bin/mailmanctl start > Arrancando el qrunner maestro de Mailman > [root@pc6426 mailman]# Traceback (most recent call last): > File "/usr/local/mailman/bin/qrunner", line 77, in ? > from Mailman.i18n import _ > File "/usr/local/mailman/Mailman/i18n.py", line 19, in ? > import gettext > File "/usr/local/lib/python2.2/gettext.py", line 49, in ? > from errno import ENOENT > ImportError: No module named errno [] > Traceback (most recent call last): > File "/usr/local/mailman/bin/qrunner", line 77, in ? > from Mailman.i18n import _ > File "/usr/local/mailman/Mailman/i18n.py", line 19, in ? > import gettext > File "/usr/local/lib/python2.2/gettext.py", line 49, in ? > from errno import ENOENT > ImportError: No module named errno > Traceback (most recent call last): > File "/usr/local/mailman/bin/qrunner", line 77, in ? > from Mailman.i18n import _ > File "/usr/local/mailman/Mailman/i18n.py", line 19, in ? > import gettext > File "/usr/local/lib/python2.2/gettext.py", line 49, in ? > from errno import ENOENT > ImportError: No module named errno > > -- > Javier Romero Casado > tel.913357274 > Dep. Comunicaciones > CEDEX > > > > ------------------------------------------------------ > Mailman-Users mailing list > Mailman-Users@python.org > http://mail.python.org/mailman/listinfo/mailman-users > Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py > Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ > > This message was sent to: javier.romero@cedex.es > Unsubscribe or change your options at > http://mail.python.org/mailman/options/mailman-users/javier.romero%40cedex.es > From Oliver.Egginger at dvz.fh-giessen.de Thu May 22 14:40:31 2003 From: Oliver.Egginger at dvz.fh-giessen.de (Oliver Egginger) Date: Thu May 22 09:40:33 2003 Subject: [Mailman-Developers] Re: [Mailman-Users] mailmanctl DOESN'T start In-Reply-To: <3ECCA0A7.7080005@cedex.es> References: <3ECCA0A7.7080005@cedex.es> Message-ID: <1053601427.3736.73.camel@chaos.dvz.fh-giessen.de> You maybe have to patch bin/mailmanctl. Here is the diff for a patch: 255c255 os.execl(mm_cfg.PYTHON, mm_cfg.PYTHON , exe, rswitch, '-s') --- os.execl(mm_cfg.PYTHON, 'qrunner', exe, rswitch, '-s') The last line namely os.execl(mm_cfg.PYTHON, 'qrunner', exe, rswitch, '-s') is the original line from the 2.1.2 mailman distribution. It cause maybe the errors on your system. Barry told us, that os.execl uses the second parameter to calculate the library path enviroment for the called python interpreter. So the original line may break your python interpreter. There exists no official patch yet, so you have to fix this manually. Let us now whether or not this patch works for you. I'am using Mandrake 9.1 and it works for me. - oliver Am Don, 2003-05-22 um 12.04 schrieb javier: > Please, i've installed glibc because i thought it was the problem... > Somebody fought with a similar problem? > > :-( :-( :-( :-( > > Hello, i've installed mailman 2.1.2 in Mandrake 9.0 (sources)with python 2.2.2, > all looks to be good, but i can't start daemon. > I can create a list, and admin it, but the list doesn't send. > sendmail is working fine (after smrsh problem solved) > here is the reply of the system... thanks > > [root@pc6426 mailman]# bin/mailmanctl start > Arrancando el qrunner maestro de Mailman > [root@pc6426 mailman]# Traceback (most recent call last): > File "/usr/local/mailman/bin/qrunner", line 77, in ? > from Mailman.i18n import _ > File "/usr/local/mailman/Mailman/i18n.py", line 19, in ? > import gettext > File "/usr/local/lib/python2.2/gettext.py", line 49, in ? > from errno import ENOENT > ImportError: No module named errno [] > Traceback (most recent call last): > File "/usr/local/mailman/bin/qrunner", line 77, in ? > from Mailman.i18n import _ > File "/usr/local/mailman/Mailman/i18n.py", line 19, in ? > import gettext > File "/usr/local/lib/python2.2/gettext.py", line 49, in ? > from errno import ENOENT > ImportError: No module named errno > Traceback (most recent call last): > File "/usr/local/mailman/bin/qrunner", line 77, in ? > from Mailman.i18n import _ > File "/usr/local/mailman/Mailman/i18n.py", line 19, in ? > import gettext > File "/usr/local/lib/python2.2/gettext.py", line 49, in ? > from errno import ENOENT > ImportError: No module named errno > > -- > Javier Romero Casado > tel.913357274 > Dep. Comunicaciones > CEDEX > > > > ------------------------------------------------------ > Mailman-Users mailing list > Mailman-Users@python.org > http://mail.python.org/mailman/listinfo/mailman-users > Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py > Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ > > This message was sent to: javier.romero@cedex.es > Unsubscribe or change your options at > http://mail.python.org/mailman/options/mailman-users/javier.romero%40cedex.es > From Oliver.Egginger at dvz.fh-giessen.de Thu May 22 14:56:02 2003 From: Oliver.Egginger at dvz.fh-giessen.de (Oliver Egginger) Date: Thu May 22 09:56:03 2003 Subject: [Mailman-Developers] Re: [Mailman-Users] mailmanctl DOESN'T start In-Reply-To: <3ECCA0A7.7080005@cedex.es> References: <3ECCA0A7.7080005@cedex.es> Message-ID: <1053601427.3736.73.camel@chaos.dvz.fh-giessen.de> You maybe have to patch bin/mailmanctl. Here is the diff for a patch: 255c255 os.execl(mm_cfg.PYTHON, mm_cfg.PYTHON , exe, rswitch, '-s') --- os.execl(mm_cfg.PYTHON, 'qrunner', exe, rswitch, '-s') The last line namely os.execl(mm_cfg.PYTHON, 'qrunner', exe, rswitch, '-s') is the original line from the 2.1.2 mailman distribution. It cause maybe the errors on your system. Barry told us, that os.execl uses the second parameter to calculate the library path enviroment for the called python interpreter. So the original line may break your python interpreter. There exists no official patch yet, so you have to fix this manually. Let us now whether or not this patch works for you. I'am using Mandrake 9.1 and it works for me. - oliver Am Don, 2003-05-22 um 12.04 schrieb javier: > Please, i've installed glibc because i thought it was the problem... > Somebody fought with a similar problem? > > :-( :-( :-( :-( > > Hello, i've installed mailman 2.1.2 in Mandrake 9.0 (sources)with python 2.2.2, > all looks to be good, but i can't start daemon. > I can create a list, and admin it, but the list doesn't send. > sendmail is working fine (after smrsh problem solved) > here is the reply of the system... thanks > > [root@pc6426 mailman]# bin/mailmanctl start > Arrancando el qrunner maestro de Mailman > [root@pc6426 mailman]# Traceback (most recent call last): > File "/usr/local/mailman/bin/qrunner", line 77, in ? > from Mailman.i18n import _ > File "/usr/local/mailman/Mailman/i18n.py", line 19, in ? > import gettext > File "/usr/local/lib/python2.2/gettext.py", line 49, in ? > from errno import ENOENT > ImportError: No module named errno [] > Traceback (most recent call last): > File "/usr/local/mailman/bin/qrunner", line 77, in ? > from Mailman.i18n import _ > File "/usr/local/mailman/Mailman/i18n.py", line 19, in ? > import gettext > File "/usr/local/lib/python2.2/gettext.py", line 49, in ? > from errno import ENOENT > ImportError: No module named errno > Traceback (most recent call last): > File "/usr/local/mailman/bin/qrunner", line 77, in ? > from Mailman.i18n import _ > File "/usr/local/mailman/Mailman/i18n.py", line 19, in ? > import gettext > File "/usr/local/lib/python2.2/gettext.py", line 49, in ? > from errno import ENOENT > ImportError: No module named errno > > -- > Javier Romero Casado > tel.913357274 > Dep. Comunicaciones > CEDEX > > > > ------------------------------------------------------ > Mailman-Users mailing list > Mailman-Users@python.org > http://mail.python.org/mailman/listinfo/mailman-users > Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py > Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ > > This message was sent to: javier.romero@cedex.es > Unsubscribe or change your options at > http://mail.python.org/mailman/options/mailman-users/javier.romero%40cedex.es > From Oliver.Egginger at dvz.fh-giessen.de Thu May 22 15:11:34 2003 From: Oliver.Egginger at dvz.fh-giessen.de (Oliver Egginger) Date: Thu May 22 10:11:35 2003 Subject: [Mailman-Developers] Re: [Mailman-Users] mailmanctl DOESN'T start In-Reply-To: <3ECCA0A7.7080005@cedex.es> References: <3ECCA0A7.7080005@cedex.es> Message-ID: <1053601427.3736.73.camel@chaos.dvz.fh-giessen.de> You maybe have to patch bin/mailmanctl. Here is the diff for a patch: 255c255 os.execl(mm_cfg.PYTHON, mm_cfg.PYTHON , exe, rswitch, '-s') --- os.execl(mm_cfg.PYTHON, 'qrunner', exe, rswitch, '-s') The last line namely os.execl(mm_cfg.PYTHON, 'qrunner', exe, rswitch, '-s') is the original line from the 2.1.2 mailman distribution. It cause maybe the errors on your system. Barry told us, that os.execl uses the second parameter to calculate the library path enviroment for the called python interpreter. So the original line may break your python interpreter. There exists no official patch yet, so you have to fix this manually. Let us now whether or not this patch works for you. I'am using Mandrake 9.1 and it works for me. - oliver Am Don, 2003-05-22 um 12.04 schrieb javier: > Please, i've installed glibc because i thought it was the problem... > Somebody fought with a similar problem? > > :-( :-( :-( :-( > > Hello, i've installed mailman 2.1.2 in Mandrake 9.0 (sources)with python 2.2.2, > all looks to be good, but i can't start daemon. > I can create a list, and admin it, but the list doesn't send. > sendmail is working fine (after smrsh problem solved) > here is the reply of the system... thanks > > [root@pc6426 mailman]# bin/mailmanctl start > Arrancando el qrunner maestro de Mailman > [root@pc6426 mailman]# Traceback (most recent call last): > File "/usr/local/mailman/bin/qrunner", line 77, in ? > from Mailman.i18n import _ > File "/usr/local/mailman/Mailman/i18n.py", line 19, in ? > import gettext > File "/usr/local/lib/python2.2/gettext.py", line 49, in ? > from errno import ENOENT > ImportError: No module named errno [] > Traceback (most recent call last): > File "/usr/local/mailman/bin/qrunner", line 77, in ? > from Mailman.i18n import _ > File "/usr/local/mailman/Mailman/i18n.py", line 19, in ? > import gettext > File "/usr/local/lib/python2.2/gettext.py", line 49, in ? > from errno import ENOENT > ImportError: No module named errno > Traceback (most recent call last): > File "/usr/local/mailman/bin/qrunner", line 77, in ? > from Mailman.i18n import _ > File "/usr/local/mailman/Mailman/i18n.py", line 19, in ? > import gettext > File "/usr/local/lib/python2.2/gettext.py", line 49, in ? > from errno import ENOENT > ImportError: No module named errno > > -- > Javier Romero Casado > tel.913357274 > Dep. Comunicaciones > CEDEX > > > > ------------------------------------------------------ > Mailman-Users mailing list > Mailman-Users@python.org > http://mail.python.org/mailman/listinfo/mailman-users > Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py > Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ > > This message was sent to: javier.romero@cedex.es > Unsubscribe or change your options at > http://mail.python.org/mailman/options/mailman-users/javier.romero%40cedex.es > From Oliver.Egginger at dvz.fh-giessen.de Thu May 22 15:26:35 2003 From: Oliver.Egginger at dvz.fh-giessen.de (Oliver Egginger) Date: Thu May 22 10:26:36 2003 Subject: [Mailman-Developers] Re: [Mailman-Users] mailmanctl DOESN'T start In-Reply-To: <3ECCA0A7.7080005@cedex.es> References: <3ECCA0A7.7080005@cedex.es> Message-ID: <1053601427.3736.73.camel@chaos.dvz.fh-giessen.de> You maybe have to patch bin/mailmanctl. Here is the diff for a patch: 255c255 os.execl(mm_cfg.PYTHON, mm_cfg.PYTHON , exe, rswitch, '-s') --- os.execl(mm_cfg.PYTHON, 'qrunner', exe, rswitch, '-s') The last line namely os.execl(mm_cfg.PYTHON, 'qrunner', exe, rswitch, '-s') is the original line from the 2.1.2 mailman distribution. It cause maybe the errors on your system. Barry told us, that os.execl uses the second parameter to calculate the library path enviroment for the called python interpreter. So the original line may break your python interpreter. There exists no official patch yet, so you have to fix this manually. Let us now whether or not this patch works for you. I'am using Mandrake 9.1 and it works for me. - oliver Am Don, 2003-05-22 um 12.04 schrieb javier: > Please, i've installed glibc because i thought it was the problem... > Somebody fought with a similar problem? > > :-( :-( :-( :-( > > Hello, i've installed mailman 2.1.2 in Mandrake 9.0 (sources)with python 2.2.2, > all looks to be good, but i can't start daemon. > I can create a list, and admin it, but the list doesn't send. > sendmail is working fine (after smrsh problem solved) > here is the reply of the system... thanks > > [root@pc6426 mailman]# bin/mailmanctl start > Arrancando el qrunner maestro de Mailman > [root@pc6426 mailman]# Traceback (most recent call last): > File "/usr/local/mailman/bin/qrunner", line 77, in ? > from Mailman.i18n import _ > File "/usr/local/mailman/Mailman/i18n.py", line 19, in ? > import gettext > File "/usr/local/lib/python2.2/gettext.py", line 49, in ? > from errno import ENOENT > ImportError: No module named errno [] > Traceback (most recent call last): > File "/usr/local/mailman/bin/qrunner", line 77, in ? > from Mailman.i18n import _ > File "/usr/local/mailman/Mailman/i18n.py", line 19, in ? > import gettext > File "/usr/local/lib/python2.2/gettext.py", line 49, in ? > from errno import ENOENT > ImportError: No module named errno > Traceback (most recent call last): > File "/usr/local/mailman/bin/qrunner", line 77, in ? > from Mailman.i18n import _ > File "/usr/local/mailman/Mailman/i18n.py", line 19, in ? > import gettext > File "/usr/local/lib/python2.2/gettext.py", line 49, in ? > from errno import ENOENT > ImportError: No module named errno > > -- > Javier Romero Casado > tel.913357274 > Dep. Comunicaciones > CEDEX > > > > ------------------------------------------------------ > Mailman-Users mailing list > Mailman-Users@python.org > http://mail.python.org/mailman/listinfo/mailman-users > Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py > Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ > > This message was sent to: javier.romero@cedex.es > Unsubscribe or change your options at > http://mail.python.org/mailman/options/mailman-users/javier.romero%40cedex.es > From barry at python.org Thu May 22 15:49:58 2003 From: barry at python.org (Barry Warsaw) Date: Thu May 22 10:49:59 2003 Subject: [Mailman-Developers] Re: [Mailman-Users] mailmanctl DOESN'T start In-Reply-To: <1053601427.3736.73.camel@chaos.dvz.fh-giessen.de> References: <3ECCA0A7.7080005@cedex.es> <1053601427.3736.73.camel@chaos.dvz.fh-giessen.de> Message-ID: <1053614965.816.18.camel@barry> On Thu, 2003-05-22 at 07:03, Oliver Egginger wrote: > Barry told us, that os.execl uses the second parameter to calculate the > library path enviroment for the called python interpreter. > So the original line may break your python interpreter. Actually, it's not os.execl() that cares -- Unix semantics essentially ignore this argument for our purposes. Python however, does care about argv[0] since it uses that to calculate its default library search paths. > There exists no official patch yet, so you have to > fix this manually. At some point, perhaps soon, I'll release a 2.1.3 to fix this. I want to see if I can have some time over the weekend to close some more bugs. -Barry From Oliver.Egginger at dvz.fh-giessen.de Thu May 22 19:53:34 2003 From: Oliver.Egginger at dvz.fh-giessen.de (Oliver Egginger) Date: Thu May 22 14:53:48 2003 Subject: [Mailman-Developers] Sorry, because of the noise today. Message-ID: <1053629579.14697.73.camel@chaos.dvz.fh-giessen.de> Hello, my last message gets send again and again. This was the guiltiness of a diabolic mail hub from the Scientific University of Giessen (JLU). We now by-pass our mail traffic by sending it directly (via dns lookup) to the corresponding mail servers. Sorry again. - oliver -- Oliver Egginger Giessen-Friedberg University of Applied Sciences Wiesenstrasse 14 35390 Giessen Tel. +49 641 309-1283 Fax +49 641 309-1288 From narnett at mccmedia.com Thu May 22 16:33:43 2003 From: narnett at mccmedia.com (Nick Arnett) Date: Thu May 22 23:19:36 2003 Subject: [Mailman-Developers] Repeating messages In-Reply-To: <1053614965.816.18.camel@barry> Message-ID: FYI, Listserv prevents duplicate messages by checksumming every message and rejecting those that appear to be identical within N minutes... in case nobody has ever suggested that feature. And as long as we're on that subject, they also stop some spam by sharing the message data and temporarily (24 hours, IIRC) blocking any address that sends the same message to N mail servers around the same time. Nick -- Nick Arnett Phone/fax: (408) 904-7198 narnett@senti-metrics.com From barry at python.org Fri May 23 00:33:15 2003 From: barry at python.org (Barry Warsaw) Date: Thu May 22 23:34:20 2003 Subject: [Mailman-Developers] Re: Repeating messages In-Reply-To: Message-ID: <49FAB483-8CCF-11D7-A2F3-003065EEFAC8@python.org> On Thursday, May 22, 2003, at 06:33 PM, Nick Arnett wrote: > FYI, Listserv prevents duplicate messages by checksumming every > message and > rejecting those that appear to be identical within N minutes... in case > nobody has ever suggested that feature. > > And as long as we're on that subject, they also stop some spam by > sharing > the message data and temporarily (24 hours, IIRC) blocking any address > that > sends the same message to N mail servers around the same time. Excellent suggestions. I'd also like to include a Message-ID duplicate suppressor, which would have also caught the recent dups. -Barry From csf at moscow.com Thu May 22 21:56:31 2003 From: csf at moscow.com (Michael Yount) Date: Thu May 22 23:55:58 2003 Subject: [Mailman-Developers] Repeating messages In-Reply-To: References: <1053614965.816.18.camel@barry> Message-ID: <20030523035631.GF434@moscow.com> There is at least one problem case: someone posts a message from an address that isn't subscribed to the list and receives a notice that the message was moderated/rejected. That person then posts the message again from the correct address, and again receives a notice, this time because the message is a duplicate. Michael On 22 May 15:33, Nick Arnett wrote: > FYI, Listserv prevents duplicate messages by checksumming every message and > rejecting those that appear to be identical within N minutes... in case > nobody has ever suggested that feature. > > And as long as we're on that subject, they also stop some spam by sharing > the message data and temporarily (24 hours, IIRC) blocking any address that > sends the same message to N mail servers around the same time. > From larva at linux.ucla.edu Fri May 23 00:08:53 2003 From: larva at linux.ucla.edu (Matt Helsley) Date: Fri May 23 02:10:06 2003 Subject: [Mailman-Developers] Repeating messages In-Reply-To: <20030523035631.GF434@moscow.com> Message-ID: Well IMO moderated messages should not be grouped with rejected messages. They are very different things. I think a simple database for each list would solve the problem. A table with the following info: hash, message id, expiration time, reference When a message is received at the site, it's hash is computed and compared to the database entries of each list. If the hash or message id match and the expiration time has not passed then look at the "reference". If the reference says the email was delivered (and not held) then this is a duplicate: discard/hold (see below) the email. If the message was held previously, discard the held copy and attempt to complete the delivery (do not remove the table entry -- maybe update the expiration time and reference. Also, it may get held again). Any hold or delivery inserts an entry into the table. Rejection/discards do nothing to the table. Of course any expired database entries could be removed either during the match, or in a separate sweep (maybe triggered by cron? a daemon?) or using both methods. In fact the separate sweep would be necessary to bound the database size. The next question is how would such a system handle cross-posting? A mailman installation I help manage does have one list that feeds another and this could be a problem with the above system: intentionally posting duplicates to different lists wouldn't work. Maybe there should be an option to hold duplicates for approval rather than discard them? Does that sound reasonable? Cheers, -Matt Helsley On Thu, 22 May 2003, Michael Yount wrote: > There is at least one problem case: someone posts a message from an > address that isn't subscribed to the list and receives a notice that the > message was moderated/rejected. That person then posts the message > again from the correct address, and again receives a notice, this time > because the message is a duplicate. > > Michael > > On 22 May 15:33, Nick Arnett wrote: > > FYI, Listserv prevents duplicate messages by checksumming every message and > > rejecting those that appear to be identical within N minutes... in case > > nobody has ever suggested that feature. > > > > And as long as we're on that subject, they also stop some spam by sharing > > the message data and temporarily (24 hours, IIRC) blocking any address that > > sends the same message to N mail servers around the same time. > > > > _______________________________________________ > Mailman-Developers mailing list > Mailman-Developers@python.org > http://mail.python.org/mailman/listinfo/mailman-developers > From jdub at perkypants.org Sat May 24 15:37:59 2003 From: jdub at perkypants.org (Jeff Waugh) Date: Sat May 24 00:38:35 2003 Subject: [Mailman-Developers] Re: [Mailman-checkins] mailman3 README.txt, NONE, 3.0 In-Reply-To: References: Message-ID: <20030524043759.GD25509@lazarus> > --- NEW FILE: README.txt --- > This is a very rough work in progress. All Mailman 3.x work will > occur in this directory under the top level CVS repository. Because I > intend to reorganize the source tree, I think it's just better to > start fresh. This does however mean that for anything we copy over > (and hopefully that will be a good bit of code), we'll lose the CVS > history for it. It might be a bit of extra work, but why not just copy the files around in the repository? History is important! :-) - Jeff -- linux.conf.au 2004: Adelaide, Australia http://lca2004.linux.org.au/ "Ah, now we see the violence inherent in the system." - From Monty Python to ESR, by way of Al Viro From barry at python.org Sat May 24 07:00:42 2003 From: barry at python.org (Barry Warsaw) Date: Sat May 24 02:00:43 2003 Subject: [Mailman-Developers] Re: [Mailman-checkins] mailman3 README.txt, NONE, 3.0 In-Reply-To: <20030524043759.GD25509@lazarus> References: <20030524043759.GD25509@lazarus> Message-ID: <1053756028.20316.9.camel@geddy> On Sat, 2003-05-24 at 00:37, Jeff Waugh wrote: > It might be a bit of extra work, but why not just copy the files around in > the repository? History is important! :-) Two reasons: - I'm not even sure what the directory structure is going to look like yet, and I don't really know how, if, or which old files will map into new files. - It's a royal PITA to do this when you don't have direct access to the repository. For now, this is all extremely experimental. I just need a place to check in some noodlings so the code isn't just sitting on my disk. -Barry From jdub at perkypants.org Sat May 24 17:12:11 2003 From: jdub at perkypants.org (Jeff Waugh) Date: Sat May 24 02:13:21 2003 Subject: [Mailman-Developers] Re: [Mailman-checkins] mailman3 README.txt, NONE, 3.0 In-Reply-To: <1053756028.20316.9.camel@geddy> References: <20030524043759.GD25509@lazarus> <1053756028.20316.9.camel@geddy> Message-ID: <20030524061211.GH25509@lazarus> > - It's a royal PITA to do this when you don't have direct access to the > repository. Well, that thoroughly nukes it. ;-) > For now, this is all extremely experimental. I just need a place to > check in some noodlings so the code isn't just sitting on my disk. Awesome! Really keen to see / help out where (er, if?) I can. :-) - Jeff -- GU4DEC: June 16th-18th in Dublin, Ireland http://www.guadec.org/ "Consensus is whatever the developers remember or agree with." - Paul Vixie, Open Sources From barry at python.org Sat May 24 15:39:42 2003 From: barry at python.org (Barry Warsaw) Date: Sat May 24 10:39:43 2003 Subject: [Mailman-Developers] Re: [Mailman-checkins] mailman3 README.txt, NONE, 3.0 In-Reply-To: <20030524061211.GH25509@lazarus> References: <20030524043759.GD25509@lazarus> <1053756028.20316.9.camel@geddy> <20030524061211.GH25509@lazarus> Message-ID: <1053787146.32318.2.camel@geddy> On Sat, 2003-05-24 at 02:12, Jeff Waugh wrote: > Awesome! Really keen to see / help out where (er, if?) I can. :-) Cool. I'm thinking that once I get the basic framework in place we should open things up so more people can contribute. -Barry From davidb at chelsea.net Thu May 22 16:49:19 2003 From: davidb at chelsea.net (David Birnbaum) Date: Mon May 26 01:07:40 2003 Subject: [Mailman-Developers] Residual bounce/Unsubscribe In-Reply-To: References: Message-ID: Howdy, I am trying to determine if this is a bug or if I simply do not understand how unsubscriptions due to bounces are handled. I am managing a list with almost 20,000 members. Naturally, addresses regularly go bad on the list and start to bounce. For whatever reason, though, unsubscriptions seem to take a long time to finally goes through. For example, here is an address that seems to have finally bounced off: bounce:May 22 09:01:34 2003 (10857) Notifying disabled member user@feist.com for list: ZZZ bounce:May 22 09:01:34 2003 (10857) ZZZ: user@feist.com deleted after exhausting notices subscribe:May 22 09:01:34 2003 (10857) ZZZ: deleted user@feist.com; disabled address subscribe:May 22 09:01:34 2003 (10857) ZZZ: user@feist.com auto-unsubscribed [reason: BYBOUNCE] bounce:May 22 09:43:11 2003 (11006) ZZZ: user@feist.com residual bounce received But when I actually go look at the list, the member is still there: stella bin 12 $ list_members ZZZ | grep user@feist.com user@feist.com Sometimes, the member will ultimately get removed. But it seems to take quite a long time, and I get a number of notifications that the removal has occurred before it finally seems to become permanent. I haven't been able to discern a pattern in determining when a user actually gets removed permanently or not. I wonder if it has something to do with the "residual bounce", or not. Perhaps Mailman is not properly discarding those extra bounces? Thanks in advance for any suggestions or pointers. David. From hchs at ns.sympatico.ca Thu May 22 21:43:11 2003 From: hchs at ns.sympatico.ca (Cody Harris) Date: Mon May 26 01:07:58 2003 Subject: [Mailman-Developers] The Mailman Mailing List Message-ID: <5.2.0.9.0.20030522203649.01ba5de0@pop1.ns.sympatico.ca> My messages ARN'T getting posted. I don't know why... From jonball at cix.co.uk Sat May 24 18:25:43 2003 From: jonball at cix.co.uk (Jon Ball) Date: Mon May 26 01:08:09 2003 Subject: [Mailman-Developers] Integration with a separate RDBMS Message-ID: An organisation I'm a member of is setting up a mailing list server to host many mailing lists that for various overlapping groups of its members. Looking at the info at list.org Mailman seems ideal as web-based maintenance of the lists is a requirement. The complication is that the organisation has a commercial (boo hiss) membership system that already stores all members' email addresses and it is important that each member's email address is only stored once. The membership data is stored in an RDBMS (SQL Server I think). Two questions for the assembled experts: 1. Has anyone already set up Mailman using email addresses stored in an external database, and ideally can point to code and a working example on the www? THIS IS VERY MUCH THE PREFERRED ANSWER. 2. Can someone speculate on the feasibility of doing this and the amount of work involved? If it would require any serious hacking to Mailman, it is probably not going to be feasible to use Mailman at this organisation at all as they have no in-house programming skills. Thanks, Jon From matze at indymedia.org Sat May 24 15:26:39 2003 From: matze at indymedia.org (matze) Date: Mon May 26 01:08:28 2003 Subject: [Mailman-Developers] ssl for admin pages Message-ID: <20030524122639.GH12780@rantanplan> Skipped content of type multipart/mixed-------------- 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/20030524/17548d43/attachment.bin From barry at python.org Mon May 26 02:27:46 2003 From: barry at python.org (Barry Warsaw) Date: Mon May 26 01:28:20 2003 Subject: [Mailman-Developers] The Mailman Mailing List In-Reply-To: <5.2.0.9.0.20030522203649.01ba5de0@pop1.ns.sympatico.ca> Message-ID: On Thursday, May 22, 2003, at 07:43 PM, Cody Harris wrote: > My messages ARN'T getting posted. I don't know why... Which messages? I've cleared out the mailman-developers held messages and didn't see any by you except this one. -Barry From barry at python.org Mon May 26 02:29:25 2003 From: barry at python.org (Barry Warsaw) Date: Mon May 26 01:29:59 2003 Subject: [Mailman-Developers] Residual bounce/Unsubscribe In-Reply-To: Message-ID: <0387194F-8F3B-11D7-8CA9-003065EEFAC8@python.org> On Thursday, May 22, 2003, at 03:49 PM, David Birnbaum wrote: > I am trying to determine if this is a bug or if I simply do not > understand > how unsubscriptions due to bounces are handled. Please tell us which version of Mailman you're using. -Barry From barry at python.org Mon May 26 02:31:57 2003 From: barry at python.org (Barry Warsaw) Date: Mon May 26 01:32:31 2003 Subject: [Mailman-Developers] Integration with a separate RDBMS In-Reply-To: Message-ID: <5E0B3976-8F3B-11D7-8CA9-003065EEFAC8@python.org> On Saturday, May 24, 2003, at 12:25 PM, Jon Ball wrote: > 1. Has anyone already set up Mailman using email addresses stored in an > external database, and ideally can point to code and a working example > on > the www? THIS IS VERY MUCH THE PREFERRED ANSWER. I think Marc-Andre Lemburg -- and perhaps others -- have solutions, which may be commercial. > 2. Can someone speculate on the feasibility of doing this and the > amount of > work involved? If it would require any serious hacking to Mailman, it > is > probably not going to be feasible to use Mailman at this organisation > at all > as they have no in-house programming skills. If you wanted to roll your own, you'd have to implement a MemberAdaptor.py implementation that talks to your commercial db. It shouldn't be too hard. -Barry From davidb at chelsea.net Mon May 26 11:36:45 2003 From: davidb at chelsea.net (David Birnbaum) Date: Mon May 26 10:39:48 2003 Subject: [Mailman-Developers] Residual bounce/Unsubscribe In-Reply-To: <0387194F-8F3B-11D7-8CA9-003065EEFAC8@python.org> References: <0387194F-8F3B-11D7-8CA9-003065EEFAC8@python.org> Message-ID: Sorry...this is with the latest release, 2.1.2. It's integrated with postfix as the MTA, and as best as I can tell from logs and such, everything is being delivered to the right place. The list database has been upgraded multiples of times, in case that makes a difference (1.X to 2.0 to 2.1).... David. ----- On Mon, 26 May 2003, Barry Warsaw wrote: > On Thursday, May 22, 2003, at 03:49 PM, David Birnbaum wrote: > > > I am trying to determine if this is a bug or if I simply do not > > understand > > how unsubscriptions due to bounces are handled. > > Please tell us which version of Mailman you're using. > > -Barry > > > From Oliver.Egginger at dvz.fh-giessen.de Wed May 28 18:27:50 2003 From: Oliver.Egginger at dvz.fh-giessen.de (Oliver Egginger) Date: Wed May 28 13:27:51 2003 Subject: [Mailman-Developers] Is this a bug? (was semantic error...) In-Reply-To: <1053418986.23343.72.camel@chaos.dvz.fh-giessen.de> References: <7719FDA6-8681-11D7-A437-003065EEFAC8@python.org> <1052987342.26247.77.camel@chaos.dvz.fh-giessen.de> <1053097915.1849.29.camel@barry> <1053329070.5387.17.camel@chaos.dvz.fh-giessen.de> <1053371773.22001.10.camel@barry> <1053418986.23343.72.camel@chaos.dvz.fh-giessen.de> Message-ID: <1054142865.11436.34.camel@chaos.dvz.fh-giessen.de> Hello again, meanwhile I set up a debian "woody" with MM 2.1.2, but I receive the same error messaes like under Mandrake 9.1. I installed both systems strict from the provides packets of this distributions (except that I used MM 2.1.2). Please oblige me and start the qrunner in the verbose mode, for example by typing python -v mailmanctl start in the mailman/bin directory. I'am sure you will get the same error messages. (See the quoted message below.) And do the following: %python -v >>> import paths >>> from Mailman.Logging.Utils import LogStdErr >>> LogStdErr('error', 'mailmanctl', manual_reprime=0) *** Then typing CTRL-D (for and of input) *** This will result in the same error messages. This means, when I comment out the line 126 in mailmanctl, namely LogStdErr('error', 'mailmanctl', manual_reprime=0), the error messages will go away. Are these error messages normal? Will they only appear under Mandrake 9.1 and debian woody? Can they cause any harm? Can I comment out line 126? Which linux distribution I should use for Mailman 2.1.2? - oliver Am Die, 2003-05-20 um 10.23 schrieb Oliver Egginger: > > What does > > > > >>> unicode('foo', 'ascii') > > > > give you? > > > > u'foo' > > > If you get the same SystemError, then there's something screwy with your > > Python installation. If not, then double check that when you applied > > the mailmanctl patch, you are really using it. This means, stop the > > original mailmanctl, re-run configure (or config.status), re-install and > > then re-start mailmanctl. > > > > I did it. > No change. > Also Mailman doesn't start up on my system without the patch, > so I have to use it. > > Independent from this error messages during the start and stop phase > mailman seems to work well. > There are no irregularities. > > But further particulars: > > when I comment out the line 126 in mailmanctl the error messages go away. > Here is the line > LogStdErr('error', 'mailmanctl', manual_reprime=0) > > I execute this function call with python -v on command line via: > >>> import paths > >>> from Mailman.Logging.Utils import LogStdErr > >>> LogStdErr('error', 'mailmanctl', manual_reprime=0) > > and receive: > > > > without error messages. > So it seems to work. > > But when I terminate the python session by typing CTRL-D (end of input) > I receive the same error messages as I get from mailmanctl during the start > and stop phase. > I have trailed them at the end of this message. > > Also it seems as if the error messages came from > Mailman.Logging.Utils import LogStdErr. > Maybe by destroying the objects which gets created by > LogStdErr('error', 'mailmanctl', manual_reprime=0). > The function seems to work, none the less the shutdown of the corresponding > objects seems to fail. > But I'am no python expert. > > Here are the error messages from: > python -v > > >>> import paths > >>> from Mailman.Logging.Utils import LogStdErr > >>> LogStdErr('error', 'mailmanctl', manual_reprime=0) > > > **** and then I typing CTRL-D and got this: > > # clear __builtin__._ > Logging error: > Traceback (most recent call last): > File "/home/mailman/Mailman/Logging/MultiLogger.py", line 43, in write > logger.write(msg) > File "/home/mailman/Mailman/Logging/StampedLogger.py", line 73, in write > Logger.write(self, "%s %s" % (prefix, msg)) > File "/home/mailman/Mailman/Logging/Logger.py", line 88, in write > msg = unicode(msg, self.__encoding) > SystemError: codec module not properly initialized > Original log message: > # clear __builtin__._ > > # clear sys.path > Logging error: > Traceback (most recent call last): > File "/home/mailman/Mailman/Logging/MultiLogger.py", line 43, in write > logger.write(msg) > File "/home/mailman/Mailman/Logging/StampedLogger.py", line 73, in write > Logger.write(self, "%s %s" % (prefix, msg)) > File "/home/mailman/Mailman/Logging/Logger.py", line 88, in write > msg = unicode(msg, self.__encoding) > SystemError: codec module not properly initialized > Original log message: > # clear sys.path > > # clear sys.argv > Logging error: > Traceback (most recent call last): > File "/home/mailman/Mailman/Logging/MultiLogger.py", line 43, in write > logger.write(msg) > File "/home/mailman/Mailman/Logging/StampedLogger.py", line 73, in write > Logger.write(self, "%s %s" % (prefix, msg)) > File "/home/mailman/Mailman/Logging/Logger.py", line 88, in write > msg = unicode(msg, self.__encoding) > SystemError: codec module not properly initialized > Original log message: > # clear sys.argv > > # clear sys.ps1 > Logging error: > Traceback (most recent call last): > File "/home/mailman/Mailman/Logging/MultiLogger.py", line 43, in write > logger.write(msg) > File "/home/mailman/Mailman/Logging/StampedLogger.py", line 73, in write > Logger.write(self, "%s %s" % (prefix, msg)) > File "/home/mailman/Mailman/Logging/Logger.py", line 88, in write > msg = unicode(msg, self.__encoding) > SystemError: codec module not properly initialized > Original log message: > # clear sys.ps1 > > # clear sys.ps2 > Logging error: > Traceback (most recent call last): > File "/home/mailman/Mailman/Logging/MultiLogger.py", line 43, in write > logger.write(msg) > File "/home/mailman/Mailman/Logging/StampedLogger.py", line 73, in write > Logger.write(self, "%s %s" % (prefix, msg)) > File "/home/mailman/Mailman/Logging/Logger.py", line 88, in write > msg = unicode(msg, self.__encoding) > SystemError: codec module not properly initialized > Original log message: > # clear sys.ps2 > > # clear sys.exitfunc > Logging error: > Traceback (most recent call last): > File "/home/mailman/Mailman/Logging/MultiLogger.py", line 43, in write > logger.write(msg) > File "/home/mailman/Mailman/Logging/StampedLogger.py", line 73, in write > Logger.write(self, "%s %s" % (prefix, msg)) > File "/home/mailman/Mailman/Logging/Logger.py", line 88, in write > msg = unicode(msg, self.__encoding) > SystemError: codec module not properly initialized > Original log message: > # clear sys.exitfunc > > # clear sys.exc_type > Logging error: > Traceback (most recent call last): > File "/home/mailman/Mailman/Logging/MultiLogger.py", line 43, in write > logger.write(msg) > File "/home/mailman/Mailman/Logging/StampedLogger.py", line 73, in write > Logger.write(self, "%s %s" % (prefix, msg)) > File "/home/mailman/Mailman/Logging/Logger.py", line 88, in write > msg = unicode(msg, self.__encoding) > SystemError: codec module not properly initialized > Original log message: > # clear sys.exc_type > > # clear sys.exc_value > Logging error: > Traceback (most recent call last): > File "/home/mailman/Mailman/Logging/MultiLogger.py", line 43, in write > logger.write(msg) > File "/home/mailman/Mailman/Logging/StampedLogger.py", line 73, in write > Logger.write(self, "%s %s" % (prefix, msg)) > File "/home/mailman/Mailman/Logging/Logger.py", line 88, in write > msg = unicode(msg, self.__encoding) > SystemError: codec module not properly initialized > Original log message: > # clear sys.exc_value > > # clear sys.exc_traceback > Logging error: > Traceback (most recent call last): > File "/home/mailman/Mailman/Logging/MultiLogger.py", line 43, in write > logger.write(msg) > File "/home/mailman/Mailman/Logging/StampedLogger.py", line 73, in write > Logger.write(self, "%s %s" % (prefix, msg)) > File "/home/mailman/Mailman/Logging/Logger.py", line 88, in write > msg = unicode(msg, self.__encoding) > SystemError: codec module not properly initialized > Original log message: > # clear sys.exc_traceback > > # clear sys.last_type > Logging error: > Traceback (most recent call last): > File "/home/mailman/Mailman/Logging/MultiLogger.py", line 43, in write > logger.write(msg) > File "/home/mailman/Mailman/Logging/StampedLogger.py", line 73, in write > Logger.write(self, "%s %s" % (prefix, msg)) > File "/home/mailman/Mailman/Logging/Logger.py", line 88, in write > msg = unicode(msg, self.__encoding) > SystemError: codec module not properly initialized > Original log message: > # clear sys.last_type > > # clear sys.last_value > Logging error: > Traceback (most recent call last): > File "/home/mailman/Mailman/Logging/MultiLogger.py", line 43, in write > logger.write(msg) > File "/home/mailman/Mailman/Logging/StampedLogger.py", line 73, in write > Logger.write(self, "%s %s" % (prefix, msg)) > File "/home/mailman/Mailman/Logging/Logger.py", line 88, in write > msg = unicode(msg, self.__encoding) > SystemError: codec module not properly initialized > Original log message: > # clear sys.last_value > > # clear sys.last_traceback > Logging error: > Traceback (most recent call last): > File "/home/mailman/Mailman/Logging/MultiLogger.py", line 43, in write > logger.write(msg) > File "/home/mailman/Mailman/Logging/StampedLogger.py", line 73, in write > Logger.write(self, "%s %s" % (prefix, msg)) > File "/home/mailman/Mailman/Logging/Logger.py", line 88, in write > msg = unicode(msg, self.__encoding) > SystemError: codec module not properly initialized > Original log message: > # clear sys.last_traceback > > # restore sys.stdin > Logging error: > Traceback (most recent call last): > File "/home/mailman/Mailman/Logging/MultiLogger.py", line 43, in write > logger.write(msg) > File "/home/mailman/Mailman/Logging/StampedLogger.py", line 73, in write > Logger.write(self, "%s %s" % (prefix, msg)) > File "/home/mailman/Mailman/Logging/Logger.py", line 88, in write > msg = unicode(msg, self.__encoding) > SystemError: codec module not properly initialized > Original log message: > # restore sys.stdin > > # restore sys.stdout > Logging error: > Traceback (most recent call last): > File "/home/mailman/Mailman/Logging/MultiLogger.py", line 43, in write > logger.write(msg) > File "/home/mailman/Mailman/Logging/StampedLogger.py", line 73, in write > Logger.write(self, "%s %s" % (prefix, msg)) > File "/home/mailman/Mailman/Logging/Logger.py", line 88, in write > msg = unicode(msg, self.__encoding) > SystemError: codec module not properly initialized > Original log message: > # restore sys.stdout > > # restore sys.stderr > Logging error: > Traceback (most recent call last): > File "/home/mailman/Mailman/Logging/MultiLogger.py", line 43, in write > logger.write(msg) > File "/home/mailman/Mailman/Logging/StampedLogger.py", line 73, in write > Logger.write(self, "%s %s" % (prefix, msg)) > File "/home/mailman/Mailman/Logging/Logger.py", line 88, in write > msg = unicode(msg, self.__encoding) > SystemError: codec module not properly initialized > Original log message: > # restore sys.stderr > > # cleanup __main__ > # cleanup[1] __future__ > # cleanup[1] site > # cleanup[1] Mailman > # cleanup[1] paths > # cleanup[1] strop > # cleanup[1] _codecs > # cleanup[1] korean > # cleanup[1] string > # cleanup[1] japanese > # cleanup[1] readline > # cleanup[1] korean.aliases > # cleanup[1] Mailman.Version > # cleanup[1] signal > # cleanup[1] posix > # cleanup[1] japanese.aliases > # cleanup[1] encodings > # cleanup[1] Mailman.Defaults > # cleanup[1] Mailman.Logging > # cleanup[1] Mailman.Logging.Utils > # cleanup[1] Mailman.Logging.Logger > # cleanup[1] encodings.latin_1 > # cleanup[1] codecs > # cleanup[1] traceback > # cleanup[1] linecache > # cleanup[1] encodings.aliases > # cleanup[1] exceptions > # cleanup[1] Mailman.mm_cfg > # cleanup[1] Mailman.Logging.MultiLogger > # cleanup[1] Mailman.Logging.StampedLogger > # cleanup[1] struct > # cleanup[1] types > # cleanup[1] time > # cleanup[2] copy_reg > # cleanup[2] os.path > # cleanup[2] stat > # cleanup[2] UserDict > # cleanup[2] posixpath > # cleanup[2] os > # cleanup sys > # cleanup __builtin__ > # cleanup ints: 5 unfreed ints in 1 out of 5 blocks > # cleanup floats > > > - oliver > > > > _______________________________________________ > Mailman-Developers mailing list > Mailman-Developers@python.org > http://mail.python.org/mailman/listinfo/mailman-developers From davidb at pins.net Fri May 30 10:09:59 2003 From: davidb at pins.net (David Birnbaum) Date: Fri May 30 09:10:03 2003 Subject: [Mailman-Developers] Residual bounce/Unsubscribe In-Reply-To: References: <0387194F-8F3B-11D7-8CA9-003065EEFAC8@python.org> Message-ID: Howdy, I was wondering if you had any more thoughts on where to look. Here's another item I should have noted before - this is being generated from CRON as of last week, also: Your "cron" job on stella /usr/local/bin/python -S /home/mailman/cron/disabled produced the following output: Traceback (most recent call last): File "/home/mailman/cron/disabled", line 209, in ? main() File "/home/mailman/cron/disabled", line 201, in main mlist.sendNextNotification(member) File "/home/mailman/Mailman/Bouncer.py", line 243, in sendNextNotification {'listname' : self.real_name, File "/home/mailman/Mailman/OldStyleMemberships.py", line 102, in getMemberPassword raise Errors.NotAMemberError, member Mailman.Errors.NotAMemberError: XXX@usa.net But the user most certainly is a member (of this list, at least): stella# ./list_members thebody | grep XXX@usa.net XXX@usa.net stella# Is it possible something is corrupted in my list database? Thanks, as always. David. ----- On Mon, 26 May 2003, David Birnbaum wrote: > Sorry...this is with the latest release, 2.1.2. It's integrated with > postfix as the MTA, and as best as I can tell from logs and such, > everything is being delivered to the right place. The list database has > been upgraded multiples of times, in case that makes a difference (1.X to > 2.0 to 2.1).... > > David. > > ----- > > On Mon, 26 May 2003, Barry Warsaw wrote: > > > On Thursday, May 22, 2003, at 03:49 PM, David Birnbaum wrote: > > > > > I am trying to determine if this is a bug or if I simply do not > > > understand > > > how unsubscriptions due to bounces are handled. > > > > Please tell us which version of Mailman you're using. > > > > -Barry > > > > > > > From benjamin at alternc.org Wed May 28 12:46:33 2003 From: benjamin at alternc.org (Benjamin Sonntag) Date: Sun Jun 1 18:48:21 2003 Subject: [Mailman-Developers] [Mailman-FR] Patchs pour la traduction FR de mailman. Message-ID: <38041.80.15.78.175.1054115193.squirrel@brassens.heberge.info> Hello, here are some patches for the french translation of mailman thanks to Evelyne Chatelain from the ATLF (atlf.org). Voici quelques patchs, issus des remarques d'un membre de Globenet, merci ? lui ... 1. Patch pour r?soudre l'impossibilit? d'acc?der ? des archives priv?es de mailman. Le fichier private.html des templates fr est incorrect, apparemment ? cause d'un probleme de balise en minuscule ou de balise mal ferm?es. J'ai repris le template original. 2. Patch du .po pour corriger l'horrible "Le archive en cours n'est disponible que pour les abonn?s" :) -------------- next part -------------- A non-text attachment was scrubbed... Name: mailman.po.patch Type: application/octet-stream Size: 986 bytes Desc: not available Url : http://mail.python.org/pipermail/mailman-developers/attachments/20030528/a890ec11/mailman.po.obj -------------- next part -------------- _______________________________________________ Mailman-FR mailing list Mailman-FR@rezo.net http://listes.rezo.net/mailman/listinfo/mailman-fr From echristley at nc.rr.com Fri May 30 22:22:30 2003 From: echristley at nc.rr.com (Ernest Christley) Date: Sun Jun 1 18:48:35 2003 Subject: [Mailman-Developers] Using the correct host Message-ID: <3ED803D6.9000007@nc.rr.com> I've been trying to set up a list behind my firewall on the local network. The machine hosting mailman uses 192.168.0.2 as a static IP, but the world sees me as ernest.isa-geek.org, the DNS entry I got through dyndns.org. If you try to subscribe to the list I created, the subscribe button sends the request to 192.168.0.2 instead of ernest.isa-geek.org. While that works fine from here, people out there aren't having any luck. How do I make the subscribe button use the dns name vs the IP? You can see what I'm talking about by going here and trying to subscribe to the list: http://www.ernest.isa-geek.org/mailman/listinfo/deltaflyers I just noticed that the listinfo page says that there "currently are no publicly-advertised Mailman mailing lists on www.ernest.isa-geek.org". How do I make the list publicly-advertised? -- ----Because I can---- http://www.ernest.isa-geek.org/ ------------------------ From mm at tentra.com Mon May 26 19:34:31 2003 From: mm at tentra.com (Tentra List Support) Date: Sun Jun 1 18:48:43 2003 Subject: [Mailman-Developers] Default link colors Message-ID: <014301c323df$5bbe6770$b302a8c0@zeus> I tryed change the default page and link colors by adding relevant fields in Default.py to mm_cfg.py. Changing all of the directives worked except for WEB_LINK_COLOR which did not result in a change. I found the offending error in htmlformat.py line 326. It should read: 'link' when it reads 'alink' Changed to 'link' and default web links now change. Mailman version 2.1.2 David Blomquist Principal, Tentra IT Solutions www.tentra.com From mm at tentra.com Tue May 27 12:44:38 2003 From: mm at tentra.com (Tentra List Support) Date: Sun Jun 1 18:48:48 2003 Subject: [Mailman-Developers] Unsubscribe link Message-ID: <015b01c3246f$4346a960$b302a8c0@zeus> I would like to generate a link in the footer of each email that would take the user directly to their options page so that, if they want to unsubscribe, they can do so with a maximum of two steps one to click to the page and one to unsubscribe via the web page with no further confirmation steps. Is there a script for this already or should I look into creating one? Thank you, David Blomquist Principal, Tentra IT Solutions From S.W.Lay at ucles-red.cam.ac.uk Thu May 29 14:03:24 2003 From: S.W.Lay at ucles-red.cam.ac.uk (Steve Lay) Date: Sun Jun 1 18:48:53 2003 Subject: [Mailman-Developers] Browser stop button (revisited from 2.0.5??) Message-ID: I have a problem with the Mailman servers I run related to an issue which was discussed during the 2.0.4 to 2.0.5 transition some time ago. The problem relates to people who click the stop button on their browser while Mailman is doing its stuff. If the person in question is the list admin, making changes to the list, then Mailman just aborts without saving the list changes. Like the posters in the original discussion on this list some 2 years ago I can live with these semantics, almost.... The problem is that Mailman always returns the content of the page, which says that everything has been done, before it saves the list. For example, see lines 236-238 of admindb.py in 2.1: print doc.Format() # Commit all changes mlist.Save() The problem with this is that mlist.Save() is taking quite a while for large lists so I have to educate my list owners to be really patient and wait for the browser to finish - with very little visual cue that it is doing anything. (OK, animated wavy windows, spinning worlds, sparkly N's apart....) What would make much more sense to me (and my users) is if these two lines were done the other way around. At least the users would then understand that the system was doing something and shouldn't be interupted because they would be looking at a blank browser window. They wouldn't be told that their changes had been successfully carried out until they actually had! What do you all think? Can you see any problems with switching these two lines (similarly in the other CGI handlers)? Steve Lay From wes at greenfieldnetworks.com Wed May 28 15:53:31 2003 From: wes at greenfieldnetworks.com (Wesley T. Perdue) Date: Sun Jun 1 18:49:23 2003 Subject: [Mailman-Developers] modifying mailman's source Message-ID: <5.2.1.1.2.20030528145133.0271b9e8@mail.greenfieldnetworks-int.com> All, I need to call an external script whenever a mailing list's membership changes. I'd like to pass the name of the modified list to my script. I've spent some time studying the Mailman source, and I think the file I need to modify is ~mailman/Mailman/MailList.py. I think the functions that need to be modified are functions ApprovedAddMember, ApprovedDeleteMember, and ChangeMemberAddress. Here are the two lines that I'd like to add to the above functions: metacmd= '~mailman/scripts/my-script.pl' + ' ' + self os.system(metacmd) Does this look correct? I'm using Mailman 2.1.2 in Linux. BTW, my external script is a solution for automatically maintaining nested lists, written in Perl. I'll share it with the world once I get it working. Thanks, Wes ---------- Wes Perdue IT Manager, Greenfield Networks