Mailman 3 March 2003 - Mailman-Developers

[Mailman-Developers] MM 2.1.1: another uncaught bounce that should have been caught
by Martin Maechler 24 Mar '03

24 Mar '03

Dear developers, thank you very much for an already fantastic product! I hope the following is helpful for improving this part of mailman... Martin Maechler <maechler(a)stat.math.ethz.ch> 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 <><

1 0

bin/remove_members & userack
by Ricardo Kustner 22 Mar '03

22 Mar '03

Hi, I just noticed that bin/remove_members turns on "userack" by default... even though it's supposed to use the list config setting whether or not it should send a message to the unsubscribers (line 111 in remove_members says "userack = 1"). is this a bug or has this been done intentionally? I just happened to me a second time that I did a mass unsubscription with remove_members (because I had to reload the entire list of addresses on an announce list) and everybody received a message that they were removed again... which caused a lot of confusion :( Regards, Ricardo.

2 1

[Mailman-Developers] Re: [Mailman-checkins] mailman/Mailman ListAdmin.py,2.42,2.43
by Barry Warsaw 22 Mar '03

22 Mar '03

Redirecting here from mailman-checkins... On Fri, 2003-03-21 at 03:30, Thomas Wouters wrote: > On Thu, Mar 20, 2003 at 11:02:29PM -0500, Barry Warsaw wrote: > > On Wed, 2003-03-19 at 19:31, twouters(a)users.sourceforge.net wrote: > > > > Fix another of Peer's annoying bugs: somehow his next_request_id ended up > > > lower than the highest entry in the list config.db, so the assertion was > > > being triggered. We can just deal with the problem instead. > > > Very strange! Does this (and Peer's other problems) make us question > > the integrity of the LockFile algorithm? > > Yes, I'm going to setup a LockFile stresstest when I get a moment (which > will probably not be in the next three weeks, unfortunately.) Note that at the bottom of LockFile.py there's an attempt at a stress test. It would be good to code review this to make sure it's testing what we think it should test and what it ought to test <wink>. It's also never been really run in an NFS environment. I don't know if Peer's using NFS, but if so that would be the first place I'd suspect. -Barry

1 0

Is there a solution to this error log output?
by ljacobs 22 Mar '03

22 Mar '03

Python 2.2.2, RedHat 7.1, Mailman 2.1. Since upgrading to Postfix 2.0.6 (although that may be unrelated to this problem) I have been unable to post to my Mailman 2.1 moderated lists. (I never had this problem before.) The "vette" file responds properly with the "held" message and then the "approved" flag gets added as I approve the posting. However the "post" file never gets updated and the message gets shunted. The error log has this: Mar 20 17:32:37 2003 (18803) Uncaught runner exception: [Errno 4] Interrupted system call Mar 20 17:32:37 2003 (18803) 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/OutgoingRunner.py", line 61, in _dispose self._func(mlist, msg, msgdata) File "/home/mailman/Mailman/Handlers/SMTPDirect.py", line 139, in process deliveryfunc(mlist, msg, msgdata, envsender, refused, conn) File "/home/mailman/Mailman/Handlers/SMTPDirect.py", line 335, in bulkdeliver refused = conn.sendmail(envsender, recips, msgtext) File "/home/mailman/Mailman/Handlers/SMTPDirect.py", line 61, in sendmail results = self.__conn.sendmail(envsender, recips, msgtext) File "/usr/local/lib/python2.2/smtplib.py", line 675, in sendmail (code,resp)=self.rcpt(each, rcpt_options) File "/usr/local/lib/python2.2/smtplib.py", line 459, in rcpt return self.getreply() File "/usr/local/lib/python2.2/smtplib.py", line 332, in getreply line = self.file.readline() Mar 20 17:32:37 2003 (18803) SHUNTING: 1048199310.616835+b29ca3709ff2c999169ceb1c0e1462215c6b2723 Is this a known bug or where should I look? Thanks. ________________________________________________________________ Sent via the WebMessaging system at mandala-designs.com

