On Thu, Dec 13, 2018 at 3:32 AM SM <s...@elandnews.com> wrote: > Hi Benoit, > At 12:29 AM 13-12-2018, Benoit Panizzon wrote: > >So based on my observation I wonder... > > > >Upon receiving a 452 4.5.3 error, what should the sending MTA do? > >Reconnect immediately and re-try the soft failed recipients as would > >be done with the usual 'too many recipients' situation? Or is it > >correct to wait for the backoff timer? > > > >Is there an RFC defining the reaction to specific error codes? > > > >What is the sending MTA exactly looking at when receiving an error > >code? Only the first 452? Combination of "452 4.5.3" or even trying to > >parse the text behind usually 'too many recipients' which we changed > >this to 'incompatible recipient settings' and this may cause this issue? > > The enhanced status code reports the error condition, e.g. "too many > recipients". The status code in the above is defined as > "insufficient system storage". It does not make sense to immediately > reconnect if the receiver says that it has insufficient storage > space. Please see RFC 3463 and RFC 5321 for more information. >
https://tools.ietf.org/html/rfc5321#section-4.5.3.1.9 and the follow-on section say 452 is for too many recipients. That does seem accurate here, though may run into the 100 minimum ... Brandon
_______________________________________________ mailop mailing list mailop@mailop.org https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
