It never creates the socket. Initially, the socket was set to reside in /var/run/spamass.sock and then I saw one suggestion that said to change it to /var/run/spamass-milter/spamass.sock. I made the change but still received the unsafe messages.
-----Original Message----- From: Daryl C. W. O'Shea [mailto:[EMAIL PROTECTED] Sent: Monday, March 19, 2007 8:14 PM To: Joey Davis Cc: users@spamassassin.apache.org Subject: Re: spamassassin not working - spamass.sock unsafe Joey Davis wrote: > Greetings ... > > I can not get spamassassin to work. I have seen this problem in some > newgroups but no definitive solution. Here is the information > > OS Version: FC5 > Sendmail: 8.13.7 > Spamassassin: 3.1.3 > > Log entries: > Mar 19 17:28:32 obwat sendmail[29903]: l2JMSW21029903: Milter > (spamassassin): local socket name /var/run/spamass-milter/spamass.sock > unsafe > Mar 19 17:28:32 obwat sendmail[29903]: l2JMSW21029903: Milter > (spamassassin): to error state > Mar 19 17:28:32 obwat sendmail[29903]: l2JMSW21029903: Milter: > initialization failed, temp failing commands Thanks for any help, > > Joey That's not SpamAssassin, that's Sendmail reporting that your spamass-milter socket has unsafe permissions (and is refusing to use it). Daryl
