Zitat von Victor Duchovni <victor.ducho...@morganstanley.com>:
On Wed, Dec 22, 2010 at 09:35:59AM -0500, Wietse Venema wrote:3 - Propagate ENVID, NOTIFY, RET, and ORCPT to one result from alias expansion only, and send no DSN. Postfix does this with one-to-one virtual aliases that translate one address into itself. The only thing I can change without breaking RFC compliance is to do (3) for all one-on-one virtual aliases.I am curious why the OP is eager to so faithfully support DSN. In my case I explicitly disable "DSN" in the ESMTP response at the incoming perimeter gateway. If they accept the mail, the sending system should consider it delivered. The sender gets to know that the message left or failed to leave his organization, that's all I am willing to disclose.
For a long time i also prayed "if you don't get a error all is fine". Unfortunately this is more and more not the case. After repeatedly disapearing mail in some content filters it was decided to try some more "modern" concept like DSN. So we set DSN for all outgoing mail (corporate environment). A system was setup which parses DSN reply and set a *visible* status for outgoing mail according to RFCs. As one can't demand something one is not willing to provide we like to *fully* honor DSN requests from clients. If we accept a mail at the border it will be delivered anyway to the user mailbox so sending out a "delivered" DSN status on request is no more disclosure anyway i guess.
Many Thanks for your help Andreas
smime.p7s
Description: S/MIME Cryptographic Signature
