John Levine writes:
In article
<cone(_dot_)1588025328(_dot_)577835(_dot_)59133(_dot_)1004(_at_)monster(_dot_)email-scan(_dot_)com>,
Sam Varshavchik <mrsam(_at_)courier-mta(_dot_)com> wrote:
>I do agree that I don't /quite/ see the value-added to the recipient of
>implementing success DSNs. Or any DSNs, for that matter. If the receiving
>mail server does not want the email it should reject it instead of accepting
>it and generate a failure DSN.
In general I agree but there are still situations where an MTA (mine
for example) accepts a message intending to forward it somewhere else
and then the forward fails. Either send a DSN or drop it on the floor
at that point.
Well, yes. You take ownership of that message by the act of forwarding, you
now own it, from the point of forwarding. If you don't want to disclose the
forwarded-to address, that's your responsibility, so either set the sender's
address to <>, or to some other address where you want the bounces to go.
Presuming that you decide to keep the original MAIL FROM, you obviously made
the decision to forward your mail knowing, fully well, that in the event of
a problem your forwarded-to address is going to be visible. This is not an
inherit problem with DSNs. That's how they work.
pgpYS_wjJ29la.pgp
Description: PGP signature
_______________________________________________
ietf-smtp mailing list
ietf-smtp(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf-smtp