Re: score=100.0 required=3.0 tests=SHORTCIRCUIT,,USER_IN_BLACKLIST

[J4K]

On 01/27/2011 01:55 PM, Florescu, Dan Alexandru wrote:

Fire up what?
Correct me if I'm wrong, but as far as I know SA does not reject at SMTP session level.
I myself am using it with amavis and I have:
$sa_quarantine_cutoff_level = 12.0;
which will drop any spammy message with that score or above it.

If you don't have any option you can use header_checks and drop spams there, although you should be warned that false positives will be dropped also. I think SA delivers by default spam-marked messages to avoid these false positives.

/^X-Spam-Level: ************/           DISCARD This is a spam message
(score 12)

Shortcircuit is useful as it will not run any other tests (less cpu usage) if it is sure that message is spam.


-----Original Message-----
From: Bowie Bailey [mailto:]
Sent: Monday 24, January 01, 2011 19:32
To: address@hidden
Subject: Re: score=100.0 required=3.0 tests=SHORTCIRCUIT,,USER_IN_BLACKLIST

On 1/24/2011 11:50 AM, J4 wrote:

    Hi all,

Just would like to check that my settings are correct.  The rcpt was
blacklisted, yet the spam was delivered. I had thought that it would
have been rejected during the SMTP session via spamass-milter, but I did
not see it fire in the logs. Perhaps I have missed something in the
spam-milter set-up and integration with postfix


Regards, S

-------- Original Message --------
Return-Path:  <address@hidden>
X-Spam-Checker-Version:       SpamAssassin 3.3.1 (2010-03-16) on
logout.niceemailserver.test
X-Spam-Flag:  YES
X-Spam-Level:         **************************************************
X-Spam-Status:        Yes, score=100.0 required=3.0 tests=SHORTCIRCUIT,
USER_IN_BLACKLIST shortcircuit=spam autolearn=disabled version=3.3.1
X-Spam-Virus:         _CLAMAVRESULT_
X-Spam-Report:        * 0.0 SHORTCIRCUIT Not all rules were run, due to a
shortcircuited rule * 100 USER_IN_BLACKLIST From: address is in the
user's black-list

SA marked it as spam.  If it was not rejected, you should check your
spamass-milter settings.

What I thought I might have missed was the -r -1 option.  The man page states that if -r -1 is used, then this could reject based on user preferences.  I have spamassassin talking back to a mysql table for userprefs.

Thus options are now set to this:-
OPTIONS="-u nobody -m -r -1 -i 127.0.0.1 -e -f -p /var/spool/postfix/spamass/spamass.sock"

However, spam was not rejected, although I think that this might cause unnecessary backscatter in the case of probably forged From addresses, which is a little unfair. 

I would prefer USER_IN_BLACKLIST reject with a message, because users who black list specific email addresses do so not because its spam, but because they simply won't want email from the address.  I this is the wrong way to go about it, but its what people do. 
I could add this into seive (dovecot) to discard the message, but I would prefer the original sender to receive the reject message during the SMTP session in this specific case.  Its not the end of the world if this cannot be done simply, but perhaps  the blacklisted people really has to send an important message. At least they know they have been rejected.   Otherwise, I shall let the Email through.

On 01/27/2011 01:59 PM, Giles Coochey wrote:

spamass-milter can reject according to SA results at the SMTP session level. The OP mentioned that.

Yep, I did.


Regards, S