Marek Kozlowski wrote:
error: no error messages post: only "post to ... <nr_of_group_members> failures" qrunner: no error messages smtp: no error messages smtp-failure: that's it! Lots of errors like:
"Aug 20 18:50:10 2009 (15479) delivery to someuser@mini.pw.edu.pl failed with code -1: Server not connected"
See below:
And Marek Kozlowski wrote:
I've found some suggestion to set SMTPPORT to 25 (it is... 0 ?) in mm_cfg.py. Now I have:
"Aug 20 19:11:13 2009 (21289) delivery to someuser@mini.pw.edu.pl failed with code -1: (104, 'Connection reset by peer')"
The fact that the error changed when you set SMTPPORT = 25 rather than the Defaults.py setting of 0 is a coincidence. There is no difference between the two. SMTPPORT = 25 tells the python smtplib module to use port 25 and SMTPPORT = 0 tells it to use the SMTP default port which is 25.
And Marek Kozlowski wrote:
SMTP_MAX_RCPTS = 1 (http://www.mailinglistarchive.com/mailman-users@python.org/msg08741.html -- thanks Mark!) helped. Still I'mnot sure why :-(
It helps because of a bug in the underlying Python smtplib. See <http://bugs.python.org/issue5713>
Your real problem is you have addresses on your list that Postfix thinks are undeliverable. The bug report linked above describes the scenario.
After 20 invalid local recipients in one SMTP transaction, Postfix disconnects with a 421 Too many errors reply, but the Python smtplib module doesn't expect a disconnect after a 421 and gets out of sync with Postfix.
Setting SMTP_MAX_RCPTS to any number less than 20 will avoid this problem.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan