Spam definitions not updating symantec brightmail gateway

Spam definitions not updating symantec brightmail gateway

On a virtual machine, we can move it to more powerful hardware and networks with bigger pipes just by hosting the VM on a different machine or upgrading the current hardware.This is the wave of the future for appliances and I was amazed that I had not thought of it before.This is very useful in managing the health of the appliances, With logging enabled, administrators have complete access to the Message Audit Logs.These are the same types of logs used in Exchange Server for tracking E-mail.To do that, we took all of the quarantines and forwarded them to another Exchange server through the 8300.We also took user mailboxes and sent them through the same process.The product can be installed as a single instance with a scanner (MTA) and a Control Center (management console) or separate virtual machines.

Management of the product is very simple and intuitive.But most of all, the guys at Symantec did something that is absolutely brilliant — a version of the product is sold as a virtual machine running under VMware ESX 3.5.No more worrying about scalability and buying outdated hardware and support contracts and then having to upgrade as the enterprise grows.Evaluation We installed the evaluation version of the product and had it up and running within a few minutes.Since we already had GFI Mail Essentials and Mail Security running in production, we decided to run the same mail through the 8300.

spam definitions not updating symantec brightmail gateway-78spam definitions not updating symantec brightmail gateway-78spam definitions not updating symantec brightmail gateway-84

This allowed us to see if: We ran these tests for about a month and our tests showed that the 8300 was far superior to the two GFI products in every way.

Join our conversation (24 Comments).
Click Here To Leave Your Comment Spam definitions not updating symantec brightmail gateway.

Comments:

Leave a Reply

Your email address will not be published. Required fields are marked *