|
|
Question : stopping the spam
|
|
We are currently using TrendMicro's Scan Mail for Exchange 5.5 and the e-manager part to filter out SPAM which leaves a lot to be desired because when a user gets a SPAM e-mail, it is deleted (about 50%) of the time, however the user, in addition, gets a message that states "The original message content contained a virus or was blocked due to blocking rules and has been removed." We have discussed the problem with Trend, and they seem to have no way to prevent the user from receiving this additional message. So what is the difference in a user getting SPAM or a user getting a message saying that your SPAM has been deleted? Isn't the whole idea to limit the number of e-mail messages to those that which have some meaning to the user.
My question to the group is: is there anyone using a product out there that they are pleased with and that is preventing SPAM from getting to the end user, that does not send additional mails to the user telling them that their SPAM has been deleted? Any advise and or guidance on this topic would be appreciated.
Thanks in advance. Fshguo.
|
Answer : stopping the spam
|
|
The key thing with antispam products is making the decision on what is and what isn't spam.
In some cases the decision is very easy, and products can delete the message with some confidence. In other cases the decision isn't quite as easy, as something can look like spam but is legitimate.
I have mentioned the product I use before, which is Sunbelt Software's I Hate Spam. This uses a scoring process, where emails over a certain score are immediately deleted and others which fall in to "not sure" are quarantined in a separate folder. This allows the user to review the messages, delete what is spam and whitelist what isn't spam. Both the user and the administrator have control over the process, and as such most of the users that I have introduced it to love the product.
For your existing product, you could use a rule in Outlook to delete any messages that have been treated in that way...
Simon.
|
|
|
|
|