Thank you! I see that shortcircuit is already enabled in 320! I think you really hit on something.
Thanks again! I knew there was a simple answer. On 01/19/2018 09:35 AM, David Jones wrote: > On 01/19/2018 08:24 AM, Chip wrote: >> Ok point take - I should have mentioned earlier that *part* of the >> reason to stick with SA is because it does spf and dkim checks. My >> mistake. >> >> Moving on now, David, good suggestions! Enlighten me about the >> Shortcirtcuit plugin please. How does one activate it or use it? >> > > 1. Enable the Shorcircuit plugin simply by uncommenting it in the > v320.pre like I said below. This file will be in the same directory > as your local.cf usually /etc/mail/spamassassin. > > 2. I gave the exact 4 lines to put in your local.cf below. > > Try this and check your mail logs for a bit. Play around with SA > settings in your local.cf and see what happens. This is how you learn > SA. It's taken me years of doing this almost daily to understand how > SA works and I am not an SA guru like some on this list. > >> The manual gives an example as follows, so is it correct to simply >> put this into my local.cf and let it run? It looks like it simply >> activates by adding the line: shortcircuit TEST on. >> >> =over 4 >> >> body TEST /test/ >> describe TEST test rule that scores barely over spam threshold >> score TEST 5.5 >> priority TEST -100 >> shortcircuit TEST on >> >> >> >> On 01/19/2018 08:38 AM, David Jones wrote: >>> On 01/18/2018 05:49 PM, Chip wrote: >>>> Very well stated. Bravo! >>>> >>>> The end point here is to examine the email headers that specifically >>>> refer to dkim and spf signatures. Based on fail or pass, or some >>>> combination in concert with the sender's email address, they get moved >>>> into fail or pass folders. >>>> >>>> That's it! >>>> >>> >>> Finally we get some details! :) This is very simple then: >>> >>> 1. Enable the Shortcircuit plugin in v320.pre >>> >>> 2. Enable these SPF and DKIM rules to be shortcircuit'd in your >>> local.cf: >>> >>> shortcircuit SPF_PASS on >>> shortcircuit DKIM_VALID_AU on >>> score SPF_PASS -100 >>> score DKIM_VALID_AU -100 >>> >>> 3. Now you should see the SHORTCIRCUIT rule hit in your logs. Setup >>> a sieve rule to look for those 2 rules above to move them to the >>> pass folder. They will always be ham (score very low) and never be >>> blocked by the "glue" even with the default required_score. >>> >>> P.S. Technically, you could just set the 2 scores and not enable the >>> shortcircuit plugin. The 2 score lines in the local.cf should do >>> what you want to do. >>> >> > >