2 1

[Mailman-Developers] New cvs-version: unshunt gives traceback directly to console.
by Jan Kellermann 21 Mar '03

21 Mar '03

Hi! after updating the cvs & installing i started unshunt. After Unshunt has ended following tracebacks came. it was the first time that I get tracebacks directly to console! it is a new error. I didnt see it before. i hoped that one day the cvs will emtpy my shunt-dir and not produce new errors :( greeting kelly. File "/usr/local/mailman-2.1/bin/qrunner", line 270, in ? main() File "/usr/local/mailman-2.1/bin/qrunner", line 230, in main qrunner.run() File "/usr/local/mailman-2.1//Mailman/Queue/Runner.py", line 59, in run filecnt = self._oneloop() File "/usr/local/mailman-2.1//Mailman/Queue/Runner.py", line 88, in _oneloop msg, msgdata = self._switchboard.dequeue(filebase) File "/usr/local/mailman-2.1//Mailman/Queue/Switchboard.py", line 151, in dequeue if data.has_key('rejection-notice'): AttributeError: 'NoneType' object has no attribute 'has_key' Traceback (most recent call last): File "/usr/local/mailman-2.1/bin/qrunner", line 270, in ? main() File "/usr/local/mailman-2.1/bin/qrunner", line 230, in main qrunner.run() File "/usr/local/mailman-2.1//Mailman/Queue/Runner.py", line 59, in run filecnt = self._oneloop() File "/usr/local/mailman-2.1//Mailman/Queue/Runner.py", line 88, in _oneloop msg, msgdata = self._switchboard.dequeue(filebase) File "/usr/local/mailman-2.1//Mailman/Queue/Switchboard.py", line 151, in dequeue if data.has_key('rejection-notice'): AttributeError: 'NoneType' object has no attribute 'has_key' Traceback (most recent call last): File "/usr/local/mailman-2.1/bin/qrunner", line 270, in ? main() File "/usr/local/mailman-2.1/bin/qrunner", line 230, in main qrunner.run() File "/usr/local/mailman-2.1//Mailman/Queue/Runner.py", line 59, in run filecnt = self._oneloop() File "/usr/local/mailman-2.1//Mailman/Queue/Runner.py", line 88, in _oneloop msg, msgdata = self._switchboard.dequeue(filebase) File "/usr/local/mailman-2.1//Mailman/Queue/Switchboard.py", line 151, in dequeue if data.has_key('rejection-notice'): AttributeError: 'NoneType' object has no attribute 'has_key' Traceback (most recent call last): File "/usr/local/mailman-2.1/bin/qrunner", line 270, in ? main() File "/usr/local/mailman-2.1/bin/qrunner", line 230, in main qrunner.run() File "/usr/local/mailman-2.1//Mailman/Queue/Runner.py", line 59, in run filecnt = self._oneloop() File "/usr/local/mailman-2.1//Mailman/Queue/Runner.py", line 88, in _oneloop msg, msgdata = self._switchboard.dequeue(filebase) File "/usr/local/mailman-2.1//Mailman/Queue/Switchboard.py", line 151, in dequeue if data.has_key('rejection-notice'): AttributeError: 'NoneType' object has no attribute 'has_key' Traceback (most recent call last): File "/usr/local/mailman-2.1/bin/qrunner", line 270, in ? main() File "/usr/local/mailman-2.1/bin/qrunner", line 230, in main qrunner.run() File "/usr/local/mailman-2.1//Mailman/Queue/Runner.py", line 59, in run filecnt = self._oneloop() File "/usr/local/mailman-2.1//Mailman/Queue/Runner.py", line 88, in _oneloop msg, msgdata = self._switchboard.dequeue(filebase) File "/usr/local/mailman-2.1//Mailman/Queue/Switchboard.py", line 151, in dequeue if data.has_key('rejection-notice'): AttributeError: 'NoneType' object has no attribute 'has_key' Traceback (most recent call last): File "/usr/local/mailman-2.1/bin/qrunner", line 270, in ? main() File "/usr/local/mailman-2.1/bin/qrunner", line 230, in main qrunner.run() File "/usr/local/mailman-2.1//Mailman/Queue/Runner.py", line 59, in run filecnt = self._oneloop() File "/usr/local/mailman-2.1//Mailman/Queue/Runner.py", line 88, in _oneloop msg, msgdata = self._switchboard.dequeue(filebase) File "/usr/local/mailman-2.1//Mailman/Queue/Switchboard.py", line 151, in dequeue if data.has_key('rejection-notice'): AttributeError: 'NoneType' object has no attribute 'has_key' Traceback (most recent call last): File "/usr/local/mailman-2.1/bin/qrunner", line 270, in ? main() File "/usr/local/mailman-2.1/bin/qrunner", line 230, in main qrunner.run() File "/usr/local/mailman-2.1//Mailman/Queue/Runner.py", line 59, in run filecnt = self._oneloop() File "/usr/local/mailman-2.1//Mailman/Queue/Runner.py", line 88, in _oneloop msg, msgdata = self._switchboard.dequeue(filebase) File "/usr/local/mailman-2.1//Mailman/Queue/Switchboard.py", line 151, in dequeue if data.has_key('rejection-notice'): AttributeError: 'NoneType' object has no attribute 'has_key' Traceback (most recent call last): File "/usr/local/mailman-2.1/bin/qrunner", line 270, in ? main() File "/usr/local/mailman-2.1/bin/qrunner", line 230, in main qrunner.run() File "/usr/local/mailman-2.1//Mailman/Queue/Runner.py", line 59, in run filecnt = self._oneloop() File "/usr/local/mailman-2.1//Mailman/Queue/Runner.py", line 88, in _oneloop msg, msgdata = self._switchboard.dequeue(filebase) File "/usr/local/mailman-2.1//Mailman/Queue/Switchboard.py", line 151, in dequeue if data.has_key('rejection-notice'): AttributeError: 'NoneType' object has no attribute 'has_key' Traceback (most recent call last): File "/usr/local/mailman-2.1/bin/qrunner", line 270, in ? main() File "/usr/local/mailman-2.1/bin/qrunner", line 230, in main qrunner.run() File "/usr/local/mailman-2.1//Mailman/Queue/Runner.py", line 59, in run filecnt = self._oneloop() File "/usr/local/mailman-2.1//Mailman/Queue/Runner.py", line 88, in _oneloop msg, msgdata = self._switchboard.dequeue(filebase) File "/usr/local/mailman-2.1//Mailman/Queue/Switchboard.py", line 151, in dequeue if data.has_key('rejection-notice'): AttributeError: 'NoneType' object has no attribute 'has_key' Traceback (most recent call last): File "/usr/local/mailman-2.1/bin/qrunner", line 270, in ? main() File "/usr/local/mailman-2.1/bin/qrunner", line 230, in main qrunner.run() File "/usr/local/mailman-2.1//Mailman/Queue/Runner.py", line 59, in run filecnt = self._oneloop() File "/usr/local/mailman-2.1//Mailman/Queue/Runner.py", line 88, in _oneloop msg, msgdata = self._switchboard.dequeue(filebase) File "/usr/local/mailman-2.1//Mailman/Queue/Switchboard.py", line 151, in dequeue if data.has_key('rejection-notice'): AttributeError: 'NoneType' object has no attribute 'has_key' Traceback (most recent call last): File "/usr/local/mailman-2.1/bin/qrunner", line 270, in ? main() File "/usr/local/mailman-2.1/bin/qrunner", line 230, in main qrunner.run() File "/usr/local/mailman-2.1//Mailman/Queue/Runner.py", line 59, in run filecnt = self._oneloop() File "/usr/local/mailman-2.1//Mailman/Queue/Runner.py", line 88, in _oneloop msg, msgdata = self._switchboard.dequeue(filebase) File "/usr/local/mailman-2.1//Mailman/Queue/Switchboard.py", line 151, in dequeue if data.has_key('rejection-notice'): AttributeError: 'NoneType' object has no attribute 'has_key'

1 0

list_members output
by Colin Mackinlay 20 Mar '03

20 Mar '03

Hi, Just used the FAQ script to harvest members for umbrella lists - worked perfectly. One minor improvement would be useful: if the list_members command also outputs the name as well as email address in a format that sync_members could cope with then the membership listing of the umbrella list would be much easier to read. i.e. couldn't it output: <name(a)domain.com> Name <moniker(a)company.org> Label ...etc as this format is acceptable on the mass subscription page. -- Colin Mackinlay

1 0

[Mailman-Developers] Paid membership system - feedback? - warning: long
by Coen de Groot 20 Mar '03

20 Mar '03

Hi there, I will be changing a Mailman discussion list into a paid discussion list. As far as I can tell there isn't anything readily available for this So, unless anyone tells me otherwise, I will have to develop something myself I will be quite happy to make the end result available to anyone else who might find it useful Whilst I have a lot of programming experience, this will be my first Python project, so wish me luck :-) Oh, and I've got about a week or so to get a beta version, so not too much pressure Initially I will be importing the payments from a file which I maintain using different software. At a later stage everything will have to be integrated and automated In case anyone is interested, I have included some documentation of my plans below. Feel free to give me your feedback, especially with ideas on what will be impossible or what can be done better differently. I assume this is the right place for this email (size and subject). If not please let me know, just be gentle :-) See below for my documentation Coen Introduction This is the functional specification for the first phase of the Mailman membership system During phase 1 part of the process will still be done manually and/or by other systems. During a later phase all parts will be integrated and automated The following functions will be part of the system: a.. Maintaining a table of free and paid membership periods for each list member b.. Email renewal reminders c.. Blocking access past the membership period The following change(s) will be required to the existing Mailman system, to facilitate the new functionality: a.. When someone unsubscribes, the details will be stored in a new list of 'previously subscribed' members b.. When someone resubscribes, any periods will be copied from the 'previously subscribed' list c.. When someone resubscribes who is on the 'previously subscribed' list, and there isn't any valid period, they will be treated the same as if they are 'expired' (see below) Area 1 - Membership periods There are three types of membership period: 1.. Trial period 2.. Paid period 3.. Free period Membership periods can be set up as follows: 1.. Batch trial period set up 2.. Batch paid period set up 3.. Batch free period set up 4.. Automatic trial period set up, as a result of subscribing Batch trial period set up A process will read a structured file which lists recent sign ups. For each list member this contains the following information: 1.. Email address 2.. Date of sign up This file will be created by hand, from the sign-up log. Only entries after 7/2/03 will be used. Members who are known to have been a member before 7/2/03 will also be excluded Step 1 - File import The file will be read and each entry will be recorded against the list of members. A period tuple will be added with the period type ('trial'), period start and period end. The period end will be two months minus 1 day after the period start In the case of duplicate entries (against the same email address), the second entry will be ignored and an error message will be generated If the member doesn't exist, then s/he has probably unsubscribed since, so generate an error message and ignore Step 2 - Default setting All other members, those who don't yet have a trial membership period will be given a trial period which ends 6th April 2003. A period tuple will be added with the type period ('trial'), period start (empty) and period end (6/4/03) Log A log will be created which lists all period which were created, showing the email address, start date, end date, period type Batch paid period set up A process will read a structured file which lists payments. For each entry this contains the following information: 1.. List email address 2.. Period in months (typically 12, but might be 13 for anyone who ended up paying a little extra) This file will be created by hand For each member which is listed, a period tuple will be added with the period type ('paid'), start date (the day after the end of the trial period), end date (the specified number of months after the start date, minus 1 day) Log A log will be created which lists all period which were created, showing the email address, start date, end date, period type Batch free period set up A process will read a structured file which lists free periods. For each entry this contains the following information: 1.. List email address 2.. Period in months, or 0 for unlimited 3.. Type of free period ('benefit' or 'gift') Log A log will be created which lists all period which were created, showing the email address, start date, end date, period type Automatic trial set up, after subscribing When someone subscribes who hasn't subscribed before (i.e. there isn't already an entry for this email address), the system automatically gives them a 2 month trial period. This will be done as part of the normal subscribe function, for subscriptions via the website and via email Area 2 - Email renewal reminders Note: the standard welcome message will be changed to explain the trial period The following emails may be sent out by the system: 1.. 1 month after start of trial membership, if not yet paid, encouragement to pay, plus info on how to get the most from the list. Don't send if more than 3 days overdue. The wording of the email will allow for slightly late sending 2.. 2 weeks before end of trial membership, if not yet paid, reminder of end of trial period. Don't send if more than 2 days overdue. The wording of the email will allow for slightly late sending 3.. 3 days before end of trial membership, if not yet paid, final warning. Don't send if more than 1 day overdue. The wording of the email will allow for slightly late sending A daily process will be run which checks for messages that need to be sent Sent messages are recorded by adding a tuple to the list member, recording date and type of message). This is to prevent messages being sent twice Area 3 - Blocking access A daily process will check for any members whose membership has just expired. As far as the system is concerned, any member who does not have a membership period which covers today is 'expired' Any member which has become 'expired' today will be sent an email with notification of removal and information about any free options. And an 'expired' flag will be set No messages will be sent to 'expired' members: 1. The member will stop receiving direct list emails 2. The member will stop receiving digest emails 3. The member will stop receiving monthly password reminders 4. The member will stop receiving admin messages No email requests will be processed from 'expired' members 5. The member will not be able to send messages to the list, from the main email address and from any additional posting addresses 6. The member will not be able to change options by email 7. The member will not be able to subscribe again by email 'Expired' members will not be able to make any changes via the website interface: 8. The member will not be able to access the management screen 9. The member will not be able to subscribe again (at least not with any known email address) via the website No more direct list emails When building the distribution list for direct emails, 'expired' members will be excluded No more digest list emails When building the distribution list for digest emails, 'expired' members will be excluded No more monthly password reminder emails 'Expired' members won't be send monthly password reminder emails No more admin emails The list has a facility for 'direct' emails, which go directly to normal members and to digest members. When building the distribution list for 'direct' emails, 'expired' members will be excluded No more sending emails to the list When an email gets sent to the list from an 'expired' member, the list will discard the message and return a friendly reply to the member, explaining how his/her membership has expired, at what date, and what they can do about this No access to management screen When an 'expired' member goes to the management screen, they will see a very simple screen which explains the expired status and what they can do about it Can't change options via email When an 'expired' member tries to change options via email, they will receive a friendly reply which explains that their membership is expired, at what date, and what they can do about this Can't resubscribe via the website When an 'expired' member tries to resubscribe via the website they will see a screen which explains the expired status and what they can do about it Can't resubscribe via email When an 'expired' member tries to resubscribe via email they will receive a friendly reply which explains that their membership is expired, at what date, and what they can do about this

