18 Planning your deployment
General deployment considerations
Positioning with other filtering products
In order for Symantec Mail Security for SMTP’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 for SMTP 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 compatibility
Symantec Mail Security for SMTP supports LDAP for Spam Quarantine
authentication and synchronization.
The system’s LDAP SyncService feature synchronizes user, alias, and group data
from your company’s LDAP accessible directories with its own database.
SyncService lets Symantec Mail Security for SMTP re-normalize and index the
data to fit the needs of Scanner, Control Center, and Spam Quarantine while
minimizing impact on your directory infrastructure.
LDAP SyncService supports the following LDAP servers:
■
Windows 2000 Active Directory
■
Windows 2003 Active Directory
■
Sun Directory Server 5.2, Patch 4 (formerly known as the iPlanet
Directory Server) on Solaris 8 and 9, and Red Hat Linux
■
SunOne LDAP Server 5.2 , Patch 4
■
Lotus Domino LDAP Server 6.5
■
Exchange 5.5
■
other (used for authentication only)
Note:
Only one LDAP source may be used for authentication. While the same
source may also be used for synchronization purposes, no other LDAP
directories may be used for authentication. This is especially important with
regard to Spam Quarantine. If email is being sent to Spam Quarantine where end
users will then process their quarantined messages, then all end users must
exist in the LDAP source used for authentication.
