Mailman 3 April 1999 - Mailman-Users

Not to bug everyone, but...
by Adam April 22, 1999

April 22, 1999

I tried posting last week, but never got a reply. Can someone point out to me why i'm getting these errors on a RedHat linux box (v5.1)? I'm getting these errors in /var/log/cron from mailman. Can anyone tell me what this is all about, and how to fix it? I know that the cron daemon is being asked to run this via mailman, but is this just a permissions issue, or possibly a bad install? I'll also attach an emailed error that I used to get, but no longer get anymore for some reason... mailman (04/15-11:12:00-5473) CMD (/usr/bin/python /home/mailman/cron/run_queue) mailman (04/15-11:42:00-5481) CMD (/usr/bin/python /home/mailman/cron/run_queue) mailman (04/15-12:00:00-5485) CMD (/usr/bin/python /home/mailman/cron/senddigests) root (04/15-12:01:00-5487) CMD (run-parts /etc/cron.hourly) mailman (04/15-12:12:00-5492) CMD (/usr/bin/python /home/mailman/cron/run_queue) mailman (04/15-12:42:00-5498) CMD (/usr/bin/python /home/mailman/cron/run_queue) root (04/15-13:01:00-5501) CMD (run-parts /etc/cron.hourly) mailman (04/15-13:12:00-5506) CMD (/usr/bin/python /home/mailman/cron/run_queue) mailman (04/15-13:42:00-5513) CMD (/usr/bin/python /home/mailman/cron/run_queue) root (04/15-14:01:00-5515) CMD (run-parts /etc/cron.hourly) mailman (04/15-14:12:00-5519) CMD (/usr/bin/python /home/mailman/cron/run_queue) mailman (04/15-14:42:00-5529) CMD (/usr/bin/python /home/mailman/cron/run_queue) root (04/15-15:01:00-5532) CMD (run-parts /etc/cron.hourly) mailman (04/15-15:12:00-5538) CMD (/usr/bin/python /home/mailman/cron/run_queue) mailman (04/15-15:42:00-5551) CMD (/usr/bin/python /home/mailman/cron/run_queue) root (04/15-16:01:00-5556) CMD (run-parts /etc/cron.hourly) mailman (04/15-16:12:00-5560) CMD (/usr/bin/python /home/mailman/cron/run_queue) mailman (04/15-16:42:00-5570) CMD (/usr/bin/python /home/mailman/cron/run_queue) mailman (04/15-17:00:00-5576) CMD (/usr/bin/python /home/mailman/cron/checkdbs) root (04/15-17:01:00-5578) CMD (run-parts /etc/cron.hourly) mailman (04/15-17:12:00-5599) CMD (/usr/bin/python /home/mailman/cron/run_queue) mailman (04/15-17:42:00-5606) CMD (/usr/bin/python /home/mailman/cron/run_queue) This is a copy of one of the emails I used to get: Traceback (innermost last): File "/home/mailman/cron/run_queue", line 31, in ? OutgoingQueue.processQueue() File "/home/mailman/Mailman/OutgoingQueue.py", line 86, in processQueue lock_file.lock() File "/home/mailman/Mailman/flock.py", line 119, in lock os.link(self.lockfile, self.tmpfname) os.error: (13, 'Permission denied') Thanx in advance, Adam

2 1

Re: [Mailman-Users] how to install
by Ken Manheimer April 21, 1999

April 21, 1999

On Fri, 16 Apr, pehr anderson wrote: > I wrote the following installation script trying to follow > all the docs. > > Please tell me what I'm doing wrong. It seems like I'm missing > something pretty fundamental. > [various stuff, including an appropriate warning about stomping existing installs] > cd /home/mailman Interesting - you're putting the distribution inside the installation dir. I do that also - i think it's a nice way to organize it, though it can be confusing to those who take over the maintenance after you, if you don't make it clear. I'm not sure the following excerpt does what you want: > tar xzf ~pehr/gz/mailman.tar.gz > chgrp mailman /home/mailman > chmod a+rx,g+ws /home/mailman Did you want to do 'chgrp -R ...' and 'chmod -R ...'? I'm not sure about the rest - it's ambitous - but have a warning about the last part: > echo "Hope it worked!" > echo "Now browse to " > echo "http://localhost/pipermail/" > echo " -pehr" > lynx http://localhost/pipermail People may be disappointed if they follow that suggestion, because the actual archives for a list are initialized when the list first gets messages, not when the list is created. I haven't looked this over as carefully as i'd like - would be interested to hear feedback from others on it... ken manheimer klm(a)digicool.com

