Additions for Exchange Server 2007 - Part 3: Email client access protection
Part 1: Introduction steps
Part 2: Default protection
Marc Grote
Before you get started, note that this article is based on the beta version of Windows Server 2008 and Exchange Server 2007 SP1, so some of the features may be altered or removed in versions final of the product.
This article will introduce a high-level overview of the security issues of different client email types such as POP3, IMAP4, OWA and Outlook Anywhere (also known as RPC over HTTP (S).
POP3
POP3 (Post Office Protocol version 3) is a relatively old protocol that takes email from a mail server like Exchange Server. Previously, with Exchange Server 2003, Exchange supported POP3, but this protocol was disabled by default. This is similar to Exchange Server 2007, so you must change the startup type of this protocol to Automatic. One of the important changes in Exchange Server 2007 POP3 access is that it is not encrypted sessions. Exchange Server 2007 uses a certificate that assigns the same type to protect the transmission of messages. Because of this, you must configure the email client to access Exchange Server on a secure connection. You should also remove this certificate after installing Exchange with a trusted certificate from a CA certificate authentication center or with a certificate from the trusted third-party CA. To configure POP3 access, you must use the Exchange Management Shell (EMS). Starting with Exchange Server 2007 SP1, POP3 management components will be in the Exchange Management Console (EMC).
IMAP4
IMAP4 (Internet Message Access Protocol version 4) is also a relatively old protocol. IMAP4 compared to POP3 has some more advanced.
Starting with Exchange Server 2003, Exchange supports IMAP4 but this protocol is disabled by default. This is also done in Exchange Server 2007, so you must change the startup type of this protocol to Automatic. One of the important changes in Exchange Server 2007's IMAP4 access is that it is not encrypted sessions. Exchange Server 2007 uses the same assigned certificate to protect mail transmission. Therefore, you must configure the email client to access Exchange Server on a secure connection.
Ports used by POP3 and IMAP4
Default gateway protocol IMAP4 / SSL 993 (TCP) IMAP4 with or without TLS143 (TCP) POP3 / SSL995 (TCP) POP3 with or without TLS 110 (TCP)
Table 1
OWA
Outlook Web Access (OWA) is protected by default. Like any Exchange client service, Outlook Web Access is protected by an equally assigned certificate and HTTPS access is enabled by default. However, for an Administrator account, it is recommended to use its own certificate for accessing OWA from a trusted internal Certificate Authority (CA) or from a trusted third-party CA. Exchange Server 2007 Outlook Web Access has some additional security settings. Some of these security settings are part of the additional Outlook Web Access security package introduced in Exchange Server 2003. Most of this tool's settings (and some additional settings) are available. provided by default in Exchange Server 2007. Exchange Server 2007 also has some security features:
- Split the Outlook Web Access segment
- Full and partial client version
- Restrict access to Outlook Web Access for certain users
- Customize Microsoft Office Sharepoint integration
- Control Direct Access for file server sharing issues.
- Lock access to certain file types.
Outlook Anywhere
Outlook Anywhere, formerly known as RPC on HTTPS in Exchange Server 2003, this feature provides the most complete access to Outlook 2007 on HTTPS from outside of the network. Since securing Outlook Anywhere is similar to OWA, we won't introduce more details about this feature.
Exchange Active Sync (EAS)
Exchange Active Sync allows access to email and other issues for mobile devices such as Smartphones, PDAs (Personal Digital Assistants) and mobile phones. EAS is enabled by default and it is possible to configure its settings using Exchange Active Sync policies. With the help of these policies, you can make the following settings:
- Password required for mobile devices
- Request a password that has both a letter and a number
- Allow or disallow download of attachments
- Allow access to Windows Sharepoint services documents
- Allows deleting lost or stolen devices
- Activate device encryption issue
ISA Server 2006
You can use ISA Server 2006 (Internet Security and Acceleration Server) to provide an additional layer of security for Exchange Server 2007 access issues using Outlook Web Access (OWA), Outlook Anywhere and Exchange Active Sync (EAS ). With the help of ISA Server 2006 you can safely publish all these Exchange Server clients. ISA Server 2006 allows additional security in HTTPS types to HTTP Bridging, Link Inspection, Content filtering, user authentication .
Patch management
You need to update the Messaging client issues and the operating system it is running regularly. You should use WSUS (Windows Server Updates Services) or some patch management software to help with this task.
Anti-SPAM
Exchange Server 2007 can integrate anti-spam features for the Hub Transport Server role and the Edge Transport Server role. You must enable anti-spam features on the Hub Transport Server through the Exchange Management Shell (EMS).
Exchange Server 2007 provides the following anti-spam features:
- The combination of Outllook's Junk mail filter lists
- IP Reputation service
- Sender information
- Sender ID
- Filter mail through the email address sent
- Prevent spam
- Filter mail by content
- SMTP Tarpitting
You can use Forefront Edge Security to provide some additional anti-spam features.
Antivirus
You should use a client-side antivirus scanner that scans access files on demand like Forefront Client Security. On the server, you should use a central antivirus solution like Microsoft Forefront Edge Security that we mentioned in the second part of this series.
Conclude
In the third part of this series, I have shown you how to secure client access via POP3, IMAP4, OWA, and Outlook Anywhere. Readers should note that this article does not focus on all the new security enhancements and security features in Exchange Server 2007 that we will introduce in another article.
You should read it
- Security features of OWA (Part 2)
- Execute Outlook Voice Access with Exchange Server 2007 (Part 2)
- Transfer Exchange 2003 to Exchange 2007 (Part 2)
- Tips or troubleshooting connection problems on Outlook
- Execute Outlook Voice Access with Exchange Server 2007 (Part 1)
- Transfer Exchange 2003 to Exchange 2007 (Part 3)
- New Outlook Web Access features in Exchange 2007 SP1
- Configure Web Services URL of Exchange Server 2007
May be interested
- Load balancing in Exchange 2007 - Part 2: Configure Windows NLB Clustersin this article, i will show you the first part of how to balance the exchange 2007 client access servers with nlb load balancing techniques.
- Introduction to Network Access Protection (Part 7)in part 6, i showed you how to set up a vpn connection on a windows vista client. this part 7 will continue the discussion of how to complete the client configuration process.
- Transfer from Linux Mail Server to Exchange Server 2007 (Part 1)in exchange server 2003, we can use the exchange migration wizard to switch from an imap4 running environment to active directory and exchange server 2003. in this article, however, i don't want to talk about exchange server 2003 but instead. gi
- Discover EMC in Exchange Server 2010 (Part 2)in the previous article, we learned some new features in exchange server 2010, including: high availability, archiving, federation and sharing.
- Access and use shared email addresses - Part 2continue to introduce two ways to set up and access shared email addresses, in this section we will focus on sharing mailboxes (shared mailbox).
- Transfer from Linux Mail Server to Exchange Server 2007 (Part 4)linux users can use web access to access their notifications and have no domain information to complement during webmail access. to avoid questions in owa, we need to change some default behavior and configuration so that we only accept user names and passwords as they are being used.
- Switch from Exchange 2000/2003 to Exchange Server 2007 (part 1)how is the conversion from exchange server 2000 or exchange server 2003 to exchange server 2007 done? you will have to move data from every available exchange server in the exchange organization to the new exchange 2007 servers after having them shut down.
- Share Hosting with Exchange 2007 (Part 1)the topic of hosting sharing with exchange server is not a new issue. it is of your interest to help many companies with simple, winning exchange configurations or start small email configurations for themselves, with exchange server fully capable of
- Managing Resource Mailboxes in Exchange Server 2007 (Part 2)in the previous part of this series, we learned how to create a resource mailbox and how to enable it so that a user can access it through the add-mailboxpermission cmdlet. at that time, we still couldn't do this through the exchange management console, but today with exchange server 2007 service pack 1
- Using POP3 and IMAP4 to access Exchange 2007 (Part 1)pop3 (post office protocol 3) and imap4 (internet message access protocol 4) are protocols that allow mail access from a remote control server. both of these protocols are also widely used outside the business to serve access and mail.