Problem resolved..

Discovered that the C:\Temp directory was missing  so Clam was failing when trying to write to it. Restored the directory and all is well.

Thanks again

Hello,

We're running Mercury/32 v4.61 and having a problem with non-local mail processing slowly. The Mercury Queue is backed up with ~ 15,000 messages and when I watch the Core process it appears to be processing messages at a very consistent 31 - 32 second increment. The setting for Core Process polling for new mail is set for 10 sec.

This all started yesterday when it appeared that a spam mailbox (routed from Spamhalter) got too full (68,000 msgs, ouch!) and Merc appeared to stop processing altogether. Once that was cleaned out, mail started flowing again but can't seem to catch up. Its virtually 24hrs behind delivering incoming mail.

I've watched the core process before and it has always appeared to process mail much more quickly than it is now.

This is a fairly good size server: Windows 2003 Server, dual Xeon processors w/ 4gb RAM (we're running merc on only one processor for stability). The hardware doesn't appear to be stressed at all. i.e. CPU and Mem usage.

A few other details: Using Spamhalter, Graywall, Clamwall, some dnsbl lists and a few manual filters in the global filter list. (tried disabling both the dnsbl's and spamhalter but no effect)

Thanks for your help!

David Silsbee

Update to this problem.

Turning off Clamwall returned processing to normal speed; very fast processing. Now, we haven't changed anything on clamwall so wondering what we should check for source of the problem w/in cw.  Don't want to go too long with cw off.....

Thanks again for any suggestions

Check your clamwall logs, sounds like Clamwall is failing & Core is waiting for the Clamwall timeout (30 sec) for each message.

Dang! I knew those logs must be good for something  <g> !

You're right, the log shows "Clam D not responding" after the 30 sec. timeout.

Will investigate why.....

Any suggestions?

Thanks much!

[quote user="viking956"]Dang! I knew those logs must be good for something  <g> !

You're right, the log shows "Clam D not responding" after the 30 sec. timeout.

Will investigate why.....

Any suggestions?

1.  Run CLAMD manually to be sure it will load.  If not fix the setup.  If it runs try leaving CLAMD running manually and check the ClamWall logs.

2.  Make sure you are running the latest version of ClamWall and ClamAV.

 Thanks much![/quote]