ConfigServer Community Forum

Hi,
Checking my exim_paniclog, I discovered many messages as these:

2012-11-06 10:05:03 1TVki7-0000i5-JO spam acl condition: warning - spamd connection to 127.0.0.1, port 783 failed: Connection refused
2012-11-06 10:05:03 1TVki7-0000i5-JO spam acl condition: all spamd servers failed

I have MailScanner installed.
Searching Google for similar problems, nothing has a clear solution to this, except that it maybe related to SA reaching out maximum connection.

There is no time pattern. When comparing exim_mainlog and exim_paniclog timestamps. Some messages are being scanned by SA others get this message.

I browsed the MailScanner settings and exim settings, but nothing seems to take care of the number of concurrent connections for SA.

Anyone else ran into this and found a solution ?
Thanks

Spamd should not be running if you are running MailScanner - MS runs spamassassin but not as a daemon. You should go through your exim settings and make sure that no spamassassin-related settings are enabled.

Hi Sarah,
Thanks for your help.
I don't recall changing any exim settings after you guys installed MS.
Looking at Exim Configuration Manager, I don't see any settings saying spamassassin is turned on. Spamd is off in Service Manager section as well. And Enable Spam Assassin Filter in Tweak Settings is also on OFF.
Is it possible to have a snapshot of the exim settings that should be there (as you tweak when installing MS)?
I'll compare them with what I have.
Thanks

Hi again,
Could it be because I imported accounts from another server where spamassassin was ON ?
When I look into the home folder of these imported accounts, I can see a .spamassassin folder and a .spamassassinenable file.

I don't know how it would do this though if the deamon is off... just exploring here.

pagchen wrote:Hi again,
Could it be because I imported accounts from another server where spamassassin was ON ?
When I look into the home folder of these imported accounts, I can see a .spamassassin folder and a .spamassassinenable file.

I don't know how it would do this though if the deamon is off... just exploring here.

Yes, it could certainly be because of that. Here's a command you can run to find and delete the .spamassassinenable files:

Hi Sarah,
I just ran the command and it removed near a dozen instances of the file.
No paniclog messages so far (15 minutes).
I'll confirm in the next hours, but it looks promising.
Thanks

SOLVED ! No more paniclog entry since the files were removed.

Thank a lot Sarah.