4.63.8: sa rules and DCC confusion

[Jeff A. Earickson]

Gang,

I admit to being a bit rusty here, things always worked before...
I see no evidence in a MailScanner debug run that either 
DCC is being used, or that the SA /var/opt state rules are
being used.  Help....

I have DCC 1.3.60 running as a daemon from /opt/dcc/bin,
with the dccifd= socket located in /opt/dcc.  My 
/opt/MailScanner/etc/spam.assassin.prefs.conf file says:

ifplugin Mail::SpamAssassin::Plugin::DCC
use_dcc 1
dcc_path    /opt/dcc/bin/dccproc
dcc_home    /opt/dcc
endif

But the MailScanner debug output says:

[23329] dbg: config: read file /etc/mail/spamassassin/init.pre
[23329] dbg: config: read file /etc/mail/spamassassin/v310.pre
[23329] dbg: config: read file /etc/mail/spamassassin/v312.pre
[23329] dbg: config: read file /etc/mail/spamassassin/v320.pre
...
[23329] dbg: dcc: dccifd is not available: no r/w dccifd socket found
[23329] dbg: dcc: dccproc is not available: no dccproc executable found
[23329] dbg: dcc: dccifd and dccproc are not available, disabling DCC

I see no evidence that /opt/MailScanner/etc/spam.assassin.prefs.conf
ever gets used.  My MailScanner.conf has:

SpamAssassin User State Dir = /var/spool/spamassassin
SpamAssassin Site Rules Dir = /etc/mail/spamassassin
SpamAssassin Local Rules Dir = /etc/mail/spamassassin
SpamAssassin Local State Dir = /var/opt

Likewise, I see no evidence that the latest sa-update rules
in /var/opt/spamassassin/3.002003 ever get used, from the MailScanner
debug output.

What have I messed up here?

Jeff Earickson
Colby College