Hi all.

So far my testing of Argo .Net with the latest MF using Sophos AV and SpamAssaaasin has been going well - until I added more than a few domains!  Now the server just kills itself by doing too much.  Although I have restricted Argo and MF to use 1 delivery thread I end up with an ever growing number of sav32cli.exe and sa.exe processes.  It was fine with just a few small domains but now it's at the point where the server barely responds.  Has anyone else encountered this?

I'll try recreating the filters, and taking them out one at a time to see where the problem lies, but wondered if there is a way to easily control the number of messages it processes at one time?

Thanks,

Dave

Hi Dave,

Have you tried excluding the Sophos AV and the SA to see if they are the cause of the tie up.  I don't recall if Sophos was listed in MF list of AV products.  I am not familiar with Sophos, but I do use AVG and find it integrates will with ArGo.  I also do not use SA, I use Paranoid instead.

Dave,
I have never used SA. Is there a different method of running it (PERL)? From the sounds of it, each time SA is called it is launching a new instance and racking up the memory.

Take a look at this solution:
http://support.sssolutions.net/kb/i...21&c=7

Steve,

I use the PERL version on 3 other servers and don't have a problem with it.  However, for some reason on this one it won't work and I've had to use the Win32 version.  The only difference is this one is running Argo .NET and the latest version of MF (this is my test server to help me sus out the problems before upgrading the other 3).

Just for my own sanity, am I right in thinking that in MF I need to use the filters on the Default tab for MailBag messages and the Incoming/Outgoing tab for POP3/SMTP messages?

Dave

Just a quick update...

I found that by running a virus check and spam check by hand through the command prompt that it was taking 15 seconds for SpamAssassin and about 5 seconds for Sophos, totalling about 20 seconds per message. Adding the -L parameter to the SA check improved things (down to about 5 seconds) but when there are about 20 processes running at once they tend to exceed the timeout specified in MailFilter (I don't want it to be above 60 seconds really).

Despite setting the number of threads in MF to 1 I am still seeing an infinite number of messages being scanned at once. How can I fix this? On my other servers it's set to 5 which works well. I am using 4.1.121.

Also, I have my rules set to save the message before deleting them if they are SPAM - since yesterday this has stopped working. It's deleting them without saving them (nothing in the rule has changed and the target path does exist).

Update 2...

The mail server is ignoring my list of valid recipients and accepting stacks of messages to random recipients, which should be ignored and not processed.  This is probably contributing to the high volume of sa.exe processes, etc.  I have emailed Archie to see if he has come accross this before.