I had a tough problem with the quarantine, using access mdb

I was away for about 3 days and did not have a chance to clean the quarantine. In this time the mdb reached 500+mb

When I tried to open the interface it started using the RAM like there is no tomorrow, it is running on a 2GB RAM machine, used that and it started to fill the page file as well

I have to kill the process

Restarting the service or the server did not help.

Eventually I opened the database with MS Access and went cleaning and compressing it manually. Took me a while... for a half GB file.

Anyway I have changed the system on tag'n'deliver as it was getting beyond manageability.

FYI I had less than .5% false positives and, combined with Cloudmark's client side antispam filter, I have some 99% rate of spam detection and removal capabilities.

Tag'n'deliver works fine but my users would be interested to know what was the trigger for tagging for each message, is this something taken in account for future versions?

Cris

Cris,

MS Access is a database platform that works fine for end users, but is not scalable enough for large database with numerous transactions. If your email traffic is high, we strongly recommend using the other platforms supported, MySQL, MS SQL, or Oracle.

That said, the quarantine should self-maintain itself. The interval at which old entries are removed defaults to 60 minutes, but is user-configurable. So are the number of days for which quarantined emails are stored in the database. Can you please let us know what you have these values set to, and ballpark how many emails/day are processed by SpamFilter? We'd also need to know which version of SpamFilter you are using.

Roberto F.
LogSat Software