Own rules work
The newly added rules do their job. The vast amount of messages I flagged with BAD_MAIL and RAT_MAIL are gone. What is left are ‘normally’ occurring messages. I noticed – scanning the logfile for today – that the vast majority are rejected because they are from a non-authorized source (check of SPF signals ‘fail’ or ‘softfail’ – adding 100 or 75 to the score) and the sender address is mentioned in one or both blacklists that I use – that alone causes the score to pass the rejection score (over 200). Still, looking on the rules, there is non RAT_MAIL and just one BAD_MAIL rule that is hit; that might be feasible if PROCESS has updated the scores for their rules that I have mentioned in mine. Or testing the headers is simply stopped after score is over the threshold.
The only thing I would like is that I could just drop the connection without message. Since there is a rejection message sent:
550 5.7.1 Requested mail action not taken: rejected for policy reasons
the sender will be notified there is a server running – and I want it to believe there is no server…
Question to process.com