From pfaff@edge.cis.mcmaster.ca Thu Dec 2 16:26:24 1999 From: pfaff@edge.cis.mcmaster.ca (Todd Pfaff) Date: Thu, 2 Dec 1999 11:26:24 -0500 (EST) Subject: [Mailman-Developers] LogMsg problem Message-ID: I'm using mailman 1.1. One of our lists consistently generates the following python traceback in the mailman error log whenever a message is posted to the list. Dec 01 13:22:45 1999 post: Traceback (innermost last): post: File "/usr/local/mailman/scripts/mailowner", line 45, in ? post: if not mlist.bounce_processing or not mlist.ScanMessage(msg): post: File "/usr/local/mailman/Mailman/Bouncer.py", line 449, in ScanMessage post: self.RegisterBounce(who, msg) post: File "/usr/local/mailman/Mailman/Bouncer.py", line 138, in RegisterBounce post: self.LogMsg("bounce", report + "exceeded limits") post: File "/usr/local/mailman/Mailman/MailList.py", line 834, in LogMsg post: logf.write(msg % args + '\n') post: TypeError : not enough arguments for format string I've had a look at the call to LogMsg() in MailList.py from RegisterBounce() in Bouncer.py, so I sort of where the error is happening. As far as I can tell, there must be some instances where LogMsg is being called with a "msg" argument that contains % variable substitutions that have not yet been satisfied, but with an empty or insufficient "args" tuple. So, when LogMsg calls logf.write(msg % args + '\n'), the % substitution fails. It seems that, in general, the use of LogMsg is inconsistent. In some cases, a variable length args tuple is passed to LogMsg and the string formatting is done within LogMsg, but in many other cases any string formatting is done before the call to LogMsg and LogMsg is called without an args tuple. It's entirely possible that something will call LogMsg with a "msg" argument that contains a valid % substitution string even though they did not intend for a % substitution to happen. I think this is what may be happening in my case - the RegisterBounce() function builds the "msg" string from other variable strings and one of these strings may contain a % substitution string. This msg string is then passed to LogMsg but without an args tuple to satisfy the % substitution. I'm no Python expert - I just started learning it a few weeks ago - but I'm trying to think of ways to debug this, or handle the situation more gracefully. I've been poking through the Python books I have and looking at the exception handling stuff. I've come up with the following simple idea for handling this in LogMsg(). Any opinions about whether this is a good idea, whether it will work, or whether there is a better way to approach this problem? try: logf.write(msg % args + '\n') except: logf.write(msg + '\n') -- Todd Pfaff \ Email: pfaff@mcmaster.ca Computing and Information Services \ Voice: (905) 525-9140 x22920 ABB 132 \ FAX: (905) 528-3773 McMaster University \ Hamilton, Ontario, Canada L8S 4M1 \ From pfaff@edge.cis.mcmaster.ca Thu Dec 2 16:57:21 1999 From: pfaff@edge.cis.mcmaster.ca (Todd Pfaff) Date: Thu, 2 Dec 1999 11:57:21 -0500 (EST) Subject: [Mailman-Developers] Re: [Mailman-Users] LogMsg problem In-Reply-To: Message-ID: Sure enough! This was exactly the problem! After applying the 'try: except:' fix I suggested below I no longer get the error traceback from LogMsg and I see the following in the bounce log. It was the email address string containing % characters in LogMsg called from RegisterBounce that was causing the failure. Dec 02 11:47:26 1999 cdn-nucl-l: DXS9%OPS%DCPP@bangate.pge.com - exceeded limits Dec 02 11:47:26 1999 cdn-nucl-l: disabled dxs9%ops%dcpp@bangate.pge.com Dec 02 11:47:27 1999 cdn-nucl-l: gonuke@bigfoot.com - first n Thu, 2 Dec 1999, Todd Pfaff wrote: > I'm using mailman 1.1. One of our lists consistently generates the > following python traceback in the mailman error log whenever a message is > posted to the list. > > Dec 01 13:22:45 1999 post: Traceback (innermost last): > post: File "/usr/local/mailman/scripts/mailowner", line 45, in ? > post: if not mlist.bounce_processing or not mlist.ScanMessage(msg): > post: File "/usr/local/mailman/Mailman/Bouncer.py", line 449, in ScanMessage > post: self.RegisterBounce(who, msg) > post: File "/usr/local/mailman/Mailman/Bouncer.py", line 138, in RegisterBounce > post: self.LogMsg("bounce", report + "exceeded limits") > post: File "/usr/local/mailman/Mailman/MailList.py", line 834, in LogMsg > post: logf.write(msg % args + '\n') > post: TypeError : not enough arguments for format string > > > I've had a look at the call to LogMsg() in MailList.py from > RegisterBounce() in Bouncer.py, so I sort of where the error is happening. > As far as I can tell, there must be some instances where LogMsg is being > called with a "msg" argument that contains % variable substitutions that > have not yet been satisfied, but with an empty or insufficient "args" > tuple. So, when LogMsg calls logf.write(msg % args + '\n'), the % > substitution fails. > > It seems that, in general, the use of LogMsg is inconsistent. In some > cases, a variable length args tuple is passed to LogMsg and the string > formatting is done within LogMsg, but in many other cases any string > formatting is done before the call to LogMsg and LogMsg is called without > an args tuple. > > It's entirely possible that something will call LogMsg with a "msg" > argument that contains a valid % substitution string even though they did > not intend for a % substitution to happen. I think this is what may be > happening in my case - the RegisterBounce() function builds the "msg" > string from other variable strings and one of these strings may contain a > % substitution string. This msg string is then passed to LogMsg but > without an args tuple to satisfy the % substitution. > > I'm no Python expert - I just started learning it a few weeks ago - but > I'm trying to think of ways to debug this, or handle the situation more > gracefully. I've been poking through the Python books I have and looking > at the exception handling stuff. I've come up with the following simple > idea for handling this in LogMsg(). Any opinions about whether this is a > good idea, whether it will work, or whether there is a better way to > approach this problem? > > try: > logf.write(msg % args + '\n') > except: > logf.write(msg + '\n') > > -- > Todd Pfaff \ Email: pfaff@mcmaster.ca > Computing and Information Services \ Voice: (905) 525-9140 x22920 > ABB 132 \ FAX: (905) 528-3773 > McMaster University \ > Hamilton, Ontario, Canada L8S 4M1 \ > > > ------------------------------------------------------ > Mailman-Users maillist - Mailman-Users@python.org > http://www.python.org/mailman/listinfo/mailman-users > -- Todd Pfaff \ Email: pfaff@mcmaster.ca Computing and Information Services \ Voice: (905) 525-9140 x22920 ABB 132 \ FAX: (905) 528-3773 McMaster University \ Hamilton, Ontario, Canada L8S 4M1 \ From wheakory@isu.edu Thu Dec 2 20:18:24 1999 From: wheakory@isu.edu (Kory Wheatley) Date: Thu, 02 Dec 1999 13:18:24 -0700 Subject: [Mailman-Developers] Run_queue Process Message-ID: <3846D40F.C9253543@isu.edu> Where in the directory structure of mailman does queued mail get placed for the cron job "run_queue" to process if the message failed to deliver the first time or the host machine was down at the time, because there are times where I don't want these messaged to be resent. I would rather deleted them then have run_queue send them out, because I had one list that had subscribed the wrong email address for 2000 users to the list and it kept trying to resend them which caused performance problems do I need to adjust sendmail to handle a situation like this? I would like to basically know how to delete the mail queue messages sometimes if I know there is going to be a lot of queued mail that I don't want delivered. -- Kory Wheatley Office Phone 236-3874 Computing & Communication Academic Computing Analyst sr. Everything you do must point to him. From claw@kanga.nu Thu Dec 2 20:32:24 1999 From: claw@kanga.nu (claw@kanga.nu) Date: Thu, 02 Dec 1999 12:32:24 -0800 Subject: [Mailman-Developers] Run_queue Process In-Reply-To: Message from Kory Wheatley of "Thu, 02 Dec 1999 13:18:24 MST." <3846D40F.C9253543@isu.edu> Message-ID: On Thu, 02 Dec 1999 13:18:24 -0700 Kory Wheatley wrote: > I would like to basically know how to delete the mail queue > messages sometimes if I know there is going to be a lot of queued > mail that I don't want delivered. IIRC (can't check now) it is stored inside the config.db for the list. Removing that mail is a question of unpickling the DB and removing the approriate records. <> -- J C Lawrence Home: claw@kanga.nu ----------(*) Other: coder@kanga.nu --=| A man is as sane as he is dangerous to his environment |=-- From bwarsaw@cnri.reston.va.us (Barry A. Warsaw) Fri Dec 3 05:20:01 1999 From: bwarsaw@cnri.reston.va.us (Barry A. Warsaw) (Barry A. Warsaw) Date: Fri, 3 Dec 1999 00:20:01 -0500 (EST) Subject: [Mailman-Developers] Re: [Mailman-Users] LogMsg problem References: Message-ID: <14407.21249.279263.173837@anthem.cnri.reston.va.us> >>>>> "TP" == Todd Pfaff writes: TP> It seems that, in general, the use of LogMsg is inconsistent. You're right about that. It would be a good thing to clean up the use of LogMsg. I usually do the substitution before passing it to LogMsg, but some of the older code does it the other way. TP> Any opinions about whether this is TP> a good idea, whether it will work, or whether there is a TP> better way to approach this problem? | try: | logf.write(msg % args + '\n') | except: | logf.write(msg + '\n') Just a point of Python style. It's almost never appropriate to use a "bare" except like this because it can mask unexpected exceptions. In this case using "except TypeError" would do the trick. This is probably okay as a stopgap, but it would be better to make the use of LogMsg more consistent. -Barry From bwarsaw@cnri.reston.va.us (Barry A. Warsaw) Fri Dec 3 05:44:32 1999 From: bwarsaw@cnri.reston.va.us (Barry A. Warsaw) (Barry A. Warsaw) Date: Fri, 3 Dec 1999 00:44:32 -0500 (EST) Subject: [Mailman-Developers] Run_queue Process References: <3846D40F.C9253543@isu.edu> Message-ID: <14407.22720.10243.882151@anthem.cnri.reston.va.us> >>>>> "claw" == writes: >> I would like to basically know how to delete the mail queue >> messages sometimes if I know there is going to be a lot of >> queued mail that I don't want delivered. claw> IIRC (can't check now) it is stored inside the config.db for claw> the list. Removing that mail is a question of unpickling claw> the DB and removing the approriate records. Actually, I don't think so. I think those queued messages are just gleaned from the file system. claw> <> And in fact, all this has changed in my current codebase. There's no queueing going on. I have two delivery modules, one that pipes to the command line interface of sendmail, the other which does direct smtp delivery to the local smtpd. This latter only handles error codes >= 500 (permanent errors), in which case it'll register a bounce to that addr just as if a bounce message was received. However, at least with Postfix, it appears that you never get error reports for non-local addrs. The dialog with the local smtpd seems nearly asynchronous, which is actually a good thing. If Postfix can't deliver the message, it'll generate a bounce message for it (more on this in another follow up). I believe this all works differently if the MTA supports DSN (delivery status notification), which sendmail does, but postfix does not. In that case, if you enable DSN, delivery becomes synchronous, and you do end up getting error codes back for failures. The problem with the synchronous deliveries is that you can't keep list object locked while that happens. I'm beginning to think it's best not to do DSN and just improve the bounce detection, or do the VERP-like approach discussed earlier. I think Dragon has said that he's got a better bulk mailer implementation that he's been using for a while. I think he's talked about porting it to the new delivery pipeline code, which would be cool to have as an alternative approach. -Barry From pfaff@edge.cis.mcmaster.ca Fri Dec 3 15:52:47 1999 From: pfaff@edge.cis.mcmaster.ca (Todd Pfaff) Date: Fri, 3 Dec 1999 10:52:47 -0500 (EST) Subject: [Mailman-Developers] Re: [Mailman-Users] LogMsg problem In-Reply-To: <14407.21249.279263.173837@anthem.cnri.reston.va.us> Message-ID: On Fri, 3 Dec 1999, Barry A. Warsaw wrote: > TP> It seems that, in general, the use of LogMsg is inconsistent. > > You're right about that. It would be a good thing to clean up the use > of LogMsg. I usually do the substitution before passing it to LogMsg, > but some of the older code does it the other way. > > TP> Any opinions about whether this is > TP> a good idea, whether it will work, or whether there is a > TP> better way to approach this problem? > > | try: > | logf.write(msg % args + '\n') > | except: > | logf.write(msg + '\n') > > Just a point of Python style. It's almost never appropriate to use a > "bare" except like this because it can mask unexpected exceptions. In > this case using "except TypeError" would do the trick. ok, thanks for the tip. > This is probably okay as a stopgap, but it would be better to make the > use of LogMsg more consistent. it wouldn't be a big job. there are only about 50 occurrences of LogMsg calls in all files under the Mailman python directory, and of these, only about 20 seem to have '%' substitution characters in the msg argument: cd ~mailman/Mailman grep LogMsg * | grep '%' | wc the ones that pass an arg tuple would simply have to be changed so that the ',' between the msg and args arguments is a '%' to do the substitutions before the call. then, remove the '%' substitution in LogMsg. -- Todd Pfaff \ Email: pfaff@mcmaster.ca Computing and Information Services \ Voice: (905) 525-9140 x22920 ABB 132 \ FAX: (905) 528-3773 McMaster University \ Hamilton, Ontario, Canada L8S 4M1 \ From randhir@kalpadrum.com Sat Dec 4 08:53:53 1999 From: randhir@kalpadrum.com (Randhir Shinde) Date: Sat, 4 Dec 1999 14:23:53 +0530 Subject: [Mailman-Developers] I want to transfer a mail to a program Message-ID: <01BF3E63.664EFC00@randhir> I am writing a Script. Now what I want to do is when I send a mail to a = list member in a mailman, I want to direct the mail to a program which = can be a script or a servlet or anything that can execute on the server. = The task of this script shall be to save the received mail to a file.=20 Can some one tell me how this can be done Randhir From ricardo@miss-janet.com Sat Dec 4 22:54:39 1999 From: ricardo@miss-janet.com (Ricardo Kustner) Date: Sat, 4 Dec 1999 23:54:39 +0100 Subject: [Mailman-Developers] bulkmailing & admin interface Message-ID: <19991204235439.A1308@miss-janet.com> Hi, the MM feature list says: "Direct SMTP delivery of messages, including integrated fast bulk mailing." i guess this is build into mailman to speed up mail delivery... but when mail is send out during approving (many) held back messages through the web admin interface, i wonder if it's still effective to use this bulk mailing technique? when all messages need improval before being send out, it's no use to have mailman try his best to deliver the mail as quickly as possible anyway... I don't know much about the way MM delivers mail, but some big annoyances i've had with using MM are that when approving several messages from the admin interface : (a) the cgi process(es) takes *too* long to finnish (causing timeouts sometimes) and (b) they cause a huge load on the system. Would it be possible to be able to choose for a "relaxed" way of delevering mail in certain situations? i'd rather have the messages being delivered with a small delay then MM trying hard to be as quick as possible with delivery... hoping for at least one reaction to this email, :) Ricardo. -- From richarde@eskom.co.za Mon Dec 6 06:52:10 1999 From: richarde@eskom.co.za (Richard Ellerbrock) Date: Mon, 06 Dec 1999 08:52:10 +0200 Subject: [Mailman-Developers] I want to transfer a mail to a program Message-ID: >I am writing a Script. Now what I want to do is when I send a mail to a = list=20 >member in a mailman, I want to direct the mail to a program which can be = a=20 >script or a servlet or anything that can execute on the server. The task = of=20 >this script shall be to save the received mail to a file.=20 > >Can some one tell me how this can be done You probably want to use procmail as a front to mailman. Modify your alias = file and run the message through procmail first, and then pass it to = mailman. I did a similar trick to block external e-mails to mailman to = prevent non-employees being able to subscribe to our internal lists. = Mailman cannot do this. Here is the method: Modify /etc/aliases: www-request: "|/usr/bin/procmail -m LIST=3D'www' /etc/mail/procm= ailrc.lists" This will call procmail instead of mailman. Mailman is called inside the = procmail script: :0 # pass along all mail for eskom * ^From:.*eskom.co.za | /home/mailman/mail/wrapper mailcmd $LIST :0 # reply to all mail not from eskom * !^FROM_DAEMON * !^X-Loop: owner-${LIST}@lists.eskom.co.za { :0 hc | (formail -r -A"Precedence: bulk" \ -A"X-Loop: owner-${LIST}@lists.eskom.co.za" ; \ echo "\ This is an ESKOM internal mailing list to which you may not \ subscribe. If you have any queries, contact owner-${LIST}@lists.eskom.co.za= \ for further information.") | \ $SENDMAIL -t -f owner-${LIST}@lists.eskom.co.za } :0 # drop all other mail /dev/null Using this method and the procmailex manpage, you should be able to do = what you want. -- Richard Ellerbrock richarde@eskom.co.za From bwarsaw@CNRI.Reston.VA.US (Barry A. Warsaw) Mon Dec 6 02:58:08 1999 From: bwarsaw@CNRI.Reston.VA.US (Barry A. Warsaw) (Barry A. Warsaw) Date: Sun, 5 Dec 1999 21:58:08 -0500 (EST) Subject: [Mailman-Developers] bulkmailing & admin interface References: <19991204235439.A1308@miss-janet.com> Message-ID: <14411.9792.611960.485273@anthem.cnri.reston.va.us> >>>>> "RK" == Ricardo Kustner writes: RK> I don't know much about the way MM delivers mail, RK> but some big annoyances i've had with using MM are that when RK> approving several messages from the admin interface : (a) the RK> cgi process(es) takes *too* long to finnish (causing timeouts RK> sometimes) and (b) they cause a huge load on the system. RK> Would it be possible to be able to choose for a "relaxed" way RK> of delevering mail in certain situations? i'd rather have the RK> messages being delivered with a small delay then MM trying RK> hard to be as quick as possible with delivery... RK> hoping for at least one reaction to this email, :) Here's one, hopefully the one you're looking for! :) All this stuff has changed in the current codebase, available via CVS. The old bulkmailer stuff is gone and Mailman now has two ways to hand a message off to your MTA: either by calling sendmail (or a sendmail compatible program) via the command line, or talking asynchronously (no-DSN) via SMTP. All these means that the handoff of messages from Mailman to your MTA happens very quickly. Dragon has mentioned that he has a robust bulk-mailer which may get ported to the new codebase and added back in. The neat thing is that with the current architecture, a site could choose any one of these delivery modules, as appropriate for their system (or easily implement their own). -Barry From julian7@kva.hu Mon Dec 6 17:03:05 1999 From: julian7@kva.hu (Balazs Nagy) Date: Mon, 6 Dec 1999 18:03:05 +0100 (CET) Subject: [Mailman-Developers] 8-bit input in administrator menu Message-ID: This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --1825891041-2098212404-944499785=:16442 Content-Type: TEXT/PLAIN; charset=US-ASCII Hi, I did a little digging about entering text with accents. It's a bit curious that one can type accents in textarea but to textbox cannot. In the latter case you can see an escaped print of your input. In the end I came to htmlformat.py's InputObj. At this point I have a humble question: who put `-s around value? After a s/`value`/value/ in line #368, almost everything works fine, because this brings up a problem about quoting. Of course, the patch is here. -- Regards: Kevin (Balazs) --1825891041-2098212404-944499785=:16442 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="mailman-8bit.patch" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Content-Disposition: attachment; filename="mailman-8bit.patch" ZGlmZiAtcnVOIG1haWxtYW4ub3JpZy9NYWlsbWFuL2h0bWxmb3JtYXQucHkg bWFpbG1hbi9NYWlsbWFuL2h0bWxmb3JtYXQucHkNCi0tLSBtYWlsbWFuLm9y aWcvTWFpbG1hbi9odG1sZm9ybWF0LnB5CU1vbiBKdW4gIDcgMTU6MjM6MDEg MTk5OQ0KKysrIG1haWxtYW4vTWFpbG1hbi9odG1sZm9ybWF0LnB5CU1vbiBE ZWMgIDYgMTY6NTk6MDAgMTk5OQ0KQEAgLTM2NSwxNiArMzY1LDE2IEBADQog ICAgIGRlZiBfX2luaXRfXyhzZWxmLCBuYW1lLCB0eSwgdmFsdWUsIGNoZWNr ZWQsICoqa3dzKToNCiAJc2VsZi5uYW1lID0gbmFtZQ0KIAlzZWxmLnR5cGUg PSB0eQ0KLQlzZWxmLnZhbHVlID0gYHZhbHVlYA0KKwlzZWxmLnZhbHVlID0g dmFsdWUNCiAJc2VsZi5jaGVja2VkID0gY2hlY2tlZA0KIAlzZWxmLmt3cyA9 IGt3cw0KIA0KICAgICBkZWYgRm9ybWF0KHNlbGYsIGluZGVudD0wKToNCi0J b3V0cHV0ID0gJzxJTlBVVCBuYW1lPSVzIHR5cGU9JXMgdmFsdWU9JXMnICUg KHNlbGYubmFtZSwgc2VsZi50eXBlLA0KKwlvdXRwdXQgPSAnPElOUFVUIG5h bWU9IiVzIiB0eXBlPSIlcyIgdmFsdWU9IiVzIicgJSAoc2VsZi5uYW1lLCBz ZWxmLnR5cGUsDQogCQkJCQkJICAgICAgc2VsZi52YWx1ZSkNCiAJDQogCWZv ciAoa2V5LCB2YWwpIGluIHNlbGYua3dzLml0ZW1zKCk6DQotCSAgICBvdXRw dXQgPSAnJXMgJXM9JXMnICUgKG91dHB1dCwga2V5LCB2YWwpDQorCSAgICBv dXRwdXQgPSAnJXMgIiVzIj0iJXMiJyAlIChvdXRwdXQsIGtleSwgdmFsKQ0K IA0KIAlpZiBzZWxmLmNoZWNrZWQ6DQogCSAgICBvdXRwdXQgPSBvdXRwdXQg KyAnIENIRUNLRUQnDQo= --1825891041-2098212404-944499785=:16442-- From jarrell@vt.edu Mon Dec 6 23:56:34 1999 From: jarrell@vt.edu (Ron Jarrell) Date: Mon, 06 Dec 1999 18:56:34 -0500 Subject: [Mailman-Developers] 1.1 cvs problem Message-ID: <4.2.0.58.19991206185531.00b8d1a0@vtserf.cc.vt.edu> You can't build a 1.1 release from the cvs archive; at the very least the src dir wasn't tagged with the Release_1_1 tag, and thus doesn't checkout... From ricardo@miss-janet.com Wed Dec 8 21:53:16 1999 From: ricardo@miss-janet.com (Ricardo Kustner) Date: Wed, 8 Dec 1999 22:53:16 +0100 Subject: [Mailman-Developers] bulkmailing & admin interface In-Reply-To: <14411.9792.611960.485273@anthem.cnri.reston.va.us>; from bwarsaw@CNRI.Reston.VA.US on Sun, Dec 05, 1999 at 09:58:08PM -0500 References: <19991204235439.A1308@miss-janet.com> <14411.9792.611960.485273@anthem.cnri.reston.va.us> Message-ID: <19991208225316.A11025@miss-janet.com> Hi, On Sun, Dec 05, 1999 at 09:58:08PM -0500, Barry A. Warsaw wrote: > RK> Would it be possible to be able to choose for a "relaxed" way > RK> of delevering mail in certain situations? i'd rather have the > RK> messages being delivered with a small delay then MM trying > RK> hard to be as quick as possible with delivery... > RK> hoping for at least one reaction to this email, :) > Here's one, hopefully the one you're looking for! :) yes it is... thanks! :) > All this stuff has changed in the current codebase, available via CVS. > The old bulkmailer stuff is gone and Mailman now has two ways to hand > a message off to your MTA: either by calling sendmail (or a sendmail > compatible program) via the command line, or talking asynchronously > (no-DSN) via SMTP. All these means that the handoff of messages from > Mailman to your MTA happens very quickly. ah very nice ... i think i'm going to test out the cvs version on my pc at home... do all the python lists use this codebase too? > ported to the new codebase and added back in. The neat thing is that > with the current architecture, a site could choose any one of these > delivery modules, as appropriate for their system (or easily implement > their own). ah even better ! btw i noticed some speed improvement when i switched from exim to postfix... I think i've tried out almost every possible MTA, but it seems postfix does it's best on a not-so-powerfull server with mailman. Ricardo. -- From bwarsaw@python.org Thu Dec 9 05:07:22 1999 From: bwarsaw@python.org (Barry A. Warsaw) Date: Thu, 9 Dec 1999 00:07:22 -0500 (EST) Subject: [Mailman-Developers] bulkmailing & admin interface References: <19991204235439.A1308@miss-janet.com> <14411.9792.611960.485273@anthem.cnri.reston.va.us> <19991208225316.A11025@miss-janet.com> Message-ID: <14415.14602.231300.438264@anthem.cnri.reston.va.us> >>>>> "RK" == Ricardo Kustner writes: RK> ah very nice ... i think i'm going to test out the cvs version RK> on my pc at home... do all the python lists use this codebase RK> too? Yes! -Barry From ddickey@wamnet.com Thu Dec 9 15:12:42 1999 From: ddickey@wamnet.com (Dan A. Dickey) Date: Thu, 09 Dec 1999 09:12:42 -0600 Subject: [Mailman-Developers] Problem with moving from /home/mailman -> /usr/mailman Message-ID: <384FC6EA.A597F178@wamnet.com> I was using mailman 1.0 on an "old" machine, and it was installed to /home/mailman - the default. We tried moving the lists to a new machine, but the admin wanted it based somewhere other than /home/mailman, so we chose /usr/mailman. I retrieved version 1.1, and installed it. The 'make update' failed. Basically, I believe this is because CheckVersion() thought the config.db that we brought over from the old machine was up to date, and so used it as is. I think it contains references to /home/mailman, and I do not know how to change them to /usr/mailman. For the time being, we are getting by because we have a symlink from /home/mailman -> /usr/mailman; but I want to do away with this scenario. Can one/more of the experts out there tell me how to correct the above problems? Can this be addressed in a new version of mailman a bit better? Or can someone tell me where to RTFM? I'm willing to try code here if someone wants to take a stab at fixing this. Thanks! -Dan From ricardo@miss-janet.com Fri Dec 10 05:57:07 1999 From: ricardo@miss-janet.com (Ricardo Kustner) Date: Fri, 10 Dec 1999 06:57:07 +0100 Subject: [Mailman-Developers] latest cvs trouble Message-ID: <19991210065707.A23888@miss-janet.com> Hi, since 1.1/postfix seems to be duplicating some posts a bit too often, i tried to install the latest cvs of MM... first of all, there were some pending posts in config.db, but the new installation doesn't recognize them (i guess this changed in 1.2) so any administrative requests get lost. When I tried posting to the list, i got an error: post: File "/usr/local/mailman/scripts/post", line 83, in ? post: main() post: File "/usr/local/mailman/scripts/post", line 56, in main post: msg = Message.Message(sys.stdin) post: File "/usr/local/mailman/Mailman/Message.py", line 49, in __init__ post: self.rewindbody() post: File "/usr/local/mailman/Mailman/pythonlib/rfc822.py", line 104, in rewindbody post: self.fp.seek(self.startofbody) post: IOError : [Errno 29] Illegal seek Ricardo. -- From bwarsaw@cnri.reston.va.us (Barry A. Warsaw) Fri Dec 10 13:46:28 1999 From: bwarsaw@cnri.reston.va.us (Barry A. Warsaw) (Barry A. Warsaw) Date: Fri, 10 Dec 1999 08:46:28 -0500 (EST) Subject: [Mailman-Developers] latest cvs trouble References: <19991210065707.A23888@miss-janet.com> Message-ID: <14417.1076.218993.63059@anthem.cnri.reston.va.us> >>>>> "RK" == Ricardo Kustner writes: RK> since 1.1/postfix seems to be duplicating some posts a bit too RK> often, i tried to install the latest cvs of MM... first of RK> all, there were some pending posts in config.db, but the new RK> installation doesn't recognize them (i guess this changed in RK> 1.2) so any administrative requests get lost. This is true. What I've done is make sure that any lists I convert have been cleared of admin requests. This clearly needs to be better handled in "make update" when 1.2 is released. RK> When I tried posting to the list, i got an error: post: File RK> "/usr/local/mailman/scripts/post", line 83, in ? post: main() RK> post: File "/usr/local/mailman/scripts/post", line 56, in main RK> post: msg = Message.Message(sys.stdin) post: File RK> "/usr/local/mailman/Mailman/Message.py", line 49, in __init__ RK> post: self.rewindbody() post: File RK> "/usr/local/mailman/Mailman/pythonlib/rfc822.py", line 104, in RK> rewindbody post: self.fp.seek(self.startofbody) post: IOError RK> : [Errno 29] Illegal seek Okay, so sys.stdin isn't seekable everywhere :) Give the below patch a try. -Barry -------------------- snip snip -------------------- Index: post =================================================================== RCS file: /projects/cvsroot/mailman/scripts/post,v retrieving revision 1.25 diff -c -r1.25 post *** post 1999/11/24 21:11:07 1.25 --- post 1999/12/10 13:44:17 *************** *** 33,38 **** --- 33,39 ---- from Mailman import Utils from Mailman.Logging.Utils import LogStdErr from Mailman.Handlers import HandlerAPI + from Mailman.pythonlib import StringIO LogStdErr("error", "post") *************** *** 53,59 **** except: pass if msg is None: ! msg = Message.Message(sys.stdin) # go ahead and post the message adminaddr = mlist.GetAdminEmail() try: --- 54,61 ---- except: pass if msg is None: ! s = StringIO(sys.stdin.read()) ! msg = Message.Message(s) # go ahead and post the message adminaddr = mlist.GetAdminEmail() try: From wheakory@isu.edu Fri Dec 10 20:22:12 1999 From: wheakory@isu.edu (Kory Wheatley) Date: Fri, 10 Dec 1999 13:22:12 -0700 Subject: [Mailman-Developers] Installing python 1.5.2 Message-ID: <385160F4.3D782A2E@isu.edu> I am going to be installing python 1.5.2 to red hat 6.0 linux. Do any of you have any information or problems that I should look at for. Is there something that I might have to tweak with this new version. -- Kory Wheatley Office Phone 236-3874 Computing & Communication Academic Computing Analyst sr. Everything you do must point to him. From ricardo@miss-janet.com Fri Dec 10 22:41:50 1999 From: ricardo@miss-janet.com (Ricardo Kustner) Date: Fri, 10 Dec 1999 23:41:50 +0100 Subject: [Mailman-Developers] latest cvs trouble In-Reply-To: <14417.1076.218993.63059@anthem.cnri.reston.va.us>; from bwarsaw@cnri.reston.va.us on Fri, Dec 10, 1999 at 08:46:28AM -0500 References: <19991210065707.A23888@miss-janet.com> <14417.1076.218993.63059@anthem.cnri.reston.va.us> Message-ID: <19991210234150.A31262@miss-janet.com> On Fri, Dec 10, 1999 at 08:46:28AM -0500, Barry A. Warsaw wrote: > > >>>>> "RK" == Ricardo Kustner writes: > RK> When I tried posting to the list, i got an error: post: File > Okay, so sys.stdin isn't seekable everywhere :) Give the below patch > a try. thanks, but this patch produces another error: : Command died with status 1: "/usr/local/mailman/mail/wrapper post mailinglist". Command output: Traceback (innermost last): File "/usr/local/mailman/scripts/post", line 85, in ? main() File "/usr/local/mailman/scripts/post", line 57, in main s = StringIO(sys.stdin.read()) TypeError: call of non-function (type module) Also, why did you add import StringIO? cause the pre-patch version already contains a call to StringIO a few lines earlier... unfortunately I haven't mastered python 100% yet, so I can't help out much with tracking down the bug :( > =================================================================== > RCS file: /projects/cvsroot/mailman/scripts/post,v > retrieving revision 1.25 > diff -c -r1.25 post > *** post 1999/11/24 21:11:07 1.25 > --- post 1999/12/10 13:44:17 > *************** > *** 33,38 **** > --- 33,39 ---- > from Mailman import Utils > from Mailman.Logging.Utils import LogStdErr > from Mailman.Handlers import HandlerAPI > + from Mailman.pythonlib import StringIO > > LogStdErr("error", "post") > > *************** > *** 53,59 **** > except: > pass > if msg is None: > ! msg = Message.Message(sys.stdin) > # go ahead and post the message > adminaddr = mlist.GetAdminEmail() > try: > --- 54,61 ---- > except: > pass > if msg is None: > ! s = StringIO(sys.stdin.read()) > ! msg = Message.Message(s) > # go ahead and post the message > adminaddr = mlist.GetAdminEmail() > try: > -- Ricardo. -- International Janet Jackson fanclub called MISS JANET. For more information write to: Miss Janet. P.O.Box 10016, 1001 EA Amsterdam, The Netherlands Fax/phone: +31-(0)20-7764493 Email: fanclub@miss-janet.com Or check out our website: http://miss-janet.com From bwarsaw@python.org Sat Dec 11 03:51:01 1999 From: bwarsaw@python.org (Barry A. Warsaw) Date: Fri, 10 Dec 1999 22:51:01 -0500 (EST) Subject: [Mailman-Developers] latest cvs trouble References: <19991210065707.A23888@miss-janet.com> <14417.1076.218993.63059@anthem.cnri.reston.va.us> <19991210234150.A31262@miss-janet.com> Message-ID: <14417.51749.991830.188873@anthem.cnri.reston.va.us> >>>>> "RK" == Ricardo Kustner writes: RK> thanks, but this patch produces another error: Oops, you should change from Mailman.pythonlib import StringIO to from Mailman.pythonlib.StringIO import StringIO RK> Also, why did you add import StringIO? cause the pre-patch RK> version already contains a call to StringIO a few lines RK> earlier... unfortunately I haven't mastered python 100% yet, RK> so I can't help out much with tracking down the bug :( Really? The CVS version of the file was missing the import of StringIO (and in fact, if the code takes the `prog is true' path through the first conditional, it would raise an exception because of that). -Barry From bwarsaw@cnri.reston.va.us (Barry A. Warsaw) Sat Dec 11 04:53:06 1999 From: bwarsaw@cnri.reston.va.us (Barry A. Warsaw) (Barry A. Warsaw) Date: Fri, 10 Dec 1999 23:53:06 -0500 (EST) Subject: [Mailman-Developers] 8-bit input in administrator menu References: Message-ID: <14417.55474.145609.535665@anthem.cnri.reston.va.us> >>>>> "BN" == Balazs Nagy writes: BN> I did a little digging about entering text with accents. It's BN> a bit curious that one can type accents in textarea but to BN> textbox cannot. In the latter case you can see an escaped BN> print of your input. BN> In the end I came to htmlformat.py's InputObj. At this point BN> I have a humble question: who put `-s around value? After a BN> s/`value`/value/ in line #368, almost everything works fine, BN> because this brings up a problem about quoting. Of course, the BN> patch is here. Near as I can tell, that's the way the code has been since its initial version. I've installed this change. Thanks, -Barry From ricardo@miss-janet.com Sat Dec 11 12:44:04 1999 From: ricardo@miss-janet.com (Ricardo Kustner) Date: Sat, 11 Dec 1999 13:44:04 +0100 Subject: [Mailman-Developers] admin approval page / cvs Message-ID: <19991211134404.D5306@miss-janet.com> Hi, i'm trying out the 1.2 cvs version of MM... I like the changes on the approval page... I do have some suggestions for changes, which should make it a bit easier to use (this page is an important part of our mailinglist setup and I've used it alot)... 1) message headers: putting the message in a TEXTAREA is a neat solution :) however, when all the message headers are being shown, you have to scroll the box alot before you see anything about the message body... maybe the headers should be left out entirely since the subject/from is being mentioned above anyway ? 2) approve/reject/discard ... please move this below the message content... since the normal way is that you read the message first, and then decide what to do with it... 3) add an option to send a copy of the message to a certain email address. I've already hacked something like this into my local copy of MM, but it just sends the message body, so any attachments are lost (you can of course retrieve them with mime tools) i've already changed these things myself... but i don't have a copy of cvs on the production machine so it's not easy to make a patch for it right now... (and to be honest my changes are more 'hacks' than clean code ;) ) Ricardo. From claw@kanga.nu Sat Dec 11 15:14:01 1999 From: claw@kanga.nu (J C Lawrence) Date: Sat, 11 Dec 1999 07:14:01 -0800 Subject: [Mailman-Developers] admin approval page / cvs In-Reply-To: Message from Ricardo Kustner of "Sat, 11 Dec 1999 13:44:04 +0100." <19991211134404.D5306@miss-janet.com> References: <19991211134404.D5306@miss-janet.com> Message-ID: On Sat, 11 Dec 1999 13:44:04 +0100 Ricardo Kustner wrote: > 1) message headers: putting the message in a TEXTAREA is a neat > solution :) Agreed. I would like to be able to edit moderated messages, given that MailMan would then insert a custom header stating that the message had been edited by the moderator. > however, when all the message headers are being shown, > you have to scroll the box alot before you see anything about the > message body... maybe the headers should be left out entirely > since the subject/from is being mentioned above anyway ? No way. The headers are essential to me. -- J C Lawrence Home: claw@kanga.nu ----------(*) Other: coder@kanga.nu --=| A man is as sane as he is dangerous to his environment |=-- From jafo@tummy.com Sat Dec 11 15:36:14 1999 From: jafo@tummy.com (Sean Reifschneider) Date: Sat, 11 Dec 1999 08:36:14 -0700 Subject: [Mailman-Developers] admin approval page / cvs In-Reply-To: ; from J C Lawrence on Sat, Dec 11, 1999 at 07:14:01AM -0800 References: <19991211134404.D5306@miss-janet.com> Message-ID: <19991211083614.E20354@tummy.com> On Sat, Dec 11, 1999 at 07:14:01AM -0800, J C Lawrence wrote: >No way. The headers are essential to me. What about having separate text fields for the headers and the body? I suppose with JavaScript you could cause the cursor to move to the first line of the body... Sean -- These go to eleven. -- _This_is_Spinal_Tap_ Sean Reifschneider, Inimitably Superfluous URL: HP-UX/Linux/FreeBSD/BSDOS scanning software. From claw@kanga.nu Sat Dec 11 15:43:28 1999 From: claw@kanga.nu (J C Lawrence) Date: Sat, 11 Dec 1999 07:43:28 -0800 Subject: [Mailman-Developers] admin approval page / cvs In-Reply-To: Message from Sean Reifschneider of "Sat, 11 Dec 1999 08:36:14 MST." <19991211083614.E20354@tummy.com> References: <19991211134404.D5306@miss-janet.com> <19991211083614.E20354@tummy.com> Message-ID: On Sat, 11 Dec 1999 08:36:14 -0700 Sean Reifschneider wrote: > On Sat, Dec 11, 1999 at 07:14:01AM -0800, J C Lawrence wrote: >> No way. The headers are essential to me. > What about having separate text fields for the headers and the > body? Please, no. I need/want the message exactly as it was sent with no extra munging, implicit edits, ochanges in presentation etc. This is actually one of the main things I like about MM -- it doesn't attempt to package the pending-moderation messages in any way, but presents them to me exactly as they are. -- J C Lawrence Home: claw@kanga.nu ----------(*) Other: coder@kanga.nu --=| A man is as sane as he is dangerous to his environment |=-- From bwarsaw@cnri.reston.va.us (Barry A. Warsaw) Sat Dec 11 15:53:24 1999 From: bwarsaw@cnri.reston.va.us (Barry A. Warsaw) (Barry A. Warsaw) Date: Sat, 11 Dec 1999 10:53:24 -0500 (EST) Subject: [Mailman-Developers] admin approval page / cvs References: <19991211134404.D5306@miss-janet.com> <19991211083614.E20354@tummy.com> Message-ID: <14418.29556.250753.901548@anthem.cnri.reston.va.us> >>>>> "SR" == Sean Reifschneider writes: SR> I suppose with JavaScript you could cause the cursor to SR> move to the first line of the body... -Barry From jafo@tummy.com Sat Dec 11 16:17:58 1999 From: jafo@tummy.com (Sean Reifschneider) Date: Sat, 11 Dec 1999 09:17:58 -0700 Subject: [Mailman-Developers] admin approval page / cvs In-Reply-To: ; from J C Lawrence on Sat, Dec 11, 1999 at 07:43:28AM -0800 References: <19991211134404.D5306@miss-janet.com> <19991211083614.E20354@tummy.com> Message-ID: <19991211091758.F20354@tummy.com> On Sat, Dec 11, 1999 at 07:43:28AM -0800, J C Lawrence wrote: >Please, no. I need/want the message exactly as it was sent with no >extra munging, implicit edits, ochanges in presentation etc. This Ok, so it should be an option... I don't do much approval, so it really doesn't impact me. However, the primary information needed when doing an approval is the *BODY*, and that's generally obscured from the page as it is presented. From a Human Factors POV, that's inexcusable... What about simply increasing the size of the edit field based on the number of lines in the message? That way you don't have to navigate into the text field and scroll to see the *PRIMARY* information you need to carry out the action. Oh, and if you have the header and the body in one text field, is there code to ensure that the space separating the header from the body hasn't been accidentally removed? Sean -- "I'll thrash you like a Netscape process on a machine with 640K." -- John Shipman, 1998 Sean Reifschneider, Inimitably Superfluous URL: HP-UX/Linux/FreeBSD/BSDOS scanning software. From ricardo@miss-janet.com Sat Dec 11 17:24:49 1999 From: ricardo@miss-janet.com (Ricardo Kustner) Date: Sat, 11 Dec 1999 18:24:49 +0100 Subject: [Mailman-Developers] admin approval page / cvs In-Reply-To: ; from claw@kanga.nu on Sat, Dec 11, 1999 at 07:14:01AM -0800 References: <19991211134404.D5306@miss-janet.com> Message-ID: <19991211182449.B7706@miss-janet.com> Hi, On Sat, Dec 11, 1999 at 07:14:01AM -0800, J C Lawrence wrote: > On Sat, 11 Dec 1999 13:44:04 +0100 > Ricardo Kustner wrote: > > 1) message headers: putting the message in a TEXTAREA is a neat > > solution :) > Agreed. I would like to be able to edit moderated messages, given > that MailMan would then insert a custom header stating that the > message had been edited by the moderator. yes i saw that the textarea data isn't used when approving the post... the complete message is read from disk when it has been approved. > > message body... maybe the headers should be left out entirely > > since the subject/from is being mentioned above anyway ? > No way. The headers are essential to me. i can understand that the headers may be very usefull sometimes... what if we meet half way? i just thought of the following solution: put the message body in a textarea... and put a select box on top if it that includes the headers... something like this: so if you click on the select box, you get the list of headers. and you don't even need to use Javascript :) Ricardo. -- From claw@kanga.nu Sat Dec 11 17:28:01 1999 From: claw@kanga.nu (J C Lawrence) Date: Sat, 11 Dec 1999 09:28:01 -0800 Subject: [Mailman-Developers] admin approval page / cvs In-Reply-To: Message from Ricardo Kustner of "Sat, 11 Dec 1999 18:24:49 +0100." <19991211182449.B7706@miss-janet.com> References: <19991211134404.D5306@miss-janet.com> <19991211182449.B7706@miss-janet.com> Message-ID: On Sat, 11 Dec 1999 18:24:49 +0100 Ricardo Kustner wrote: > Hi, On Sat, Dec 11, 1999 at 07:14:01AM -0800, J C Lawrence wrote: >> Agreed. I would like to be able to edit moderated messages, >> given that MailMan would then insert a custom header stating that >> the message had been edited by the moderator. > yes i saw that the textarea data isn't used when approving the > post... the complete message is read from disk when it has been > approved. This is not surprising given that a single message may be several Meg in size (and yes, some of my list posts are that big). >> > message body... maybe the headers should be left out entirely > >> since the subject/from is being mentioned above anyway ? No way. >> The headers are essential to me. > i can understand that the headers may be very usefull sometimes... > what if we meet half way? i just thought of the following > solution: put the message body in a textarea... and put a select > box on top if it that includes the headers... This works badly when you have a large number of messages to approve. -- J C Lawrence Home: claw@kanga.nu ----------(*) Other: coder@kanga.nu --=| A man is as sane as he is dangerous to his environment |=-- From ricardo@miss-janet.com Sun Dec 12 11:29:12 1999 From: ricardo@miss-janet.com (Ricardo Kustner) Date: Sun, 12 Dec 1999 12:29:12 +0100 Subject: [Mailman-Developers] admin approval page / cvs In-Reply-To: ; from claw@kanga.nu on Sat, Dec 11, 1999 at 09:28:01AM -0800 References: <19991211134404.D5306@miss-janet.com> <19991211182449.B7706@miss-janet.com> Message-ID: <19991212122912.B25191@miss-janet.com> Hi, On Sat, Dec 11, 1999 at 09:28:01AM -0800, J C Lawrence wrote: > On Sat, 11 Dec 1999 18:24:49 +0100 > Ricardo Kustner wrote: > >> Agreed. I would like to be able to edit moderated messages, > >> given that MailMan would then insert a custom header stating that > >> the message had been edited by the moderator. > > yes i saw that the textarea data isn't used when approving the > > post... the complete message is read from disk when it has been > > approved. > This is not surprising given that a single message may be several > Meg in size (and yes, some of my list posts are that big). Yes i'm glad they're no longer in config.db :) > >> The headers are essential to me. > > solution: put the message body in a textarea... and put a select > > box on top if it that includes the headers... > This works badly when you have a large number of messages to > approve. for me the reason to seperate the headers is just because i always have a large number of messages to approve... now it takes me much longer to approve everything because i have to stop at each message and move the mouse to scroll the textarea... normally it was just read, scroll, click accept/reject and scroll to the next message. Even if the full message is visible in the textarea, my mind needs a bit of time to focus on where the headers end and the message begins... Ricardo. -- From root@theporch.com Sun Dec 12 13:21:54 1999 From: root@theporch.com (Phillip Porch) Date: Sun, 12 Dec 1999 07:21:54 -0600 (CST) Subject: [Mailman-Developers] Mailman 1.2 CVS Message-ID: I Noticed the following error message in my error log for mailman and wondered if you could give me a pointer to tracking down the problem. beer: lost digest file: /home mailman/list/beer/next-digest (No such file or directory) I also started seeing this message a couple of days ago from the cron daemon. Traceback (innermost last): File "/home/mailman/cron/checkdbs", line 83, in ? main() File "/home/mailman/cron/checkdbs", line 50, in main mlist.SendTextToUser( AttributeError: SendTextToUser ************************************************* Cron: The previous message is the standard output and standard error of one of your cron commands. From root@theporch.com Sun Dec 12 13:39:08 1999 From: root@theporch.com (Phillip Porch) Date: Sun, 12 Dec 1999 07:39:08 -0600 (CST) Subject: [Mailman-Developers] Mailman 1.2 CVS Message-ID: I have noticed another quirk. In the archives, with the original version, I had the archive gzipped on the fly. The links would indicate that the text could be obtained gzipped. With the current version, I have elected to not gzip on the fly but to run the cron script to gzip the archives. The gzipping is working fine, but the link on the archive page doesn;t indicate the file is available gzipped. What is needed to update that link? -- Phillip P. Porch NIC:PP1573 finger for http://www.theporch.com UTM - 16 514548E 3994397N PGP key From bwarsaw@cnri.reston.va.us (Barry A. Warsaw) Sun Dec 12 21:01:36 1999 From: bwarsaw@cnri.reston.va.us (Barry A. Warsaw) (Barry A. Warsaw) Date: Sun, 12 Dec 1999 16:01:36 -0500 (EST) Subject: [Mailman-Developers] Mailman 1.2 CVS References: Message-ID: <14420.3376.144281.520784@anthem.cnri.reston.va.us> >>>>> "PP" == Phillip Porch writes: PP> I Noticed the following error message in my error log for PP> mailman and wondered if you could give me a pointer to PP> tracking down the problem. PP> beer: lost digest file: /home mailman/list/beer/next-digest PP> (No such file or directory) Ignore this. There was a situation where this message was being unnecessarily logged. I checked in a fix for this. PP> I also started seeing this message a couple of days ago from PP> the cron daemon. PP> Traceback (innermost last): | File "/home/mailman/cron/checkdbs", line 83, in ? | main() | File "/home/mailman/cron/checkdbs", line 50, in main | mlist.SendTextToUser( PP> AttributeError: SendTextToUser Oh dang, I forgot to convert checkdbs. Will do. -Barry From bbum@codefab.com Sun Dec 12 22:54:24 1999 From: bbum@codefab.com (Bill Bumgarner) Date: Sun, 12 Dec 1999 17:54:24 -0500 Subject: [Mailman-Developers] Developers Needed for addition of specific feature(s) Message-ID: <199912122254.RAA15190@bjork.codefab.com> I'm looking for some Python/MailMan savvy developers to add some features to MailMan. In particular, we [CodeFab] have a need-- both internally and on a client project-- to augment MailMan such that it can gracefully handle attachments. In particular: - decode MIME (and other formats?) encoded messages upon receipt - file attachments into archive via either the current archive scheme or via WebDAV (WebDAV preferred) - rewrite message such that it contains URLs to the attachements instead of the attachments themselves The overriding goal of this is to solve the above problems in an extremely timely manner and provide all resulting modifications/extensions to MailMan back to the MailMan development community in such a fashion that it can be integrated into future releases. However, we are under a severe time crunch and, as such, it is likely that what we need done and what needs to be done to integrate this into the next release will not be in complete parity-- which is another reason why I would really like to bring a focused MailMan/Python developer into this project to ensure that the short term work will feed directly into a long term, viable integration of this solution into MailMan. The code is not just for CodeFab's benefit-- we have a client that also needs this solution. This client is also interested in helping fund this development effort. The funds are limited and the client [and CodeFab] would both like to be able to further leverage this by generating some positive "we support open source projects & MailMan/Python is really cool" PR-- so we would like to work with a developer or developers that are amicable to having their name thrown into a press release and wouldn't mind signing the standard NDA/contracting style agreements. Let me reiterate-- regardless of contractual agreements necessary to move this forward-- all code developed under this arrangement will be under the GPL. Regardless of whether or not we can find someone to formally assist us, this work has to get done anyway. I would rather see it done with formal assistance from the MailMan development community... If we can't find someone to help from the community, then consider this message a request for comments as to how to best implement the above features and I guess I'll have to go read the "hacking MailMan" HOWTO. :-) thanks, b.bum From ricardo@miss-janet.com Mon Dec 13 05:27:48 1999 From: ricardo@miss-janet.com (Ricardo Kustner) Date: Mon, 13 Dec 1999 06:27:48 +0100 Subject: [Mailman-Developers] cvs errors Message-ID: <19991213062748.A1073@miss-janet.com> I noticed the following errors in the CVS version of MM: Dec 13 03:48:05 1999 mailcmd: Traceback (innermost last): mailcmd: File "/usr/local/mailman/scripts/mailcmd", line 52, in ? mailcmd: list.ParseMailCommands() mailcmd: File "/usr/local/mailman/Mailman/MailCommandHandler.py", line 112, in mailcmd: msg = Message.Message(sys.stdin) mailcmd: File "/usr/local/mailman/Mailman/Message.py", line 49, in __init__ mailcmd: self.rewindbody() mailcmd: File "/usr/local/mailman/Mailman/pythonlib/rfc822.py", line 104, in r mailcmd: self.fp.seek(self.startofbody) mailcmd: IOError : [Errno 29] Illegal seek I'm not sure what could be causing this, but i got one complaint from somebody who received an error message from postfix when trying to confirm subscribing to the list. Also I've noticed the number of posts to the lists have decreased dramatically, though this saves me a lot of approval work, i hope this doesn't mean some posts are getting lost... Ricardo. -- From ricardo@miss-janet.com Mon Dec 13 06:26:01 1999 From: ricardo@miss-janet.com (Ricardo Kustner) Date: Mon, 13 Dec 1999 07:26:01 +0100 Subject: [Mailman-Developers] latest cvs trouble In-Reply-To: <14417.1076.218993.63059@anthem.cnri.reston.va.us>; from bwarsaw@cnri.reston.va.us on Fri, Dec 10, 1999 at 08:46:28AM -0500 References: <19991210065707.A23888@miss-janet.com> <14417.1076.218993.63059@anthem.cnri.reston.va.us> Message-ID: <19991213072601.B1073@miss-janet.com> Hi, On Fri, Dec 10, 1999 at 08:46:28AM -0500, Barry A. Warsaw wrote: > RK> post: File "/usr/local/mailman/scripts/post", line 56, in main > RK> post: msg = Message.Message(sys.stdin) post: File > RK> "/usr/local/mailman/Mailman/Message.py", line 49, in __init__ > RK> post: self.rewindbody() post: File > RK> "/usr/local/mailman/Mailman/pythonlib/rfc822.py", line 104, in > RK> rewindbody post: self.fp.seek(self.startofbody) post: IOError > RK> : [Errno 29] Illegal seek > Okay, so sys.stdin isn't seekable everywhere :) Give the below patch > a try. will this be added to the cvs version too? I want to have the latest cvs version running, but I keep having to change this in scripts/post :) also, it looks like the problem I reported earlier today is related to this one... Thanks, Ricardo. -- From richarde@eskom.co.za Mon Dec 13 08:12:25 1999 From: richarde@eskom.co.za (Richard Ellerbrock) Date: Mon, 13 Dec 1999 10:12:25 +0200 Subject: [Mailman-Developers] admin approval page / cvs Message-ID: >Hi, > >i'm trying out the 1.2 cvs version of MM... >I like the changes on the approval page... I do have some >suggestions for changes, which should make it a bit easier to >use (this page is an important part of our mailinglist >setup and I've used it alot)... {cut} >3) add an option to send a copy of the message to a certain > email address. I've already hacked something like this > into my local copy of MM, but it just sends the message body, > so any attachments are lost (you can of course retrieve them > with mime tools) I would really like this feature too! -- Richard Ellerbrock richarde@eskom.co.za From uwannags@swd.de Mon Dec 13 08:43:44 1999 From: uwannags@swd.de (Uwe Wannags) Date: Mon, 13 Dec 1999 09:43:44 +0100 Subject: [Mailman-Developers] unsubscribe Message-ID: <019e01bf4546$2b7b6e80$0964a8c0@SWD.DE> This is a multi-part message in MIME format. ------=_NextPart_000_0198_01BF454E.8BCE9340 Content-Type: multipart/alternative; boundary="----=_NextPart_001_0199_01BF454E.8BCE9340" ------=_NextPart_001_0199_01BF454E.8BCE9340 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable unsubscribe ------=_NextPart_001_0199_01BF454E.8BCE9340 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
unsubscribe
------=_NextPart_001_0199_01BF454E.8BCE9340-- ------=_NextPart_000_0198_01BF454E.8BCE9340 Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIIpDCCAlcw ggHAoAMCAQICAwGWtTANBgkqhkiG9w0BAQQFADCBlDELMAkGA1UEBhMCWkExFTATBgNVBAgTDFdl c3Rlcm4gQ2FwZTEUMBIGA1UEBxMLRHVyYmFudmlsbGUxDzANBgNVBAoTBlRoYXd0ZTEdMBsGA1UE CxMUQ2VydGlmaWNhdGUgU2VydmljZXMxKDAmBgNVBAMTH1BlcnNvbmFsIEZyZWVtYWlsIFJTQSAx OTk5LjkuMTYwHhcNOTkxMDI3MTYxOTU1WhcNMDAxMDI2MTYxOTU1WjBBMR8wHQYDVQQDExZUaGF3 dGUgRnJlZW1haWwgTWVtYmVyMR4wHAYJKoZIhvcNAQkBFg91d2FubmFnc0Bzd2QuZGUwXDANBgkq hkiG9w0BAQEFAANLADBIAkEAxLhJ77nyZX9c82rwsfqcYnh4PYgBo9E18KB0GBa1dwuzhqOy0Kmv eFK3q9tbJ+4E9sVo3Q5F+fx/NRifM8P5IQIDAQABo00wSzAaBgNVHREEEzARgQ91d2FubmFnc0Bz d2QuZGUwDAYDVR0TAQH/BAIwADAfBgNVHSMEGDAWgBSIq/Fgg2ZV9ORYx0YdwGG9I9fDjDANBgkq hkiG9w0BAQQFAAOBgQBVLuMif4ucBR8np8l48vqVVSmzYPZecuM1WO0i7kYj6+0Az/gPLetFUnEz 4C1stoFadv+VtWpyDcqJEqjNmRGR+zA2dL78Q/gfmJZNK5D4/RWvqYdGUL/YpmcF1CC/Z+aBa8bz EpGl92gEae4MhVsKEveGOJ3yboFyewtLK8AnKTCCAxQwggJ9oAMCAQICAQswDQYJKoZIhvcNAQEE BQAwgdExCzAJBgNVBAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUg VG93bjEaMBgGA1UEChMRVGhhd3RlIENvbnN1bHRpbmcxKDAmBgNVBAsTH0NlcnRpZmljYXRpb24g U2VydmljZXMgRGl2aXNpb24xJDAiBgNVBAMTG1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBDQTEr MCkGCSqGSIb3DQEJARYccGVyc29uYWwtZnJlZW1haWxAdGhhd3RlLmNvbTAeFw05OTA5MTYxNDAx NDBaFw0wMTA5MTUxNDAxNDBaMIGUMQswCQYDVQQGEwJaQTEVMBMGA1UECBMMV2VzdGVybiBDYXBl MRQwEgYDVQQHEwtEdXJiYW52aWxsZTEPMA0GA1UEChMGVGhhd3RlMR0wGwYDVQQLExRDZXJ0aWZp Y2F0ZSBTZXJ2aWNlczEoMCYGA1UEAxMfUGVyc29uYWwgRnJlZW1haWwgUlNBIDE5OTkuOS4xNjCB nzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAs2lal9TQFgt6tcVd6SGcI3LNEkxL937Px/vKciT0 QlKsV5Xje2F6F4Tn/XI5OJS06u1lp5IGXr3gZfYZu5R5dkw+uWhwdYQc9BF0ALwFLE8JAxcxzPRB 1HLGpl3iiESwiy7ETfHw1oU+bPOVlHiRfkDpnNGNFVeOwnPlMN5G9U8CAwEAAaM3MDUwEgYDVR0T AQH/BAgwBgEB/wIBADAfBgNVHSMEGDAWgBRyScJzNMZV9At2coF+d/SH58ayDjANBgkqhkiG9w0B AQQFAAOBgQBrxlnpMfrptuyxA9jfcnL+kWBI6sZV3XvwZ47GYXDnbcKlN9idtxcoVgWL3Vx1b8aR kMZsZnET0BB8a5FvhuAhNi3B1+qyCa3PLW3Gg1Kb+7v+nIed/LfpdJLkXJeu/H6syg1vcnpnLGtz 9Yb5nfUAbvQdB86dnoJjKe+TCX5V3jCCAy0wggKWoAMCAQICAQAwDQYJKoZIhvcNAQEEBQAwgdEx CzAJBgNVBAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUgVG93bjEa MBgGA1UEChMRVGhhd3RlIENvbnN1bHRpbmcxKDAmBgNVBAsTH0NlcnRpZmljYXRpb24gU2Vydmlj ZXMgRGl2aXNpb24xJDAiBgNVBAMTG1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBDQTErMCkGCSqG SIb3DQEJARYccGVyc29uYWwtZnJlZW1haWxAdGhhd3RlLmNvbTAeFw05NjAxMDEwMDAwMDBaFw0y MDEyMzEyMzU5NTlaMIHRMQswCQYDVQQGEwJaQTEVMBMGA1UECBMMV2VzdGVybiBDYXBlMRIwEAYD VQQHEwlDYXBlIFRvd24xGjAYBgNVBAoTEVRoYXd0ZSBDb25zdWx0aW5nMSgwJgYDVQQLEx9DZXJ0 aWZpY2F0aW9uIFNlcnZpY2VzIERpdmlzaW9uMSQwIgYDVQQDExtUaGF3dGUgUGVyc29uYWwgRnJl ZW1haWwgQ0ExKzApBgkqhkiG9w0BCQEWHHBlcnNvbmFsLWZyZWVtYWlsQHRoYXd0ZS5jb20wgZ8w DQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBANRp19SwlGRbcelH2AxRtupykbCEXn0tDY97Et+FJXUo dDpCLGMnn5V7S+9+GYcdhuqj3bnOlmQawhRuRKx85o/oTQ9xH0A4pgCjh3j2+ZSGXq3qwF5269kU o11uenwMpUtVfwYZKX+emibVars4JAhqmMex2qOYkf152+VaxBy5AgMBAAGjEzARMA8GA1UdEwEB /wQFMAMBAf8wDQYJKoZIhvcNAQEEBQADgYEAx+ySfk749ZalZ2IqpPBNEWDQb41gWGGsJrtSNVwI zzD7qEqWih9iQiOMFw/0umScF6xHKd+dmF7SbGBxXKKs3Hnj524ARx+1DSjoAp3kmv0T9KbZfLH4 3F8jJgmRgHPQFBveQ6mDJfLmnC8Vyv6mq4oHdYsM3VGEa+T40c53ooExggGLMIIBhwIBATCBnDCB lDELMAkGA1UEBhMCWkExFTATBgNVBAgTDFdlc3Rlcm4gQ2FwZTEUMBIGA1UEBxMLRHVyYmFudmls bGUxDzANBgNVBAoTBlRoYXd0ZTEdMBsGA1UECxMUQ2VydGlmaWNhdGUgU2VydmljZXMxKDAmBgNV BAMTH1BlcnNvbmFsIEZyZWVtYWlsIFJTQSAxOTk5LjkuMTYCAwGWtTAJBgUrDgMCGgUAoIGGMBgG CSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTk5MTIxMzA5NDM0NFowIwYJ KoZIhvcNAQkEMRYEFKcoLKkxeLAtCbBs0hzoyUKRIBYKMCcGCSqGSIb3DQEJDzEaMBgwDQYIKoZI hvcNAwICASgwBwYFKw4DAh0wDQYJKoZIhvcNAQEBBQAEQF7LKRLVhEThjcgF5vKylsyt9dZYFWUY Q1LQfzKYzprYDlJ20eybfhW6FAQvUqsOvxrsgFOOg+2YHXcG/vVIcP0AAAAAAAA= ------=_NextPart_000_0198_01BF454E.8BCE9340-- From wheakory@isu.edu Mon Dec 13 16:41:15 1999 From: wheakory@isu.edu (Kory Wheatley) Date: Mon, 13 Dec 1999 09:41:15 -0700 Subject: [Mailman-Developers] Cron error message Message-ID: <385521AB.8B7CB744@isu.edu> This error message below is generated when the cron scheduled job gate_news is ran. Would this error happen in result that I am running mailman 1.1 and have Python1.5.1 do I need upgrade to Python 1.5.2 for this cron entry to run? I have been getting similar errors from the other mailman cron job entries to (like senddigests, nightly-gzip), since I upgraded mailman from 1.0 to 1.1. Mailman is installed on red hat 6.0 using the MTA Sendmail. What's funny is I can still receive mail messages fine from the lists and send them out if I have all of the cron jobs commented out. Once I have the cron jobs running after a while when getting error message sent to me the postmaster of mailman about the cron processes errors, I can't receive any messages from the mailman subscript lists that I have myself on. I receive usually a mailer 2 error. All of the permissions are setup correctly for mailman 1.1. If I shutdown and reboot my Linux machine then everything will work again until those cron jobs processes run for a while., then eventually I can't receive any message from the lists or if I send messages to the lists I just get error message back form mailman admin. I really need help I have 20 production list on mailman that need to be working all the time. Do I need to upgrade to python 1.5.2? Will mailman 1.1 work with python 1.5.1 and I just need to tweak something? I am desperately seeking support here. If anyone has the answer please respond immediately. I have not found any documentation that says mailman 1.1 will not work with python 1.5.1. If I have missed this documentation please point me to the link that explains what's needed for mailman 1.1 to work with red hat 6.0. Is there anyway to pay for getting support for mailman being installed on a system. Here is the error message below, sorry so long but I need help badly. Traceback (innermost last): File "/home/mailman/cron/gate_news", line 119, in ? main() File "/home/mailman/cron/gate_news", line 58, in main mlist = MailList.MailList(name, lock=0) File "/home/mailman/Mailman/MailList.py", line 62, in __init__ self.Load() File "/home/mailman/Mailman/MailList.py", line 820, in Load setattr(self, key, value) TypeError: setattr, argument 2: expected string, None found -- Kory Wheatley Office Phone 236-3874 Computing & Communication Academic Computing Analyst sr. Everything you do must point to him. From joe@lawlearn.wuacc.edu Mon Dec 13 20:45:18 1999 From: joe@lawlearn.wuacc.edu (Joe Hewitt) Date: Mon, 13 Dec 1999 14:45:18 -0600 (CST) Subject: [Mailman-Developers] Re: [Mailman-Users] Installing python 1.5.2 In-Reply-To: <385160F4.3D782A2E@isu.edu> Message-ID: Kory, You probably want to use the Red Hat CD to install your python 1.5.2 which is the version on the 6.0 CD. I tried installing it from src and it wouldn't work properly, so I reinstalled from CD and all was fine. Duh! Joe On Fri, 10 Dec 1999, Kory Wheatley wrote: > I am going to be installing python 1.5.2 to red hat 6.0 linux. Do any > of you have any information or problems that I should look at for. Is > there something that I might have to tweak with this new version. > > -- > Kory Wheatley Office Phone 236-3874 > Computing & Communication > Academic Computing Analyst sr. > > Everything you do must point to him. > > > > ------------------------------------------------------ > Mailman-Users maillist - Mailman-Users@python.org > http://www.python.org/mailman/listinfo/mailman-users > From Dan Mick Tue Dec 14 01:51:34 1999 From: Dan Mick (Dan Mick) Date: Mon, 13 Dec 1999 17:51:34 -0800 (PST) Subject: [Mailman-Developers] Wish list item: anyone working on it? Message-ID: <199912140151.RAA13497@utopia.West.Sun.COM> I wish that the admindb interface would show a different "default" message based on the type of the 'post' request; that is, now, it always displays the suggested text Please do *not* post administrative requests to the mailing list! If you wish to subscribe, visit %s or send a 'help' message to the the request address, %s , for instructions but that's only appropriate for some sort of post requests. I see that "AddRequest" sometimes gets called with standard members of Errors, but sometimes gets called with hard-coded strings; what one would need is to regularize all those, and then have a mapping between the Errors argument and the suggested text argument (like a more-complicated Errors object, perhaps). I could probably hack this together for MM 1.1; is there any point in me doing so and shipping diffs to somewhere? i.e. * is anyone working on this, or * is anyone known to be completely reorganizing this source anyway, and * what's the least-painful way to contribute changes? From bwarsaw@cnri.reston.va.us (Barry A. Warsaw) Tue Dec 14 04:46:55 1999 From: bwarsaw@cnri.reston.va.us (Barry A. Warsaw) (Barry A. Warsaw) Date: Mon, 13 Dec 1999 23:46:55 -0500 (EST) Subject: [Mailman-Developers] Wish list item: anyone working on it? References: <199912140151.RAA13497@utopia.West.Sun.COM> Message-ID: <14421.52159.913977.859212@anthem.cnri.reston.va.us> >>>>> "DM" == Dan Mick writes: DM> I see that "AddRequest" sometimes gets called with standard DM> members of Errors, but sometimes gets called with hard-coded DM> strings; what one would need is to regularize all those, and DM> then have a mapping between the Errors argument and the DM> suggested text argument (like a more-complicated Errors DM> object, perhaps). DM> I could probably hack this together for MM 1.1; is there any DM> point in me doing so and shipping diffs to somewhere? All this /has/ changed for the next release, so if you're interested in doing something like this, you'll need to checkout the current CVS tree and produce diffs against that. I suspect the changes will be large enough that a disclaimer or FSF assignment will be required they can be folded into the distribution. -Barry From bwarsaw@cnri.reston.va.us (Barry A. Warsaw) Tue Dec 14 05:17:16 1999 From: bwarsaw@cnri.reston.va.us (Barry A. Warsaw) (Barry A. Warsaw) Date: Tue, 14 Dec 1999 00:17:16 -0500 (EST) Subject: [Mailman-Developers] CVS access via web Message-ID: <14421.53980.59877.30446@anthem.cnri.reston.va.us> FYI: The Mailman CVS tree can be accessed via the web, using Greg Stein's cool ViewCVS stuff. See http://cvs.python.org/cgi-bin/viewcvs.cgi Enjoy! -Barry From ricardo@miss-janet.com Tue Dec 14 07:34:57 1999 From: ricardo@miss-janet.com (Ricardo Kustner) Date: Tue, 14 Dec 1999 08:34:57 +0100 Subject: [Mailman-Developers] illegal seek Message-ID: <19991214083457.A21332@miss-janet.com> >Okay, so sys.stdin isn't seekable everywhere :) Give the below patch >a try. a few days ago Barry send me a patch that fixes an "Illegal Seek" error which I'm getting on my system (in scripts/post)... this hasn't been checked in the CVS yet... but I noticed this problem pops up in other places too... I think my mailinglist isn't working 100% now (but thats what you get for using 'experimental' version ;) ) Mailman/Message.py (49) also does a self.rewindbody(), causing the same error on my system. ... i'm seeing this appear several times a day in the error log so something isn't going that good on my list .... :) i'm curious to know what this problem is related to? is it the C library? my system is running good old libc5 Ricardo. -- From bwarsaw@cnri.reston.va.us (Barry A. Warsaw) Tue Dec 14 16:30:54 1999 From: bwarsaw@cnri.reston.va.us (Barry A. Warsaw) (Barry A. Warsaw) Date: Tue, 14 Dec 1999 11:30:54 -0500 (EST) Subject: [Mailman-Developers] illegal seek References: <19991214083457.A21332@miss-janet.com> Message-ID: <14422.28862.425131.935200@anthem.cnri.reston.va.us> >>>>> "RK" == Ricardo Kustner writes: RK> a few days ago Barry send me a patch that fixes an "Illegal RK> Seek" error which I'm getting on my system (in RK> scripts/post)... this hasn't been checked in the CVS RK> yet... I just checked it in. RK> but I noticed this problem pops up in other places too... I RK> think my mailinglist isn't working 100% now (but thats what RK> you get for using 'experimental' version ;) ) RK> Mailman/Message.py (49) also does a self.rewindbody(), causing RK> the same error on my system. ... stdin can't be guaranteed to be seekable, so for portability we should read it into a StringIO object and use that as the underlying `file-like input'. Can you tell me what else breaks? A quick grep through the source shows that mailcmd is probably broken (i.e. yourlist-request I'll bet doesn't work). I'll check in some patches for that next. -Barry From mats@laplaza.org Tue Dec 14 17:03:33 1999 From: mats@laplaza.org (Mats Wichmann) Date: Tue, 14 Dec 1999 10:03:33 -0700 Subject: [Mailman-Developers] Re: [Mailman-Users] fetch by email In-Reply-To: <14422.30277.889782.393367@anthem.cnri.reston.va.us> References: <199912141203.MAA25090@ma101.gold.ac.uk> <3.0.6.32.19991214073542.00fab5c0@laplaza.org> Message-ID: <3.0.6.32.19991214100333.00e429f0@laplaza.org> At 11:54 AM 12/14/1999 -0500, you wrote: > >>>>>> "MW" == Mats Wichmann writes: > > MW> That is - fetch-by-email of arbitrary files from an archive > MW> area. In addition to automatically generated archives > MW> which mailman makes available in downloadable form via > MW> a web page, can an arbitrary file be added to the area and > MW> picked up - and is there a way archive files can be picked > MW> up by email request? > >Mailman currently doesn't support this, but it would not be hard to >add, if you're up for a bit of Python hacking. If you think you'd >like to implement something like this, please move the discussion over >to mailman-developers where we can design an approach. > >-Barry I'm game to try, since I have the incentive to get this working.... So...consider it moved. Mats From Dan Mick Wed Dec 15 05:45:53 1999 From: Dan Mick (Dan Mick) Date: Tue, 14 Dec 1999 21:45:53 -0800 (PST) Subject: [Mailman-Developers] Secure admin pages Message-ID: <199912150546.VAA22956@utopia.West.Sun.COM> We set up an SSL arrangement so our admin password isn't traversing the net in clear text, but were temporarily thwarted by the fact that the admin CGI scripts sometimes use Absolute paths, which didn't include the https://. I made some hacks; comments? (Does this look right, Barry et. al.?) (This is to v1.1; if it looks good, I'll put it in CVS and put it back) How does the putback process usually work? Does someone review code, or do we have a "holding area" that's protected somehow, or?... Anyway, here are context diffs: =================================================================== RCS file: RCS/admin.py,v retrieving revision 1.1 diff -c -r1.1 admin.py *** admin.py 1999/12/15 05:29:10 1.1 --- admin.py 1999/12/15 05:29:50 *************** *** 534,540 **** buttons = [] for ci in chunk_indices: start, end = chunks[ci][0], chunks[ci][-1] ! url = lst.GetAbsoluteScriptURL('admin') buttons.append(" from %s to %s " % ( url, ci, start, end)) buttons = apply(UnorderedList, tuple(buttons)) --- 534,540 ---- buttons = [] for ci in chunk_indices: start, end = chunks[ci][0], chunks[ci][-1] ! url = lst.GetRelativeScriptURL('admin') buttons.append(" from %s to %s " % ( url, ci, start, end)) buttons = apply(UnorderedList, tuple(buttons)) *************** *** 544,550 **** footer = "

