Exchange Server 2003 is designed to be secure by default and in deployment. Exchange Server 2003 protects your messaging environment as well as your privacy with:
- Distribution lists restricted to authenticated users. You can allow sending only from authenticated users or specify which users can or cannot send mail to specified distribution lists.
- Support of real-time Safe and Block lists. Reduce the amount of unsolicited junk email messages delivered with connection filtering.
- Inbound recipient filtering. Reduce unsolicited junk email messages by filtering inbound messages based on the recipient. Messages that are addressed to users who are not found, or to whom the sender does not have the permissions to send, are rejected. This applies only to messages sent by anonymously authenticated users.
- Kerberos authentication between a front-end and back-end server. To help ensure that credentials are secure, Exchange Server 2003 uses Kerberos delegation when sending user credentials between a front-end server, running services such as Microsoft Office Outlook Web Access or Microsoft Outlook Mobile Access, and a back-end server such as the mailbox store.
- Privacy protection in Outlook and Outlook Web Access. By default, content from outside your network is blocked in Outlook 2003 and Outlook Web Access. This feature helps prevent spammers from identifying valid email addresses through links to external content. You can, however, override this feature to view external content.
- Antispam integration with Outlook 2003 and Outlook Web Access. You can upload the Safe and Block Senders List to Exchange Server 2003 for filtering.
- Microsoft Exchange Intelligent Message Filter. Integrated in Exchange Server 2003 for server-side filtering of unsolicited junk email messages and also in Outlook 2003 for client-side filtering, Exchange Intelligent Message Filter uses Microsoft SmartScreen technology to help reduce cost and boost productivity by unsolicited junk email messages.
- Virus Scanning API 2.5. Non-Microsoft antivirus products can run on servers running Exchange Server 2003 that do not have resident Exchange Server mailboxes and are allowed to delete and send messages to the sender.
- Clustering security. Exchange Server 2003 clustering supports Kerberos authentication against an Exchange Server virtual server. Exchange Server 2003 also supports Internet Protocol security (IPSec) between front-end servers and clustered back-end servers running Exchange Server.
- Administrative permissions. Cross-forest support and the ability to administer both Exchange 2000 Server and Exchange Server 2003 helps organizations that have segmented the administration of their Microsoft Windows–based environment and Exchange Server environment into two unique groups and are concerned about security.
- Restricted relaying. You can restrict relaying to a limited number of security principles through the standard Windows 2000 discretionary access control list (DACL). The ability to grant relaying to an IP address is still present.
- Restricted submissions. You can restrict submissions to a limited number of security principles through the standard Windows 2000 DACL. This feature helps prevent blocked senders from sending to internal-only distribution lists by spoofing, which is the practice of tricking users into providing passwords and other information to allow unauthorized access into a system.
- Public folder permissions for unknown users. Folders with distinguished names in access control lists that cannot be resolved to security identifiers drop the unresolvable distinguished names.
- Public folder store replication. Public folder servers replicate with local servers for updates even if the local servers do not have the full set of replication content that they need. You can use a registry key to identify the first server that is used for backfilling.
- Microsoft Baseline Security Analyzer (MBSA). Download an easy, streamlined method of identifying common security misconfigurations for Microsoft products including Exchange Server and Windows Server 2003.
NOTE: This information was quoted from Microsoft.com. For more information, visit:
https://www.microsoft.com/middleeast/windowsserversystem/exchange/evaluation/features/default.mspx.
eHelp
