[Mailman-Users] Slow Processing/Delivery

[Mark Sapiro]

jrotunno at swarthmore.edu wrote:
>
>post.1:Dec 13 04:39:48 2006 (23382) post to star from XXXX at XXXX.com,
>size=28696, message-id=<327B036070F4D945B189BAB84E4A92C36F5D5D at XXXX.com>,
>16 failures


The smtp-failure entries give more info about the same event.


>The same goes for these in the smtp-failure logs:
>
>Dec 13 04:29:46 2006 (23382) Low level smtp error: Connection unexpectedly
>closed, msgid: <327B036070F4D945B189BAB84E4A92C36F5D5D at XXXX.com>
>
>Dec 13 04:39:48 2006 (23382) delivery to XXXX at XXXX failed with code -
>1: Connection unexpectedly closed


The outgoing MTA is 'hanging up' on Mailman during SMTP delivery from
Mailman. This may be because of something it doesn't like about a
recipient or some other reason. It should not be doing DNS validation,
spam scanning or any such things on messages coming from Mailman. That
is a real performance killer. See the relevant hits from
<http://www.python.org/cgi-bin/faqw-mm.py?query=performance&querytype=simple&casefold=yes&req=search>.


>Anyone know what exactly these mean or how to handle it? Or point me in
>the right direction of where to look to get this resolved since it's an
>smtp problem?


If your Python is 2.4 or later, see
<http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq04.073.htp>
for a way to get debugging information from Python's smtplib.

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