Szymon, > I have a following problem with an amavisd-new (2.5.2) + Postfix (2.3.8) > installation (Amavis set up as a content filter). When the sender > requests DSN (such as Microsoft Outlook can do when certain checkboxes > are ticked), Amavis sends reports like this: > > Your message WAS SUCCESSFULLY RELAYED to: > <[EMAIL PROTECTED]> > and you explicitly requested a delivery status notification on success. > > This delivery report was generated by the program amavisd-new at host > blah.blah.com. Our internal reference code for your message is > 27217-09/qpsSsHIz-vMO > > The problem is, that this DSN is misleading, because it does not really > mean anything more than that the message passed the content filter > control. In fact the sender can still receive another delivery report > from Postfix stating that the message could not be delivered, especially > when receipient is external and the email was rejeted by the destination > server.
Exactly. It all works according to RFC 3462 and RFC 3464. The text says 'relayed', not 'delivered' or 'expanded' or 'delayed' or 'failed'. Also the message/delivery-status notification part says so: Action: relayed Status: 2.0.0 Remote-MTA: dns; 127.0.0.1 Diagnostic-Code: smtp; 250 2.0.0 Ok: queued as ... > Should Amavis really send these 'SUCCESSFULLY RELAYED' notifications? If it accepts DSN option and is unable to delegate it further, then it MUST send a requested notification. If it is able to delegete the DSN option further, then it will NOT send a notification itself. > I searched the documentation and the source but I couldn't find any switch > to disable this. In fact from the following piece of Amavis's code: > > $propagate_dsn_if_possible = 1; # pass on DSN if MTA announces this > # capability; useful to be turned off globally but enabled in > # MYNETS policy bank # to hide internal mail routing from outsiders > $terminate_dsn_on_notify_success = 0; > # when true=>handle DSN NOTIFY=SUCCESS > # locally, do not let NOTIFY=SUCCESS propagate to MTA (but allow > # other DSN options like NOTIFY=NEVER/FAILURE/DELAY, ORCPT, RET, > # and ENVID to propagate if possible) > > i would rather expect that Amavis will pass on DSN NOTIFY=SUCCESS along > with the message and do nothing about it itself. Yes, this it what should happen. I suspect that your MTA at port 10025 is not announcing its DSN capability. Try telnet to 10025 and see what options are announced to an EHLO command. > Is there a way to switch off these SUCCESSFULLY RELAYED notifications? Either by not announcing DSN capability by amavisd (in which case the MTA before will be obliged to send the notification), or by arranging that the next MTA in chain is willing to accept its reponsibility for DSN. See also RELEASE_NOTES and search for $propagate_dsn_if_possible and $terminate_dsn_on_notify_success. Mark ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ AMaViS-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/amavis-user AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3 AMaViS-HowTos:http://www.amavis.org/howto/