" for member in all: mtext = '%s' % ( ! lst.GetAbsoluteOptionsURL(member, obscured=1), lst.GetUserSubscribedAddress(member)) cells = [mtext + "" % (member), Center(CheckBox(member + "_subscribed", "on", 1).Format())] --- 544,550 ---- footer = "

" for member in all: mtext = '%s' % ( ! lst.GetRelativeOptionsURL(member, obscured=1), lst.GetUserSubscribedAddress(member)) cells = [mtext + "" % (member), Center(CheckBox(member + "_subscribed", "on", 1).Format())] =================================================================== RCS file: RCS/MailList.py,v retrieving revision 1.1 diff -c -r1.1 MailList.py *** MailList.py 1999/12/15 05:30:09 1.1 --- MailList.py 1999/12/15 05:31:01 *************** *** 194,199 **** --- 194,209 ---- treated = addr return "%s/%s" % (options, treated) + def GetRelativeOptionsURL(self, addr, obscured=0): + # address could come in case-preserved + addr = string.lower(addr) + options = self.GetRelativeScriptURL('options') + if obscured: + treated = Utils.ObscureEmail(addr, for_text=0) + else: + treated = addr + return "%s/%s" % (options, treated) + def GetUserOption(self, user, option): """Return user's setting for option, defaulting to 0 if no settings.""" user = self.GetUserCanonicalAddress(user) From luca.ghedini@mail.ing.unibo.it Wed Dec 15 16:38:17 1999 From: luca.ghedini@mail.ing.unibo.it (Luca ghedini) Date: Wed, 15 Dec 1999 17:38:17 +0100 Subject: [Mailman-Developers] subscriber additional data References: <19991214083457.A21332@miss-janet.com> Message-ID: <3857C3F9.E5BA72B9@mail.ing.unibo.it> HI. I'm using mailman to manage a bunk of mailing list. Is it possible store some information about the subscriber? It will be usefull store some personal data as real name, adresses, tel num. etc? Tnk in advance Luca "ghedo" ghedini From lalo@webcom.com Thu Dec 16 11:00:58 1999 From: lalo@webcom.com (Lalo Martins) Date: Thu, 16 Dec 1999 09:00:58 -0200 Subject: [Mailman-Developers] Technical CGI question Message-ID: <19991216090058.B15823@webcom.com> Hi. I'm not currently subscribed to this list, but I probably will as soon as I get back from vacation. I'm writing a Zope Product to interface with Mailman, for sites (like mine) that don't do any webserving stuff outside Zope. I chose Mailman mostly because it's Python-based, and GNU. After the introduction... I'm at step 1, which is trying to figure out mailman's internals, specially the CGI stuff. What I'd like to know is, is there any good reason why you run all your CGI interface trough a compiled wrapper, instead of just directly running the python scripts? I found out python is quite cool for CGI (before I found out Zope and dumped CGI completely). And of course you know that the python path stuff is quite easy to solve. (Of course, please CC replies back to me. I'll be glad to discuss arguments when I'm back, for now I only want a quick explanation.) []s, |alo +---- -- I am Lalo of deB-org. You will be freed. Resistance is futile. http://www.webcom.com/lalo mailto:lalo@webcom.com pgp key in the web page Debian GNU/Linux --- http://www.debian.org Brazil of Darkness -- http://zope.gf.com.br/BroDar From mr@uniway.be Thu Dec 16 14:18:58 1999 From: mr@uniway.be (mr) Date: Thu, 16 Dec 1999 15:18:58 +0100 Subject: [Mailman-Developers] [Fwd: [Mailman-Users] Cron Daemon errors] Message-ID: <3858F4D2.A88CE3A0@uniway.be> --------------06478C8F0600EC889B40BA04 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit mr wrote: > Hello, > > I just learned about and am using mailman in my job. I have installed > it and have got it half-way working (I see the "Your New Mailing List" > mail and can click on these links. However I do not understand the > error messages I am receiving from the Cron Daemon. The most important > one being (I believe, because it is the first one I always receive): > > Traceback (innermost last): > File "/home/mailman/cron/gate_news", line 119, in ? > main() > File "/home/mailman/cron/gate_news", line 58, in main > mlist = MailList.MailList(name, lock=0) > File "/home/mailman/Mailman/MailList.py", line 62, in __init__ > self.Load() > File "/home/mailman/Mailman/MailList.py", line 810, in Load > raise Errors.MMBadListError, 'Failed to access config info' > MMBadListError: Failed to access config info > > I have just been able to locate these errors but have no idea what > these errors mean or how to fix them. > > Can someone help me? > > Thanks in advance, > > Kirsten Melanie Royal > > -- > > "?.I don't have to eat, I don't have to drink, I just have to study." > > -- "?.I don't have to eat, I don't have to drink, I just have to study." --------------06478C8F0600EC889B40BA04 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit mr wrote:

