Mailman 3 May 2003 - Mailman-Developers

Problem with Administrative Requests functions
by Kory Wheatley 12 May '03

12 May '03

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.

1 0

Converting from MM1.1 to MM2.1.1
by Grant Cullen 12 May '03

12 May '03

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 <grant(a)libertyrms.info> Liberty RMS

2 1

virus infection?
by Graeme Bell 12 May '03

12 May '03

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.

3 2

Re: [Mailman-Developers] Re: [Mailman-Users] Problem with Date:-headers
by Mark Martinec 09 May '03

09 May '03

>> 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

2 1

Re: [Mailman-Users] Problem with Date:-headers
by Tokio Kikuchi 08 May '03

08 May '03

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(a)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 >> >

2 3

adding list url to sent out message
by Hunter Peress 08 May '03

08 May '03

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 '<a href="%s">' % 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

1 0

adding list url to sent out message
by Hunter Peress 08 May '03

08 May '03

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 '<a href="%s">' % 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

1 0

mailman 2.1.2 upgrade warning on OS X.
by Chuq Von Rospach 08 May '03

08 May '03

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?

2 8

Re: [Mailman-Developers] message data storage
by Charlie Clark 08 May '03

08 May '03

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

1 0

Problem with Administrative requests functions
by Kory Wheatley 07 May '03

07 May '03

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.

2 1