[Mailman-Users] Troublesome Mailman Errors

[George Booth]

Mark,

Removing that line indeed caused our listserv mail to flow once again. You
are a genius! I still got a failure showing up in the /var/log/mailman/post
log when when I tried sending a test message to the list that hasn't been
delivering to everyone, but I'm just glad the mail is flowing again. :) And
I guess Mailman is using the 2.3 installation of Python on our system; I did
a search on Python to see which version we were using, and it appears we
have both 2.3 and 2.6.16 installed (I'd thought maybe we were using the
2.6.16 until I saw the 2.3 version up there - I'll ask the server admins to
verify that).

I also did still see the smtp error in the /var/log/mailman/error log when I
restarted Mailman after removing that line:

Jun 21 05:48:11 2007 (28494) Cannot connect to SMTP server 131.95.82.161 on
port smtp

But since mail is flowing, I don't know if I should even concern myself over
that or not.

Anyway, thank you again! Next time I make it to San Francisco, I owe you a
beer. :)

Thanks,
George Booth

-----Original Message-----
From: Mark Sapiro [mailto:msapiro at value.net] 
Sent: Thursday, June 21, 2007 12:47 AM
To: George Booth; mailman-users at python.org
Subject: Re: [Mailman-Users] Troublesome Mailman Errors

George Booth wrote:

>There was indeed a very large digest.mbox for one of the lists (not for the
>one we've been having issues with, though), so I removed the digest.mbox
>(that list is set up to be used as a departmental email address, so there
>are only 2 recipients on the list and they weren't digesting anyway), and
>that removed the MemoryErrors I've been seeing. BTW, I should mention that
>my version of Mailman is 2.1.5
>
>However, now I'm getting different errors. When I restarted Mailman after
>removing the digest.mbox file, the errors were:
>

Various errors and tracebacks snipped.

In your OP you said

>I've also come across a suggestion to add the line
> " self.__conn.set_debuglevel(1)" to the SMTPDirect.py file and
> restarted Mailman, but that hasn't seemed to help either.

No, but if it is still there it will definitely cause multiple problems
of the type you are seeing with your Python version (2.3.?)

That suggestion is only applicable to Python 2.4 and above. See
<http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq04.073.htp>.


>At this point, I'm at a loss. I've gone through the steps outline in the
FAQ
>entry "4.78. Troubleshooting: No mail going out to lists members", and all
>seems well there. Only other thing I can think of is that under my
>/var/mailman/locks directory, I have the following:
>
>[root at mail1 locks]# ls -al
>total 8
>drwxrwsr-x   2 root    mailman 4096 Jun 20 13:30 .
>drwxrwsr-x  21 root    mailman 4096 Jun 19 20:02 ..
>-rw-rw-r--   2 mailman mailman   53 Jun 21  2007 master-qrunner
>-rw-rw-r--   2 mailman mailman   53 Jun 21  2007
>master-qrunner.mail1.usm.edu.28475
>-rw-rw-r--   1 mailman mailman   53 Jan 18  2006
>master-qrunner.mail.usm.edu.1757.1
>[root at mail1 locks]#
>
>I don't know if these are required or if I should delete them, or if they
>even have anything whatsoever to do with the issue at hand. I did find it
>odd that two of them seem to be dated as June 21, 2007, which is tomorrow
>(assuming I read that correctly), although a check of the "date" command on
>the server shows the correct date and time.


I'm not sure about the date issue, but those are the mailmanctl locks
that attempt to prevent you starting (not restarting) Mailman when
it's already running. Those locks should be there and are not the
cause of your problems.

If you still have the self.__conn.set_debuglevel(1) in SMTPDirect.py,
remove it, and then let us know if there are any errors/problems
remaining.

-- 
Mark Sapiro <msapiro at value.net>       The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan