https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7825
--- Comment #1 from Henrik Krohns <[email protected]> --- Implemented, with HashBL as test. Will need to go through all plugins to add ruletypes. Sending trunk/lib/Mail/SpamAssassin/Conf/Parser.pm Sending trunk/lib/Mail/SpamAssassin/Conf.pm Sending trunk/lib/Mail/SpamAssassin/Plugin/HashBL.pm Sending trunk/lib/Mail/SpamAssassin/Plugin.pm Transmitting file data ....done Committing transaction... Committed revision 1878582. Example $ spamassassin --cf 'body FOO eval:check_hashbl_emails()' --lint Jun 8 10:48:59.294 [2723560] warn: wrong rule type defined for FOO, expected 'header' Jun 8 10:48:59.589 [2723560] warn: lint: 1 issues detected, please rerun with debug enabled for more information Added $ruletype to docs $plugin->register_eval_rule ($nameofevalsub, $ruletype) Plugins that implement an eval test will need to call this, so that SpamAssassin calls into the object when that eval test is encountered. See the REGISTERING EVAL RULES section for full details. Since 4.0, optional $ruletype can be specified to enforce that eval function cannot be called with wrong ruletype from configuration, for example user using "header FOO eval:foobar()" instead of "body FOO eval:foobar()". Mismatch will result in lint failure. $ruletype can be one of: $Mail::SpamAssassin::Conf::TYPE_HEAD_EVALS $Mail::SpamAssassin::Conf::TYPE_BODY_EVALS $Mail::SpamAssassin::Conf::TYPE_RAWBODY_EVALS $Mail::SpamAssassin::Conf::TYPE_FULL_EVALS -- You are receiving this mail because: You are the assignee for the bug.
