On 6/29/2015 7:09 PM, PGNd wrote: > I've amavisd+spamassassin setup as a post-queue content-filter. > > If a message PASSes postscreen+smtpd_mumble_restrictions, it's handed off to > amavisd+SA for content analysis. > > Currently, amavisd is configured to 'D_DISCARD' mail that scores above a > specified level. It works as intended. > > That DISCARD action is logged in the amavisd logs, but occurs silently from > Postfix's perspective -- it's not notified, and does not log the message > disposition in its log. >
This is correct. From postfix's perspective, the message was successfully sent and accepted. > My question is -- what's typical, good practice here? Should Postfix receive > notice from amavisd for any particular reason? If so, in what form -- > turning the amavisd action 'up' to a REJECT, and passing a 5xx/4xx to Postfix? > > I still do NOT want any notice or communication returned to the spammy sender > -- the message has been accepted/queued and I want no further backscatter > outside my network. > It's generally considered bad form to discard messages, even illegal in some countries. Typically one would also save discarded messages to the amavisd quarantine due to false positives. With an after-queue content filter, reasonable choices include tag-and-deliver, and quarantine. These days it's probably more common to use amavisd-new as a pre-queue smtpd_proxy_filter so that unwanted mail can be rejected during the SMTP transaction. Note that pre-queue filtering may require more hardware resources compared to an after-queue content_filter. -- Noel Jones
