.sock file unsafe?

[Michael Sullivan]

I'm seeing lots of these in my log files:

May  6 15:23:29 baby sm-mta[22643]: l46KNTQf022643: Milter
(spamassassin): local socket name /var/run/spamass-milter.sock unsafe

The trouble is that the file doesn't even exist:

baby log # ls /var/run/spamass-milter.sock
ls: cannot access /var/run/spamass-milter.sock: No such file or
directory

However, I think the file it's searching for is in /var/run/milter:

baby log # ls /var/run/milter
spamass-milter.pid  spamass-milter.sock

Where can I change this setting so that it no longer looks for the
socket file in /var/run?  Also, in the meantime, spamassassin is not
labeling anything.  Please help.  I'm running:

baby log # emerge -pv spamassassin spamass-milter sendmail

These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild   R   ] mail-filter/spamassassin-3.1.8-r1  USE="berkdb doc mysql
ssl -ipv6 -ldap -postgres -qmail -sqlite -tools" 0 kB 
[ebuild   R   ] mail-filter/spamass-milter-0.3.1-r1  114 kB 
[ebuild   R   ] mail-mta/sendmail-8.14.0  USE="ssl tcpd -ipv6 -ldap
-mailwrapper -mbox -nis -sasl -sockets" 0 kB 

baby log # uname -a
Linux baby 2.6.19-gentoo-r5 #1 SMP Fri Apr 27 11:27:20 CDT 2007 i686 AMD
Duron(tm) Processor AuthenticAMD GNU/Linux