On Thu, Feb 20, 2014 at 12:11:14PM +0100, Klaus Ethgen wrote:
> The Problem with DSN is that every MTA between sender and recipient has
> to support it otherwise it is useless. And it is very likely that there
> is one in between that does not support it.
>
> Moreover it is a privacy violation for the recipient the same way as web
> bugs are in mails.
The BCP in this space is to enable DSN on outbound MTAs up to the
edge of your organization, and (disable it at the edge in both
directions) so that users sending outbound mail can get DSN notices
about mail leaving if they wish and outside senders can get DSN
notices from their own MTAs, but not from your own systems.
In other words no DSN support on the Internet backbone, but DSN
used inside each organization, to track mail leaving their domain
and accepted or rejected by the first external hop.
--
Viktor.
