No specific action for bad content?

Kai Schaetzl maillists at
Fri Nov 27 14:29:29 UTC 2015

Hello everyone,

my MailScanners are running untouched for months and years and so on ...
and seldom there is a problem. But now ... am I missing something? 

Lately, I'm getting phishing spam from a faked address and 
was just about to use postfix header checks to stop them. Looked up the 
messages in Mailwatch and found they were detected as "bad content" (by 
filename rules for .js). A "detected" message was sent to postmaster, but 
the message was delivered normally. I would rather have it stored and not 
delivered and thought this being the case in the past. As it is not 
detected as spam spam actions do not apply, but I cannot find another 
actions config setting which could apply here. Obviously, I do not want to 
block other "non spam" messages.
Are we missing such a setting or do I have to apply a delivery rule to 
filename.rules.conf or create a new file for that?



Get your web at Conactive Internet Services:

More information about the MailScanner mailing list