Re: [Emailcore] Ticket #5: G.5. Remove or deprecate the work-around from code 552 to 452?

[Todd Herr <[e-mail]>]

On Mon, Feb 15, 2021 at 8:42 AM Alexey Melnikov <[e-mail]>
wrote:

> Hi,
>
> On Tue, Jan 19, 2021, at 4:24 PM, Alexey Melnikov wrote:
> > Hi all,
> >
> > The first pagaraph of Section 4.5.3.1.10 (Too Many Recipients Code)
> > currently says:
> >
> >     RFC 821 [3] incorrectly listed the error where an SMTP server
> >     exhausts its implementation limit on the number of RCPT commands
> >     ("too many recipients") as having reply code 552.  The correct reply
> >     code for this condition is 452.  Clients SHOULD treat a 552 code in
> >     this case as a temporary, rather than permanent, failure so the logic
> >     below works.
> >
> > John noted that this suggestion may have outlived its usefulness
> > and/or be inconsistent with current practice. Should it be removed
> > and/or explicitly deprecated?
>
> I did a bit of digging and it doesn't look like Sendmail emits 552 or
> treats it as 442 if received from other MTA.
> Postfix code has this commented out with a note that this workaround
> creates more problems than it solves, due to other meaning of 552.
>
> Do people have information about other MTAs (not necessarily open source)
> on this topic?
>
>
I've reached out to a few large mailbox providers and a couple of
commercial MTA vendors on this question. Still collecting answers, but hope
to post results here by the end of the week.
-- 

*Todd Herr* | Sr. Technical Program Manager
*e:* [e-mail]
*p:*

`

This email and all data transmitted with it contains confidential and/or
proprietary information intended solely for the use of individual(s)
authorized to receive it. If you are not an intended and authorized
recipient you are hereby notified of any use, disclosure, copying or
distribution of the information included in this transmission is prohibited
and may be unlawful. Please immediately notify the sender by replying to
this email and then delete it from your system.