Scratch my last sentence in the post before this one.  I did find some bayesian marked messages in the quarantine before I had to turn it off.

Hillard

|On our servers when Bayesian is disabled the memory is 20-30MB without any trouble.
|When our SF memory reaches above 300MB with Bayesian enabled, it starts acking |strange. (It normally runs about 50-70MB) The memory climbs higher, the CPU will hang |at 100% more often and the concurrent connections starts climbing and stay higher then |normal until I restart SF service.

Okay, that is what happens to me.  Without the bayesian filter running I run about 30MB for the SpamFiltersvc.  When I enable the bayesian the memory usage goes way up, even over 300MB and the CPU stays at 100% and the concurrent connections climb and stay high, this all takes a number of hours for it to hit. Sometimes I can get the numbers to go down when I turn off the bayesian and sometimes I have to turn off the bayesian and restart the service.

I installed the 306 patch and still got the same problem.

Another thing is even when I have the bayesian filter enabled I fail to see any messages marked as being found by it, only my keyword, other blacklists and reverse dns marked messages. My corpus is Spam=29171 and Good=56842; however, still nothing marked by it when I have it enabled.  Is this because I have keyword filter entries?

Hillard

Wow,  that is a lot of memory being used by SF.

On our servers when Bayesian is disabled the memory is 20-30MB without any trouble.
When our SF memory reaches above 300MB with Bayesian enabled, it starts acking strange. (It normally runs about 50-70MB) The memory climbs higher, the CPU will hang at 100% more often and the concurrent connections starts climbing and stay higher then normal until I restart SF service.

We have MS SQL sitting on its own 2000 server and the database size is in upwords of 25GB for only 4 days of retaining quarantine messages.

Dan B

Hillard,

We are in the process of testing internally build 306 which should help solve some memory issues. While it still has not been officially released, we have placed a link to it in the registered user's area. Could you please try this build to see if it solves any problems?

Roberto F.
LogSat Software

You should be able to run the database on the same box without issue.

I would go to Windows 2000 or 2003, if possible.

If not, at least get away from Access (which version, btw?)      I'd go with MSDE or MySQL.

Version 2 of the SpamFilter flies under 2000 and 2003, using MSSQL, MSDE or MySQL...

Hillard,

I know nothing about access except that it has issues if it gets very large.  I am running MS-SQL on the same server as SpamFilter and have no problems in that area.  What I am looking for is with Bayes enabled, do you show a ton of "Stale" connections that do not seem to go away when your problem is happening?  If so, please email me directly at daseligmann at hotmail dot com.  We may have a common issue that has no obvious (yet) cause.  Also, do you have a feel for what your total daily message volume is?  And do you receive LOTS of large (10Meg plus) attachments?

Regards,

Dan S.

Oh, as I a side note when I turned connection grid back on all connections to the spam filter quit.  I restarted the service and it was okay, not sure why that happened?  Also noticed even though I had the bayesian turned of my server was using 360MB (it has 515MB) and when I restarted the spam filter service memory went down to 100MB.  I must have a memory leak going on with the spam filter service.  Again someone mentioned moving from NT (which is what it is and has been since August with version 1+) to 2000.

Hillard

>Can you "indulge me"?  Please run wth the "Disable Connections Grid" check box NOT >set and when the cpu goes high, are there a lot of RCPT TO's that are not going away?  >Also, make sure that you go to the quarantine grid and "hide" the quarantine.

Okay, I had both disabled or turned off.  I have turned back on the connections grid to watch it.  I do remember when it hits seeing a lot of  "Current Outbound Connections" and "Current Inbound Connections" when the problem is occuring.  Disable the bayesian and the numbers start coming down in a few minutes and so does the CPU and memory usage.  One other person recommended putting the quarantine on another server instead of the spam filter box and I know Access is not as good as SQL (I have some MySQL servers running that if I have to I can put the quarantine on them, I just was trying to keep it all on one server).

Hillard