If reinjection of mail fails, Amavis will send a DSN back to the sender to notify him about this failure.
But if D_REJECT is active this leads to *2* DSN back to the user: One DSN from the sending MTA (because Amavis blocks that mail to the feeding MTA), second DSN from Amavis himself. In my understanding Amavis should not send his own DSN in case of D_REJECT if the mail has been already rejected against the feeding local MTA (and in case of Postfix' smtpd_proxy_filter also against the external sending MTA). Amavis does not send his DSN if D_DISCARD is active: # next, look for some good _excuses_ for not sending a DSN } elsif ($dest==D_DISCARD) { # requested by final_*_destiny $suppressed = 1; do_log(4, "DSN: FILTER %s %s %s, destiny=DISCARD: <%s> -> <%s>", $remote_or_local,$smtp_resp_code,$ccat_name,$sender, $recip); same should happen in case of D_REJECT. Sending always a DSN would make Amavis to a backscatter system which should be avoided in any circumstances. And, of course, users are confused if they receive TWO bounce-mails: one from their own MTA, one from the the remote system. Right? Peer -- Heinlein Professional Linux Support GmbH Linux: Akademie - Support - Hosting http://www.heinlein-support.de Zwangsangaben lt. §35a GmbHG: HRB 93818 B / Amtsgericht Berlin-Charlottenburg, Geschäftsführer: Peer Heinlein -- Sitz: Berlin ------------------------------------------------------------------------------ Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge _______________________________________________ AMaViS-user mailing list AMaViS-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amavis-user AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3 AMaViS-HowTos:http://www.amavis.org/howto/