Re: Detecting which shortcircuit rule fires

[Reindl Harald]

Am 02.12.2015 um 10:30 schrieb Sebastian Arcus:

After properly configuring a bayes database and training it following
the great advice from this list, I am now having this problem where some
spam is not detected properly due to a shortcircuit rule. However, I'm
having some difficulty figuring out which one of them is causing the
problem. Here is the X-Spam-Report - which should cause the email to be
classed as spam, really:

But when the message goes through Exim

* show the headers of such a message
* there must be a rulename which was triggered for SC
* SC is *not* enabled by default
* SC is even not loaded by default

i can't even respond quoting your headers

Dec 2 10:46:51 mail postfix/cleanup[19539]: 3p9b6f33lRz21: milter-reject: END-OF-MESSAGE from rh.thelounge.net: 5.7.1 Blocked by Spamfilter; from=<h.rei...@thelounge.net> to=<users@spamassassin.apache.org> proto=ESMTP helo=<rh.thelounge.net> Dec 2 10:46:51 mail spamd[5847]: spamd: result: Y 11 - ALL_TRUSTED,BAYES_00,T_RP_MATCHES_RCVD,URIBL_BLACK,URIBL_JP_SURBL,URIBL_SBL,URIBL_SBL_A scantime=0.8,size=3825,user=sa-milt,uid=189,required_score=7.8,rhost=localhost,raddr=127.0.0.1,rport=/run/spamassassin/spamassassin.sock,mid=<565ebe09.5070...@thelounge.net>,bayes=0.000000,autolearn=disabled

signature.asc
Description: OpenPGP digital signature