mwalters

I am still having issues with spam getting through that is above the threshold of the score I have set to mark as spam. I have anything over 70 set to spam, but I am getting mail ratings that are 75 and above passing through. is there a rule I could create that states that any mail with a 70 or above be sent to the quarantine mailbox? I have attached some screenies as proof. Thanks Mike..

Hi Chadh and thanks for the reply. Yep, we are using ESet for Exchange and all of our client workstations. I have all of our spam going to a quarantine mailbox, and ESet throws the Quarantine flag on it when it is sent there as in the screenshot I attached. I am writing the spam score to the header of the message, but if I tighten it down then quite a bit of valid mail is thought to be spam. I am not sure what else I can do to get the volume of spam to decrease any more. Can I filter out spam with keywords within a mail? Thanks a bunch, Mike...

Greetings, Anti-spam has been up and running for quite some time on our Exchange server and it is catching most, but we are still seeing quite a bit of spam getting in to our users inbox. Maybe someone can help me with additional ways to stop it. I have all the spam Eset catches going into a spam inbox, and it is working well. I am also using 3 DNSBL (spamhaus, sorbs, spamcop) but I am still seeing a bunch of spam that is making it through from smptserver.submit in the message header. I will attach a screenshot of the message header for you to see. is there any way to block this from even getting to us? Is DNSBL the way to go as well in trying to eliminate spam or should I just go with ESet with a different configuration? I am just not sure we are using ESet to it's maximum potential or not on our Exchange server (we are running 2007 Exchange as FYI). Thanks a bunch for any help provided, Mike...

Greetings, Running Eset for Exchange, version 4.5.10015.0 and recently our logging and quarantine has stopped working for spam mailings. I am getting an error within the application log of the server that says the following: Eset Reporting Service XmonAgent: invalid scanner handle Also seeing this error: ESET Reporting Service XmonSmtpAgent: Invalid scanner handle Any ideas as what this error is and why I am receiving it? Thanks a bunch