Usually (almost always) REJECT is a more appropriate action for unwanted mail. Is there some reason you can't use REJECT until this is fixed?
I guess you're using this to trap mail your users send to bad/typo domains eg. hotmal.com? In that case, REJECT would be better to notify the user of their mistake. -- Noel Jones On 11/14/2017 12:11 PM, flowhosts wrote: > Yes this is such a decent feature! > I use it with the hold action now as this doesn't break things. > So bad domains (in my case) which would never accept mails are now > kept in place, i call it the bad destination hold quarantine. > Looking forward to massive discarding soon :) > > @Noel Jones, thanks! > > Am 14/11/2017 um 18:52 schrieb @lbutlr: >> On 14 Nov 2017, at 05:00, flowhosts <flowho...@gmail.com> wrote: >>> # main.cf >>> smtpd_recipient_restrictions = >>> reject_non_fqdn_sender >>> ... >>> check_recipient_a_access >>> hash:/etc/postfix/lookup/recipient_a_access >>> ... >>> permit >>> >>> # cat /etc/postfix/lookup/recipient_a_access >>> 185.140.110.3 DISCARD >> I hope this bug gets fixed soon, because that looks like it might >> be super useful with a log monitor and blacklist. >> >
