Heh. Almost a violation of RFC 1891:
(c) is stable, in that a failed attempt to deliver a DSN should never
result in the transmission of another DSN over the network,
And it does not cause. IIS SMTP does not generate email loop this way.
however, definitely in direct violation of:
NOTE: A DSN MUST NOT be returned to the sender for any message for
which the return address from the SMTP MAIL command was NULL
("<>"), even if the sender's address is available from other sources (e.g.
the message header). -- snip!
And IIS SMTP does not return DSN for another DSN.
at any rate its dodgy and non-standard behaviour likey because following
logically defined and imperative guidelines for writing Internet services
software isn't "User Friendly", but of course we expect nothing less from
our super friends over in Redmond.
It's a design decision. I agree that it's not the standard behaviour
but I don't see how it would violate the Internet standards.
Peter