It's specifically targeting the response code and string you provided: 450 4.3.2 Please retry immediately
Unfortunately we cant make a rule that retries all 4xx and doesn't retry all 5xx. Despite very smart, well intended people writing RFCs and other specs that make this feel super clean cut in an acedemic or lab environment, it's just not how it works in the wild. So we have rules that sometimes collide with each other. An "obvious" erorr is often lost in a sea of 30 million unique response codes and strings we see every single day. Well-intended rules fall short of perfection. Your ~300 mishandled messages per week is someone else's 300 million messages per week that are properly handled. Don't delude yourself into thinking this is some zero sum game where there are good guys and bad guys. Reality is rarely that simple. But we are here to help if well can. Luke On Thu, Jun 22, 2023, 12:10 PM Michael Orlitzky via mailop < mailop@mailop.org> wrote: > On Thu, 2023-06-22 at 10:52 -0700, Luke via mailop wrote: > > I got a rule in place that should cover this. I'll monitor and make sure > > the desired behavior is occurring. > > > > Thanks, but which "this"? Should all 4xx replies now get a retry, or > just the ones containing a certain phrase? (And which phrase, in that > case?) > > > _______________________________________________ > mailop mailing list > mailop@mailop.org > https://list.mailop.org/listinfo/mailop >
_______________________________________________ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
