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
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
I got a rule in place that should cover this. I'll monitor and make sure
the desired behavior is occurring.
On Wed, Jun 21, 2023, 7:27 PM Michael Orlitzky wrote:
> On 2023-06-21 18:39:59, Luke wrote:
> > Ahh. Thats funny. Apologies. You'll have to refresh my memory.
> >
> > Happy to help if I
Am 22.06.23 um 06:52 schrieb Matt Harris via mailop:
On Wed, Jun 21, 2023 at 6:11 PM Sebastian Nielsen via mailop
wrote:
>>The RFC forbids doing that, and I argued against it
The RFC and reality is two different things. If a client don't want to
retry, I think they are free to
