-----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160 Alexander Dalloz wrote: > Am Mo, den 17.10.2005 schrieb Timothy Murphy um 14:06: > >> Craig White wrote: >> >>>> spamassassin seems to have stopped performing on my desktop. >>>> I am getting the following 2-line message in /var/log/maillog >>>> : >>>> =============================================================== >>>> Oct 16 03:25:10 alfred sendmail[7341]: j9G2PAGa007341: >>>> Milter (spamassassin): local socket name >>>> /var/run/spamass.sock unsafe Oct 16 03:25:10 alfred >>>> sendmail[7341]: j9G2PAGa007341: Milter (spamassassin): to >>>> error state >>>> =============================================================== >>>> >> >> ... >> >>>> I'm running Fedora-4, with spamassassin-3.0.4-1.fc4 and >>>> spamass-milter-0.3.0-8.fc4 , > > >> The message comes from sendmail, and seems to suggest that >> sendmail does not like to open a socket with local name >> /var/run/spamass.sock . > > > Correct. > >> What does it mean to say that this is "unsafe"? > > > Unfortunately that error message is a bit general and can even be > misleading as Craig already explained (the case where the socket > file is even missing would generate the same message). > >> I notice that spamass-milter seems to have no problem with >> /var/run/spamass-milter/spamass-milter.sock . > > > And that is the kind of setup the spamass-milter package from > Fedora Extras, packaged by Paul Howarth, ships with. > > http://cvs.fedora.redhat.com/viewcvs/rpms/spamass-milter/FC-4/spamass-milter.spec?root=extras&rev=1.5&view=markup > > >> Timothy Murphy > > > The reason for the problem is, that /var/run has too much > permissions. Let the socket file reside in /var/run/spamass-milter, > which is owned by the owner of the process (sa-milt) and be sure > the directory has only chmod 700. > > Alexander > > Another thing to check also is to be sure that spamass-milter is setup to automatically startup on system reboot. I had this problem with clamav-milter at one time and when I made sure it was setup to start on bootup the problem went away. All of these are good starting points and cover all the setup. Unfortunately, like Alexander points out this error is rather general in nature and misleading to some extent; because it covers a broad range of possible outcomes. James -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDU6hHkNLDmnu1kSkRA7lMAJ94Ai/UbqRP+V3U8dHVk5qY/g7G0wCeM3Ms mNbYbjTZO9vx2rNXYOuk1Rg= =akYM -----END PGP SIGNATURE----- -- Scanned by ClamAV - http://www.clamav.net
