Skipping SpamAssassin if sender is on an RBL

[Matt Kettler]

Vlad Mazek wrote:
> Nope, still gets processed by MailScanner:
> 
> Feb  7 17:18:45 MailScanner[18224]: RBL checks: m17M9lxS016045 found in 
> SBL+XBL
> Feb  7 17:18:46 inbound42 MailScanner[18224]: SpamAssassin cache hit for 
> message m17M9lxS016045
> Feb  7 17:18:46 MailScanner[18224]: Message m17M9lxS016045 from 
> 75.63.44.11 <http://75.63.44.11> (ka at creativeholidays.com.au 
> <mailto:ka at creativeholidays.com.au>) to rmel.org <http://rmel.org> is 
> spam, SBL+XBL, SpamAssassin (cached, score=23.378, required 5, 
> autolearn=disabled, RAZOR2_CF_RANGE_51_100 0.50, 
> RAZOR2_CF_RANGE_E4_51_100 1.50, RAZOR2_CF_RANGE_E8_51_100 1.50, 
> RAZOR2_CHECK 0.50, RCVD_IN_BL_SPAMCOP_NET 2.19, RCVD_IN_XBL 2.90, 
> STOX_REPLY_TYPE 0.00, TVD_FINGER_02 2.72, URIBL_BLACK 1.96, 
> URIBL_JP_SURBL 2.86, URIBL_OB_SURBL 2.13, URIBL_SC_SURBL 2.52, 
> URIBL_WS_SURBL 2.10)
> 
> Notice that it still passes it through SpamAssassin.
> 
> I have the the following in my MailScanner.conf:
> 
> Spam List = SBL+XBL
> Spam Lists To Be Spam = 1
> Spam Lists To Reach High Score = 1
> 
> -Vlad
> 

Do you have:
Always Include SpamAssassin Report = yes

There's always been a bit of a double-edged sword on this setting. IIRC, this 
setting forces MailScanner to *ALWAYS* scan with SA, so it can always include a 
report.

Of course, most folks that turn this on do so because they want the SA report to 
always be included whenever its generated, and not left off of nonspam. But 
MailScanner takes this option pretty literally from what I remember.


Makes me wish there was two separate options:

"Always scan with SpamAssassin"
"Include SpamAssassin Report In NonSpam".