[Mimedefang] Razor2 problems with mimedefang 2.33...

[Dan Tulovsky]

Hello.

I am trying to get razor2 functionality enabled into a working
mimedefang 2.33 installation.  I believe I've done all the steps
correctly.

I did a razor-admin -register as the defang user, which created a .razor
directory with all sorts of files in it.  I did a -discover.  I can do,
as the defang user:

/usr/local/bin/spamassassin -t < sample-spam.txt

And get back:

---- Start SpamAssassin results
9.00 points, 5 required;
*  0.8 -- From: does not include a real name
*  1.2 -- Valid-looking To "undisclosed-recipients"
*  0.6 -- Invalid Date: header (not RFC 2822)
*  0.2 -- BODY: Once in a lifetime, apparently
*  1.6 -- BODY: Information on how to work at home (2)
*  0.9 -- BODY: List removal information
*  1.0 -- BODY: Drastically Reduced
*  2.1 -- Listed in Razor2, see http://razor.sf.net/
*  0.1 -- Date: is 12 to 24 hours before Received: date
*  0.5 -- Message-Id is not valid, according to RFC 2822

---- End of SpamAssassin results

So razor2 is being called and is working.  After the above command, in
the ./razor/razor-agent.log file I see a line:

Jun 17 10:31:37.277416 check[27299]: [ 1] [bootup] Logging initiated
LogDebugLevel=3 to file:/home/defang/.razor/razor-agent.log
Jun 17 10:31:38.349022 check[27299]: [ 3] mail 1 is known spam.

Which is all good.

In my mimedefang-filter, I have:

$SALocalTestOnly = 0;

And in sa-mimedefang.cf I have:

use_razor2      1

... But I don't see any evidence that any mail is getting passed through
razor.  The /home/defang/.razor/razor-agent.log file is not written to
(only when I run from command line).

Did I miss something obvious?

Thank you,
Dan