Well, the OBVIOUS answer to that, is to take the DSN information out of
the
envelope and put it into the header. This won't break any existing MTAs,
and the header gets passed through and ignored any MTA which doesn't
understand it.
and you lose your assurance of getting a delivery report, because you have
no idea about whether the ultimate destination MTA supports such a feature.
Agreed - but the same would apply to an 'envelope blob' mechanism (which is
what we were talking about)
right, but the envelope blob mechanism wouldn't be appropriate for requesting
delivery notifications either.
actually, it's not at all clear whether the envelope blob is useful for
anything -
arguments have mostly been of the form "it sure would be nice if..." without
explaining how that would benefit the user.
Keith