TABLE OF CONTENTS Now that we have secured most of the components of your Exchange 2003 Messaging environment, this chapter will explore securing the communication between your servers and clients by using encryption. Not every organization s security policy demands that all communication is encrypted, but you should get acquainted with its implementation. We will also take a closer look at the new Remote Procedure Calls over Hyper Text Transfer Protocol (RPC over HTTP) feature introduced in Exchange 2003.
In this chapter, we explore the following topics:
Encrypting SMTP traffic
Encrypting POP3 and IMAP4 traffic
Securing clients using S/MIME
Configuring and securing RPC over HTTP(S)
By the time you reach the end of this chapter you will know how to secure SMTP and POP3/IMAP4 traffic by enabling encryption. In addition, you will be shown where you configure the S/MIME settings in an Outlook 2003 client. To finish the chapter, we give step-by-step instructions on how to use the new, exciting Remote Procedure Calls over Hypertext Transfer Protocol (RPC over HTTP) Exchange 2003 feature.
If you re really serious about protecting e-mail traffic in your Exchange messaging environment, you might want to enable Transport Layer Security/Secure Socket Layer (TLS/SSL) on your Exchange 2003 SMTP virtual server(s) in your organization. This feature can encrypt the SMTP traffic between the clients and the server. If you are concerned about SMTP traffic being intercepted on the network, we recommend using IPSec between Exchange servers. IPSec can be used to encrypt not only the...
