On Thu, 14 Mar 2024, Johann Klasek via mailop wrote:
On Thu, Mar 14, 2024 at 12:03:46PM +0100, Marco Moock via mailop wrote:
Am 14.03.2024 schrieb Julian Bradfield via mailop <mailop@mailop.org>:
On 2024-03-14, Marco Moock via mailop <mailop@mailop.org> wrote:
sendmail tried to deliver it 20 times during the night - this
morning I deleted the mail from mqueue.
That's a fairly aggressive retry strategy.
That is the default in sendmail.
Is there any standard that defines the retry rates or at least a best
practise?
The exim default is (description from the documentation):
* * F,2h,15m; G,16h,1h,1.5; F,4d,6h
This causes any temporarily failing address to be retried every 15
minutes for 2 hours, then at intervals starting at one hour and
increasing by a factor of 1.5 until 16 hours have passed, then every 6
hours up to 4 days. If an address is not delivered after 4 days of
temporary failure, it is bounced. The time is measured from first
failure, not from the time the message was received.
It depends on the average queue size and contention of the queue.
With many entry a queue runner interval might be exhausted easily and
retry streches over multiple intervals.
I would regard a 10 to 15 minute queue runner interval as acceptable.
If the queue is nearly empty the retry happens 4 to 6 times a hour.
That's not very aggressive meanwhile.
Exim's queue runner doesn't try to deliver every mail on every run through.
I hadn't expected that other queue runners would.
Our inbound queuerunner operates in permanent queue running mode which
could lead to a retry every minute if the queue is nearly empty.
This is more or less "aggressive" ...
An *inbound* queue runner sounds like a special case
- I would expect it to be more "aggressive".
--
Andrew C. Aitchison Kendal, UK
and...@aitchison.me.uk
_______________________________________________
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop
