On Wed, Sep 14, 2005 at 02:16:06PM +0100, Paul Smith wrote:
I'm saying that if the average time for a transaction (which is under the
control of the receiving MTA) increases, there will be a definite impact -
which will be most keenly felt by high-volume sites.
So, RFC 2821 needs to be adjusted so that the post-DATA timeout is set to
less than 30 seconds? If that's what you're saying is necessary, then
that's what the standard should say... Currently it says 10 minutes!
The __AVERAGE__ time is important here. If ALL processes need to wait
600 seconds, it is the worst case scenario. If on the other hand only
a few need to wait 600 seconds and most others finish in 1 second, it
is easily seen that the average could very well be under 30 seconds.
If you can reject in the RCPT TO stage (virtually no time needed) you
need not process the message through spamassassin, amavis, SPF, whatever.
This saves time so the AVERAGE time needed is less. And this is just
an example, there will be more possibilities to save time.