Hello,

I just learned about and am using mailman in my job. I have installed it and have got it half-way working (I see the "Your New Mailing List" mail and can click on these links. However I do not understand the error messages I am receiving from the Cron Daemon. The most important one being (I believe, because it is the first one I always receive):

Traceback (innermost last):
File "/home/mailman/cron/gate_news", line 119, in ?
main()
File "/home/mailman/cron/gate_news", line 58, in main
mlist = MailList.MailList(name, lock=0)
File "/home/mailman/Mailman/MailList.py", line 62, in __init__
self.Load()
File "/home/mailman/Mailman/MailList.py", line 810, in Load
raise Errors.MMBadListError, 'Failed to access config info'
MMBadListError: Failed to access config info

I have just been able to locate these errors but have no idea what these errors mean or how to fix them.

Can someone help me?

Thanks in advance,

Kirsten Melanie Royal 

-- 

"?.I don't have to eat, I don't have to drink, I just have to study."
 
-- 

"?.I don't have to eat, I don't have to drink, I just have to study."
  --------------06478C8F0600EC889B40BA04-- From mr@uniway.be Thu Dec 16 16:09:26 1999 From: mr@uniway.be (mr) Date: Thu, 16 Dec 1999 17:09:26 +0100 Subject: [Mailman-Developers] Cron error messages Message-ID: <38590EB6.A6A8CB78@uniway.be> --------------E3F19FA1CE01AA2848C554B0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hello once again, I have some other messages that I do not understand at all either, here they are: Traceback (innermost last): File "/home/mailman/cron/checkdbs", line 77, in ? main(verbose=(len(sys.argv) > 1 File "/home/mailman/cron/checkdbs", line 34, in main list = MailList.MailList(name, lock = 0) File "/home/mailman/Mailman/MailList.py", line 62, in __init__ self.Load() File "/home/mailman/Mailman/MailList.py", line 810, in Load raise Errors.MMBadListError, 'Failed to access config info' MMBadListError: Failed to access config info AND Traceback (innermost last): File "/home/mailman/cron/run_queue", line 46, in ? main() File "/home/mailman/cron/run_queue", line 39, in main lockfile.lock() File "/home/mailman/Mailman/LockFile.py", line 186, in lock os.link(self.__lockfile, self.__tmpfname) OSError: [Errno 2] No such file or directory IN ADDITION TO: Traceback (innermost last): File "/home/mailman/cron/gate_news", line 119, in ? main() File "/home/mailman/cron/gate_news", line 58, in main mlist = MailList.MailList(name, lock=0) File "/home/mailman/Mailman/MailList.py", line 62, in __init__ self.Load() File "/home/mailman/Mailman/MailList.py", line 810, in Load raise Errors.MMBadListError, 'Failed to access config info' MMBadListError: Failed to access config info Like I said in a previous message, I see my "Your new mailing list" page and I can click on the links but I have these errors. I just got assigned this project to use mailman a week ago and have never heard about it before that time so I am very sorry if my explainations are not very good ones. Another note: I had no errors on the installation. Thank you in advance for any help you can give me. Kirsten Melanie Royal -- "...I don't have to eat, I don't have to drink, I just have to study." --------------E3F19FA1CE01AA2848C554B0 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit Hello once again,

I have some other messages that I do not understand at all either, here they are:
 

Traceback (innermost last):
File "/home/mailman/cron/checkdbs", line 77, in ?
main(verbose=(len(sys.argv) > 1
File "/home/mailman/cron/checkdbs", line 34, in main
list = MailList.MailList(name, lock = 0)
File "/home/mailman/Mailman/MailList.py", line 62, in __init__
self.Load()
File "/home/mailman/Mailman/MailList.py", line 810, in Load
raise Errors.MMBadListError, 'Failed to access config info'
MMBadListError: Failed to access config info

AND

Traceback (innermost last):
File "/home/mailman/cron/run_queue", line 46, in ?
main()
File "/home/mailman/cron/run_queue", line 39, in main
lockfile.lock()
File "/home/mailman/Mailman/LockFile.py", line 186, in lock
os.link(self.__lockfile, self.__tmpfname)
OSError: [Errno 2] No such file or directory

IN ADDITION TO:
 
Traceback (innermost last):  File "/home/mailman/cron/gate_news", line 119, in ?
main()
File "/home/mailman/cron/gate_news", line 58, in main
mlist = MailList.MailList(name, lock=0)
File "/home/mailman/Mailman/MailList.py", line 62, in __init__
self.Load()
File "/home/mailman/Mailman/MailList.py", line 810, in Load
raise Errors.MMBadListError, 'Failed to access config info'
MMBadListError: Failed to access config info

Like I said in a previous message,  I see my "Your new mailing list" page and I can click on the links but I have these
errors. I just got assigned this project to use mailman a week ago and have never heard about it before that time so I am very sorry if my explainations are not very good ones.

Another note: I had no errors on the installation.

Thank you in advance for any help you can give me.

Kirsten Melanie Royal 

-- 

"...I don't have to eat, I don't have to drink, I just have to study."
  --------------E3F19FA1CE01AA2848C554B0-- From bwarsaw@cnri.reston.va.us (Barry A. Warsaw) Fri Dec 17 05:38:46 1999 From: bwarsaw@cnri.reston.va.us (Barry A. Warsaw) (Barry A. Warsaw) Date: Fri, 17 Dec 1999 00:38:46 -0500 (EST) Subject: [Mailman-Developers] Secure admin pages References: <199912150546.VAA22956@utopia.West.Sun.COM> Message-ID: <14425.52326.802876.889079@anthem.cnri.reston.va.us> >>>>> "DM" == Dan Mick writes: DM> We set up an SSL arrangement so our admin password isn't DM> traversing the net in clear text, but were temporarily DM> thwarted by the fact that the admin CGI scripts sometimes use DM> Absolute paths, which didn't include the https://. I made DM> some hacks; comments? (Does this look right, Barry et. al.?) What do you think of the following instead. def GetScriptURL(self, scriptname, relative=0): if relative: prefix = '../' * Utils.GetNestingLevel() elif self.web_page_url: prefix = self.web_page_url else: prefix = mm_cfg.DEFAULT_URL i = len(prefix)-1 while i >= 0 and prefix[i] == '/': i = i - 1 prefix = prefix[:i+1] return '%s/%s%s/%s' % (prefix, scriptname, mm_cfg.CGIEXT, self.internal_name()) def GetOptionsURL(self, scriptname, obscure=0, relative=0): addr = string.lower(addr) url = self.GetScriptURL('options', relative) if obscured: addr = Utils.ObscureEmail(addr) return '%s/%s' % (url, addr) and getting rid of GetRelativeScriptURL(), GetAbsoluteScriptURL(), GetAbsoluteOptionsURL(). Also, modifying the rest of the source to use just one of these two new functions. If you like it, I'll make these changes to the CVS tree. DM> How does the putback process usually work? Does someone DM> review code, or do we have a "holding area" that's protected DM> somehow, or?... Basically, post the code to mailman-developers, or send it to mailman-cabal. It's up to one of the core maintainers to integrate it with the CVS code base. -Barry From ricardo@miss-janet.com Fri Dec 17 19:31:39 1999 From: ricardo@miss-janet.com (Ricardo Kustner) Date: Fri, 17 Dec 1999 20:31:39 +0100 Subject: [Mailman-Developers] Mailman/Cgi/admindb.py Message-ID: <19991217203139.A21188@miss-janet.com> Hi, I've added to following lines of code to seperate the message body from the header in PrintPostRequest() around line 197 ... fp = open(os.path.join(mm_cfg.DATA_DIR, filename)) # text = fp.read(mm_cfg.ADMINDB_PAGE_TEXT_LIMIT) msg_header = "" msg_body = "" for line in fp.readlines(): if msg_body == "": if line != "\n": msg_header = msg_header + line else: msg_body = line else: msg_body = msg_body + line fp.close() in my copy of admindb.py i don't need the mail headers, so I just output msg_body in the textarea... but maybe it could be made as an option "Include message headers on approval page Y/N" in the mailinglist configuration... Ricardo. -- From ricardo@miss-janet.com Fri Dec 17 20:23:31 1999 From: ricardo@miss-janet.com (Ricardo Kustner) Date: Fri, 17 Dec 1999 21:23:31 +0100 Subject: [Mailman-Developers] sending mail Message-ID: <19991217212331.A21790@miss-janet.com> Hi, i'd like to add a "send copy of email to..." function inside admindb.py (to optionally allow posts on the approval page to be send to a certain email address)... what i need to do i guess is pipe it to the MTA and only change the "To:" line ... can anybody advise me on which is the best python or MM function to use for this? Thanks, Ricardo. -- From Budde@tu-harburg.de Sun Dec 19 14:54:49 1999 From: Budde@tu-harburg.de (Marco Budde) Date: Sun, 19 Dec 1999 14:54:49 +0000 Subject: [Mailman-Developers] Bad/Invalid email address Message-ID: <385CF1B9.7146E4DF@tu-harburg.de> Hi! When subscribing a local user address like "mbudde" or even "mbudde@local" I get this error message: "Bad/Invalid email address". Why? This is a normal email address. I´m using version 1.0b8. cu, Marco -- -- Linux HOWTOs: Die besten Lösungen der Linuxgemeinde -- ISBN 3-8266-0498-9 Uni: Budde@tu-harburg.de Fido: 2:240/6298.5 Mailbox: mbudde@sms.antar.com http://www.tu-harburg.de/~semb2204/ From mailman-users@python.org Sun Dec 19 23:00:26 1999 From: mailman-users@python.org (Sean Reifschneider) Date: Sun, 19 Dec 1999 16:00:26 -0700 Subject: [Mailman-Developers] Bad/Invalid email address In-Reply-To: <385CF1B9.7146E4DF@tu-harburg.de>; from Marco Budde on Sun, Dec 19, 1999 at 02:54:49PM +0000 References: <385CF1B9.7146E4DF@tu-harburg.de> Message-ID: <19991219160026.E26508@tummy.com> [I'm setting replies to go to mailman-users] On Sun, Dec 19, 1999 at 02:54:49PM +0000, Marco Budde wrote: >When subscribing a local user address like >"mbudde" or even "mbudde@local" I get this >error message: "Bad/Invalid email address". > >Why? This is a normal email address. Understand the distinction between "normal" and "valid". You can send mail to a local user simply by specifying "user", however that's because the local MTA does some magic to figure out where it goes. Since mailman has historicly simply handed delivery off to a standard SMTP mail server for the actual delivery, it means that the addresses it gets need to be RFC-822 compliant. I presume if you use "mbudde@domain.com", where "domain.com" is your domain, that it works fine? Mailman is simply being canonical, which IMHO is better than relying on magic to happen behind the scenes. For example, if you specified "mbudde", and then later changed the SMTP server, or moved the mailman installation to another host, the behavior may change. Sean -- If you have too many special cases, you are doing it wrong. -- Craig Zerouni Sean Reifschneider, Inimitably Superfluous URL: HP-UX/Linux/FreeBSD/BSDOS scanning software. From ricardo@miss-janet.com Mon Dec 20 19:29:30 1999 From: ricardo@miss-janet.com (Ricardo Kustner) Date: Mon, 20 Dec 1999 20:29:30 +0100 Subject: [Mailman-Developers] 1.2 bug Message-ID: <19991220202930.B30707@miss-janet.com> Hi, i'm getting the following error often when approving posts on the admindb page... there were 12 posts and about 3 of them were marked as "Discard", the rest was approved... i had this earlier... and when i reloaded the admindb page, some posts showed up again, even though they were send out to the list anyway... Traceback (innermost last): File "/usr/local/mailman/scripts/driver", line 112, in run_main main() File "../Mailman/Cgi/admindb.py", line 123, in main mlist.Save() File "/usr/local/mailman/Mailman/MailList.py", line 814, in Save self.SaveRequestsDb() File "/usr/local/mailman/Mailman/ListAdmin.py", line 89, in SaveRequestsDb self.__closedb() File "/usr/local/mailman/Mailman/ListAdmin.py", line 73, in __closedb assert self.Locked() AssertionError: -- Ricardo. -- International Janet Jackson fanclub called MISS JANET. For more information write to: Miss Janet. P.O.Box 10016, 1001 EA Amsterdam, The Netherlands Fax/phone: +31-(0)20-7764493 Email: fanclub@miss-janet.com Or check out our website: http://miss-janet.com From bwarsaw@cnri.reston.va.us (Barry A. Warsaw) Mon Dec 20 19:35:27 1999 From: bwarsaw@cnri.reston.va.us (Barry A. Warsaw) (Barry A. Warsaw) Date: Mon, 20 Dec 1999 14:35:27 -0500 (EST) Subject: [Mailman-Developers] 1.2 bug References: <19991220202930.B30707@miss-janet.com> Message-ID: <14430.34047.185174.886328@anthem.cnri.reston.va.us> >>>>> "RK" == Ricardo Kustner writes: RK> i'm getting the following error often when approving posts RK> on the admindb page... there were 12 posts and about 3 of RK> them were marked as "Discard", the rest was approved... RK> i had this earlier... and when i reloaded the admindb page, RK> some posts showed up again, even though they were send out RK> to the list anyway... I've seen this too when doing approves of python-list. However, I haven't seen any lately, while using the very freshest CVS update. I'm not sure why these are happening, but I've added more logging to try to help nail down the bug. -Barry From allen@gist.net.au Fri Dec 24 02:50:47 1999 From: allen@gist.net.au (Allen Bolderoff) Date: Fri, 24 Dec 1999 13:20:47 +1030 Subject: [Mailman-Developers] UPDATE-2 - problem with cookies? Round 2 In-Reply-To: Your message of "Thu, 23 Dec 1999 11:10:01 MDT." <014701bf4d68$8e7011b0$ea17a8c0@jordan> Message-ID: <199912240250.NAA13557@harper.gist.net.au> OK. let me clarify myself. it appears, that if mailman has not set a cookie, but a sitewide cookie exists in the browser, mailman will try to use the sitewide cookie, without checking if it is in fact the correct cookie (which at this point is not created). so, instead of creating a new cookie, as it should, it is dying in the process of parsing the wrong cookie. Hope this helps the developers. Allen -- +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Allen Bolderoff LNC - Redhat and Linux, help and commentary http://linux.netnerve.com CTPC - Caffeine - get it here: http://www.coffee-tea-pots-cups.com/ +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ GPG fingerprint = CBB0 8626 702C 3D01 B5AD A54A DC2C 93B7 3E4B 6472 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Return-Path: Delivered-To: mailman-developers@dinsdale.python.org Received: from python.org (parrot.python.org [132.151.1.90]) by dinsdale.python.org (Postfix) with ESMTP id A809B1CD21; Thu, 23 Dec 1999 21:50:36 -0500 (EST) Received: from ns1.gist.net.au (IDENT:root@main.gist.net.au [203.20.102.2]) by python.org (8.9.1a/8.9.1) with ESMTP id VAA21724; Thu, 23 Dec 1999 21:50:33 -0500 (EST) Received: from harper.gist.net.au (root@harper.gist.net.au [203.20.102.68]) by ns1.gist.net.au (8.8.7/8.8.7) with ESMTP id MAA03331; Fri, 24 Dec 1999 12:18:59 +1030 Received: from harper.gist.net.au (IDENT:allen@localhost [127.0.0.1]) by harper.gist.net.au (8.9.3/8.8.7) with ESMTP id NAA13571; Fri, 24 Dec 1999 13:21:14 +1030 Resent-Message-Id: <199912240251.NAA13571@harper.gist.net.au> Message-Id: <199912240251.NAA13571@harper.gist.net.au> X-Mailer: exmh version 2.1.0 To: blurr@txraves.org In-Reply-To: Your message of "Thu, 23 Dec 1999 11:10:01 MDT." <014701bf4d68$8e7011b0$ea17a8c0@jordan> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 24 Dec 1999 13:14:17 +1030 From: Allen Bolderoff Resent-To: mailman-users@python.org Resent-Cc: mailman-developers@python.org Resent-Date: Fri, 24 Dec 1999 13:21:14 +1030 Resent-From: Allen Bolderoff Resent-Sender: allen@harper.gist.net.au Subject: [Mailman-Developers] UPDATE - problem with cookies? Round 2 Sender: mailman-developers-admin@python.org Errors-To: mailman-developers-admin@python.org X-BeenThere: mailman-developers@python.org X-Mailman-Version: 1.2 (experimental) Precedence: bulk List-Id: Mailman mailing list developers > > What would you like us to do? Yes, it looks like a bug. Have you tried > > either examining the cookie or deleting it?... since the error message > > pretty > > clearly points to the file of code, and the code is pretty clearly > > examining > > the cookie data itself and finding something wrong.... > > > > You might add something like > > > > if len(cookiedata) < len(key): return 0 > > > > before > > > > if cookiedata[keylen+1] <> '"' and cookiedata[-1].... > > > > in SecurityManager.py. > > > > I haven't tested the fix, because I don't know if that's what's going > > wrong. This does not work, however, what I can tell you is that if there is another cookie set by the webserver, it appears to confuse mailman. Mailman then tries to use the other cookie. ie - I use roxen - http://www.roxen.com roxen sets a unique cookie for every user that comes to the site. when I turn on the debug messages by removing the commented debug code, and access a bad page, I get the cookie, which is called RoxenUserID showing in the debug file, not the one we would expect. In fact, this seems to happen when the cookie does not exist (the authentication cookie that mailman makesm that is) Hope this helps -- +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Allen Bolderoff LNC - Redhat and Linux, help and commentary http://linux.netnerve.com CTPC - Caffeine - get it here: http://www.coffee-tea-pots-cups.com/ +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ GPG fingerprint = CBB0 8626 702C 3D01 B5AD A54A DC2C 93B7 3E4B 6472 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ From gstein@lyra.org Sun Dec 26 17:58:11 1999 From: gstein@lyra.org (Greg Stein) Date: Sun, 26 Dec 1999 09:58:11 -0800 (PST) Subject: [Mailman-Developers] Error encountered on the Mailman webpage (fwd) Message-ID: This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. ------_=_NextPart_000_01BF4FBE.BCC7413E Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-ID: -- Greg Stein, http://www.lyra.org/ ---------- Forwarded message ---------- Date: Sun, 26 Dec 1999 11:32:01 -0500 From: Aaron La Mar To: "'webmaster@list.org '" Subject: Error encountered on the Mailman webpage I got the following error when I clicked on "Mailman-Users" on your index page. Bug in Mailman version 1.2 (experimental) 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 (innermost last): File "/home/mailman/scripts/driver", line 112, in run_main main() File "/home/mailman/Mailman/Cgi/listinfo.py", line 54, in main FormatListListinfo(mlist) File "/home/mailman/Mailman/Cgi/listinfo.py", line 163, in FormatListListinfo replacements = mlist.GetStandardReplacements() File "/home/mailman/Mailman/HTMLFormatter.py", line 347, in GetStandardReplacements return { File "/home/mailman/Mailman/HTMLFormatter.py", line 50, in GetMailmanFooter Address( File "/home/mailman/Mailman/MailList.py", line 209, in GetRelativeScriptURL return GetScriptURL(self, scriptname, relative=1) NameError: GetScriptURL ---------------------------------------------------------------------------- ---- Environment variables: Variable Value DOCUMENT_ROOT /usr/local/apache/htdocs SERVER_ADDR 132.151.1.21 HTTP_ACCEPT_ENCODING gzip, deflate REMOTE_HOST parrot.python.org SERVER_PORT 80 PATH_TRANSLATED /usr/local/apache/htdocs/mailman-users REMOTE_ADDR 132.151.1.90 HTTP_ACCEPT_LANGUAGE en-us GATEWAY_INTERFACE CGI/1.1 SERVER_NAME dinsdale.python.org TZ US/Eastern HTTP_USER_AGENT Mozilla/4.0 (compatible; MSIE 5.0; Windows 98; DigExt) HTTP_ACCEPT image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, application/vnd.ms-excel, application/msword, application/vnd.ms-powerpoint, */* REQUEST_URI /mailman/listinfo/mailman-users PATH /usr/sbin:/usr/bin QUERY_STRING SCRIPT_FILENAME /home/mailman/cgi-bin/listinfo PATH_INFO /mailman-users HTTP_HOST dinsdale.python.org REQUEST_METHOD GET SERVER_SIGNATURE Apache/1.3.9 Server at dinsdale.python.org Port 80 SCRIPT_NAME /mailman/listinfo SERVER_ADMIN webmaster@python.org SERVER_SOFTWARE Apache/1.3.9 (Unix) PYTHONPATH /home/mailman HTTP_REFERER http://www.list.org/ SERVER_PROTOCOL HTTP/1.0 REMOTE_PORT 58702 ------_=_NextPart_000_01BF4FBE.BCC7413E Content-Type: APPLICATION/OCTET-STREAM; NAME="Bug in Mailman version 1_2 (experimental).htm" Content-ID: Content-Description: Content-Disposition: ATTACHMENT; FILENAME="Bug in Mailman version 1_2 (experimental).htm" Bug in Mailman version 1.2 (experimental)

Bug in Mailman version 1.2 (experimental)

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 (innermost last):
  File "/home/mailman/scripts/driver", line 112, in run_main
    main()
  File "/home/mailman/Mailman/Cgi/listinfo.py", line 54, in main
    FormatListListinfo(mlist)
  File "/home/mailman/Mailman/Cgi/listinfo.py", line 163, in FormatListListinfo
    replacements = mlist.GetStandardReplacements()
  File "/home/mailman/Mailman/HTMLFormatter.py", line 347, in GetStandardReplacements
    return {
  File "/home/mailman/Mailman/HTMLFormatter.py", line 50, in GetMailmanFooter
    Address(
  File "/home/mailman/Mailman/MailList.py", line 209, in GetRelativeScriptURL
    return GetScriptURL(self, scriptname, relative=1)
NameError: GetScriptURL

Environment variables:

Variable Value
DOCUMENT_ROOT /usr/local/apache/htdocs
SERVER_ADDR 132.151.1.21
HTTP_ACCEPT_ENCODING gzip, deflate
REMOTE_HOST parrot.python.org
SERVER_PORT 80
PATH_TRANSLATED /usr/local/apache/htdocs/mailman-users
REMOTE_ADDR 132.151.1.90
HTTP_ACCEPT_LANGUAGE en-us
GATEWAY_INTERFACE CGI/1.1
SERVER_NAME dinsdale.python.org
TZ US/Eastern
HTTP_USER_AGENT Mozilla/4.0 (compatible; MSIE 5.0; Windows 98; DigExt)
HTTP_ACCEPT */*
REQUEST_URI /mailman/listinfo/mailman-users
PATH /usr/sbin:/usr/bin
QUERY_STRING
SCRIPT_FILENAME /home/mailman/cgi-bin/listinfo
PATH_INFO /mailman-users
HTTP_HOST dinsdale.python.org
REQUEST_METHOD GET
SERVER_SIGNATURE
Apache/1.3.9 Server at dinsdale.python.org Port 80
SCRIPT_NAME /mailman/listinfo
SERVER_ADMIN webmaster@python.org
SERVER_SOFTWARE Apache/1.3.9 (Unix)
PYTHONPATH /home/mailman
SERVER_PROTOCOL HTTP/1.0
REMOTE_PORT 58710

------_=_NextPart_000_01BF4FBE.BCC7413E-- From bwarsaw@python.org Sun Dec 26 19:24:47 1999 From: bwarsaw@python.org (Barry A. Warsaw) Date: Sun, 26 Dec 1999 14:24:47 -0500 (EST) Subject: [Mailman-Developers] Re: Error encountered on the Mailman webpage (fwd) References: Message-ID: <14438.27519.908881.720297@anthem.cnri.reston.va.us> Temporary glitch, now fixed. From bwarsaw@cnri.reston.va.us (Barry A. Warsaw) Mon Dec 27 16:18:23 1999 From: bwarsaw@cnri.reston.va.us (Barry A. Warsaw) (Barry A. Warsaw) Date: Mon, 27 Dec 1999 11:18:23 -0500 (EST) Subject: [Mailman-Developers] New mailing list for internationalization Message-ID: <14439.37199.785784.796071@anthem.cnri.reston.va.us> Mailman Developers, I have created a new mailing list called mailman-i18n@python.org for discussions focused on internationalizing Mailman. This SIG has a very narrow mission: at first it will be to discuss design issues and patches to the source code to support multi-lingual mailing lists. Once that is integrated into the codebase, the SIG will primarily be a forum for translators. I urge any interested parties to subscribe by visiting http://www.python.org/mailman/listinfo/mailman-i18n I'd like to keep I18N discussions off of mailman-developers. Current status: I received a large patchset from Juan and Victoriano, which contained some stuff by Mads and others, which I started looking at over the Xmas break. I'd like to move all private discussions on this stuff to the SIG so everyone can contribute. I plan on posting a more detailed summary to the SIG within a couple of days (I'm too busy right now). That'll also give people a chance to subscribe to the new list. Cheers, -Barry From root@theporch.com Mon Dec 27 22:21:49 1999 From: root@theporch.com (Phillip Porch) Date: Mon, 27 Dec 1999 16:21:49 -0600 (CST) Subject: [Mailman-Developers] Bug in Mailman version 1.2 (experimental) (fwd) Message-ID: ---------- Forwarded message ---------- Date: Mon, 27 Dec 1999 16:14:43 -0000 From: Phillip Porch To: root@theporch.com Subject: Bug in Mailman version 1.2 (experimental) Bug in Mailman version 1.2 (experimental) Bug in Mailman version 1.2 (experimental) 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 (innermost last): File "/home/mailman/scripts/driver", line 112, in run_main main() File "../Mailman/Cgi/admin.py", line 165, in main FormatConfiguration(doc, mlist, category, category_suffix, cgi_data) File "../Mailman/Cgi/admin.py", line 311, in FormatConfiguration form.AddItem(FormatOptionsSection(category, mlist, cgi_data)) File "../Mailman/Cgi/admin.py", line 326, in FormatOptionsSection return FormatMembershipOptions(mlist, cgi_data) File "../Mailman/Cgi/admin.py", line 565, in FormatMembershipOptions mtext = '%s' % ( TypeError: unexpected keyword argument: obscured -------------------------------------------------------------------------------- Environment variables: Variable Value DOCUMENT_ROOT /home SERVER_ADDR 207.234.31.38 HTTP_ACCEPT_ENCODING gzip, deflate SERVER_PORT 8080 PATH_TRANSLATED /home/notam/members REMOTE_ADDR 207.234.31.43 HTTP_ACCEPT_LANGUAGE en-us GATEWAY_INTERFACE CGI/1.1 SERVER_NAME sco.theporch.com TZ CST6CDT HTTP_USER_AGENT Mozilla/4.0 (compatible; MSIE 5.01; Windows 98) QUERY_STRING HTTP_ACCEPT image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, */* REQUEST_URI /mailman/admin/notam/members PATH /etc:/bin:/usr/bin REMOTE_PORT 1052 SCRIPT_FILENAME /home/mailman/cgi-bin/admin PATH_INFO /notam/members HTTP_HOST www.theporch.com:8080 REQUEST_METHOD GET SERVER_SIGNATURE Apache/1.3.9 Server at sco.theporch.com Port 8080 SCRIPT_NAME /mailman/admin SERVER_ADMIN root@sco.theporch.com SERVER_SOFTWARE Apache/1.3.9 (Unix) PYTHONPATH /home/mailman HTTP_COOKIE notam:admin="(lp1\012F946332841.40999997\012aI946343641\012aS'^g\\304\\245\\300Bop\\356\\261\\020\\332\\005\\324\\245\\026'\012p2\012a." SERVER_PROTOCOL HTTP/1.1 HTTP_CONNECTION Keep-Alive HTTP_REFERER http://www.theporch.com:8080/mailman/admin/notam From bwarsaw@cnri.reston.va.us (Barry A. Warsaw) Mon Dec 27 22:28:48 1999 From: bwarsaw@cnri.reston.va.us (Barry A. Warsaw) (Barry A. Warsaw) Date: Mon, 27 Dec 1999 17:28:48 -0500 (EST) Subject: [Mailman-Developers] Bug in Mailman version 1.2 (experimental) (fwd) References: Message-ID: <14439.59424.716696.37336@anthem.cnri.reston.va.us> Thanks, fixed. From pfaff@edge.cis.mcmaster.ca Thu Dec 2 16:26:24 1999 From: pfaff@edge.cis.mcmaster.ca (Todd Pfaff) Date: Thu, 2 Dec 1999 11:26:24 -0500 (EST) Subject: [Mailman-Developers] LogMsg problem Message-ID: I'm using mailman 1.1. One of our lists consistently generates the following python traceback in the mailman error log whenever a message is posted to the list. Dec 01 13:22:45 1999 post: Traceback (innermost last): post: File "/usr/local/mailman/scripts/mailowner", line 45, in ? post: if not mlist.bounce_processing or not mlist.ScanMessage(msg): post: File "/usr/local/mailman/Mailman/Bouncer.py", line 449, in ScanMessage post: self.RegisterBounce(who, msg) post: File "/usr/local/mailman/Mailman/Bouncer.py", line 138, in RegisterBounce post: self.LogMsg("bounce", report + "exceeded limits") post: File "/usr/local/mailman/Mailman/MailList.py", line 834, in LogMsg post: logf.write(msg % args + '\n') post: TypeError : not enough arguments for format string I've had a look at the call to LogMsg() in MailList.py from RegisterBounce() in Bouncer.py, so I sort of where the error is happening. As far as I can tell, there must be some instances where LogMsg is being called with a "msg" argument that contains % variable substitutions that have not yet been satisfied, but with an empty or insufficient "args" tuple. So, when LogMsg calls logf.write(msg % args + '\n'), the % substitution fails. It seems that, in general, the use of LogMsg is inconsistent. In some cases, a variable length args tuple is passed to LogMsg and the string formatting is done within LogMsg, but in many other cases any string formatting is done before the call to LogMsg and LogMsg is called without an args tuple. It's entirely possible that something will call LogMsg with a "msg" argument that contains a valid % substitution string even though they did not intend for a % substitution to happen. I think this is what may be happening in my case - the RegisterBounce() function builds the "msg" string from other variable strings and one of these strings may contain a % substitution string. This msg string is then passed to LogMsg but without an args tuple to satisfy the % substitution. I'm no Python expert - I just started learning it a few weeks ago - but I'm trying to think of ways to debug this, or handle the situation more gracefully. I've been poking through the Python books I have and looking at the exception handling stuff. I've come up with the following simple idea for handling this in LogMsg(). Any opinions about whether this is a good idea, whether it will work, or whether there is a better way to approach this problem? try: logf.write(msg % args + '\n') except: logf.write(msg + '\n') -- Todd Pfaff \ Email: pfaff@mcmaster.ca Computing and Information Services \ Voice: (905) 525-9140 x22920 ABB 132 \ FAX: (905) 528-3773 McMaster University \ Hamilton, Ontario, Canada L8S 4M1 \ From pfaff@edge.cis.mcmaster.ca Thu Dec 2 16:57:21 1999 From: pfaff@edge.cis.mcmaster.ca (Todd Pfaff) Date: Thu, 2 Dec 1999 11:57:21 -0500 (EST) Subject: [Mailman-Developers] Re: [Mailman-Users] LogMsg problem In-Reply-To: Message-ID: Sure enough! This was exactly the problem! After applying the 'try: except:' fix I suggested below I no longer get the error traceback from LogMsg and I see the following in the bounce log. It was the email address string containing % characters in LogMsg called from RegisterBounce that was causing the failure. Dec 02 11:47:26 1999 cdn-nucl-l: DXS9%OPS%DCPP@bangate.pge.com - exceeded limits Dec 02 11:47:26 1999 cdn-nucl-l: disabled dxs9%ops%dcpp@bangate.pge.com Dec 02 11:47:27 1999 cdn-nucl-l: gonuke@bigfoot.com - first n Thu, 2 Dec 1999, Todd Pfaff wrote: > I'm using mailman 1.1. One of our lists consistently generates the > following python traceback in the mailman error log whenever a message is > posted to the list. > > Dec 01 13:22:45 1999 post: Traceback (innermost last): > post: File "/usr/local/mailman/scripts/mailowner", line 45, in ? > post: if not mlist.bounce_processing or not mlist.ScanMessage(msg): > post: File "/usr/local/mailman/Mailman/Bouncer.py", line 449, in ScanMessage > post: self.RegisterBounce(who, msg) > post: File "/usr/local/mailman/Mailman/Bouncer.py", line 138, in RegisterBounce > post: self.LogMsg("bounce", report + "exceeded limits") > post: File "/usr/local/mailman/Mailman/MailList.py", line 834, in LogMsg > post: logf.write(msg % args + '\n') > post: TypeError : not enough arguments for format string > > > I've had a look at the call to LogMsg() in MailList.py from > RegisterBounce() in Bouncer.py, so I sort of where the error is happening. > As far as I can tell, there must be some instances where LogMsg is being > called with a "msg" argument that contains % variable substitutions that > have not yet been satisfied, but with an empty or insufficient "args" > tuple. So, when LogMsg calls logf.write(msg % args + '\n'), the % > substitution fails. > > It seems that, in general, the use of LogMsg is inconsistent. In some > cases, a variable length args tuple is passed to LogMsg and the string > formatting is done within LogMsg, but in many other cases any string > formatting is done before the call to LogMsg and LogMsg is called without > an args tuple. > > It's entirely possible that something will call LogMsg with a "msg" > argument that contains a valid % substitution string even though they did > not intend for a % substitution to happen. I think this is what may be > happening in my case - the RegisterBounce() function builds the "msg" > string from other variable strings and one of these strings may contain a > % substitution string. This msg string is then passed to LogMsg but > without an args tuple to satisfy the % substitution. > > I'm no Python expert - I just started learning it a few weeks ago - but > I'm trying to think of ways to debug this, or handle the situation more > gracefully. I've been poking through the Python books I have and looking > at the exception handling stuff. I've come up with the following simple > idea for handling this in LogMsg(). Any opinions about whether this is a > good idea, whether it will work, or whether there is a better way to > approach this problem? > > try: > logf.write(msg % args + '\n') > except: > logf.write(msg + '\n') > > -- > Todd Pfaff \ Email: pfaff@mcmaster.ca > Computing and Information Services \ Voice: (905) 525-9140 x22920 > ABB 132 \ FAX: (905) 528-3773 > McMaster University \ > Hamilton, Ontario, Canada L8S 4M1 \ > > > ------------------------------------------------------ > Mailman-Users maillist - Mailman-Users@python.org > http://www.python.org/mailman/listinfo/mailman-users > -- Todd Pfaff \ Email: pfaff@mcmaster.ca Computing and Information Services \ Voice: (905) 525-9140 x22920 ABB 132 \ FAX: (905) 528-3773 McMaster University \ Hamilton, Ontario, Canada L8S 4M1 \ From wheakory@isu.edu Thu Dec 2 20:18:24 1999 From: wheakory@isu.edu (Kory Wheatley) Date: Thu, 02 Dec 1999 13:18:24 -0700 Subject: [Mailman-Developers] Run_queue Process Message-ID: <3846D40F.C9253543@isu.edu> Where in the directory structure of mailman does queued mail get placed for the cron job "run_queue" to process if the message failed to deliver the first time or the host machine was down at the time, because there are times where I don't want these messaged to be resent. I would rather deleted them then have run_queue send them out, because I had one list that had subscribed the wrong email address for 2000 users to the list and it kept trying to resend them which caused performance problems do I need to adjust sendmail to handle a situation like this? I would like to basically know how to delete the mail queue messages sometimes if I know there is going to be a lot of queued mail that I don't want delivered. -- Kory Wheatley Office Phone 236-3874 Computing & Communication Academic Computing Analyst sr. Everything you do must point to him. From claw@kanga.nu Thu Dec 2 20:32:24 1999 From: claw@kanga.nu (claw@kanga.nu) Date: Thu, 02 Dec 1999 12:32:24 -0800 Subject: [Mailman-Developers] Run_queue Process In-Reply-To: Message from Kory Wheatley of "Thu, 02 Dec 1999 13:18:24 MST." <3846D40F.C9253543@isu.edu> Message-ID: On Thu, 02 Dec 1999 13:18:24 -0700 Kory Wheatley wrote: > I would like to basically know how to delete the mail queue > messages sometimes if I know there is going to be a lot of queued > mail that I don't want delivered. IIRC (can't check now) it is stored inside the config.db for the list. Removing that mail is a question of unpickling the DB and removing the approriate records. <> -- J C Lawrence Home: claw@kanga.nu ----------(*) Other: coder@kanga.nu --=| A man is as sane as he is dangerous to his environment |=-- From bwarsaw@cnri.reston.va.us (Barry A. Warsaw) Fri Dec 3 05:20:01 1999 From: bwarsaw@cnri.reston.va.us (Barry A. Warsaw) (Barry A. Warsaw) Date: Fri, 3 Dec 1999 00:20:01 -0500 (EST) Subject: [Mailman-Developers] Re: [Mailman-Users] LogMsg problem References: Message-ID: <14407.21249.279263.173837@anthem.cnri.reston.va.us> >>>>> "TP" == Todd Pfaff writes: TP> It seems that, in general, the use of LogMsg is inconsistent. You're right about that. It would be a good thing to clean up the use of LogMsg. I usually do the substitution before passing it to LogMsg, but some of the older code does it the other way. TP> Any opinions about whether this is TP> a good idea, whether it will work, or whether there is a TP> better way to approach this problem? | try: | logf.write(msg % args + '\n') | except: | logf.write(msg + '\n') Just a point of Python style. It's almost never appropriate to use a "bare" except like this because it can mask unexpected exceptions. In this case using "except TypeError" would do the trick. This is probably okay as a stopgap, but it would be better to make the use of LogMsg more consistent. -Barry From bwarsaw@cnri.reston.va.us (Barry A. Warsaw) Fri Dec 3 05:44:32 1999 From: bwarsaw@cnri.reston.va.us (Barry A. Warsaw) (Barry A. Warsaw) Date: Fri, 3 Dec 1999 00:44:32 -0500 (EST) Subject: [Mailman-Developers] Run_queue Process References: <3846D40F.C9253543@isu.edu> Message-ID: <14407.22720.10243.882151@anthem.cnri.reston.va.us> >>>>> "claw" == writes: >> I would like to basically know how to delete the mail queue >> messages sometimes if I know there is going to be a lot of >> queued mail that I don't want delivered. claw> IIRC (can't check now) it is stored inside the config.db for claw> the list. Removing that mail is a question of unpickling claw> the DB and removing the approriate records. Actually, I don't think so. I think those queued messages are just gleaned from the file system. claw> <> And in fact, all this has changed in my current codebase. There's no queueing going on. I have two delivery modules, one that pipes to the command line interface of sendmail, the other which does direct smtp delivery to the local smtpd. This latter only handles error codes >= 500 (permanent errors), in which case it'll register a bounce to that addr just as if a bounce message was received. However, at least with Postfix, it appears that you never get error reports for non-local addrs. The dialog with the local smtpd seems nearly asynchronous, which is actually a good thing. If Postfix can't deliver the message, it'll generate a bounce message for it (more on this in another follow up). I believe this all works differently if the MTA supports DSN (delivery status notification), which sendmail does, but postfix does not. In that case, if you enable DSN, delivery becomes synchronous, and you do end up getting error codes back for failures. The problem with the synchronous deliveries is that you can't keep list object locked while that happens. I'm beginning to think it's best not to do DSN and just improve the bounce detection, or do the VERP-like approach discussed earlier. I think Dragon has said that he's got a better bulk mailer implementation that he's been using for a while. I think he's talked about porting it to the new delivery pipeline code, which would be cool to have as an alternative approach. -Barry From pfaff@edge.cis.mcmaster.ca Fri Dec 3 15:52:47 1999 From: pfaff@edge.cis.mcmaster.ca (Todd Pfaff) Date: Fri, 3 Dec 1999 10:52:47 -0500 (EST) Subject: [Mailman-Developers] Re: [Mailman-Users] LogMsg problem In-Reply-To: <14407.21249.279263.173837@anthem.cnri.reston.va.us> Message-ID: On Fri, 3 Dec 1999, Barry A. Warsaw wrote: > TP> It seems that, in general, the use of LogMsg is inconsistent. > > You're right about that. It would be a good thing to clean up the use > of LogMsg. I usually do the substitution before passing it to LogMsg, > but some of the older code does it the other way. > > TP> Any opinions about whether this is > TP> a good idea, whether it will work, or whether there is a > TP> better way to approach this problem? > > | try: > | logf.write(msg % args + '\n') > | except: > | logf.write(msg + '\n') > > Just a point of Python style. It's almost never appropriate to use a > "bare" except like this because it can mask unexpected exceptions. In > this case using "except TypeError" would do the trick. ok, thanks for the tip. > This is probably okay as a stopgap, but it would be better to make the > use of LogMsg more consistent. it wouldn't be a big job. there are only about 50 occurrences of LogMsg calls in all files under the Mailman python directory, and of these, only about 20 seem to have '%' substitution characters in the msg argument: cd ~mailman/Mailman grep LogMsg * | grep '%' | wc the ones that pass an arg tuple would simply have to be changed so that the ',' between the msg and args arguments is a '%' to do the substitutions before the call. then, remove the '%' substitution in LogMsg. -- Todd Pfaff \ Email: pfaff@mcmaster.ca Computing and Information Services \ Voice: (905) 525-9140 x22920 ABB 132 \ FAX: (905) 528-3773 McMaster University \ Hamilton, Ontario, Canada L8S 4M1 \ From randhir@kalpadrum.com Sat Dec 4 08:53:53 1999 From: randhir@kalpadrum.com (Randhir Shinde) Date: Sat, 4 Dec 1999 14:23:53 +0530 Subject: [Mailman-Developers] I want to transfer a mail to a program Message-ID: <01BF3E63.664EFC00@randhir> I am writing a Script. Now what I want to do is when I send a mail to a = list member in a mailman, I want to direct the mail to a program which = can be a script or a servlet or anything that can execute on the server. = The task of this script shall be to save the received mail to a file.=20 Can some one tell me how this can be done Randhir From ricardo@miss-janet.com Sat Dec 4 22:54:39 1999 From: ricardo@miss-janet.com (Ricardo Kustner) Date: Sat, 4 Dec 1999 23:54:39 +0100 Subject: [Mailman-Developers] bulkmailing & admin interface Message-ID: <19991204235439.A1308@miss-janet.com> Hi, the MM feature list says: "Direct SMTP delivery of messages, including integrated fast bulk mailing." i guess this is build into mailman to speed up mail delivery... but when mail is send out during approving (many) held back messages through the web admin interface, i wonder if it's still effective to use this bulk mailing technique? when all messages need improval before being send out, it's no use to have mailman try his best to deliver the mail as quickly as possible anyway... I don't know much about the way MM delivers mail, but some big annoyances i've had with using MM are that when approving several messages from the admin interface : (a) the cgi process(es) takes *too* long to finnish (causing timeouts sometimes) and (b) they cause a huge load on the system. Would it be possible to be able to choose for a "relaxed" way of delevering mail in certain situations? i'd rather have the messages being delivered with a small delay then MM trying hard to be as quick as possible with delivery... hoping for at least one reaction to this email, :) Ricardo. -- From richarde@eskom.co.za Mon Dec 6 06:52:10 1999 From: richarde@eskom.co.za (Richard Ellerbrock) Date: Mon, 06 Dec 1999 08:52:10 +0200 Subject: [Mailman-Developers] I want to transfer a mail to a program Message-ID: >I am writing a Script. Now what I want to do is when I send a mail to a = list=20 >member in a mailman, I want to direct the mail to a program which can be = a=20 >script or a servlet or anything that can execute on the server. The task = of=20 >this script shall be to save the received mail to a file.=20 > >Can some one tell me how this can be done You probably want to use procmail as a front to mailman. Modify your alias = file and run the message through procmail first, and then pass it to = mailman. I did a similar trick to block external e-mails to mailman to = prevent non-employees being able to subscribe to our internal lists. = Mailman cannot do this. Here is the method: Modify /etc/aliases: www-request: "|/usr/bin/procmail -m LIST=3D'www' /etc/mail/procm= ailrc.lists" This will call procmail instead of mailman. Mailman is called inside the = procmail script: :0 # pass along all mail for eskom * ^From:.*eskom.co.za | /home/mailman/mail/wrapper mailcmd $LIST :0 # reply to all mail not from eskom * !^FROM_DAEMON * !^X-Loop: owner-${LIST}@lists.eskom.co.za { :0 hc | (formail -r -A"Precedence: bulk" \ -A"X-Loop: owner-${LIST}@lists.eskom.co.za" ; \ echo "\ This is an ESKOM internal mailing list to which you may not \ subscribe. If you have any queries, contact owner-${LIST}@lists.eskom.co.za= \ for further information.") | \ $SENDMAIL -t -f owner-${LIST}@lists.eskom.co.za } :0 # drop all other mail /dev/null Using this method and the procmailex manpage, you should be able to do = what you want. -- Richard Ellerbrock richarde@eskom.co.za From bwarsaw@CNRI.Reston.VA.US (Barry A. Warsaw) Mon Dec 6 02:58:08 1999 From: bwarsaw@CNRI.Reston.VA.US (Barry A. Warsaw) (Barry A. Warsaw) Date: Sun, 5 Dec 1999 21:58:08 -0500 (EST) Subject: [Mailman-Developers] bulkmailing & admin interface References: <19991204235439.A1308@miss-janet.com> Message-ID: <14411.9792.611960.485273@anthem.cnri.reston.va.us> >>>>> "RK" == Ricardo Kustner writes: RK> I don't know much about the way MM delivers mail, RK> but some big annoyances i've had with using MM are that when RK> approving several messages from the admin interface : (a) the RK> cgi process(es) takes *too* long to finnish (causing timeouts RK> sometimes) and (b) they cause a huge load on the system. RK> Would it be possible to be able to choose for a "relaxed" way RK> of delevering mail in certain situations? i'd rather have the RK> messages being delivered with a small delay then MM trying RK> hard to be as quick as possible with delivery... RK> hoping for at least one reaction to this email, :) Here's one, hopefully the one you're looking for! :) All this stuff has changed in the current codebase, available via CVS. The old bulkmailer stuff is gone and Mailman now has two ways to hand a message off to your MTA: either by calling sendmail (or a sendmail compatible program) via the command line, or talking asynchronously (no-DSN) via SMTP. All these means that the handoff of messages from Mailman to your MTA happens very quickly. Dragon has mentioned that he has a robust bulk-mailer which may get ported to the new codebase and added back in. The neat thing is that with the current architecture, a site could choose any one of these delivery modules, as appropriate for their system (or easily implement their own). -Barry From julian7@kva.hu Mon Dec 6 17:03:05 1999 From: julian7@kva.hu (Balazs Nagy) Date: Mon, 6 Dec 1999 18:03:05 +0100 (CET) Subject: [Mailman-Developers] 8-bit input in administrator menu Message-ID: This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --1825891041-2098212404-944499785=:16442 Content-Type: TEXT/PLAIN; charset=US-ASCII Hi, I did a little digging about entering text with accents. It's a bit curious that one can type accents in textarea but to textbox cannot. In the latter case you can see an escaped print of your input. In the end I came to htmlformat.py's InputObj. At this point I have a humble question: who put `-s around value? After a s/`value`/value/ in line #368, almost everything works fine, because this brings up a problem about quoting. Of course, the patch is here. -- Regards: Kevin (Balazs) --1825891041-2098212404-944499785=:16442 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="mailman-8bit.patch" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Content-Disposition: attachment; filename="mailman-8bit.patch" ZGlmZiAtcnVOIG1haWxtYW4ub3JpZy9NYWlsbWFuL2h0bWxmb3JtYXQucHkg bWFpbG1hbi9NYWlsbWFuL2h0bWxmb3JtYXQucHkNCi0tLSBtYWlsbWFuLm9y aWcvTWFpbG1hbi9odG1sZm9ybWF0LnB5CU1vbiBKdW4gIDcgMTU6MjM6MDEg MTk5OQ0KKysrIG1haWxtYW4vTWFpbG1hbi9odG1sZm9ybWF0LnB5CU1vbiBE ZWMgIDYgMTY6NTk6MDAgMTk5OQ0KQEAgLTM2NSwxNiArMzY1LDE2IEBADQog ICAgIGRlZiBfX2luaXRfXyhzZWxmLCBuYW1lLCB0eSwgdmFsdWUsIGNoZWNr ZWQsICoqa3dzKToNCiAJc2VsZi5uYW1lID0gbmFtZQ0KIAlzZWxmLnR5cGUg PSB0eQ0KLQlzZWxmLnZhbHVlID0gYHZhbHVlYA0KKwlzZWxmLnZhbHVlID0g dmFsdWUNCiAJc2VsZi5jaGVja2VkID0gY2hlY2tlZA0KIAlzZWxmLmt3cyA9 IGt3cw0KIA0KICAgICBkZWYgRm9ybWF0KHNlbGYsIGluZGVudD0wKToNCi0J b3V0cHV0ID0gJzxJTlBVVCBuYW1lPSVzIHR5cGU9JXMgdmFsdWU9JXMnICUg KHNlbGYubmFtZSwgc2VsZi50eXBlLA0KKwlvdXRwdXQgPSAnPElOUFVUIG5h bWU9IiVzIiB0eXBlPSIlcyIgdmFsdWU9IiVzIicgJSAoc2VsZi5uYW1lLCBz ZWxmLnR5cGUsDQogCQkJCQkJICAgICAgc2VsZi52YWx1ZSkNCiAJDQogCWZv ciAoa2V5LCB2YWwpIGluIHNlbGYua3dzLml0ZW1zKCk6DQotCSAgICBvdXRw dXQgPSAnJXMgJXM9JXMnICUgKG91dHB1dCwga2V5LCB2YWwpDQorCSAgICBv dXRwdXQgPSAnJXMgIiVzIj0iJXMiJyAlIChvdXRwdXQsIGtleSwgdmFsKQ0K IA0KIAlpZiBzZWxmLmNoZWNrZWQ6DQogCSAgICBvdXRwdXQgPSBvdXRwdXQg KyAnIENIRUNLRUQnDQo= --1825891041-2098212404-944499785=:16442-- From jarrell@vt.edu Mon Dec 6 23:56:34 1999 From: jarrell@vt.edu (Ron Jarrell) Date: Mon, 06 Dec 1999 18:56:34 -0500 Subject: [Mailman-Developers] 1.1 cvs problem Message-ID: <4.2.0.58.19991206185531.00b8d1a0@vtserf.cc.vt.edu> You can't build a 1.1 release from the cvs archive; at the very least the src dir wasn't tagged with the Release_1_1 tag, and thus doesn't checkout... From ricardo@miss-janet.com Wed Dec 8 21:53:16 1999 From: ricardo@miss-janet.com (Ricardo Kustner) Date: Wed, 8 Dec 1999 22:53:16 +0100 Subject: [Mailman-Developers] bulkmailing & admin interface In-Reply-To: <14411.9792.611960.485273@anthem.cnri.reston.va.us>; from bwarsaw@CNRI.Reston.VA.US on Sun, Dec 05, 1999 at 09:58:08PM -0500 References: <19991204235439.A1308@miss-janet.com> <14411.9792.611960.485273@anthem.cnri.reston.va.us> Message-ID: <19991208225316.A11025@miss-janet.com> Hi, On Sun, Dec 05, 1999 at 09:58:08PM -0500, Barry A. Warsaw wrote: > RK> Would it be possible to be able to choose for a "relaxed" way > RK> of delevering mail in certain situations? i'd rather have the > RK> messages being delivered with a small delay then MM trying > RK> hard to be as quick as possible with delivery... > RK> hoping for at least one reaction to this email, :) > Here's one, hopefully the one you're looking for! :) yes it is... thanks! :) > All this stuff has changed in the current codebase, available via CVS. > The old bulkmailer stuff is gone and Mailman now has two ways to hand > a message off to your MTA: either by calling sendmail (or a sendmail > compatible program) via the command line, or talking asynchronously > (no-DSN) via SMTP. All these means that the handoff of messages from > Mailman to your MTA happens very quickly. ah very nice ... i think i'm going to test out the cvs version on my pc at home... do all the python lists use this codebase too? > ported to the new codebase and added back in. The neat thing is that > with the current architecture, a site could choose any one of these > delivery modules, as appropriate for their system (or easily implement > their own). ah even better ! btw i noticed some speed improvement when i switched from exim to postfix... I think i've tried out almost every possible MTA, but it seems postfix does it's best on a not-so-powerfull server with mailman. Ricardo. -- From bwarsaw@python.org Thu Dec 9 05:07:22 1999 From: bwarsaw@python.org (Barry A. Warsaw) Date: Thu, 9 Dec 1999 00:07:22 -0500 (EST) Subject: [Mailman-Developers] bulkmailing & admin interface References: <19991204235439.A1308@miss-janet.com> <14411.9792.611960.485273@anthem.cnri.reston.va.us> <19991208225316.A11025@miss-janet.com> Message-ID: <14415.14602.231300.438264@anthem.cnri.reston.va.us> >>>>> "RK" == Ricardo Kustner writes: RK> ah very nice ... i think i'm going to test out the cvs version RK> on my pc at home... do all the python lists use this codebase RK> too? Yes! -Barry From ddickey@wamnet.com Thu Dec 9 15:12:42 1999 From: ddickey@wamnet.com (Dan A. Dickey) Date: Thu, 09 Dec 1999 09:12:42 -0600 Subject: [Mailman-Developers] Problem with moving from /home/mailman -> /usr/mailman Message-ID: <384FC6EA.A597F178@wamnet.com> I was using mailman 1.0 on an "old" machine, and it was installed to /home/mailman - the default. We tried moving the lists to a new machine, but the admin wanted it based somewhere other than /home/mailman, so we chose /usr/mailman. I retrieved version 1.1, and installed it. The 'make update' failed. Basically, I believe this is because CheckVersion() thought the config.db that we brought over from the old machine was up to date, and so used it as is. I think it contains references to /home/mailman, and I do not know how to change them to /usr/mailman. For the time being, we are getting by because we have a symlink from /home/mailman -> /usr/mailman; but I want to do away with this scenario. Can one/more of the experts out there tell me how to correct the above problems? Can this be addressed in a new version of mailman a bit better? Or can someone tell me where to RTFM? I'm willing to try code here if someone wants to take a stab at fixing this. Thanks! -Dan From ricardo@miss-janet.com Fri Dec 10 05:57:07 1999 From: ricardo@miss-janet.com (Ricardo Kustner) Date: Fri, 10 Dec 1999 06:57:07 +0100 Subject: [Mailman-Developers] latest cvs trouble Message-ID: <19991210065707.A23888@miss-janet.com> Hi, since 1.1/postfix seems to be duplicating some posts a bit too often, i tried to install the latest cvs of MM... first of all, there were some pending posts in config.db, but the new installation doesn't recognize them (i guess this changed in 1.2) so any administrative requests get lost. When I tried posting to the list, i got an error: post: File "/usr/local/mailman/scripts/post", line 83, in ? post: main() post: File "/usr/local/mailman/scripts/post", line 56, in main post: msg = Message.Message(sys.stdin) post: File "/usr/local/mailman/Mailman/Message.py", line 49, in __init__ post: self.rewindbody() post: File "/usr/local/mailman/Mailman/pythonlib/rfc822.py", line 104, in rewindbody post: self.fp.seek(self.startofbody) post: IOError : [Errno 29] Illegal seek Ricardo. -- From bwarsaw@cnri.reston.va.us (Barry A. Warsaw) Fri Dec 10 13:46:28 1999 From: bwarsaw@cnri.reston.va.us (Barry A. Warsaw) (Barry A. Warsaw) Date: Fri, 10 Dec 1999 08:46:28 -0500 (EST) Subject: [Mailman-Developers] latest cvs trouble References: <19991210065707.A23888@miss-janet.com> Message-ID: <14417.1076.218993.63059@anthem.cnri.reston.va.us> >>>>> "RK" == Ricardo Kustner writes: RK> since 1.1/postfix seems to be duplicating some posts a bit too RK> often, i tried to install the latest cvs of MM... first of RK> all, there were some pending posts in config.db, but the new RK> installation doesn't recognize them (i guess this changed in RK> 1.2) so any administrative requests get lost. This is true. What I've done is make sure that any lists I convert have been cleared of admin requests. This clearly needs to be better handled in "make update" when 1.2 is released. RK> When I tried posting to the list, i got an error: post: File RK> "/usr/local/mailman/scripts/post", line 83, in ? post: main() RK> post: File "/usr/local/mailman/scripts/post", line 56, in main RK> post: msg = Message.Message(sys.stdin) post: File RK> "/usr/local/mailman/Mailman/Message.py", line 49, in __init__ RK> post: self.rewindbody() post: File RK> "/usr/local/mailman/Mailman/pythonlib/rfc822.py", line 104, in RK> rewindbody post: self.fp.seek(self.startofbody) post: IOError RK> : [Errno 29] Illegal seek Okay, so sys.stdin isn't seekable everywhere :) Give the below patch a try. -Barry -------------------- snip snip -------------------- Index: post =================================================================== RCS file: /projects/cvsroot/mailman/scripts/post,v retrieving revision 1.25 diff -c -r1.25 post *** post 1999/11/24 21:11:07 1.25 --- post 1999/12/10 13:44:17 *************** *** 33,38 **** --- 33,39 ---- from Mailman import Utils from Mailman.Logging.Utils import LogStdErr from Mailman.Handlers import HandlerAPI + from Mailman.pythonlib import StringIO LogStdErr("error", "post") *************** *** 53,59 **** except: pass if msg is None: ! msg = Message.Message(sys.stdin) # go ahead and post the message adminaddr = mlist.GetAdminEmail() try: --- 54,61 ---- except: pass if msg is None: ! s = StringIO(sys.stdin.read()) ! msg = Message.Message(s) # go ahead and post the message adminaddr = mlist.GetAdminEmail() try: From wheakory@isu.edu Fri Dec 10 20:22:12 1999 From: wheakory@isu.edu (Kory Wheatley) Date: Fri, 10 Dec 1999 13:22:12 -0700 Subject: [Mailman-Developers] Installing python 1.5.2 Message-ID: <385160F4.3D782A2E@isu.edu> I am going to be installing python 1.5.2 to red hat 6.0 linux. Do any of you have any information or problems that I should look at for. Is there something that I might have to tweak with this new version. -- Kory Wheatley Office Phone 236-3874 Computing & Communication Academic Computing Analyst sr. Everything you do must point to him. From ricardo@miss-janet.com Fri Dec 10 22:41:50 1999 From: ricardo@miss-janet.com (Ricardo Kustner) Date: Fri, 10 Dec 1999 23:41:50 +0100 Subject: [Mailman-Developers] latest cvs trouble In-Reply-To: <14417.1076.218993.63059@anthem.cnri.reston.va.us>; from bwarsaw@cnri.reston.va.us on Fri, Dec 10, 1999 at 08:46:28AM -0500 References: <19991210065707.A23888@miss-janet.com> <14417.1076.218993.63059@anthem.cnri.reston.va.us> Message-ID: <19991210234150.A31262@miss-janet.com> On Fri, Dec 10, 1999 at 08:46:28AM -0500, Barry A. Warsaw wrote: > > >>>>> "RK" == Ricardo Kustner writes: > RK> When I tried posting to the list, i got an error: post: File > Okay, so sys.stdin isn't seekable everywhere :) Give the below patch > a try. thanks, but this patch produces another error: : Command died with status 1: "/usr/local/mailman/mail/wrapper post mailinglist". Command output: Traceback (innermost last): File "/usr/local/mailman/scripts/post", line 85, in ? main() File "/usr/local/mailman/scripts/post", line 57, in main s = StringIO(sys.stdin.read()) TypeError: call of non-function (type module) Also, why did you add import StringIO? cause the pre-patch version already contains a call to StringIO a few lines earlier... unfortunately I haven't mastered python 100% yet, so I can't help out much with tracking down the bug :( > =================================================================== > RCS file: /projects/cvsroot/mailman/scripts/post,v > retrieving revision 1.25 > diff -c -r1.25 post > *** post 1999/11/24 21:11:07 1.25 > --- post 1999/12/10 13:44:17 > *************** > *** 33,38 **** > --- 33,39 ---- > from Mailman import Utils > from Mailman.Logging.Utils import LogStdErr > from Mailman.Handlers import HandlerAPI > + from Mailman.pythonlib import StringIO > > LogStdErr("error", "post") > > *************** > *** 53,59 **** > except: > pass > if msg is None: > ! msg = Message.Message(sys.stdin) > # go ahead and post the message > adminaddr = mlist.GetAdminEmail() > try: > --- 54,61 ---- > except: > pass > if msg is None: > ! s = StringIO(sys.stdin.read()) > ! msg = Message.Message(s) > # go ahead and post the message > adminaddr = mlist.GetAdminEmail() > try: > -- Ricardo. -- International Janet Jackson fanclub called MISS JANET. For more information write to: Miss Janet. P.O.Box 10016, 1001 EA Amsterdam, The Netherlands Fax/phone: +31-(0)20-7764493 Email: fanclub@miss-janet.com Or check out our website: http://miss-janet.com From bwarsaw@python.org Sat Dec 11 03:51:01 1999 From: bwarsaw@python.org (Barry A. Warsaw) Date: Fri, 10 Dec 1999 22:51:01 -0500 (EST) Subject: [Mailman-Developers] latest cvs trouble References: <19991210065707.A23888@miss-janet.com> <14417.1076.218993.63059@anthem.cnri.reston.va.us> <19991210234150.A31262@miss-janet.com> Message-ID: <14417.51749.991830.188873@anthem.cnri.reston.va.us> >>>>> "RK" == Ricardo Kustner writes: RK> thanks, but this patch produces another error: Oops, you should change from Mailman.pythonlib import StringIO to from Mailman.pythonlib.StringIO import StringIO RK> Also, why did you add import StringIO? cause the pre-patch RK> version already contains a call to StringIO a few lines RK> earlier... unfortunately I haven't mastered python 100% yet, RK> so I can't help out much with tracking down the bug :( Really? The CVS version of the file was missing the import of StringIO (and in fact, if the code takes the `prog is true' path through the first conditional, it would raise an exception because of that). -Barry From bwarsaw@cnri.reston.va.us (Barry A. Warsaw) Sat Dec 11 04:53:06 1999 From: bwarsaw@cnri.reston.va.us (Barry A. Warsaw) (Barry A. Warsaw) Date: Fri, 10 Dec 1999 23:53:06 -0500 (EST) Subject: [Mailman-Developers] 8-bit input in administrator menu References: Message-ID: <14417.55474.145609.535665@anthem.cnri.reston.va.us> >>>>> "BN" == Balazs Nagy writes: BN> I did a little digging about entering text with accents. It's BN> a bit curious that one can type accents in textarea but to BN> textbox cannot. In the latter case you can see an escaped BN> print of your input. BN> In the end I came to htmlformat.py's InputObj. At this point BN> I have a humble question: who put `-s around value? After a BN> s/`value`/value/ in line #368, almost everything works fine, BN> because this brings up a problem about quoting. Of course, the BN> patch is here. Near as I can tell, that's the way the code has been since its initial version. I've installed this change. Thanks, -Barry From ricardo@miss-janet.com Sat Dec 11 12:44:04 1999 From: ricardo@miss-janet.com (Ricardo Kustner) Date: Sat, 11 Dec 1999 13:44:04 +0100 Subject: [Mailman-Developers] admin approval page / cvs Message-ID: <19991211134404.D5306@miss-janet.com> Hi, i'm trying out the 1.2 cvs version of MM... I like the changes on the approval page... I do have some suggestions for changes, which should make it a bit easier to use (this page is an important part of our mailinglist setup and I've used it alot)... 1) message headers: putting the message in a TEXTAREA is a neat solution :) however, when all the message headers are being shown, you have to scroll the box alot before you see anything about the message body... maybe the headers should be left out entirely since the subject/from is being mentioned above anyway ? 2) approve/reject/discard ... please move this below the message content... since the normal way is that you read the message first, and then decide what to do with it... 3) add an option to send a copy of the message to a certain email address. I've already hacked something like this into my local copy of MM, but it just sends the message body, so any attachments are lost (you can of course retrieve them with mime tools) i've already changed these things myself... but i don't have a copy of cvs on the production machine so it's not easy to make a patch for it right now... (and to be honest my changes are more 'hacks' than clean code ;) ) Ricardo. From claw@kanga.nu Sat Dec 11 15:14:01 1999 From: claw@kanga.nu (J C Lawrence) Date: Sat, 11 Dec 1999 07:14:01 -0800 Subject: [Mailman-Developers] admin approval page / cvs In-Reply-To: Message from Ricardo Kustner of "Sat, 11 Dec 1999 13:44:04 +0100." <19991211134404.D5306@miss-janet.com> References: <19991211134404.D5306@miss-janet.com> Message-ID: On Sat, 11 Dec 1999 13:44:04 +0100 Ricardo Kustner wrote: > 1) message headers: putting the message in a TEXTAREA is a neat > solution :) Agreed. I would like to be able to edit moderated messages, given that MailMan would then insert a custom header stating that the message had been edited by the moderator. > however, when all the message headers are being shown, > you have to scroll the box alot before you see anything about the > message body... maybe the headers should be left out entirely > since the subject/from is being mentioned above anyway ? No way. The headers are essential to me. -- J C Lawrence Home: claw@kanga.nu ----------(*) Other: coder@kanga.nu --=| A man is as sane as he is dangerous to his environment |=-- From jafo@tummy.com Sat Dec 11 15:36:14 1999 From: jafo@tummy.com (Sean Reifschneider) Date: Sat, 11 Dec 1999 08:36:14 -0700 Subject: [Mailman-Developers] admin approval page / cvs In-Reply-To: ; from J C Lawrence on Sat, Dec 11, 1999 at 07:14:01AM -0800 References: <19991211134404.D5306@miss-janet.com> Message-ID: <19991211083614.E20354@tummy.com> On Sat, Dec 11, 1999 at 07:14:01AM -0800, J C Lawrence wrote: >No way. The headers are essential to me. What about having separate text fields for the headers and the body? I suppose with JavaScript you could cause the cursor to move to the first line of the body... Sean -- These go to eleven. -- _This_is_Spinal_Tap_ Sean Reifschneider, Inimitably Superfluous URL: HP-UX/Linux/FreeBSD/BSDOS scanning software. From claw@kanga.nu Sat Dec 11 15:43:28 1999 From: claw@kanga.nu (J C Lawrence) Date: Sat, 11 Dec 1999 07:43:28 -0800 Subject: [Mailman-Developers] admin approval page / cvs In-Reply-To: Message from Sean Reifschneider of "Sat, 11 Dec 1999 08:36:14 MST." <19991211083614.E20354@tummy.com> References: <19991211134404.D5306@miss-janet.com> <19991211083614.E20354@tummy.com> Message-ID: On Sat, 11 Dec 1999 08:36:14 -0700 Sean Reifschneider wrote: > On Sat, Dec 11, 1999 at 07:14:01AM -0800, J C Lawrence wrote: >> No way. The headers are essential to me. > What about having separate text fields for the headers and the > body? Please, no. I need/want the message exactly as it was sent with no extra munging, implicit edits, ochanges in presentation etc. This is actually one of the main things I like about MM -- it doesn't attempt to package the pending-moderation messages in any way, but presents them to me exactly as they are. -- J C Lawrence Home: claw@kanga.nu ----------(*) Other: coder@kanga.nu --=| A man is as sane as he is dangerous to his environment |=-- From bwarsaw@cnri.reston.va.us (Barry A. Warsaw) Sat Dec 11 15:53:24 1999 From: bwarsaw@cnri.reston.va.us (Barry A. Warsaw) (Barry A. Warsaw) Date: Sat, 11 Dec 1999 10:53:24 -0500 (EST) Subject: [Mailman-Developers] admin approval page / cvs References: <19991211134404.D5306@miss-janet.com> <19991211083614.E20354@tummy.com> Message-ID: <14418.29556.250753.901548@anthem.cnri.reston.va.us> >>>>> "SR" == Sean Reifschneider writes: SR> I suppose with JavaScript you could cause the cursor to SR> move to the first line of the body... -Barry From jafo@tummy.com Sat Dec 11 16:17:58 1999 From: jafo@tummy.com (Sean Reifschneider) Date: Sat, 11 Dec 1999 09:17:58 -0700 Subject: [Mailman-Developers] admin approval page / cvs In-Reply-To: ; from J C Lawrence on Sat, Dec 11, 1999 at 07:43:28AM -0800 References: <19991211134404.D5306@miss-janet.com> <19991211083614.E20354@tummy.com> Message-ID: <19991211091758.F20354@tummy.com> On Sat, Dec 11, 1999 at 07:43:28AM -0800, J C Lawrence wrote: >Please, no. I need/want the message exactly as it was sent with no >extra munging, implicit edits, ochanges in presentation etc. This Ok, so it should be an option... I don't do much approval, so it really doesn't impact me. However, the primary information needed when doing an approval is the *BODY*, and that's generally obscured from the page as it is presented. From a Human Factors POV, that's inexcusable... What about simply increasing the size of the edit field based on the number of lines in the message? That way you don't have to navigate into the text field and scroll to see the *PRIMARY* information you need to carry out the action. Oh, and if you have the header and the body in one text field, is there code to ensure that the space separating the header from the body hasn't been accidentally removed? Sean -- "I'll thrash you like a Netscape process on a machine with 640K." -- John Shipman, 1998 Sean Reifschneider, Inimitably Superfluous URL: HP-UX/Linux/FreeBSD/BSDOS scanning software. From ricardo@miss-janet.com Sat Dec 11 17:24:49 1999 From: ricardo@miss-janet.com (Ricardo Kustner) Date: Sat, 11 Dec 1999 18:24:49 +0100 Subject: [Mailman-Developers] admin approval page / cvs In-Reply-To: ; from claw@kanga.nu on Sat, Dec 11, 1999 at 07:14:01AM -0800 References: <19991211134404.D5306@miss-janet.com> Message-ID: <19991211182449.B7706@miss-janet.com> Hi, On Sat, Dec 11, 1999 at 07:14:01AM -0800, J C Lawrence wrote: > On Sat, 11 Dec 1999 13:44:04 +0100 > Ricardo Kustner wrote: > > 1) message headers: putting the message in a TEXTAREA is a neat > > solution :) > Agreed. I would like to be able to edit moderated messages, given > that MailMan would then insert a custom header stating that the > message had been edited by the moderator. yes i saw that the textarea data isn't used when approving the post... the complete message is read from disk when it has been approved. > > message body... maybe the headers should be left out entirely > > since the subject/from is being mentioned above anyway ? > No way. The headers are essential to me. i can understand that the headers may be very usefull sometimes... what if we meet half way? i just thought of the following solution: put the message body in a textarea... and put a select box on top if it that includes the headers... something like this: so if you click on the select box, you get the list of headers. and you don't even need to use Javascript :) Ricardo. -- From claw@kanga.nu Sat Dec 11 17:28:01 1999 From: claw@kanga.nu (J C Lawrence) Date: Sat, 11 Dec 1999 09:28:01 -0800 Subject: [Mailman-Developers] admin approval page / cvs In-Reply-To: Message from Ricardo Kustner of "Sat, 11 Dec 1999 18:24:49 +0100." <19991211182449.B7706@miss-janet.com> References: <19991211134404.D5306@miss-janet.com> <19991211182449.B7706@miss-janet.com> Message-ID: On Sat, 11 Dec 1999 18:24:49 +0100 Ricardo Kustner wrote: > Hi, On Sat, Dec 11, 1999 at 07:14:01AM -0800, J C Lawrence wrote: >> Agreed. I would like to be able to edit moderated messages, >> given that MailMan would then insert a custom header stating that >> the message had been edited by the moderator. > yes i saw that the textarea data isn't used when approving the > post... the complete message is read from disk when it has been > approved. This is not surprising given that a single message may be several Meg in size (and yes, some of my list posts are that big). >> > message body... maybe the headers should be left out entirely > >> since the subject/from is being mentioned above anyway ? No way. >> The headers are essential to me. > i can understand that the headers may be very usefull sometimes... > what if we meet half way? i just thought of the following > solution: put the message body in a textarea... and put a select > box on top if it that includes the headers... This works badly when you have a large number of messages to approve. -- J C Lawrence Home: claw@kanga.nu ----------(*) Other: coder@kanga.nu --=| A man is as sane as he is dangerous to his environment |=-- From ricardo@miss-janet.com Sun Dec 12 11:29:12 1999 From: ricardo@miss-janet.com (Ricardo Kustner) Date: Sun, 12 Dec 1999 12:29:12 +0100 Subject: [Mailman-Developers] admin approval page / cvs In-Reply-To: ; from claw@kanga.nu on Sat, Dec 11, 1999 at 09:28:01AM -0800 References: <19991211134404.D5306@miss-janet.com> <19991211182449.B7706@miss-janet.com> Message-ID: <19991212122912.B25191@miss-janet.com> Hi, On Sat, Dec 11, 1999 at 09:28:01AM -0800, J C Lawrence wrote: > On Sat, 11 Dec 1999 18:24:49 +0100 > Ricardo Kustner wrote: > >> Agreed. I would like to be able to edit moderated messages, > >> given that MailMan would then insert a custom header stating that > >> the message had been edited by the moderator. > > yes i saw that the textarea data isn't used when approving the > > post... the complete message is read from disk when it has been > > approved. > This is not surprising given that a single message may be several > Meg in size (and yes, some of my list posts are that big). Yes i'm glad they're no longer in config.db :) > >> The headers are essential to me. > > solution: put the message body in a textarea... and put a select > > box on top if it that includes the headers... > This works badly when you have a large number of messages to > approve. for me the reason to seperate the headers is just because i always have a large number of messages to approve... now it takes me much longer to approve everything because i have to stop at each message and move the mouse to scroll the textarea... normally it was just read, scroll, click accept/reject and scroll to the next message. Even if the full message is visible in the textarea, my mind needs a bit of time to focus on where the headers end and the message begins... Ricardo. -- From root@theporch.com Sun Dec 12 13:21:54 1999 From: root@theporch.com (Phillip Porch) Date: Sun, 12 Dec 1999 07:21:54 -0600 (CST) Subject: [Mailman-Developers] Mailman 1.2 CVS Message-ID: I Noticed the following error message in my error log for mailman and wondered if you could give me a pointer to tracking down the problem. beer: lost digest file: /home mailman/list/beer/next-digest (No such file or directory) I also started seeing this message a couple of days ago from the cron daemon. Traceback (innermost last): File "/home/mailman/cron/checkdbs", line 83, in ? main() File "/home/mailman/cron/checkdbs", line 50, in main mlist.SendTextToUser( AttributeError: SendTextToUser ************************************************* Cron: The previous message is the standard output and standard error of one of your cron commands. From root@theporch.com Sun Dec 12 13:39:08 1999 From: root@theporch.com (Phillip Porch) Date: Sun, 12 Dec 1999 07:39:08 -0600 (CST) Subject: [Mailman-Developers] Mailman 1.2 CVS Message-ID: I have noticed another quirk. In the archives, with the original version, I had the archive gzipped on the fly. The links would indicate that the text could be obtained gzipped. With the current version, I have elected to not gzip on the fly but to run the cron script to gzip the archives. The gzipping is working fine, but the link on the archive page doesn;t indicate the file is available gzipped. What is needed to update that link? -- Phillip P. Porch NIC:PP1573 finger for http://www.theporch.com UTM - 16 514548E 3994397N PGP key From bwarsaw@cnri.reston.va.us (Barry A. Warsaw) Sun Dec 12 21:01:36 1999 From: bwarsaw@cnri.reston.va.us (Barry A. Warsaw) (Barry A. Warsaw) Date: Sun, 12 Dec 1999 16:01:36 -0500 (EST) Subject: [Mailman-Developers] Mailman 1.2 CVS References: Message-ID: <14420.3376.144281.520784@anthem.cnri.reston.va.us> >>>>> "PP" == Phillip Porch writes: PP> I Noticed the following error message in my error log for PP> mailman and wondered if you could give me a pointer to PP> tracking down the problem. PP> beer: lost digest file: /home mailman/list/beer/next-digest PP> (No such file or directory) Ignore this. There was a situation where this message was being unnecessarily logged. I checked in a fix for this. PP> I also started seeing this message a couple of days ago from PP> the cron daemon. PP> Traceback (innermost last): | File "/home/mailman/cron/checkdbs", line 83, in ? | main() | File "/home/mailman/cron/checkdbs", line 50, in main | mlist.SendTextToUser( PP> AttributeError: SendTextToUser Oh dang, I forgot to convert checkdbs. Will do. -Barry From bbum@codefab.com Sun Dec 12 22:54:24 1999 From: bbum@codefab.com (Bill Bumgarner) Date: Sun, 12 Dec 1999 17:54:24 -0500 Subject: [Mailman-Developers] Developers Needed for addition of specific feature(s) Message-ID: <199912122254.RAA15190@bjork.codefab.com> I'm looking for some Python/MailMan savvy developers to add some features to MailMan. In particular, we [CodeFab] have a need-- both internally and on a client project-- to augment MailMan such that it can gracefully handle attachments. In particular: - decode MIME (and other formats?) encoded messages upon receipt - file attachments into archive via either the current archive scheme or via WebDAV (WebDAV preferred) - rewrite message such that it contains URLs to the attachements instead of the attachments themselves The overriding goal of this is to solve the above problems in an extremely timely manner and provide all resulting modifications/extensions to MailMan back to the MailMan development community in such a fashion that it can be integrated into future releases. However, we are under a severe time crunch and, as such, it is likely that what we need done and what needs to be done to integrate this into the next release will not be in complete parity-- which is another reason why I would really like to bring a focused MailMan/Python developer into this project to ensure that the short term work will feed directly into a long term, viable integration of this solution into MailMan. The code is not just for CodeFab's benefit-- we have a client that also needs this solution. This client is also interested in helping fund this development effort. The funds are limited and the client [and CodeFab] would both like to be able to further leverage this by generating some positive "we support open source projects & MailMan/Python is really cool" PR-- so we would like to work with a developer or developers that are amicable to having their name thrown into a press release and wouldn't mind signing the standard NDA/contracting style agreements. Let me reiterate-- regardless of contractual agreements necessary to move this forward-- all code developed under this arrangement will be under the GPL. Regardless of whether or not we can find someone to formally assist us, this work has to get done anyway. I would rather see it done with formal assistance from the MailMan development community... If we can't find someone to help from the community, then consider this message a request for comments as to how to best implement the above features and I guess I'll have to go read the "hacking MailMan" HOWTO. :-) thanks, b.bum From ricardo@miss-janet.com Mon Dec 13 05:27:48 1999 From: ricardo@miss-janet.com (Ricardo Kustner) Date: Mon, 13 Dec 1999 06:27:48 +0100 Subject: [Mailman-Developers] cvs errors Message-ID: <19991213062748.A1073@miss-janet.com> I noticed the following errors in the CVS version of MM: Dec 13 03:48:05 1999 mailcmd: Traceback (innermost last): mailcmd: File "/usr/local/mailman/scripts/mailcmd", line 52, in ? mailcmd: list.ParseMailCommands() mailcmd: File "/usr/local/mailman/Mailman/MailCommandHandler.py", line 112, in mailcmd: msg = Message.Message(sys.stdin) mailcmd: File "/usr/local/mailman/Mailman/Message.py", line 49, in __init__ mailcmd: self.rewindbody() mailcmd: File "/usr/local/mailman/Mailman/pythonlib/rfc822.py", line 104, in r mailcmd: self.fp.seek(self.startofbody) mailcmd: IOError : [Errno 29] Illegal seek I'm not sure what could be causing this, but i got one complaint from somebody who received an error message from postfix when trying to confirm subscribing to the list. Also I've noticed the number of posts to the lists have decreased dramatically, though this saves me a lot of approval work, i hope this doesn't mean some posts are getting lost... Ricardo. -- From ricardo@miss-janet.com Mon Dec 13 06:26:01 1999 From: ricardo@miss-janet.com (Ricardo Kustner) Date: Mon, 13 Dec 1999 07:26:01 +0100 Subject: [Mailman-Developers] latest cvs trouble In-Reply-To: <14417.1076.218993.63059@anthem.cnri.reston.va.us>; from bwarsaw@cnri.reston.va.us on Fri, Dec 10, 1999 at 08:46:28AM -0500 References: <19991210065707.A23888@miss-janet.com> <14417.1076.218993.63059@anthem.cnri.reston.va.us> Message-ID: <19991213072601.B1073@miss-janet.com> Hi, On Fri, Dec 10, 1999 at 08:46:28AM -0500, Barry A. Warsaw wrote: > RK> post: File "/usr/local/mailman/scripts/post", line 56, in main > RK> post: msg = Message.Message(sys.stdin) post: File > RK> "/usr/local/mailman/Mailman/Message.py", line 49, in __init__ > RK> post: self.rewindbody() post: File > RK> "/usr/local/mailman/Mailman/pythonlib/rfc822.py", line 104, in > RK> rewindbody post: self.fp.seek(self.startofbody) post: IOError > RK> : [Errno 29] Illegal seek > Okay, so sys.stdin isn't seekable everywhere :) Give the below patch > a try. will this be added to the cvs version too? I want to have the latest cvs version running, but I keep having to change this in scripts/post :) also, it looks like the problem I reported earlier today is related to this one... Thanks, Ricardo. -- From richarde@eskom.co.za Mon Dec 13 08:12:25 1999 From: richarde@eskom.co.za (Richard Ellerbrock) Date: Mon, 13 Dec 1999 10:12:25 +0200 Subject: [Mailman-Developers] admin approval page / cvs Message-ID: >Hi, > >i'm trying out the 1.2 cvs version of MM... >I like the changes on the approval page... I do have some >suggestions for changes, which should make it a bit easier to >use (this page is an important part of our mailinglist >setup and I've used it alot)... {cut} >3) add an option to send a copy of the message to a certain > email address. I've already hacked something like this > into my local copy of MM, but it just sends the message body, > so any attachments are lost (you can of course retrieve them > with mime tools) I would really like this feature too! -- Richard Ellerbrock richarde@eskom.co.za From uwannags@swd.de Mon Dec 13 08:43:44 1999 From: uwannags@swd.de (Uwe Wannags) Date: Mon, 13 Dec 1999 09:43:44 +0100 Subject: [Mailman-Developers] unsubscribe Message-ID: <019e01bf4546$2b7b6e80$0964a8c0@SWD.DE> This is a multi-part message in MIME format. ------=_NextPart_000_0198_01BF454E.8BCE9340 Content-Type: multipart/alternative; boundary="----=_NextPart_001_0199_01BF454E.8BCE9340" ------=_NextPart_001_0199_01BF454E.8BCE9340 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable unsubscribe ------=_NextPart_001_0199_01BF454E.8BCE9340 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
unsubscribe
------=_NextPart_001_0199_01BF454E.8BCE9340-- ------=_NextPart_000_0198_01BF454E.8BCE9340 Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIIpDCCAlcw ggHAoAMCAQICAwGWtTANBgkqhkiG9w0BAQQFADCBlDELMAkGA1UEBhMCWkExFTATBgNVBAgTDFdl c3Rlcm4gQ2FwZTEUMBIGA1UEBxMLRHVyYmFudmlsbGUxDzANBgNVBAoTBlRoYXd0ZTEdMBsGA1UE CxMUQ2VydGlmaWNhdGUgU2VydmljZXMxKDAmBgNVBAMTH1BlcnNvbmFsIEZyZWVtYWlsIFJTQSAx OTk5LjkuMTYwHhcNOTkxMDI3MTYxOTU1WhcNMDAxMDI2MTYxOTU1WjBBMR8wHQYDVQQDExZUaGF3 dGUgRnJlZW1haWwgTWVtYmVyMR4wHAYJKoZIhvcNAQkBFg91d2FubmFnc0Bzd2QuZGUwXDANBgkq hkiG9w0BAQEFAANLADBIAkEAxLhJ77nyZX9c82rwsfqcYnh4PYgBo9E18KB0GBa1dwuzhqOy0Kmv eFK3q9tbJ+4E9sVo3Q5F+fx/NRifM8P5IQIDAQABo00wSzAaBgNVHREEEzARgQ91d2FubmFnc0Bz d2QuZGUwDAYDVR0TAQH/BAIwADAfBgNVHSMEGDAWgBSIq/Fgg2ZV9ORYx0YdwGG9I9fDjDANBgkq hkiG9w0BAQQFAAOBgQBVLuMif4ucBR8np8l48vqVVSmzYPZecuM1WO0i7kYj6+0Az/gPLetFUnEz 4C1stoFadv+VtWpyDcqJEqjNmRGR+zA2dL78Q/gfmJZNK5D4/RWvqYdGUL/YpmcF1CC/Z+aBa8bz EpGl92gEae4MhVsKEveGOJ3yboFyewtLK8AnKTCCAxQwggJ9oAMCAQICAQswDQYJKoZIhvcNAQEE BQAwgdExCzAJBgNVBAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUg VG93bjEaMBgGA1UEChMRVGhhd3RlIENvbnN1bHRpbmcxKDAmBgNVBAsTH0NlcnRpZmljYXRpb24g U2VydmljZXMgRGl2aXNpb24xJDAiBgNVBAMTG1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBDQTEr MCkGCSqGSIb3DQEJARYccGVyc29uYWwtZnJlZW1haWxAdGhhd3RlLmNvbTAeFw05OTA5MTYxNDAx NDBaFw0wMTA5MTUxNDAxNDBaMIGUMQswCQYDVQQGEwJaQTEVMBMGA1UECBMMV2VzdGVybiBDYXBl MRQwEgYDVQQHEwtEdXJiYW52aWxsZTEPMA0GA1UEChMGVGhhd3RlMR0wGwYDVQQLExRDZXJ0aWZp Y2F0ZSBTZXJ2aWNlczEoMCYGA1UEAxMfUGVyc29uYWwgRnJlZW1haWwgUlNBIDE5OTkuOS4xNjCB nzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAs2lal9TQFgt6tcVd6SGcI3LNEkxL937Px/vKciT0 QlKsV5Xje2F6F4Tn/XI5OJS06u1lp5IGXr3gZfYZu5R5dkw+uWhwdYQc9BF0ALwFLE8JAxcxzPRB 1HLGpl3iiESwiy7ETfHw1oU+bPOVlHiRfkDpnNGNFVeOwnPlMN5G9U8CAwEAAaM3MDUwEgYDVR0T AQH/BAgwBgEB/wIBADAfBgNVHSMEGDAWgBRyScJzNMZV9At2coF+d/SH58ayDjANBgkqhkiG9w0B AQQFAAOBgQBrxlnpMfrptuyxA9jfcnL+kWBI6sZV3XvwZ47GYXDnbcKlN9idtxcoVgWL3Vx1b8aR kMZsZnET0BB8a5FvhuAhNi3B1+qyCa3PLW3Gg1Kb+7v+nIed/LfpdJLkXJeu/H6syg1vcnpnLGtz 9Yb5nfUAbvQdB86dnoJjKe+TCX5V3jCCAy0wggKWoAMCAQICAQAwDQYJKoZIhvcNAQEEBQAwgdEx CzAJBgNVBAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUgVG93bjEa MBgGA1UEChMRVGhhd3RlIENvbnN1bHRpbmcxKDAmBgNVBAsTH0NlcnRpZmljYXRpb24gU2Vydmlj ZXMgRGl2aXNpb24xJDAiBgNVBAMTG1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBDQTErMCkGCSqG SIb3DQEJARYccGVyc29uYWwtZnJlZW1haWxAdGhhd3RlLmNvbTAeFw05NjAxMDEwMDAwMDBaFw0y MDEyMzEyMzU5NTlaMIHRMQswCQYDVQQGEwJaQTEVMBMGA1UECBMMV2VzdGVybiBDYXBlMRIwEAYD VQQHEwlDYXBlIFRvd24xGjAYBgNVBAoTEVRoYXd0ZSBDb25zdWx0aW5nMSgwJgYDVQQLEx9DZXJ0 aWZpY2F0aW9uIFNlcnZpY2VzIERpdmlzaW9uMSQwIgYDVQQDExtUaGF3dGUgUGVyc29uYWwgRnJl ZW1haWwgQ0ExKzApBgkqhkiG9w0BCQEWHHBlcnNvbmFsLWZyZWVtYWlsQHRoYXd0ZS5jb20wgZ8w DQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBANRp19SwlGRbcelH2AxRtupykbCEXn0tDY97Et+FJXUo dDpCLGMnn5V7S+9+GYcdhuqj3bnOlmQawhRuRKx85o/oTQ9xH0A4pgCjh3j2+ZSGXq3qwF5269kU o11uenwMpUtVfwYZKX+emibVars4JAhqmMex2qOYkf152+VaxBy5AgMBAAGjEzARMA8GA1UdEwEB /wQFMAMBAf8wDQYJKoZIhvcNAQEEBQADgYEAx+ySfk749ZalZ2IqpPBNEWDQb41gWGGsJrtSNVwI zzD7qEqWih9iQiOMFw/0umScF6xHKd+dmF7SbGBxXKKs3Hnj524ARx+1DSjoAp3kmv0T9KbZfLH4 3F8jJgmRgHPQFBveQ6mDJfLmnC8Vyv6mq4oHdYsM3VGEa+T40c53ooExggGLMIIBhwIBATCBnDCB lDELMAkGA1UEBhMCWkExFTATBgNVBAgTDFdlc3Rlcm4gQ2FwZTEUMBIGA1UEBxMLRHVyYmFudmls bGUxDzANBgNVBAoTBlRoYXd0ZTEdMBsGA1UECxMUQ2VydGlmaWNhdGUgU2VydmljZXMxKDAmBgNV BAMTH1BlcnNvbmFsIEZyZWVtYWlsIFJTQSAxOTk5LjkuMTYCAwGWtTAJBgUrDgMCGgUAoIGGMBgG CSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTk5MTIxMzA5NDM0NFowIwYJ KoZIhvcNAQkEMRYEFKcoLKkxeLAtCbBs0hzoyUKRIBYKMCcGCSqGSIb3DQEJDzEaMBgwDQYIKoZI hvcNAwICASgwBwYFKw4DAh0wDQYJKoZIhvcNAQEBBQAEQF7LKRLVhEThjcgF5vKylsyt9dZYFWUY Q1LQfzKYzprYDlJ20eybfhW6FAQvUqsOvxrsgFOOg+2YHXcG/vVIcP0AAAAAAAA= ------=_NextPart_000_0198_01BF454E.8BCE9340-- From wheakory@isu.edu Mon Dec 13 16:41:15 1999 From: wheakory@isu.edu (Kory Wheatley) Date: Mon, 13 Dec 1999 09:41:15 -0700 Subject: [Mailman-Developers] Cron error message Message-ID: <385521AB.8B7CB744@isu.edu> This error message below is generated when the cron scheduled job gate_news is ran. Would this error happen in result that I am running mailman 1.1 and have Python1.5.1 do I need upgrade to Python 1.5.2 for this cron entry to run? I have been getting similar errors from the other mailman cron job entries to (like senddigests, nightly-gzip), since I upgraded mailman from 1.0 to 1.1. Mailman is installed on red hat 6.0 using the MTA Sendmail. What's funny is I can still receive mail messages fine from the lists and send them out if I have all of the cron jobs commented out. Once I have the cron jobs running after a while when getting error message sent to me the postmaster of mailman about the cron processes errors, I can't receive any messages from the mailman subscript lists that I have myself on. I receive usually a mailer 2 error. All of the permissions are setup correctly for mailman 1.1. If I shutdown and reboot my Linux machine then everything will work again until those cron jobs processes run for a while., then eventually I can't receive any message from the lists or if I send messages to the lists I just get error message back form mailman admin. I really need help I have 20 production list on mailman that need to be working all the time. Do I need to upgrade to python 1.5.2? Will mailman 1.1 work with python 1.5.1 and I just need to tweak something? I am desperately seeking support here. If anyone has the answer please respond immediately. I have not found any documentation that says mailman 1.1 will not work with python 1.5.1. If I have missed this documentation please point me to the link that explains what's needed for mailman 1.1 to work with red hat 6.0. Is there anyway to pay for getting support for mailman being installed on a system. Here is the error message below, sorry so long but I need help badly. Traceback (innermost last): File "/home/mailman/cron/gate_news", line 119, in ? main() File "/home/mailman/cron/gate_news", line 58, in main mlist = MailList.MailList(name, lock=0) File "/home/mailman/Mailman/MailList.py", line 62, in __init__ self.Load() File "/home/mailman/Mailman/MailList.py", line 820, in Load setattr(self, key, value) TypeError: setattr, argument 2: expected string, None found -- Kory Wheatley Office Phone 236-3874 Computing & Communication Academic Computing Analyst sr. Everything you do must point to him. From joe@lawlearn.wuacc.edu Mon Dec 13 20:45:18 1999 From: joe@lawlearn.wuacc.edu (Joe Hewitt) Date: Mon, 13 Dec 1999 14:45:18 -0600 (CST) Subject: [Mailman-Developers] Re: [Mailman-Users] Installing python 1.5.2 In-Reply-To: <385160F4.3D782A2E@isu.edu> Message-ID: Kory, You probably want to use the Red Hat CD to install your python 1.5.2 which is the version on the 6.0 CD. I tried installing it from src and it wouldn't work properly, so I reinstalled from CD and all was fine. Duh! Joe On Fri, 10 Dec 1999, Kory Wheatley wrote: > I am going to be installing python 1.5.2 to red hat 6.0 linux. Do any > of you have any information or problems that I should look at for. Is > there something that I might have to tweak with this new version. > > -- > Kory Wheatley Office Phone 236-3874 > Computing & Communication > Academic Computing Analyst sr. > > Everything you do must point to him. > > > > ------------------------------------------------------ > Mailman-Users maillist - Mailman-Users@python.org > http://www.python.org/mailman/listinfo/mailman-users > From Dan Mick Tue Dec 14 01:51:34 1999 From: Dan Mick (Dan Mick) Date: Mon, 13 Dec 1999 17:51:34 -0800 (PST) Subject: [Mailman-Developers] Wish list item: anyone working on it? Message-ID: <199912140151.RAA13497@utopia.West.Sun.COM> I wish that the admindb interface would show a different "default" message based on the type of the 'post' request; that is, now, it always displays the suggested text Please do *not* post administrative requests to the mailing list! If you wish to subscribe, visit %s or send a 'help' message to the the request address, %s , for instructions but that's only appropriate for some sort of post requests. I see that "AddRequest" sometimes gets called with standard members of Errors, but sometimes gets called with hard-coded strings; what one would need is to regularize all those, and then have a mapping between the Errors argument and the suggested text argument (like a more-complicated Errors object, perhaps). I could probably hack this together for MM 1.1; is there any point in me doing so and shipping diffs to somewhere? i.e. * is anyone working on this, or * is anyone known to be completely reorganizing this source anyway, and * what's the least-painful way to contribute changes? From bwarsaw@cnri.reston.va.us (Barry A. Warsaw) Tue Dec 14 04:46:55 1999 From: bwarsaw@cnri.reston.va.us (Barry A. Warsaw) (Barry A. Warsaw) Date: Mon, 13 Dec 1999 23:46:55 -0500 (EST) Subject: [Mailman-Developers] Wish list item: anyone working on it? References: <199912140151.RAA13497@utopia.West.Sun.COM> Message-ID: <14421.52159.913977.859212@anthem.cnri.reston.va.us> >>>>> "DM" == Dan Mick writes: DM> I see that "AddRequest" sometimes gets called with standard DM> members of Errors, but sometimes gets called with hard-coded DM> strings; what one would need is to regularize all those, and DM> then have a mapping between the Errors argument and the DM> suggested text argument (like a more-complicated Errors DM> object, perhaps). DM> I could probably hack this together for MM 1.1; is there any DM> point in me doing so and shipping diffs to somewhere? All this /has/ changed for the next release, so if you're interested in doing something like this, you'll need to checkout the current CVS tree and produce diffs against that. I suspect the changes will be large enough that a disclaimer or FSF assignment will be required they can be folded into the distribution. -Barry From bwarsaw@cnri.reston.va.us (Barry A. Warsaw) Tue Dec 14 05:17:16 1999 From: bwarsaw@cnri.reston.va.us (Barry A. Warsaw) (Barry A. Warsaw) Date: Tue, 14 Dec 1999 00:17:16 -0500 (EST) Subject: [Mailman-Developers] CVS access via web Message-ID: <14421.53980.59877.30446@anthem.cnri.reston.va.us> FYI: The Mailman CVS tree can be accessed via the web, using Greg Stein's cool ViewCVS stuff. See http://cvs.python.org/cgi-bin/viewcvs.cgi Enjoy! -Barry From ricardo@miss-janet.com Tue Dec 14 07:34:57 1999 From: ricardo@miss-janet.com (Ricardo Kustner) Date: Tue, 14 Dec 1999 08:34:57 +0100 Subject: [Mailman-Developers] illegal seek Message-ID: <19991214083457.A21332@miss-janet.com> >Okay, so sys.stdin isn't seekable everywhere :) Give the below patch >a try. a few days ago Barry send me a patch that fixes an "Illegal Seek" error which I'm getting on my system (in scripts/post)... this hasn't been checked in the CVS yet... but I noticed this problem pops up in other places too... I think my mailinglist isn't working 100% now (but thats what you get for using 'experimental' version ;) ) Mailman/Message.py (49) also does a self.rewindbody(), causing the same error on my system. ... i'm seeing this appear several times a day in the error log so something isn't going that good on my list .... :) i'm curious to know what this problem is related to? is it the C library? my system is running good old libc5 Ricardo. -- From bwarsaw@cnri.reston.va.us (Barry A. Warsaw) Tue Dec 14 16:30:54 1999 From: bwarsaw@cnri.reston.va.us (Barry A. Warsaw) (Barry A. Warsaw) Date: Tue, 14 Dec 1999 11:30:54 -0500 (EST) Subject: [Mailman-Developers] illegal seek References: <19991214083457.A21332@miss-janet.com> Message-ID: <14422.28862.425131.935200@anthem.cnri.reston.va.us> >>>>> "RK" == Ricardo Kustner writes: RK> a few days ago Barry send me a patch that fixes an "Illegal RK> Seek" error which I'm getting on my system (in RK> scripts/post)... this hasn't been checked in the CVS RK> yet... I just checked it in. RK> but I noticed this problem pops up in other places too... I RK> think my mailinglist isn't working 100% now (but thats what RK> you get for using 'experimental' version ;) ) RK> Mailman/Message.py (49) also does a self.rewindbody(), causing RK> the same error on my system. ... stdin can't be guaranteed to be seekable, so for portability we should read it into a StringIO object and use that as the underlying `file-like input'. Can you tell me what else breaks? A quick grep through the source shows that mailcmd is probably broken (i.e. yourlist-request I'll bet doesn't work). I'll check in some patches for that next. -Barry From mats@laplaza.org Tue Dec 14 17:03:33 1999 From: mats@laplaza.org (Mats Wichmann) Date: Tue, 14 Dec 1999 10:03:33 -0700 Subject: [Mailman-Developers] Re: [Mailman-Users] fetch by email In-Reply-To: <14422.30277.889782.393367@anthem.cnri.reston.va.us> References: <199912141203.MAA25090@ma101.gold.ac.uk> <3.0.6.32.19991214073542.00fab5c0@laplaza.org> Message-ID: <3.0.6.32.19991214100333.00e429f0@laplaza.org> At 11:54 AM 12/14/1999 -0500, you wrote: > >>>>>> "MW" == Mats Wichmann writes: > > MW> That is - fetch-by-email of arbitrary files from an archive > MW> area. In addition to automatically generated archives > MW> which mailman makes available in downloadable form via > MW> a web page, can an arbitrary file be added to the area and > MW> picked up - and is there a way archive files can be picked > MW> up by email request? > >Mailman currently doesn't support this, but it would not be hard to >add, if you're up for a bit of Python hacking. If you think you'd >like to implement something like this, please move the discussion over >to mailman-developers where we can design an approach. > >-Barry I'm game to try, since I have the incentive to get this working.... So...consider it moved. Mats From Dan Mick Wed Dec 15 05:45:53 1999 From: Dan Mick (Dan Mick) Date: Tue, 14 Dec 1999 21:45:53 -0800 (PST) Subject: [Mailman-Developers] Secure admin pages Message-ID: <199912150546.VAA22956@utopia.West.Sun.COM> We set up an SSL arrangement so our admin password isn't traversing the net in clear text, but were temporarily thwarted by the fact that the admin CGI scripts sometimes use Absolute paths, which didn't include the https://. I made some hacks; comments? (Does this look right, Barry et. al.?) (This is to v1.1; if it looks good, I'll put it in CVS and put it back) How does the putback process usually work? Does someone review code, or do we have a "holding area" that's protected somehow, or?... Anyway, here are context diffs: =================================================================== RCS file: RCS/admin.py,v retrieving revision 1.1 diff -c -r1.1 admin.py *** admin.py 1999/12/15 05:29:10 1.1 --- admin.py 1999/12/15 05:29:50 *************** *** 534,540 **** buttons = [] for ci in chunk_indices: start, end = chunks[ci][0], chunks[ci][-1] ! url = lst.GetAbsoluteScriptURL('admin') buttons.append(" from %s to %s " % ( url, ci, start, end)) buttons = apply(UnorderedList, tuple(buttons)) --- 534,540 ---- buttons = [] for ci in chunk_indices: start, end = chunks[ci][0], chunks[ci][-1] ! url = lst.GetRelativeScriptURL('admin') buttons.append(" from %s to %s " % ( url, ci, start, end)) buttons = apply(UnorderedList, tuple(buttons)) *************** *** 544,550 **** footer = "

" for member in all: mtext = '%s' % ( ! lst.GetAbsoluteOptionsURL(member, obscured=1), lst.GetUserSubscribedAddress(member)) cells = [mtext + "" % (member), Center(CheckBox(member + "_subscribed", "on", 1).Format())] --- 544,550 ---- footer = "

" for member in all: mtext = '%s' % ( ! lst.GetRelativeOptionsURL(member, obscured=1), lst.GetUserSubscribedAddress(member)) cells = [mtext + "" % (member), Center(CheckBox(member + "_subscribed", "on", 1).Format())] =================================================================== RCS file: RCS/MailList.py,v retrieving revision 1.1 diff -c -r1.1 MailList.py *** MailList.py 1999/12/15 05:30:09 1.1 --- MailList.py 1999/12/15 05:31:01 *************** *** 194,199 **** --- 194,209 ---- treated = addr return "%s/%s" % (options, treated) + def GetRelativeOptionsURL(self, addr, obscured=0): + # address could come in case-preserved + addr = string.lower(addr) + options = self.GetRelativeScriptURL('options') + if obscured: + treated = Utils.ObscureEmail(addr, for_text=0) + else: + treated = addr + return "%s/%s" % (options, treated) + def GetUserOption(self, user, option): """Return user's setting for option, defaulting to 0 if no settings.""" user = self.GetUserCanonicalAddress(user) From luca.ghedini@mail.ing.unibo.it Wed Dec 15 16:38:17 1999 From: luca.ghedini@mail.ing.unibo.it (Luca ghedini) Date: Wed, 15 Dec 1999 17:38:17 +0100 Subject: [Mailman-Developers] subscriber additional data References: <19991214083457.A21332@miss-janet.com> Message-ID: <3857C3F9.E5BA72B9@mail.ing.unibo.it> HI. I'm using mailman to manage a bunk of mailing list. Is it possible store some information about the subscriber? It will be usefull store some personal data as real name, adresses, tel num. etc? Tnk in advance Luca "ghedo" ghedini From lalo@webcom.com Thu Dec 16 11:00:58 1999 From: lalo@webcom.com (Lalo Martins) Date: Thu, 16 Dec 1999 09:00:58 -0200 Subject: [Mailman-Developers] Technical CGI question Message-ID: <19991216090058.B15823@webcom.com> Hi. I'm not currently subscribed to this list, but I probably will as soon as I get back from vacation. I'm writing a Zope Product to interface with Mailman, for sites (like mine) that don't do any webserving stuff outside Zope. I chose Mailman mostly because it's Python-based, and GNU. After the introduction... I'm at step 1, which is trying to figure out mailman's internals, specially the CGI stuff. What I'd like to know is, is there any good reason why you run all your CGI interface trough a compiled wrapper, instead of just directly running the python scripts? I found out python is quite cool for CGI (before I found out Zope and dumped CGI completely). And of course you know that the python path stuff is quite easy to solve. (Of course, please CC replies back to me. I'll be glad to discuss arguments when I'm back, for now I only want a quick explanation.) []s, |alo +---- -- I am Lalo of deB-org. You will be freed. Resistance is futile. http://www.webcom.com/lalo mailto:lalo@webcom.com pgp key in the web page Debian GNU/Linux --- http://www.debian.org Brazil of Darkness -- http://zope.gf.com.br/BroDar From mr@uniway.be Thu Dec 16 14:18:58 1999 From: mr@uniway.be (mr) Date: Thu, 16 Dec 1999 15:18:58 +0100 Subject: [Mailman-Developers] [Fwd: [Mailman-Users] Cron Daemon errors] Message-ID: <3858F4D2.A88CE3A0@uniway.be> --------------06478C8F0600EC889B40BA04 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit mr wrote: > Hello, > > I just learned about and am using mailman in my job. I have installed > it and have got it half-way working (I see the "Your New Mailing List" > mail and can click on these links. However I do not understand the > error messages I am receiving from the Cron Daemon. The most important > one being (I believe, because it is the first one I always receive): > > Traceback (innermost last): > File "/home/mailman/cron/gate_news", line 119, in ? > main() > File "/home/mailman/cron/gate_news", line 58, in main > mlist = MailList.MailList(name, lock=0) > File "/home/mailman/Mailman/MailList.py", line 62, in __init__ > self.Load() > File "/home/mailman/Mailman/MailList.py", line 810, in Load > raise Errors.MMBadListError, 'Failed to access config info' > MMBadListError: Failed to access config info > > I have just been able to locate these errors but have no idea what > these errors mean or how to fix them. > > Can someone help me? > > Thanks in advance, > > Kirsten Melanie Royal > > -- > > "?.I don't have to eat, I don't have to drink, I just have to study." > > -- "?.I don't have to eat, I don't have to drink, I just have to study." --------------06478C8F0600EC889B40BA04 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit mr wrote:

Hello,

I just learned about and am using mailman in my job. I have installed it and have got it half-way working (I see the "Your New Mailing List" mail and can click on these links. However I do not understand the error messages I am receiving from the Cron Daemon. The most important one being (I believe, because it is the first one I always receive):

Traceback (innermost last):
File "/home/mailman/cron/gate_news", line 119, in ?
main()
File "/home/mailman/cron/gate_news", line 58, in main
mlist = MailList.MailList(name, lock=0)
File "/home/mailman/Mailman/MailList.py", line 62, in __init__
self.Load()
File "/home/mailman/Mailman/MailList.py", line 810, in Load
raise Errors.MMBadListError, 'Failed to access config info'
MMBadListError: Failed to access config info

I have just been able to locate these errors but have no idea what these errors mean or how to fix them.

Can someone help me?

Thanks in advance,

Kirsten Melanie Royal 

-- 

"?.I don't have to eat, I don't have to drink, I just have to study."
 
-- 

"?.I don't have to eat, I don't have to drink, I just have to study."
  --------------06478C8F0600EC889B40BA04-- From mr@uniway.be Thu Dec 16 16:09:26 1999 From: mr@uniway.be (mr) Date: Thu, 16 Dec 1999 17:09:26 +0100 Subject: [Mailman-Developers] Cron error messages Message-ID: <38590EB6.A6A8CB78@uniway.be> --------------E3F19FA1CE01AA2848C554B0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hello once again, I have some other messages that I do not understand at all either, here they are: Traceback (innermost last): File "/home/mailman/cron/checkdbs", line 77, in ? main(verbose=(len(sys.argv) > 1 File "/home/mailman/cron/checkdbs", line 34, in main list = MailList.MailList(name, lock = 0) File "/home/mailman/Mailman/MailList.py", line 62, in __init__ self.Load() File "/home/mailman/Mailman/MailList.py", line 810, in Load raise Errors.MMBadListError, 'Failed to access config info' MMBadListError: Failed to access config info AND Traceback (innermost last): File "/home/mailman/cron/run_queue", line 46, in ? main() File "/home/mailman/cron/run_queue", line 39, in main lockfile.lock() File "/home/mailman/Mailman/LockFile.py", line 186, in lock os.link(self.__lockfile, self.__tmpfname) OSError: [Errno 2] No such file or directory IN ADDITION TO: Traceback (innermost last): File "/home/mailman/cron/gate_news", line 119, in ? main() File "/home/mailman/cron/gate_news", line 58, in main mlist = MailList.MailList(name, lock=0) File "/home/mailman/Mailman/MailList.py", line 62, in __init__ self.Load() File "/home/mailman/Mailman/MailList.py", line 810, in Load raise Errors.MMBadListError, 'Failed to access config info' MMBadListError: Failed to access config info Like I said in a previous message, I see my "Your new mailing list" page and I can click on the links but I have these errors. I just got assigned this project to use mailman a week ago and have never heard about it before that time so I am very sorry if my explainations are not very good ones. Another note: I had no errors on the installation. Thank you in advance for any help you can give me. Kirsten Melanie Royal -- "...I don't have to eat, I don't have to drink, I just have to study." --------------E3F19FA1CE01AA2848C554B0 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit Hello once again,

I have some other messages that I do not understand at all either, here they are:
 

Traceback (innermost last):
File "/home/mailman/cron/checkdbs", line 77, in ?
main(verbose=(len(sys.argv) > 1
File "/home/mailman/cron/checkdbs", line 34, in main
list = MailList.MailList(name, lock = 0)
File "/home/mailman/Mailman/MailList.py", line 62, in __init__
self.Load()
File "/home/mailman/Mailman/MailList.py", line 810, in Load
raise Errors.MMBadListError, 'Failed to access config info'
MMBadListError: Failed to access config info

AND

Traceback (innermost last):
File "/home/mailman/cron/run_queue", line 46, in ?
main()
File "/home/mailman/cron/run_queue", line 39, in main
lockfile.lock()
File "/home/mailman/Mailman/LockFile.py", line 186, in lock
os.link(self.__lockfile, self.__tmpfname)
OSError: [Errno 2] No such file or directory

IN ADDITION TO:
 
Traceback (innermost last):  File "/home/mailman/cron/gate_news", line 119, in ?
main()
File "/home/mailman/cron/gate_news", line 58, in main
mlist = MailList.MailList(name, lock=0)
File "/home/mailman/Mailman/MailList.py", line 62, in __init__
self.Load()
File "/home/mailman/Mailman/MailList.py", line 810, in Load
raise Errors.MMBadListError, 'Failed to access config info'
MMBadListError: Failed to access config info

Like I said in a previous message,  I see my "Your new mailing list" page and I can click on the links but I have these
errors. I just got assigned this project to use mailman a week ago and have never heard about it before that time so I am very sorry if my explainations are not very good ones.

Another note: I had no errors on the installation.

Thank you in advance for any help you can give me.

Kirsten Melanie Royal 

-- 

"...I don't have to eat, I don't have to drink, I just have to study."
  --------------E3F19FA1CE01AA2848C554B0-- From bwarsaw@cnri.reston.va.us (Barry A. Warsaw) Fri Dec 17 05:38:46 1999 From: bwarsaw@cnri.reston.va.us (Barry A. Warsaw) (Barry A. Warsaw) Date: Fri, 17 Dec 1999 00:38:46 -0500 (EST) Subject: [Mailman-Developers] Secure admin pages References: <199912150546.VAA22956@utopia.West.Sun.COM> Message-ID: <14425.52326.802876.889079@anthem.cnri.reston.va.us> >>>>> "DM" == Dan Mick writes: DM> We set up an SSL arrangement so our admin password isn't DM> traversing the net in clear text, but were temporarily DM> thwarted by the fact that the admin CGI scripts sometimes use DM> Absolute paths, which didn't include the https://. I made DM> some hacks; comments? (Does this look right, Barry et. al.?) What do you think of the following instead. def GetScriptURL(self, scriptname, relative=0): if relative: prefix = '../' * Utils.GetNestingLevel() elif self.web_page_url: prefix = self.web_page_url else: prefix = mm_cfg.DEFAULT_URL i = len(prefix)-1 while i >= 0 and prefix[i] == '/': i = i - 1 prefix = prefix[:i+1] return '%s/%s%s/%s' % (prefix, scriptname, mm_cfg.CGIEXT, self.internal_name()) def GetOptionsURL(self, scriptname, obscure=0, relative=0): addr = string.lower(addr) url = self.GetScriptURL('options', relative) if obscured: addr = Utils.ObscureEmail(addr) return '%s/%s' % (url, addr) and getting rid of GetRelativeScriptURL(), GetAbsoluteScriptURL(), GetAbsoluteOptionsURL(). Also, modifying the rest of the source to use just one of these two new functions. If you like it, I'll make these changes to the CVS tree. DM> How does the putback process usually work? Does someone DM> review code, or do we have a "holding area" that's protected DM> somehow, or?... Basically, post the code to mailman-developers, or send it to mailman-cabal. It's up to one of the core maintainers to integrate it with the CVS code base. -Barry From ricardo@miss-janet.com Fri Dec 17 19:31:39 1999 From: ricardo@miss-janet.com (Ricardo Kustner) Date: Fri, 17 Dec 1999 20:31:39 +0100 Subject: [Mailman-Developers] Mailman/Cgi/admindb.py Message-ID: <19991217203139.A21188@miss-janet.com> Hi, I've added to following lines of code to seperate the message body from the header in PrintPostRequest() around line 197 ... fp = open(os.path.join(mm_cfg.DATA_DIR, filename)) # text = fp.read(mm_cfg.ADMINDB_PAGE_TEXT_LIMIT) msg_header = "" msg_body = "" for line in fp.readlines(): if msg_body == "": if line != "\n": msg_header = msg_header + line else: msg_body = line else: msg_body = msg_body + line fp.close() in my copy of admindb.py i don't need the mail headers, so I just output msg_body in the textarea... but maybe it could be made as an option "Include message headers on approval page Y/N" in the mailinglist configuration... Ricardo. -- From ricardo@miss-janet.com Fri Dec 17 20:23:31 1999 From: ricardo@miss-janet.com (Ricardo Kustner) Date: Fri, 17 Dec 1999 21:23:31 +0100 Subject: [Mailman-Developers] sending mail Message-ID: <19991217212331.A21790@miss-janet.com> Hi, i'd like to add a "send copy of email to..." function inside admindb.py (to optionally allow posts on the approval page to be send to a certain email address)... what i need to do i guess is pipe it to the MTA and only change the "To:" line ... can anybody advise me on which is the best python or MM function to use for this? Thanks, Ricardo. -- From Budde@tu-harburg.de Sun Dec 19 14:54:49 1999 From: Budde@tu-harburg.de (Marco Budde) Date: Sun, 19 Dec 1999 14:54:49 +0000 Subject: [Mailman-Developers] Bad/Invalid email address Message-ID: <385CF1B9.7146E4DF@tu-harburg.de> Hi! When subscribing a local user address like "mbudde" or even "mbudde@local" I get this error message: "Bad/Invalid email address". Why? This is a normal email address. I´m using version 1.0b8. cu, Marco -- -- Linux HOWTOs: Die besten Lösungen der Linuxgemeinde -- ISBN 3-8266-0498-9 Uni: Budde@tu-harburg.de Fido: 2:240/6298.5 Mailbox: mbudde@sms.antar.com http://www.tu-harburg.de/~semb2204/ From mailman-users@python.org Sun Dec 19 23:00:26 1999 From: mailman-users@python.org (Sean Reifschneider) Date: Sun, 19 Dec 1999 16:00:26 -0700 Subject: [Mailman-Developers] Bad/Invalid email address In-Reply-To: <385CF1B9.7146E4DF@tu-harburg.de>; from Marco Budde on Sun, Dec 19, 1999 at 02:54:49PM +0000 References: <385CF1B9.7146E4DF@tu-harburg.de> Message-ID: <19991219160026.E26508@tummy.com> [I'm setting replies to go to mailman-users] On Sun, Dec 19, 1999 at 02:54:49PM +0000, Marco Budde wrote: >When subscribing a local user address like >"mbudde" or even "mbudde@local" I get this >error message: "Bad/Invalid email address". > >Why? This is a normal email address. Understand the distinction between "normal" and "valid". You can send mail to a local user simply by specifying "user", however that's because the local MTA does some magic to figure out where it goes. Since mailman has historicly simply handed delivery off to a standard SMTP mail server for the actual delivery, it means that the addresses it gets need to be RFC-822 compliant. I presume if you use "mbudde@domain.com", where "domain.com" is your domain, that it works fine? Mailman is simply being canonical, which IMHO is better than relying on magic to happen behind the scenes. For example, if you specified "mbudde", and then later changed the SMTP server, or moved the mailman installation to another host, the behavior may change. Sean -- If you have too many special cases, you are doing it wrong. -- Craig Zerouni Sean Reifschneider, Inimitably Superfluous URL: HP-UX/Linux/FreeBSD/BSDOS scanning software. From ricardo@miss-janet.com Mon Dec 20 19:29:30 1999 From: ricardo@miss-janet.com (Ricardo Kustner) Date: Mon, 20 Dec 1999 20:29:30 +0100 Subject: [Mailman-Developers] 1.2 bug Message-ID: <19991220202930.B30707@miss-janet.com> Hi, i'm getting the following error often when approving posts on the admindb page... there were 12 posts and about 3 of them were marked as "Discard", the rest was approved... i had this earlier... and when i reloaded the admindb page, some posts showed up again, even though they were send out to the list anyway... Traceback (innermost last): File "/usr/local/mailman/scripts/driver", line 112, in run_main main() File "../Mailman/Cgi/admindb.py", line 123, in main mlist.Save() File "/usr/local/mailman/Mailman/MailList.py", line 814, in Save self.SaveRequestsDb() File "/usr/local/mailman/Mailman/ListAdmin.py", line 89, in SaveRequestsDb self.__closedb() File "/usr/local/mailman/Mailman/ListAdmin.py", line 73, in __closedb assert self.Locked() AssertionError: -- Ricardo. -- International Janet Jackson fanclub called MISS JANET. For more information write to: Miss Janet. P.O.Box 10016, 1001 EA Amsterdam, The Netherlands Fax/phone: +31-(0)20-7764493 Email: fanclub@miss-janet.com Or check out our website: http://miss-janet.com From bwarsaw@cnri.reston.va.us (Barry A. Warsaw) Mon Dec 20 19:35:27 1999 From: bwarsaw@cnri.reston.va.us (Barry A. Warsaw) (Barry A. Warsaw) Date: Mon, 20 Dec 1999 14:35:27 -0500 (EST) Subject: [Mailman-Developers] 1.2 bug References: <19991220202930.B30707@miss-janet.com> Message-ID: <14430.34047.185174.886328@anthem.cnri.reston.va.us> >>>>> "RK" == Ricardo Kustner writes: RK> i'm getting the following error often when approving posts RK> on the admindb page... there were 12 posts and about 3 of RK> them were marked as "Discard", the rest was approved... RK> i had this earlier... and when i reloaded the admindb page, RK> some posts showed up again, even though they were send out RK> to the list anyway... I've seen this too when doing approves of python-list. However, I haven't seen any lately, while using the very freshest CVS update. I'm not sure why these are happening, but I've added more logging to try to help nail down the bug. -Barry From allen@gist.net.au Fri Dec 24 02:50:47 1999 From: allen@gist.net.au (Allen Bolderoff) Date: Fri, 24 Dec 1999 13:20:47 +1030 Subject: [Mailman-Developers] UPDATE-2 - problem with cookies? Round 2 In-Reply-To: Your message of "Thu, 23 Dec 1999 11:10:01 MDT." <014701bf4d68$8e7011b0$ea17a8c0@jordan> Message-ID: <199912240250.NAA13557@harper.gist.net.au> OK. let me clarify myself. it appears, that if mailman has not set a cookie, but a sitewide cookie exists in the browser, mailman will try to use the sitewide cookie, without checking if it is in fact the correct cookie (which at this point is not created). so, instead of creating a new cookie, as it should, it is dying in the process of parsing the wrong cookie. Hope this helps the developers. Allen -- +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Allen Bolderoff LNC - Redhat and Linux, help and commentary http://linux.netnerve.com CTPC - Caffeine - get it here: http://www.coffee-tea-pots-cups.com/ +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ GPG fingerprint = CBB0 8626 702C 3D01 B5AD A54A DC2C 93B7 3E4B 6472 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Return-Path: Delivered-To: mailman-developers@dinsdale.python.org Received: from python.org (parrot.python.org [132.151.1.90]) by dinsdale.python.org (Postfix) with ESMTP id A809B1CD21; Thu, 23 Dec 1999 21:50:36 -0500 (EST) Received: from ns1.gist.net.au (IDENT:root@main.gist.net.au [203.20.102.2]) by python.org (8.9.1a/8.9.1) with ESMTP id VAA21724; Thu, 23 Dec 1999 21:50:33 -0500 (EST) Received: from harper.gist.net.au (root@harper.gist.net.au [203.20.102.68]) by ns1.gist.net.au (8.8.7/8.8.7) with ESMTP id MAA03331; Fri, 24 Dec 1999 12:18:59 +1030 Received: from harper.gist.net.au (IDENT:allen@localhost [127.0.0.1]) by harper.gist.net.au (8.9.3/8.8.7) with ESMTP id NAA13571; Fri, 24 Dec 1999 13:21:14 +1030 Resent-Message-Id: <199912240251.NAA13571@harper.gist.net.au> Message-Id: <199912240251.NAA13571@harper.gist.net.au> X-Mailer: exmh version 2.1.0 To: blurr@txraves.org In-Reply-To: Your message of "Thu, 23 Dec 1999 11:10:01 MDT." <014701bf4d68$8e7011b0$ea17a8c0@jordan> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 24 Dec 1999 13:14:17 +1030 From: Allen Bolderoff Resent-To: mailman-users@python.org Resent-Cc: mailman-developers@python.org Resent-Date: Fri, 24 Dec 1999 13:21:14 +1030 Resent-From: Allen Bolderoff Resent-Sender: allen@harper.gist.net.au Subject: [Mailman-Developers] UPDATE - problem with cookies? Round 2 Sender: mailman-developers-admin@python.org Errors-To: mailman-developers-admin@python.org X-BeenThere: mailman-developers@python.org X-Mailman-Version: 1.2 (experimental) Precedence: bulk List-Id: Mailman mailing list developers > > What would you like us to do? Yes, it looks like a bug. Have you tried > > either examining the cookie or deleting it?... since the error message > > pretty > > clearly points to the file of code, and the code is pretty clearly > > examining > > the cookie data itself and finding something wrong.... > > > > You might add something like > > > > if len(cookiedata) < len(key): return 0 > > > > before > > > > if cookiedata[keylen+1] <> '"' and cookiedata[-1].... > > > > in SecurityManager.py. > > > > I haven't tested the fix, because I don't know if that's what's going > > wrong. This does not work, however, what I can tell you is that if there is another cookie set by the webserver, it appears to confuse mailman. Mailman then tries to use the other cookie. ie - I use roxen - http://www.roxen.com roxen sets a unique cookie for every user that comes to the site. when I turn on the debug messages by removing the commented debug code, and access a bad page, I get the cookie, which is called RoxenUserID showing in the debug file, not the one we would expect. In fact, this seems to happen when the cookie does not exist (the authentication cookie that mailman makesm that is) Hope this helps -- +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Allen Bolderoff LNC - Redhat and Linux, help and commentary http://linux.netnerve.com CTPC - Caffeine - get it here: http://www.coffee-tea-pots-cups.com/ +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ GPG fingerprint = CBB0 8626 702C 3D01 B5AD A54A DC2C 93B7 3E4B 6472 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ From gstein@lyra.org Sun Dec 26 17:58:11 1999 From: gstein@lyra.org (Greg Stein) Date: Sun, 26 Dec 1999 09:58:11 -0800 (PST) Subject: [Mailman-Developers] Error encountered on the Mailman webpage (fwd) Message-ID: This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. ------_=_NextPart_000_01BF4FBE.BCC7413E Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-ID: -- Greg Stein, http://www.lyra.org/ ---------- Forwarded message ---------- Date: Sun, 26 Dec 1999 11:32:01 -0500 From: Aaron La Mar To: "'webmaster@list.org '" Subject: Error encountered on the Mailman webpage I got the following error when I clicked on "Mailman-Users" on your index page. Bug in Mailman version 1.2 (experimental) 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 (innermost last): File "/home/mailman/scripts/driver", line 112, in run_main main() File "/home/mailman/Mailman/Cgi/listinfo.py", line 54, in main FormatListListinfo(mlist) File "/home/mailman/Mailman/Cgi/listinfo.py", line 163, in FormatListListinfo replacements = mlist.GetStandardReplacements() File "/home/mailman/Mailman/HTMLFormatter.py", line 347, in GetStandardReplacements return { File "/home/mailman/Mailman/HTMLFormatter.py", line 50, in GetMailmanFooter Address( File "/home/mailman/Mailman/MailList.py", line 209, in GetRelativeScriptURL return GetScriptURL(self, scriptname, relative=1) NameError: GetScriptURL ---------------------------------------------------------------------------- ---- Environment variables: Variable Value DOCUMENT_ROOT /usr/local/apache/htdocs SERVER_ADDR 132.151.1.21 HTTP_ACCEPT_ENCODING gzip, deflate REMOTE_HOST parrot.python.org SERVER_PORT 80 PATH_TRANSLATED /usr/local/apache/htdocs/mailman-users REMOTE_ADDR 132.151.1.90 HTTP_ACCEPT_LANGUAGE en-us GATEWAY_INTERFACE CGI/1.1 SERVER_NAME dinsdale.python.org TZ US/Eastern HTTP_USER_AGENT Mozilla/4.0 (compatible; MSIE 5.0; Windows 98; DigExt) HTTP_ACCEPT image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, application/vnd.ms-excel, application/msword, application/vnd.ms-powerpoint, */* REQUEST_URI /mailman/listinfo/mailman-users PATH /usr/sbin:/usr/bin QUERY_STRING SCRIPT_FILENAME /home/mailman/cgi-bin/listinfo PATH_INFO /mailman-users HTTP_HOST dinsdale.python.org REQUEST_METHOD GET SERVER_SIGNATURE Apache/1.3.9 Server at dinsdale.python.org Port 80 SCRIPT_NAME /mailman/listinfo SERVER_ADMIN webmaster@python.org SERVER_SOFTWARE Apache/1.3.9 (Unix) PYTHONPATH /home/mailman HTTP_REFERER http://www.list.org/ SERVER_PROTOCOL HTTP/1.0 REMOTE_PORT 58702 ------_=_NextPart_000_01BF4FBE.BCC7413E Content-Type: APPLICATION/OCTET-STREAM; NAME="Bug in Mailman version 1_2 (experimental).htm" Content-ID: Content-Description: Content-Disposition: ATTACHMENT; FILENAME="Bug in Mailman version 1_2 (experimental).htm" Bug in Mailman version 1.2 (experimental)

Bug in Mailman version 1.2 (experimental)

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 (innermost last):
  File "/home/mailman/scripts/driver", line 112, in run_main
    main()
  File "/home/mailman/Mailman/Cgi/listinfo.py", line 54, in main
    FormatListListinfo(mlist)
  File "/home/mailman/Mailman/Cgi/listinfo.py", line 163, in FormatListListinfo
    replacements = mlist.GetStandardReplacements()
  File "/home/mailman/Mailman/HTMLFormatter.py", line 347, in GetStandardReplacements
    return {
  File "/home/mailman/Mailman/HTMLFormatter.py", line 50, in GetMailmanFooter
    Address(
  File "/home/mailman/Mailman/MailList.py", line 209, in GetRelativeScriptURL
    return GetScriptURL(self, scriptname, relative=1)
NameError: GetScriptURL

Environment variables:

Variable Value
DOCUMENT_ROOT /usr/local/apache/htdocs
SERVER_ADDR 132.151.1.21
HTTP_ACCEPT_ENCODING gzip, deflate
REMOTE_HOST parrot.python.org
SERVER_PORT 80
PATH_TRANSLATED /usr/local/apache/htdocs/mailman-users
REMOTE_ADDR 132.151.1.90
HTTP_ACCEPT_LANGUAGE en-us
GATEWAY_INTERFACE CGI/1.1
SERVER_NAME dinsdale.python.org
TZ US/Eastern
HTTP_USER_AGENT Mozilla/4.0 (compatible; MSIE 5.0; Windows 98; DigExt)
HTTP_ACCEPT */*
REQUEST_URI /mailman/listinfo/mailman-users
PATH /usr/sbin:/usr/bin
QUERY_STRING
SCRIPT_FILENAME /home/mailman/cgi-bin/listinfo
PATH_INFO /mailman-users
HTTP_HOST dinsdale.python.org
REQUEST_METHOD GET
SERVER_SIGNATURE
Apache/1.3.9 Server at dinsdale.python.org Port 80
SCRIPT_NAME /mailman/listinfo
SERVER_ADMIN webmaster@python.org
SERVER_SOFTWARE Apache/1.3.9 (Unix)
PYTHONPATH /home/mailman
SERVER_PROTOCOL HTTP/1.0
REMOTE_PORT 58710

------_=_NextPart_000_01BF4FBE.BCC7413E-- From bwarsaw@python.org Sun Dec 26 19:24:47 1999 From: bwarsaw@python.org (Barry A. Warsaw) Date: Sun, 26 Dec 1999 14:24:47 -0500 (EST) Subject: [Mailman-Developers] Re: Error encountered on the Mailman webpage (fwd) References: Message-ID: <14438.27519.908881.720297@anthem.cnri.reston.va.us> Temporary glitch, now fixed. From bwarsaw@cnri.reston.va.us (Barry A. Warsaw) Mon Dec 27 16:18:23 1999 From: bwarsaw@cnri.reston.va.us (Barry A. Warsaw) (Barry A. Warsaw) Date: Mon, 27 Dec 1999 11:18:23 -0500 (EST) Subject: [Mailman-Developers] New mailing list for internationalization Message-ID: <14439.37199.785784.796071@anthem.cnri.reston.va.us> Mailman Developers, I have created a new mailing list called mailman-i18n@python.org for discussions focused on internationalizing Mailman. This SIG has a very narrow mission: at first it will be to discuss design issues and patches to the source code to support multi-lingual mailing lists. Once that is integrated into the codebase, the SIG will primarily be a forum for translators. I urge any interested parties to subscribe by visiting http://www.python.org/mailman/listinfo/mailman-i18n I'd like to keep I18N discussions off of mailman-developers. Current status: I received a large patchset from Juan and Victoriano, which contained some stuff by Mads and others, which I started looking at over the Xmas break. I'd like to move all private discussions on this stuff to the SIG so everyone can contribute. I plan on posting a more detailed summary to the SIG within a couple of days (I'm too busy right now). That'll also give people a chance to subscribe to the new list. Cheers, -Barry From root@theporch.com Mon Dec 27 22:21:49 1999 From: root@theporch.com (Phillip Porch) Date: Mon, 27 Dec 1999 16:21:49 -0600 (CST) Subject: [Mailman-Developers] Bug in Mailman version 1.2 (experimental) (fwd) Message-ID: ---------- Forwarded message ---------- Date: Mon, 27 Dec 1999 16:14:43 -0000 From: Phillip Porch To: root@theporch.com Subject: Bug in Mailman version 1.2 (experimental) Bug in Mailman version 1.2 (experimental) Bug in Mailman version 1.2 (experimental) 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 (innermost last): File "/home/mailman/scripts/driver", line 112, in run_main main() File "../Mailman/Cgi/admin.py", line 165, in main FormatConfiguration(doc, mlist, category, category_suffix, cgi_data) File "../Mailman/Cgi/admin.py", line 311, in FormatConfiguration form.AddItem(FormatOptionsSection(category, mlist, cgi_data)) File "../Mailman/Cgi/admin.py", line 326, in FormatOptionsSection return FormatMembershipOptions(mlist, cgi_data) File "../Mailman/Cgi/admin.py", line 565, in FormatMembershipOptions mtext = '%s' % ( TypeError: unexpected keyword argument: obscured -------------------------------------------------------------------------------- Environment variables: Variable Value DOCUMENT_ROOT /home SERVER_ADDR 207.234.31.38 HTTP_ACCEPT_ENCODING gzip, deflate SERVER_PORT 8080 PATH_TRANSLATED /home/notam/members REMOTE_ADDR 207.234.31.43 HTTP_ACCEPT_LANGUAGE en-us GATEWAY_INTERFACE CGI/1.1 SERVER_NAME sco.theporch.com TZ CST6CDT HTTP_USER_AGENT Mozilla/4.0 (compatible; MSIE 5.01; Windows 98) QUERY_STRING HTTP_ACCEPT image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, */* REQUEST_URI /mailman/admin/notam/members PATH /etc:/bin:/usr/bin REMOTE_PORT 1052 SCRIPT_FILENAME /home/mailman/cgi-bin/admin PATH_INFO /notam/members HTTP_HOST www.theporch.com:8080 REQUEST_METHOD GET SERVER_SIGNATURE Apache/1.3.9 Server at sco.theporch.com Port 8080 SCRIPT_NAME /mailman/admin SERVER_ADMIN root@sco.theporch.com SERVER_SOFTWARE Apache/1.3.9 (Unix) PYTHONPATH /home/mailman HTTP_COOKIE notam:admin="(lp1\012F946332841.40999997\012aI946343641\012aS'^g\\304\\245\\300Bop\\356\\261\\020\\332\\005\\324\\245\\026'\012p2\012a." SERVER_PROTOCOL HTTP/1.1 HTTP_CONNECTION Keep-Alive HTTP_REFERER http://www.theporch.com:8080/mailman/admin/notam From bwarsaw@cnri.reston.va.us (Barry A. Warsaw) Mon Dec 27 22:28:48 1999 From: bwarsaw@cnri.reston.va.us (Barry A. Warsaw) (Barry A. Warsaw) Date: Mon, 27 Dec 1999 17:28:48 -0500 (EST) Subject: [Mailman-Developers] Bug in Mailman version 1.2 (experimental) (fwd) References: Message-ID: <14439.59424.716696.37336@anthem.cnri.reston.va.us> Thanks, fixed.