1 0

trailing garbage??
by Fil 20 Mar '03

20 Mar '03

Hi, I've received this for the first time (almost uptodate CVS + email2.5b1 installed) Subject: Cron <mailman@miel> /usr/local/bin/python -S /usr/local/mailman/cron/senddigests Warning: Trailing garbage Warning: Trailing garbage -- Fil

1 0

odd problem: since MM 2.1 upgrade all links to public list archives are broken
by Chris Dagdigian 19 Mar '03

19 Mar '03

Hi mailman developers, First off; thanks for a wonderful package. We've been using Mailman for years to keep thousands of open source bioinformatics developers and users in touch with each other. Now I've got a problem that seems really odd. I'm a little bit afraid that it may have been caused by some old cruft left over in our mailman dir which has been subjected to many mailman upgrade installs over the years. The SMTP/mailman box is a Dec Alpha workstation running Redhat Linux 6.x with python 2.3. The problem: Since upgrading to Mailman 2.1 (problem persists with MM 2.1.1) all of our mailman list pages that point to the public list archives are broken. The URL is presented as "<server>/pipermail/" instead of "<server>/pipermail/<mm-listname>/" This prevents our web vistors from getting to our list archives as they are presented with a "you are not allowed to access /pipermail/" error each time. We have not changed our templates at all. In fact I blew away the templates directory right before upgrading to 2.1.1. I've verified in the template HTML that the "MM-List-Name" etc. data seems to be in the right place. Here are a couple of example pages with broken links to the public list archives: http://bioperl.org/mailman/listinfo/bioperl-l http://open-bio.org/mailman/listinfo/moby-l The list name is obviously getting substituted into other parts of the page. It's just not getting appended to the end of "/pipermail/" in the URL for the public list archive. Private archives work fine. I've taken one list and converted the archives from public->private and the resulting "listinfo" page then produces a perfect link to the private archive. Any hints? Has anyone seen this before? Regards, Chris -- Chris Dagdigian, <dag(a)sonsorol.org> 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

