Thanks for the advice -- I believe your suggestion that the issue is related to OutgoingRunner is most likely correct, but I'm not out of the woods yet.
> >How much time? They should appear almost immediately in qfiles/out/ > >unless they've been spending time in qfiles/retry/. This was probably the wrong thing to do, but out of frustration, I blasted out my installation, put in a clean install, and recovered the list itself from backup using instructions at http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq03.004.htp This has had the effect of clearing logs and removing ineffective and possibly harmful changes I made. I'm still having problems delivering mail. I've sent a few messages to the lists over the past couple hours. Here is what I'm seeing: 1) The files are appearing almost immediately in qfiles/out/ where they seem to stay. Nothing is in retry or the other qfiles directories. 2) Even a couple hours later, nothing shows up in post, smtp, or smtp-failure. However, someone who belonged to one of the lists sent one through. I found the entry Aug 31 02:18:53 2007 (40546) <[EMAIL PROTECTED]> smtp to innopac for 2014 recips, completed in 11231.212 seconds The amount of time for the transaction seems insane. Load is practically nonexistent. 3) When I send a message to the list, maillog makes it look like everything happened. For example, if I send it to the list with 4 people in it Aug 31 02:47:54 innopacusers sm-mta[52010]: l7V2lmww052010: from=<[EMAIL PROTECTED]>, size=5888, class=0, nrcpts=1, msgid=<[EMAIL PROTECTED]>, proto=ESMTP, daemon =MTA-v4, relay=wa-out-1112.google.com [209.85.146.180] Aug 31 02:48:01 innopacusers sm-mta[52012]: l7V2lmww052010: [EMAIL PROTECTED], delay=00:00:07, xdelay=00:00:02, mailer=esmtp, pri=156118, relay=bus-ex02.bus.umich.edu. [141.211.239.195], dsn=2.0.0, stat=Sent ( <[EMAIL PROTECTED]> Queued mail for delivery) Aug 31 02:48:02 innopacusers sm-mta[52012]: l7V2lmww052010: [EMAIL PROTECTED] , delay=00:00:08 , xdelay=00:00:01, mailer=esmtp, pri=156118, relay=mx10.colorado.edu. [128.138.128.110], dsn=2.0.0, stat= Sent (Ok: queued as 31AB7C4A4B0) Aug 31 02:48:03 innopacusers sm-mta[52012]: l7V2lmww052010: [EMAIL PROTECTED], delay=00:00:09, x delay=00:00:01, mailer=esmtp, pri=156118, relay=gmail-smtp-in.l.google.com. [64.233.167.27], dsn=2.0.0, stat=Sent (OK 1188528483 a70si1963649pye) Aug 31 02:48:04 innopacusers sm-mta[52012]: l7V2lmww052010: [EMAIL PROTECTED], delay=00:00:10, x delay=00:00:01, mailer=esmtp, pri=156118, relay=mail1.mail.lib.msu.edu. [35.8.223.61], dsn=2.0.0, stat=Sent ( <[EMAIL PROTECTED]> Queued mail for delivery) Aug 31 02:48:22 innopacusers sm-mta[52012]: l7V2lmww052010:[EMAIL PROTECTED], delay=00:00:28, xdelay=00:00:18, mailer=esmtp, pri=156118, relay=relay.oregonstate.edu. [128.193.15.33], dsn=2.0.0, stat=Sent (Ok: queued as 5D01C410AE6) The handoff to mailman shows up and it appears in /qfiles/out Aug 31 02:40:58 innopacusers sm-mta[51781]: l7V2ep7j051777: to="|/usr/local/bin/stripmime.pl|/usr/local/mailman/mail/mailman post webguru" , ctladdr=<[EMAIL PROTECTED]> (26/0), delay=00:00:01, xdelay=00: 00:01, mailer=prog, pri=31857, dsn=2.0.0, stat=Sent > In fact, in a well running Mailman installation qfiles/out/ is normally > empty except for the occasional entry you see for a second or so while > it's waiting to be picked up. (In 2.1.9, it will remain longer as a > *.bak file while it is being processed by > OutgoingRunner/SMTPDirect.py.) > > If *.pck files are hanging around in qfiles/out/, either there is a > backlog (probably due to a configuration issue if it persists), or > there is some problem with OutgoingRunner. This sounds like my problem. OutgoingRunner is running mailman 40546 0.0 1.7 19204 17236 ?? S 11:11PM 0:01.49 /usr/local/bin/python2.4 /usr/local/mailman/bin/qrunner --runner=OutgoingRunner:0:1 -s I can easily buy that there's a config issue, but the strange thing is that we were functional for years and all of a sudden quit working (having said that, we have a hosted server, so it's conceivable something was done to our machine -- it's happened before). I don't understand how OutgoingRunner works -- any suggestions for directions for me to explore in seeing if my sendmail or mailman config is screwing things up? Thanks, kyle ------------------------------------------------------ Mailman-Users mailing list [email protected] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
