Positioning with other filtering products
In order for Symantec Mail Security's spam and Content Compliance filters to
function properly, you should avoid placing the product behind other filtering
products (such as content filters) or MTAs that alter or remove pre-existing
message headers or modify the message body.
Filtering internal deliveries
You can force internal mail through Symantec Mail Security to avoid propagation
of viruses and spam generated by email mass-mailing worms that may have been
picked up by individuals via Web browsing or downloading.
LDAP services
LDAP (Lightweight Directory Access Protocol) is a directory name service that
allows organizations to structure email directory data according to the
organization's own structure, whether by location, business unit, department, or
other criteria. Organizations with multiple internal mail hosts rely on centralized
LDAP servers to synchronize changes made to email directories across the
organization. Symantec Mail Security supports LDAP services to authenticate
user access to Spam Quarantine and to synchronize email directory information
stored in the Control Center with LDAP directories. These services synchronize
LDAP user, alias, and group directory data with the Control Center's own directory
data stores for subsequent replication to attached and enabled Scanners. They
convert the data to formats compatible with Spam Quarantine, Scanner, and
Control Center data stores while minimizing impact on directory infrastructure.
If your organization uses an LDAP server, Symantec Mail Security must be
configured so that it can access LDAP directories and update the Control Center's
data stores.
The Control Center can use directory information from LDAP servers at your site
for any of the following purposes:
The Control Center can use data from your LDAP server to
determine whether users are allowed access to Quarantine.
The Control Center authenticates users by checking their
user-name and password data directly against the LDAP source.
Authentication
Planning your deployment
General deployment considerations
12