Hi,
I got an email from netdev@vger.kernel.org that was a lengthy (422K) regression test report from a patch someone had submitted.
I got the message, saved it to a flat file, and ran "spamassassin -t -D rules < netdev.eml" and saw:
...
Nov 12 11:45:38.048 [36367] dbg: rules: ran eval rule __ANY_TEXT_ATTACH_DOC ======> got hit (1)
...
Nov 12 11:45:38.063 [36367] dbg: rules: ran eval rule __ANY_TEXT_ATTACH ======> got hit (1)
Nov 12 11:49:58.565 [36367] info: check: exceeded time limit in Mail::SpamAssassin::Plugin::Check::_eval_tests_type11_pri0_set1, skipping further tests
...
Am I correct that __ANY_TEXT_ATTACH alone took 4:30s? Looking at the rule, I don't understand why it's taking so long... unless that's not the smoking gun. Could there be rules that *aren't* matching but are taking a while?
72_active.cf: mimeheader __ANY_TEXT_ATTACH Content-Type =~ /text\/\w+/i
And how do I dig into why I'm getting that last message?
I can't even find type11_pri0_set1 as a string in /usr/share/perl5/vendor_perl/Mail/SpamAssassin/
Also, why are there multiple runs of:
Nov 12 15:05:37.368 [38290] dbg: rules: ran body rule __LOWER_E ======> got hit: "e"
Nov 12 15:05:37.368 [38290] dbg: rules: ran body rule __LOWER_E ======> got hit: "e"
Nov 12 15:05:37.368 [38290] dbg: rules: ran body rule __LOWER_E ======> got hit: "e"
Nov 12 15:05:37.368 [38290] dbg: rules: ran body rule __LOWER_E ======> got hit: "e"
Nov 12 15:05:37.368 [38290] dbg: rules: ran body rule __LOWER_E ======> got hit: "e"
Nov 12 15:05:37.368 [38290] dbg: rules: ran body rule __LOWER_E ======> got hit: "e"
Nov 12 15:05:37.369 [38290] dbg: rules: ran body rule __LOWER_E ======> got hit: "e"
Nov 12 15:05:37.369 [38290] dbg: rules: ran body rule __LOWER_E ======> got hit: "e"
Nov 12 15:05:37.369 [38290] dbg: rules: ran body rule __LOWER_E ======> got hit: "e"
Nov 12 15:05:37.369 [38290] dbg: rules: ran body rule __LOWER_E ======> got hit: "e"
Should this be capped to a maximum number of matches the way __HIGHBITS is?
And I'm not sure I want messages that haven't been fully scanned being delivered. Should I crank TIME_LIMIT_EXCEEDED to 20.0?
Thanks,
-Philip
I got an email from netdev@vger.kernel.org that was a lengthy (422K) regression test report from a patch someone had submitted.
I got the message, saved it to a flat file, and ran "spamassassin -t -D rules < netdev.eml" and saw:
...
Nov 12 11:45:38.048 [36367] dbg: rules: ran eval rule __ANY_TEXT_ATTACH_DOC ======> got hit (1)
...
Nov 12 11:45:38.063 [36367] dbg: rules: ran eval rule __ANY_TEXT_ATTACH ======> got hit (1)
Nov 12 11:49:58.565 [36367] info: check: exceeded time limit in Mail::SpamAssassin::Plugin::Check::_eval_tests_type11_pri0_set1, skipping further tests
...
Am I correct that __ANY_TEXT_ATTACH alone took 4:30s? Looking at the rule, I don't understand why it's taking so long... unless that's not the smoking gun. Could there be rules that *aren't* matching but are taking a while?
72_active.cf: mimeheader __ANY_TEXT_ATTACH Content-Type =~ /text\/\w+/i
And how do I dig into why I'm getting that last message?
I can't even find type11_pri0_set1 as a string in /usr/share/perl5/vendor_perl/Mail/SpamAssassin/
Also, why are there multiple runs of:
Nov 12 15:05:37.368 [38290] dbg: rules: ran body rule __LOWER_E ======> got hit: "e"
Nov 12 15:05:37.368 [38290] dbg: rules: ran body rule __LOWER_E ======> got hit: "e"
Nov 12 15:05:37.368 [38290] dbg: rules: ran body rule __LOWER_E ======> got hit: "e"
Nov 12 15:05:37.368 [38290] dbg: rules: ran body rule __LOWER_E ======> got hit: "e"
Nov 12 15:05:37.368 [38290] dbg: rules: ran body rule __LOWER_E ======> got hit: "e"
Nov 12 15:05:37.368 [38290] dbg: rules: ran body rule __LOWER_E ======> got hit: "e"
Nov 12 15:05:37.369 [38290] dbg: rules: ran body rule __LOWER_E ======> got hit: "e"
Nov 12 15:05:37.369 [38290] dbg: rules: ran body rule __LOWER_E ======> got hit: "e"
Nov 12 15:05:37.369 [38290] dbg: rules: ran body rule __LOWER_E ======> got hit: "e"
Nov 12 15:05:37.369 [38290] dbg: rules: ran body rule __LOWER_E ======> got hit: "e"
Should this be capped to a maximum number of matches the way __HIGHBITS is?
And I'm not sure I want messages that haven't been fully scanned being delivered. Should I crank TIME_LIMIT_EXCEEDED to 20.0?
Thanks,
-Philip