Warren,
> http://spameatingmonkey.com/usage.html
>
> Are these URI rules really valid syntax? They don't look right, and
> spamassassin lint rejects them.
>rulesrc/sandbox/wtogami/20_unsafe.cf: 0 active rules, 5 other
>lint: config: failed to parse line, skipping, in "rules/70_sandbox.cf":
urirhssub SEM_FRESH fresh.spameatingmonkey.net. A 2 at build/mkrules line 253.
>lint: config: failed to parse line, skipping, in "rules/70_sandbox.cf":
urirhssub SEM_URI uribl.spameatingmonkey.net. A 2 at build/mkrules line 253.
>lint: config: failed to parse line, skipping, in "rules/70_sandbox.cf":
urirhssub SEM_URIRED urired.spameatingmonkey.net. A 2 at build/mkrules line
253.
Rules are alright. What I can see is that build/mkrules intentionally
does not load plugins (except for the Plugin::Check), which means
the 'urirhssub' directive in your .cf file is not recognized.
An quick-and-dirty hack (without understanding the consequences) is:
--- build/mkrules (revision 823750)
+++ build/mkrules (working copy)
@@ -239,7 +239,7 @@
# debug => 1,
local_tests_only => 1,
dont_copy_prefs => 1,
- config_text => $pretext.$text
+ # config_text => $pretext.$text
});
my $errors = 0;
I don't know what the proper solution is, and where actually
lies the core of a problem.
Mark
