Scalix Forums

Hi,
I just installed spam assassin and followed the technotes on configuring it. The only thing is that when i send mail and look at the log it says the the spamassassin milter is in an error state. Any ideas?

This is error is usually because the 'SOCKET' value in /etc/sysconfig/spamass-milter doesn't match what's in the sendmail config.

Thank you for your quick reply.

Hmm. So how would I fix it? I looked for that config file and it wasn't in that location.

Some ideas:

It might be set directly in the init script (somewhere in /etc/init.d).

If you're on an rpm-based system then this will give you a listing of the config files installed by <package>:



You could do this:



Or if all else fails this :-)

Ok, I looked in both the start up files for spamassassin and sendmail.cf and it seems like both have the socket pointing to /var/run/spamass.sock
It is still erroring out on me. Any more ideas?
Thank ahead of time.

Ok, I got it out of the error state, but evertime i restart the server i have to type

spamass-milter -p /var/run/spamass.sock -f

to get it up. I tried changing the startup script for it, but I still can't get it to start up at boot. Any ideas?

I suspect your spamass-milter is not configured to start on boot. Edit /etc/init.d/spamass-milter and add the variables you require to this section:



Then configure the script to start on boot with:

chkconfig --level 35 spamass-milter on

To check it use:

chkconfig --list spamass-milter

Also make sure your spamassassin script is configured to start on boot.

Regards,
Don

The spamass-milter is set up to start on boot. The error that i keep getting is that

Aug 15 09:33:02 mail sendmail[4233]: k7FFX2q4004233: Milter (spamassassin): local socket name /var/run/spamass.sock unsafe
Aug 15 09:33:02 mail sendmail[4233]: k7FFX2q4004233: Milter (spamassassin): to error state

Both spamass-milter and spamassassin are set to boot.

A little googling goes a long way...

http://www.google.com/search?hl=en&q=Mi ... gle+Search

This may be of most use to you...

http://comments.gmane.org/gmane.mail.sp ... eral/54594

Regards,
Don

the configuring spammassassin guide is wrong for FC4

the location to the spamass-milter socket file should be

/var/run/spamass-milter/spamass-milter.sock

All - I just had a problem with the spamass-milter socket and found that somehow, the /etc/init.d/spamass-milter was creating a socket with a different name from the one specified in /etc/mail.sendmail.cf.

Here is what I learned from this and fixed:

SpamAssassin - fixing errors with socket

Startup script is /etc/init.d/spamass-milter

In that file it specifies creation of a socket at (hopefully) /var/run/spamass-milter/spamass-milter.sock

In /etc/sendmail.cf should be a line looking for the above socket. The paths and socket names should match.

You can also navigate to the path given and see the sockets there and the dates created.

If they don't match, fix the spamass-milter startup script first to match what is in sendmail.cf, then make sure the paths match with /etc/sendmail.cf and then restart
SpamAssassin and sendmail as follows:

/etc/init.d/spamassassin restart
/etc/init.d/spamass-milter restart
/etc/init.d/sendmail restart

If they don't match you may see the following error in /var/log/maillog:

Feb 18 12:52:03 mailpa sendmail[23268]: m1IHq3xq023268: Milter (spamassassin): error connecting to filter: Connection refused by /var/run/spamass-milter/spamass-milter.sock
Feb 18 12:52:03 mailpa sendmail[23268]: m1IHq3xq023268: Milter (spamassassin): to error state

You can easily see the health of spamassassin with the following command:

tail -f /var/log/maillog | grep spam

My OS is Linux Redhat EL4

Ruthiness wrote:All - I just had a problem with the spamass-milter socket and found that somehow, the /etc/init.d/spamass-milter was creating a socket with a different name from the one specified in /etc/mail.sendmail.cf.

Here is what I learned from this and fixed:

SpamAssassin - fixing errors with socket

Startup script is /etc/init.d/spamass-milter

In that file it specifies creation of a socket at (hopefully) /var/run/spamass-milter/spamass-milter.sock

In /etc/sendmail.cf should be a line looking for the above socket. The paths and socket names should match.

You can also navigate to the path given and see the sockets there and the dates created.

If they don't match, fix the spamass-milter startup script first to match what is in sendmail.cf, then make sure the paths match with /etc/sendmail.cf and then restart
SpamAssassin and sendmail as follows:

/etc/init.d/spamassassin restart
/etc/init.d/spamass-milter restart
/etc/init.d/sendmail restart

If they don't match you may see the following error in /var/log/maillog:

Feb 18 12:52:03 mailpa sendmail[23268]: m1IHq3xq023268: Milter (spamassassin): error connecting to filter: Connection refused by /var/run/spamass-milter/spamass-milter.sock
Feb 18 12:52:03 mailpa sendmail[23268]: m1IHq3xq023268: Milter (spamassassin): to error state

You can easily see the health of spamassassin with the following command:

tail -f /var/log/maillog | grep spam

My OS is Linux Redhat EL4

Its actually better to set the socket via /etc/sysconfig/spamass-milter

That way when you next upgrade spamass-milter it wont blow away your change to the init script.

And its possible to set the socket to a file and location of your choice.