I see similar things from Comcast occasionally (including this morning). The "retry time not reached for any host for 'comcast.net'" error does in fact appear to come from Exim. The error from Comcast is from the first send attempt: "Remote host closed connection in response to initial connection."
What I think is happening is this: We try to send initially and get "Remote host closed connection in response to initial connection" errors on both mx1.comcast.net and mx2.comcast.net. Then, as we try to send more messages and get more "Remote host closed connection in response to initial connection" errors, the retry time (5 minutes in our case) is never reached. In other words, every time we get a "Remote host closed connection in response to initial connection" error from Comcast, the clock seems to reset on the retry time. Eventually, later in the day, traffic slows down and the queue starts to clear. I also try to flush the queue manually when I see it starting to grow. Some sends still fail when I do that but some go through. At least, that's how it looks from here. The problem isn't new but it comes and goes. It appears to be just congestion at Comcast. There's a very helpful Comcast rep on this list and I won't out him but maybe he will speak up at some point and correct any mistakes I've made here. rac On Mon, Dec 2, 2019 at 9:33 AM Ken O'Driscoll via mailop <mailop@mailop.org> wrote: > On Mon, 2019-12-02 at 17:08 +0000, Ryan Prihoda via mailop wrote: > > defer (-53): retry time not reached for any host for 'comcast.net' > > That looks like an MTA (Exim?) error, and not a SMTP 4xx type message. > > You need to work out if the messages are backing up because a) Comcast are > throttling you or b) you have a local configuration issue. > > If you are being throttled then you'll see an SMTP 4xx type message in your > logs generated by the Comcast MX servers in response to your attempt to > deliver to them. The messages will stay in the queue and delivery re- > attempted as per the local MTA setting. > > If the error messages is being generated by the MTA software itself, then > that could be a local server misconfiguration, network or resource issue. > > My advice would be to look at all of your logs, not just the maillog. > > Ken. > > > _______________________________________________ > mailop mailing list > mailop@mailop.org > https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop > -- =============================================== Russell Clemings <russ...@clemings.com> ===============================================
_______________________________________________ mailop mailing list mailop@mailop.org https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
