Wietse Venema wrote:
> Noel Jones:
>> Wietse Venema wrote:
>>> Something that will drastically cut the time per session:
>>>
>>> smtpd_timeout = ${stress?10s}${stress:300s}
>> I would be concerned about sites that are chronically short of smtpd
>> processes with an inexperienced or inattentive admin.
>> Maybe 20s~30s rather than 10s. That's still 10x or more better performance
>> under stress, and 30s has been shown to be safe for everyday use.
>
> I see that observation as an argument for < 30s timeouts under
> stress :-)
> (The idea is to help properly configured sites primarily. Sites
> that are permanently overloaded will already be missing some email,
> due to TCP-level or SMTP-level timeouts.)
Yes, I see that too. I'm concerned about the possibility of stress=yes for an
extended period of time with no one at the wheel.
I agree this is an edge case and should only affect servers that are already
somewhat broken. I'm just trying to think of robust defaults that won't give
the appearance of making things worse.
-- Noel Jones
---Could there be a notification alert be sent via SMS or another means to the
administrator of the post server in question, stating something is wrong with
the server?
