So, we inform the "original sender" that the *forwarded to* address
(which
they may never have heard of) is broken? How useful is this?
Seth Breidbart:
When I can read the headers to determine who forwarded it (so I know
who I sent it to), that's quite useful.
The 'owner' of the forwarding doesn't get to know that there's something
wrong. This is a pity. Also, the forwarding is exposed to the sender (as
you point out) which might be (in some circumstances) a significant leak of
(private) information. Perhaps it would be better for forwarders to accept
responsibility for the mail they generate (remembering the mapping so that
they can produce appropriate DSNs) and stop pretending to be relays.
As far as I'm aware the strongest objection to a well-designed sender
rewriting scheme is that it imposes costs on operators of forwarding
systems (while providing some small benefits to their users and to
senders).
Actually - having just read wot I wrote - another obvious objection is that
in the absence of something like SPF there's no urgent need for something
like SRS, although it would address the issues of loss and leakage of
information (as above) which will occur in traditional forwarding.
John Levine:
When it's a bounce of an actual no kidding message and I can look at
what's quoted in the bounce to see what I wrote, extremely useful.
I find that my messages usually bounce for reasons not depending on body
content. Often, the last thing I'd want is another copy of the message - I
have one in 'Sent' already. The address I sent it to and the Subject would
normally be enough for me. Do DSNs always include the body? Must they? And
anyway - who's saying that bounces be done away with? Isn't the point that
they should explicitly refer to the address that the sender used. Isn't
this what a SRS forwarder would do? 'Unwrap' (or lookup) the address and
'Forward' the bounce to the original sender?
JL:
Sometimes I get the impression that people who attempt to design mail
systems don't actually use them.
Thanks for sharing your "impression" with us.
Rgds,
JRK
Rgds
_______________________________________________
Asrg mailing list
Asrg(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/asrg