On Sun, Nov 18, 2018 at 1:48 PM Mark Sapiro <mark@msapiro.net> wrote:
The Yahoo page at <https://help.yahoo.com/kb/postmaster/SLN3434.html> has some tips. You may need to adjust the retry strategy of your MTA.
So looking at the EXIM config on the host VPS server, there is a Section:RETRYSTART that is blank, A RETRYBLOCK that has this:
+secondarymx * F,4h,5m; G,16h,1h,1.5; F,4d,8h
* F,2h,15m; G,16h,1h,1.5; F,4d,8h
And a RETRYEND which is blank. So I suppose the RETRYBLOCK is where the edit would go. This server is basically just handling the mailman list, plus some very small traffic from server reports, website stuff (very rare), and other stuff not worth mentioning. So a couple attempts in case some server or service is down somewhere temporarily.. but otherwise I hardly think it should be trying for what looks like 4 days, if this is what I'm correctly seeing. Any one have thoughts on how to edit, given that qualification? /jim
On 11/18/18 4:46 PM, Jim Dory wrote:
So looking at the EXIM config on the host VPS server, there is a Section:RETRYSTART that is blank, A RETRYBLOCK that has this:
+secondarymx * F,4h,5m; G,16h,1h,1.5; F,4d,8h
* F,2h,15m; G,16h,1h,1.5; F,4d,8hAnd a RETRYEND which is blank. So I suppose the RETRYBLOCK is where the edit would go.
I don't think you need any changes here. I'm not sure what the +secondarymx entry matches, but the default
* F,2h,15m; G,16h,1h,1.5; F,4d,8h
says retry 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, after which if the message is still not delivered, it is bounced.
This is a common strategy and should be OK.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (2)
-
Jim Dory -
Mark Sapiro