Hello Valdis,
the intent is not to accept more recipients at RCPT TO:, which can disagree on
the overall acceptance/rejection after DATA.
In this case, it knows that 'user2' will accept the message, so it defers it.
No. In this case it does not know whether 'user2' will accept the message, so
it defers it.
Or more correct reading:
In this case it does not know whether 'user2' will have the same opinion as
'user1' on accepting/rejecting the message, so it defers 'user2'.
Regards
Дилян
On February 7, 2019 6:50:41 PM GMT+01:00,
valdis(_dot_)kletnieks(_at_)vt(_dot_)edu wrote:
On Thu, 07 Feb 2019 17:27:03 +0000, Paul Smith said:
How would the server know to give the two different responses to the
RCPT TO?
Or does it just always temporarily reject any messages for
'two(_at_)example(_dot_)com', just in case?
It took me a while to figure out the intent was to *defer* any RCPT TO
that you
planned to actually accept, but *accept* any that may or may not be
acceptable,
so it can 550 it further down the line if needed. In this case, it
knows that
'user2' will accept the message, so it defers it. It doesn't know if
'user1'
will accept it, so it 250's it, gets the message, and then either 250
or 550
after DATA as needed.
_______________________________________________
ietf-smtp mailing list
ietf-smtp(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf-smtp
_______________________________________________
ietf-smtp mailing list
ietf-smtp(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf-smtp