1 0

Unable to send due to localhost?
by Douglas Eadline April 21, 1999

April 21, 1999

I have installed mailman 1.0b11 on a RH Linux 5.2 (2.0.36) system. Everything works Ok, except for this one annoying problem. I can not get the list to recognized my posts. The list is restricted so that you must subscribe to post. Well I subscribed, with my address of deadline(a)plogic.com, but mailman treats this as deadline@local host and rejects it. The rejection mail looks fine : Your authorization is required for a mailing list posting request approval: List: Bert(a)plogic.com Reason held: Postings from member addresses only. From: deadline(a)plogic.com Subject: Bert problem (fwd) BUT, the administrative page shows the following:

1 0

Cron <list@petunia> /usr/bin/python /usr/lib/mailman/cron/run_queue
by Omar Walid Llorente April 21, 1999

April 21, 1999

See this message, maybe can help: http://www.python.org/pipermail/mailman-users/1999-April/001145.html Cheers Omar. -------------------------------------------------------------------------------- Centro de Calculo Departamento Ingenieria Telematica (ETSIT) e-mail: omar(a)dit.upm.es Universidad Politecnica de Madrid Tel:(+34) 913367366-Ext.328 Ciudad Universitaria, s/n 28040 Madrid (Spain) Fax:(+34) 913367333 --------------------------------------------------------------------------------

1 0

None
by mailman＠cs.uchicago.edu April 21, 1999

April 21, 1999

To: mailman Subject: Output from "cron" command Your "cron" job /opt/local/bin/python /homes/mailman/cron/gate_news produced the following output: Exception exceptions.IOError: (2, 'No such file or directory') in <method FileLock.__del__ of FileLock instance at bad70> ignored --Multipart_Wed_Apr_21_11:41:31_1999-1--

1 0

RE: [Mailman-Users] Still need code info for privacy option
by Nicholson James D April 20, 1999

April 20, 1999

[Nicholson James D] I found the problem with the list not remailing anonymously. In routine Post(), it deletes the sender and reply-to fields and then sets the from field. However, it set the From field to self.GetAdminEmail. What I needed it to do (and what I believe it should be doing) is setting the From field to self.GetListEmail, which will return the list address. However, I can't get the damned thing to change the From field for anything. I've even done a msg.setheader( 'From', 'listname@machine' ). That's hardwired in the Post() routine just for testing, and it isn't bloody changing the header... at all. I altered the MailList.py file, moved the MailList.pyc to oldMailList.pyc, and it still does the same damned thing. It sets the From field to whoever sent the message. Was I supposed to recompile the package or something to get my changes to take effect? I just don't know python or mailman well enough to know even this. Sorry. -Jim

1 0

Re: [Mailman-Users] 1.0b11 bug with underscores in member name?
by Gerhard Gonter April 20, 1999

April 20, 1999

I already replied in direct mail but realized that there is in fact another bug burried in Terry Grace's report. Addresses with underscores work fine, the problem below was IMO at the Notes gateway as indicated by the error message. However, mailman does not recognize the bounced address: Lotus Notes says: ------- Failure Reasons -------- User not listed in public Name & Address Book latoya_lemur(a)notes.wu-wien.ac.at Mailman apparently matches "not" as the username and thus concludes: List: Test-b8 Member: not(a)notes.wu-wien.ac.at Action: Subscription not disabled. Reason: Excessive or fatal bounces. BUT: User not found. It's certainly not easy to recognize all possible gateway error message formats, so maybe that's not even a bug after all ;) +gg [earlier direct mail] According to Grace, Terry: > I have a list member with underscores in the username (eg > username_at_hostname(a)domain.com). When a message goes out to the list the > following is returned to the list admin and the message is never delivered > to the user: > [...] > User not listed in public Name & Address Book > username_at_hostname(a)domain.com That's not Mailman's fault, the Lotus Notes(?) internet mail gateway involved rejects the mail. This happens quite frequently, as far as I know, especially if the Lotus mail gateway loses the contact to the Lotus server which has the address book. P.S: Some of our lists also have subscribers with underscores in their address. +gg -- Gerhard.Gonter(a)wu-wien.ac.at Fax: +43/1/31336/702 g.gonter(a)ieee.org Zentrum fuer Informatikdienste, Wirtschaftsuniversitaet Wien, Austria

