MCP not working

[Glenn Steen]

On 10/08/07, Daniel Eiland <daniel at bokko.nl> wrote:
> I get 4 warnings:
>
> [26720] warn: config: failed to parse line, skipping, in
> "/usr/local/etc/MailScanner/mcp/mcp.spam.assassin.prefs.conf": use_razor1 0
> [26720] warn: config: failed to parse line, skipping, in
> "/usr/local/etc/MailScanner/mcp/mcp.spam.assassin.prefs.conf":
> decode_attachments 1
> [26720] warn: config: failed to parse line, skipping, in
> "/usr/local/etc/MailScanner/mcp/mcp.spam.assassin.prefs.conf": use_razor1 0
> [26720] warn: config: failed to parse line, skipping, in
> "/usr/local/etc/MailScanner/mcp/mcp.spam.assassin.prefs.conf":
> decode_attachments 1
These are quite OK, ignore them.
The reason is that the newer SA versions don't have these keywords
built in, rather loaded from specific plugins... So when you don't
load the plugins, you don't have the setting to turn those functions
off... But they are still off. Only warnings, so harmless.

> I also see that the cf files are not read from
> /usr/local/etc/MailScanner/mcp
> But from
> [26720] dbg: config: using "/usr/local/etc/mail/spamassassin" for site rules
> dir

You need be more like MCP itself... Something like
spamassassin --config-file=/etc/MailScanner/mcp/mcp.spam.assassin.prefs.conf
--siteconfigpath=/etc/MailScanner/mcp -p
/etc/MailScanner/mcp/mcp.spam.assassin.prefs.conf --lint -D 2>&1 |
less -e
... should get you there:-).
Far better than to lint like this, is to actually use that on a text
file wemulating an actual message that it should match... Just do:
spamassassin --config-file=/etc/MailScanner/mcp/mcp.spam.assassin.prefs.conf
--siteconfigpath=/etc/MailScanner/mcp -p
/etc/MailScanner/mcp/mcp.spam.assassin.prefs.conf -t -D <
/path/to/file 2>&1 | less -e

... and you should see whether the rule you're testing triggers or not.

Cheers
-- 
-- Glenn
email: glenn < dot > steen < at > gmail < dot > com
work: glenn < dot > steen < at > ap1 < dot > se