Exxhange SQL And IIS- P66 pot

Managing POP3/IMAP4Like its predecessors, Exchange Server 2007 also supports the Post Offi ce Protocol version 3 POP3 and Internet Message Access Protocol version 4 IMAP4 clients; howeve

Chapter 5 • Managing the Client Access Server

Managing POP3/IMAP4

Like its predecessors, Exchange Server 2007 also supports the Post Offi ce Protocol version 3 (POP3) and Internet Message Access Protocol version 4 (IMAP4) clients; however, since these client protocols aren’t that popular anymore (especially now that we have Outlook Anywhere, a superb Web mail

client and EAS), the POP3 and IMAP4 protocols are disabled by default

Both the POP3 and IMAP4 protocols have been rewritten from the ground up in managed

code, and are no longer dependent on the IIS component Instead, they run as a separate

Windows Service

Because the Exchange Product group focused on rewriting the POP3 and IMAP4 protocols

in managed code, and because of the general time pressure that lay over their heads during the

development of the Exchange Server 2007 product, they unfortunately didn’t have time to build

a GUI to administer these protocols This means that you cannot use the Exchange Management

Console to confi gure or manage the POP3 and IMAP4 protocols Instead, this must be done using

the respective cmdlets in the Exchange Management Shell

TIP

To remove a mobile device partnership or remote wipe a mobile device using the

Exchange Management Shell, you must use the Remove-ActiveSyncDevice and

ClearActiveSyncDevice cmdlets, respectively For further details on how to do this,

type Get-Help Remove-ActiveSyncDevice and/or Get-Help ClearActiveSyncDevice in

the Exchange Management Shell

NOTE

If the Exchange Product group receives suffi cient feedback from customers requiring

a GUI for managing the POP3 and IMAP4 protocols, we can expect one to be

included in Exchange Server 2007 Service Pack 1

Other things worth noting about the POP3 and IMAP4 services in Exchange Server 2007 is that we are limited to only one POP3 or IMAP4 service per server, and the same SSL certifi cate

must be used for all POP3 and IMAP4 connections to the respective Client Access Server In

addition, Public Folder access through an IMAP4 client is no longer supported Also, bear in mind that IPSec isn’t supported when you have an ISA Server deployed between clients and the

Exchange server

Okay, enough focus on what’s missing with the POP3 and IMAP4 protocols After all, there are

a few new improvements Support for TLS encryptions has been added, Kerberos authentication is now supported, and, fi nally, the search feature for both POP3 and IMAP4 clients has been heavily improved

Enabling the POP3 and IMAP4 Services

As mentioned earlier, both the POP3 and IMAP4 services are disabled by default If you decide

to use one or both of these services, the fi rst thing you must do is enable them and set them

to an Automatic service startup type using the Services MMC snap-in You can do this by

clicking Start | Run and typing Services.msc, which brings up the Services snap-in

(shown in Figure 5.54)

Figure 5.54 Starting the POP3 and IMAP4 Services in the Services Snap-in

Then drill down and open the property page for Microsoft Exchange POP3, as shown in Figure 5.55 Select Automatic in the Startup type drop-down menu, and then click Start.

Repeat these steps for the Microsoft Exchange IMAP4 service, if needed.

Figure 5.55 Setting the Service to Automatic Startup

NOTE

You can also enable the POP3 and IMAP4 services using the Set-Service and

Start-Service cmdlets in the Exchange Management Shell To set the services

to start automatically, use the Set-Service MSExchangePOP3 and Set-Service

MSExchangeIMAP4 cmdlet options, respectively Next, you can start the services by

typing Start-Service MSExchangePOP3 and Start-Service MSExchangeIMAP4.

When you have enabled the POP3 or IMAP4 service, you can verify functionality by making a telnet call to the Client Access Server on port 110 or 143, respectively To do so, open a Command Prompt window and type: Telnet <server> 110 or Telnet <server> 143, and press Enter You will then get the POP3 or IMAP4 banner, as shown in Figure 5.56

Figure 5.56 Verifying the Service Is Running

Confi guring the POP3 or IMAP4 Services

In order to confi gure more specifi c settings for the POP3 or IMAP4 services, you must use the

Set-PopSettings and Set-ImapSettings cmdlets We won’t dive further into the parameters available with

these commands, but instead will briefl y mention that you can confi gure features such as maximum

connections, connection timeouts, banner to displayed, login method, and so on.

To see a full list of each parameter available, as well as their descriptions, type either Get-Help Set-PopSettings or Get-Help Set-ImapSettings, depending on which service you want to confi gure further

Limiting Access to the POP3 and IMAP4 Service

When the POP3 and IMAP4 services have been started, all mailbox-enabled users can access their mailbox using one of these two services Since there might be situations where you want to lock down access to these two services to a specifi c set of users (for example, in a shared hosting

environment), I thought it would be a good idea to show you how to set access these services

on a per-user basis

To enable or disable access to POP3, use the following cmdlets:

Set-CASMailbox <user mailbox> -ImapEnabled $true

Set-CASMailbox <user mailbox> -ImapEnabled $false

To enable or disable access to IMAP4, use the following cmdlets:

Set-CASMailbox <user mailbox> -PopEnabled $true