atom feed8 messages in net.sourceforge.lists.courier-usersRe: [courier-users] Putting a limit o...
FromSent OnAttachments
Ben KennedyJun 28, 2005 2:15 pm 
Juri HaberlandJun 28, 2005 2:38 pm 
Sam VarshavchikJun 28, 2005 3:11 pm 
Randall ShawJun 28, 2005 3:32 pm 
Ben KennedyJun 29, 2005 8:47 pm 
Martijn LievaartJul 2, 2005 4:13 pm 
Flavio StanchinaJul 18, 2005 8:25 am 
Martijn LievaartAug 3, 2005 12:04 am 
Subject:Re: [courier-users] Putting a limit on MSA floods?
From:Martijn Lievaart (m@rtij.nl)
Date:Jul 2, 2005 4:13:19 pm
List:net.sourceforge.lists.courier-users

Sam Varshavchik wrote:

If Courier would do that, there's a far greater possibility that a broken SMTP client would interpret a rude socket teardown of this kind as a temporary error, which calls for an immediate retry.

Been there, done that, FW-1 smtp proxy does this, and boy, does it cause trouble.

It's not just broken smtp clients. A rude socket teardown is rightly interpreted by MTAs as a temporary error. So they try again later, starting with the same mail that caused the problem in the first place, causing the same error. At least with Lotus Notes (alright, that is not an MTA) this completely halts your mailflow. With other MTAs I suspect roughly the same behaviour.

M4