Best practices for deploying Symantec Messaging Gateway (SMG) appliances.
Symantec recommends multiple SMG hosts are placed in the same physical location.
If Messaging Gateway hosts must be deployed in different remote locations and communication issues occur between hosts (i.e. outdated statistics, timeouts, host status not available on the GUI, etc), Symantec recommends that you have one Messaging Gateway Control Center at each location.
DNS records for each host
Each hostname must have proper A and PTR record in your DNS. To ensure you have proper entries, use nslookup.
The following commands must return the same results for each host that you query.
Note: This command asks if you have an A record against the hostname mx.domain.com.
Sender ID is DNS-based, and helps maintain your sender reputation. See Sender ID on Microsoft.com.
Note: Symantec also supports this technology with Messaging Gateway, accessible by clicking Spam > Settings, and then clicking the Sender Authentication tab. Here we perform the same check against other external domains.
Enable outbound spam scanning on Messaging Gateway
By default, Messaging Gateway will not enable antispam scanning for outbound traffic. However, there are cases where this may help mitigate threats coming from your internal environment to the Internet that were previously unknown.
To enable outbound spam scanning
Log in to the SMG Control Center.
Click Administration > Users > Policy Groups.
In the right pane, click Default.
Click the Spam tab.
Check Enable outbound email spam scanning for this group.
In the drop-down menu, select the appropriate policies for Spam and Suspected Spam.
Note: You can customize these policies later under the Spam tab.