SMTPDirect timeout
We recently experienced a problem with our smtp delivery where the connection is lost to the SMTPHOST which caused all the OutgoingRunners to lock up. There is no connection reset or anything so the connection appears to be ESTABLISTED and it just sits there. Eventually all OutgoingRunners are consumed in this state.
The only reference I see to something similar to this happening is at:
http://www.mail-archive.com/mailman-developers@python.org/msg07442.html
The patch I've attached is a simple alarm around the SMTPDirect.py call into smtplib to terminate the connection after a configurable amount of time. Right now I have it set to minutes(10) but it's completely configurable via mm_cfg.py
Any thoughts about this?
Thien
At 9:00 PM -0800 2005-01-27, Thien Vu wrote:
The patch I've attached is a simple alarm around the SMTPDirect.py call into smtplib to terminate the connection after a configurable amount of time. Right now I have it set to minutes(10) but it's completely configurable via mm_cfg.py
That's very weird. The MTA should be dropping those connections after five minutes of idle time (I think that's the recommended value). Obviously, in your case the MTA is not doing this, so the client should definitely be protecting itself against being hung indefinitely.
-- Brad Knowles, <brad@stop.mail-abuse.org>
"Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety."
-- Benjamin Franklin (1706-1790), reply of the Pennsylvania
Assembly to the Governor, November 11, 1755SAGE member since 1995. See <http://www.sage.org/> for more info.
participants (2)
-
Brad Knowles -
Thien Vu