Spamassassin: How to test homemade rules?

[Tenshi]

Everything is running smoothly (so far!) but I can't seem to figure this one out...

Trying to install my own personal rules and FuzzyOCR but both seemed to be ignore at the moment. On a "normal" system, I would do 'spamassassin --lint' but how can we achieve the same purpose with Zimbra?

PS: And no, signing-up for spam is not part of the solution in my mind

[scottnelson]

That's why I keep a bunch of old spam in a special folder.
Just wack some old .gif, etc.,etc., spams that into an e-mail from outside and e-mail into your server.

All you want to check are the FuzzyOCR engine score anyway right?

I actually haven't seen much of those lately..........

Scotty

[Tenshi]

Yeah, the goal is to see why FuzzyOcr is not reporting anything... oh well

[garyo]

Sorry to revive an old thread, but I didn't see this resolved anywhere else. I have some custom SA tests in ~zimbra/spamassassin/conf, and I need to test them to see if they're working. In a normal SA install, I use spamassassin -D -t and look at the debug lines to make sure all my rules and modules are active. How can I do this within Zimbra? I think SA doesn't really run normally, it's run within amavisd as a perl module, correct? Any help would be appreciated.

[phoenix]

Originally Posted by garyo

Sorry to revive an old thread, but I didn't see this resolved anywhere else. I have some custom SA tests in ~zimbra/spamassassin/conf, and I need to test them to see if they're working. In a normal SA install, I use spamassassin -D -t and look at the debug lines to make sure all my rules and modules are active. How can I do this within Zimbra? I think SA doesn't really run normally, it's run within amavisd as a perl module, correct? Any help would be appreciated.

Install spamassassin for your operating system and run the normal command to verify the rules.

[uxbod]

Once installed

su - zimbra
spamassassin -C /opt/zimbra/conf/spamassassin -D --lint > /tmp/sadebug.txt 2>&1

[garyo]

Thanks uxbod! I found I also had to say --siteconfigpath=/dev/null to prevent it from trying to load my regular SA site config from /etc/spamassassin (which would not be used when amavisd calls it).

I also tried /opt/zimbra/amavisd/sbin/amavisd debug-sa, but that didn't work (gave me errors about the daemon already running). That seemed like, if it had worked, it would be the most correct invocation of SA since it would call it with the correct env vars and options -- one of the things I wanted to test for was calling pyzor/razor2/dcc, which all require some config files in certain places. But your way seems good enough for now. Thanks!