2 2

How to use real virtual hosting?
by Remco van den Berg 19 Mar '03

19 Mar '03

Dear developpers, I'm working as a volunteer for an non-profit ISP-like organisation named Digitale Stad Eindhoven (Digital City Eindhoven) in de Netherlands. (DSE http://www.dse.nl/) We provide web service to all kind of organisations in and around Eindhoven. Many sports clubs for example do have their website on our DSE server. The sports clubs do have their own virtual domain on our server. For exaple: volleyballclub.dse.nl and soccerclub.dse.nl Every club also have their own account name. Let's asume we are dealing with the unix accounts "volley" and "soccer" in this example. So far the intro... now my problem/questions... I'm looking at installing mailman on our server with the purpose to give the mailing list service to our clubs. But, as far as I understand mailman for now, mailman isn't really programmed in such a way that it can deal with virtual hosts. Only the web interface is aware of virtual hosting. Am I right? When installing a mailing list for a soccerclub we cannot run the same list on a different virtual domain for the volleyball club. True? We want for example these (different!) lists: team1(a)volleybalclub.dse.nl and team1(a)soccerclub.dse.nl The aliases needed for these mailing lists are stored in the same alias file and so they cannot exist together. OK, I think everybody understands our problem now. Main questions are: Is there a work-around to use mailmain in this environment? Can we store lists-data and archives in the home directories of the accounts linked to the virtual domains? We don't want to compile and install mailman for every club, so is it possible to only compile and install the mail wrapper program for every account? And then install a private mm_cfg.py file for every account which then points to the private data and archives directories? Or, can we include an extra command-line-parameter to a global mail wrapper program which holds the account name? Such that this parameter will tell the other scripts (post admin bounces etc.) to look in the home directory of the account. Can we work around the fact that all mailing list aliases are also stored in the non-virtual alias file? So that the aliases in the virtual alias file directly point to the private mail wrapper of the clubs? etc. etc. Any help is appreciated. Thanks for some answers, Regards, Remco van den Berg (sysadmin DSE) -- ---------------------------------------------------------------------------- Remco van den Berg <Remco.vandenBerg(a)dse.nl> Admin DSE http://www.dse.nl/rvdberg/ GSX750F http://www.dse.nl/ ----------------------------------------------------------------------------

3 2