Mark; Thanks ever so much you pointed me to a way to debug, unfortunately we rolled out the fix yesterday and I was unable to replicate the issue. It did however appear that the user mailman lacked access to the /etc/hosts file. There is a side question one of the System Administrators was curious as to why when exim would be restarted it force mailman to function.......albeit very slowly... is it caching or something alike?
----- Original Message ----- From: "Mark Sapiro" <[EMAIL PROTECTED]> To: "Stephen" <[EMAIL PROTECTED]>; <mailman-users@python.org> Sent: Tuesday, April 18, 2006 1:51 PM Subject: Re: [Mailman-Users] Issues with SMTPdirect > Stephen wrote: > >>We are currently having issues, with we suspect SMTPdirect, which is >>currently set to "localhost". The following are some error messages we >>recieve; >> >>Apr 18 09:00:04 2006 (7284) Low level smtp error: (111, 'Connection >>refused') >>delivery to [EMAIL PROTECTED] failed with code -1: (111, >>'Connection refused') >> >> >>We are seeing hours to multiple days in delay of sending, what appears to >>be happening is it tries to send to smtpdirect for a period of time then >>finally gives up and uses /usr/lib/sendmail, now we think we tracked it >>down. > > > Mailman doesn't do this. If SMTPDirect thinks the error is retryable, > it will queue the message for retry in the retry queue and it will be > retried later, but by SMTPDirect, not by any other method. > > >>But we would like to be able to have more verbose logging, to see what >>smtpdirect is trying to connect too. Is this possible, minding that we >>have perl programmers and what not but no one that is a python wizard. > > > SMTPDirect by default is trying to connect to port 25 on 'localhost'. > You can change either or both of these by assigning SMTPHOST and/or > SMTPPORT in mm_cfg.py. (Note that SMTPPORT = 0 says use the smtplib > default port which is port 25.) > > > See > <http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq06.014.htp>. > It is about a different problem, so the solutions probably aren't > directly relevant, but there are small Python snippets and pointers to > others in the archives that may help you with diagnosis. > > The logging in SMTPDirect is pretty verbose already. Between the > 'post', 'smtp' and 'smtp-failure' logs, you get quite a bit. You can > change the SMTP_LOG_* settings in mm_cfg.py (see the descriptions in > Defaults.py) to get more things reported by the various log > statements, but you can't add additional log statements this way. For > that you actually have to modify SMTPDirect.py. > > But, the debug suggestions in the FAQ article should help you find more > information. > > -- > Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > > ------------------------------------------------------ Mailman-Users mailing list Mailman-Users@python.org 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
