Glad to hear it is working.
For completeness, readers please note that you need to "service spamassassin restart" to get changes you make to come into effect.
Also for completeness on this forum, here are the Razor instructions:
First: mkdir /etc/mail/spamassassin/.razor then chown it popuser.popuser
Next, run the following commands (as root is fine):
azor-admin -home=/etc/mail/spamassassin/.razor -register
razor-admin -home=/etc/mail/spamassassin/.razor -create
razor-admin -home=/etc/mail/spamassassin/.razor -discover
Now chown popuser.popuser everything in .razor
Next, tell spamd where to find Razor's config file by editing /etc/mail/spamassassin/local.cf and adding:
Finally, edit /etc/mail/spamassassin/.razor/razor-agent.conf to add:
razorhome = /etc/mail/spamassassin/.razor/
just add: dcc_path /usr/bin/dccproc to local.cf, although I don't know how much good or bad this might be doing, because DCC seems to work just fine without it and still complains (in a non-fatal way)about stuff when you run spamassassin -D
When you run spamassassin -D < some-test-email.txt note that you are doing so as root. As spamassassin does not generally run as root (it runs as popuser usually), this does not give you the full story.
So, what you need to do is a trick I learned from breun:
su -s /bin/bash - popuser
This will give you a bash shell running as popuser.
You can then try spamassassin -D < some-test-email.txt (make sure some-email-txt is readable by popuser first!) which will run as popuser and may give you errors you would not normally have seen.
Note that I still don't know how one controls which user spamassassin runs as in a qmail-scanner environment. It would be handy to know, at least how to find out the correct user if it is not popuser.
EDIT: I'm doubting myself over whether spamd runs as root or not now. Somebody come to my rescue please?