Re: Detecting which shortcircuit rule fires

[Reindl Harald]

Am 02.12.2015 um 12:29 schrieb Sebastian Arcus:

On 02/12/15 09:49, Reindl Harald wrote:

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

Thank you. What I've done:

1. I've disabled shortcircuiting in local.pre. This is not a busy
server, and on reflection it is not needed at all.
2. The shortcircuit does get disabled - although I thought it doesn't.
It turns out that I should have pointed "spamassassin -D" to the proper
site config files with the "--siteconfigpath". The mail daemon process
(spamd) does pick on the proper config files fine.

I can still post the headers of the email, if you think it would help
the list - but without shortcircuiting things look ok now

well i wonder which shortcircuit rules are active by default

i needed even "loadplugin Mail::SpamAssassin::Plugin::Shortcircuit" in "local.cf" on Fedora to get my own rules wokring at all

signature.asc
Description: OpenPGP digital signature