Bug 5906 - Shortcircuit Fails to execute on specific priorites
Summary: Shortcircuit Fails to execute on specific priorites
Status: RESOLVED INVALID
Alias: None
Product: Spamassassin
Classification: Unclassified
Component: Plugins (show other bugs)
Version: 3.2.4
Hardware: Other Linux
: P5 major
Target Milestone: Undefined
Assignee: SpamAssassin Developer Mailing List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-05-08 19:41 UTC by Clayton Keller
Modified: 2019-06-24 15:57 UTC (History)
1 user (show)



Attachment Type Modified Status Actions Submitter/CLA Status
debug output showing shortcircuit rules text/plain None Clayton Keller [NoCLA]

Note You need to log in before you can comment on or make changes to this bug.
Description Clayton Keller 2008-05-08 19:41:13 UTC
Created attachment 4313 [details]
debug output showing shortcircuit rules

As discussed in the post to the user list. I am having issues with Network based tests having priorities and the shortcircuit occurring and bypassing remaining rules.

Here's is a sample of my priorities:

# HIGH PRIORITY TESTS
#
priority URIBL_BLACK            -500
priority URIBL_JP_SURBL         -498
priority URIBL_SC_SURBL         -488
priority URIBL_OB_SURBL         -487

priority SC_URIBL_SURBL         -480
priority SC_URIBL_SBL           -479

priority RAZOR2_CHECK           -450
priority DCC_CHECK              -449
priority PYZOR_CHECK            -448

priority SC_URIBL_HASH          -440
priority SC_DIGEST_MULTI        -430

priority SC_URIBL_BAYES         -390
priority SC_DIGEST_BAYES        -389
#

# If the plugin is enabled let's go forth
ifplugin Mail::SpamAssassin::Plugin::Shortcircuit

# Shortcircuit Metas
#
meta SC_URIBL_SURBL             (URIBL_BLACK && (URIBL_SC_SURBL || URIBL_JP_SURBL || URIBL_OB_SURBL ))
meta SC_URIBL_HASH              ((URIBL_BLACK || URIBL_SC_SURBL || URIBL_JP_SURBL || URIBL_OB_SURBL) && (RAZOR2_CHECK || DCC_CHECK || PYZOR_CHECK))
meta SC_URIBL_SBL               ((URIBL_BLACK || URIBL_SC_SURBL || URIBL_JP_SURBL || URIBL_OB_SURBL) && URIBL_SBL)
meta SC_URIBL_BAYES             ((URIBL_BLACK || URIBL_SC_SURBL || URIBL_JP_SURBL || URIBL_OB_SURBL) && BAYES_99)
meta SC_DIGEST_BAYES            ((RAZOR2_CHECK + DCC_CHECK + PYZOR_CHECK) && BAYES_99)
meta SC_DIGEST_MULTI            ((RAZOR2_CHECK + DCC_CHECK + PYZOR_CHECK) > 1)

describe SC_URIBL_SURBL         Multiple URIBLs hit
describe SC_URIBL_HASH          URI/Checksum Combo hit
describe SC_URIBL_SBL           URI/NS Blacklist Combo hit
describe SC_URIBL_BAYES         URIBL/Bayes99 Combo hit
describe SC_DIGEST_BAYES        Checksum/Bayes99 Combo hit
describe SC_DIGEST_MULTI        Multiple HASHs hit  # same as DIGEST_MULTIPLE, but we want SC_ prefix.
#

# Shortcircuits
#
shortcircuit SC_URIBL_SURBL             spam
shortcircuit SC_URIBL_HASH              spam
shortcircuit SC_URIBL_SBL               spam
shortcircuit SC_URIBL_BAYES             spam
shortcircuit SC_DIGEST_BAYES            spam
shortcircuit SC_DIGEST_MULTI            spam
#

# Shortcircuit Scores
#
score SC_URIBL_SURBL            100.00
score SC_URIBL_HASH             100.00
score SC_URIBL_SBL              100.00
score SC_URIBL_BAYES            100.00
score SC_DIGEST_BAYES           100.00
score SC_DIGEST_MULTI           100.00
#

endif # Mail::SpamAssassin::Plugin::Shortcircuit
#EOF

I have sent a test message which contains a URI found in both URIBL and SURBL. This should as I understand the plugin trigger the SC_URIBL_SURBL, shortcircuit and be tagged as spam with a score of 100. However, the message itself does trigger this rule, but other possible rules as well before exiting after finishing all remaining priorities. 

[3342]dbg: check: is spam? score=204.86 required=5
[3342]dbg: check: tests=RAZOR2_CHECK,RCVD_IN_PBL,SC_URIBL_HASH,SC_URIBL_SURBL,URIBL_BLACK,URIBL_OB_SURBL

I will be attaching the full SpamAssassin debug along with this bug report. Also, is it not possible to now provide autolearning functionality with tflags? I was told this is disabled permanently in shortcircuit for performance benefits.

If you need further info, please let me know.

I have attached a .txt file with the debug output showing the behavior.
Comment 1 Clayton Keller 2008-05-08 19:59:32 UTC
I would like to include this version of SpamAssassin is 3.2.4 as provided by the RPM packages from rpmforge.

# spamassassin -V
SpamAssassin version 3.2.4
  running on Perl version 5.8.8
Comment 2 Henrik Krohns 2019-06-24 15:57:35 UTC
Closing old stale bugs. Network lookups are async so there's no way to do exact shortcircuiting.