1 0

`Moderated' list bypass feature doesn't work for me
by Ian Jackson April 20, 1999

April 20, 1999

I've tried to set up a list so that only certain posters can post, but all the postings seem to require administrative approval. I have set Must posts be approved by an administrator: No Restrict posting privilege to list members? No Addresses of members accepted for posting ... <list of email addresses one per line> When I post, the posting is held. The poster (as specified in the From: and envelope, and whose address appears in the accepted posters list) gets a notification, and when I look at the admin requests page I see: Post held because: Only approved posters may post without moderator approval. The headers of the message as displayed on that page seem slightly odd. They give the From: correctly, but the Return-Path and Message-Id are blank. I'm using Mailman 1.0b8 (Debian revision 3) and Python 1.5.1 (Debian revision 7), on Debian GNU/Linux i386 2.0 with some 2.1 upgrades, notably the libc. Ian.

2 1

Re: [Mailman-Users] Cron <list@petunia> /usr/bin/python /usr/lib/ma
by dmacdoug＠hsc.usc.edu April 20, 1999

April 20, 1999

On 20 Apr, Christopher Lindsey wrote: >> found" so I figured I was on the right track. It was created with >> ownership of root. Thinking this should, perhaps be mailman, I changed >> it, but "permission denied" persists. It's permissions are -rw-rw-r--. >> The lock directory is permission drwxrwxr-x also owned by mailman. > > What happens if you change the lock directory to be sgid mailman? That's the > way that most of the mailman directories are: > > [root@lorien]# /bin/ls -lgd ~mailman/locks/ > drwxrwsr-x 2 mailman mailman 1024 Apr 20 02:12 /home/staff/mailman/locks/ > > Chris Oops. I mistyped. It already is set just that way.

1 0

Re: [Mailman-Users] Cron <list@petunia> /usr/bin/python /usr/lib/ma ilman/cron/run_queue
by dmacdoug＠hsc.usc.edu April 20, 1999

April 20, 1999

Update on cron run_queue problem: Thanks to Christopher Lindsey and Gerhard Gonter for their help. I found that for some reason there was no file in the lock directory called mmqueue_run.lock. So I ran cron/run_queue by hand and it was created. But now the error message said "Permission denied" instead of "File not found" so I figured I was on the right track. It was created with ownership of root. Thinking this should, perhaps be mailman, I changed it, but "permission denied" persists. It's permissions are -rw-rw-r--. The lock directory is permission drwxrwxr-x also owned by mailman. The file system isn't full as I am just setting it up new and there's nothing on it yet. I suppose I've probably done something wrong in the setup. I compiled it as user mailman. I set up a test list according to the instructions but it isn't accepting mail. I had supposed that this was a separate issue and was perhaps a matter of how things were set up in my MTA which is Exim, but maybe I've just botched up the installation of Mailman. Don MacDougall dmacdoug(a)hsc.usc.edu On 20 Apr, Gerhard Gonter wrote: > According to dmacdoug(a)hsc.usc.edu: >> Can anyone tell me why I get the following error message every time >> cron runs the queue? This is Mailman 1.0b11. I've looked at flock.py >> but Python is still a foreign language to me. I can't figure out what >> file it isn't able to open or if that is even the problem. > > To find out what the file is, just add a print statement before the > line 119 and run the cron job once by hand: > > +117 while 1: > +118 # create the hard link and test for exactly 2 links to the file > +119 print "lockfile=%s tmpfname=%s" % (self.lockfile, self.tmpfname) > +120 os.link(self.lockfile, self.tmpfname) > +121 if os.stat(self.tmpfname)[ST_NLINK] == 2: > > mailman> /usr/local/bin/python /home/mailman/cron/run_queue > lockfile=/home/mailman/locks/mmqueue_run.lock > tmpfname=/home/mailman/locks/mmqueue_run.lock.augenblix.82222 > > Mailman has a problem when it's file system is full, this may > be the case actually. > > Don't forget to comment or remove the print statement when the > problem is fixed. > > +gg > > -- > Gerhard.Gonter(a)wu-wien.ac.at Fax: +43/1/31336/702 g.gonter(a)ieee.org > Zentrum fuer Informatikdienste, Wirtschaftsuniversitaet Wien, Austria

1 0