&RQWHQWV##
2YHUYLHZ#4#
6XSSRUWHG#,QWHUQHW#3URWRFROV#5#
&UHDWLQJ#0XOWLSOH#9LUWXDO#6HUYHUV#6#
6LPSOH#0DLO#7UDQVIHU#3URWRFRO#8#
3RVW#2IILFH#3URWRFRO#62,QWHUQHW#0DLO##
$FFHVV#3URWRFRO#7# 46#
+\SHUWH[W#7UDQVIHU#3URWRFRO# 47#
1HWZRUN#1HZV#7UDQVIHU#3URWRFRO# 4:#
6FDOLQJ#WKH#3URWRFRO#6HUYHUV# 59#
/DE#$=#&UHDWLQJ#9LUWXDO#6HUYHUV# 64#
5HYLHZ# 6;#
#
Module 8: Managing
Virtual Servers and
Protocols in
Exchange 2000 Information in this document is subject to change without notice. The names of companies,
products, people, characters, and/or data mentioned herein are fictitious and are in no way intended
to represent any real individual, company, product, or event, unless otherwise noted. Complying
with all applicable copyright laws is the responsibility of the user. No part of this document may
be reproduced or transmitted in any form or by any means, electronic or mechanical, for any
purpose, without the express written permission of Microsoft Corporation. If, however, your only
means of access is electronic, permission to print one copy is hereby granted.


Graphic Artist:
Kimberly Jackson, Andrea Heuston (Artitudes Layout and Design)
Editing Manager:
Lynette Skinner
Editor:
Elizabeth Reese (Write Stuff)
Copy Editor:
Ed Casper (S&T Consulting), Carolyn Emory (S&T Consulting), Patricia Neff
(S&T Consulting), Noelle Robertson (S&T Consulting)
Online Program Manager:
Debbi Conger
Online Publications Manager:
Arlo Emerson (Aquent Partners)
Online Support:
Eric Brandt
Multimedia Developer
: Kelly Renner (Entex)
Compact Disc Testing:
Data Dimensions, Inc.
Production Support:
Ed Casper (S&T Consulting)
Manufacturing Manager:
Bo Galford
Manufacturing Support:
Rick Terek
Lead Product Manager, Development Services:

Lead Product Manager:
David Bramble
Group Product Manager:

Complete the lab.

3UHVHQWDWLRQ=##
78#0LQXWHV#
#
/DE=#
63#0LQXWHV#
LY##0RGXOH#;=#0DQDJLQJ#9LUWXDO#6HUYHUV#DQG#3URWRFROV#LQ#([FKDQJH#5333#
0RGXOH#6WUDWHJ\#
Use the following strategy to present this module:
„#
Supported Internet Protocols
This section lists the Internet protocols that Exchange 2000 supports and
also provides a brief discussion of how to administer them.
Students should already possess base knowledge about each of these
protocols.
„#
Creating Virtual Servers
This section discusses the benefits of creating virtual servers, covers how to
identify multiple virtual servers, and concludes by outlining typical
scenarios in which creating multiple virtual servers would be beneficial.
Consider asking students to share “real-life” examples from their work
environments in which they think creating multiple virtual servers would be
beneficial.
„#
Simple Mail Transfer Protocol
This section focuses on how to configure an SMTP server, how to manage


# 0RGXOH#;=#0DQDJLQJ#9LUWXDO#6HUYHUV#DQG#3URWRFROV#LQ#([FKDQJH#5333# # 4#2YHUYLHZ#
„
6XSSRUWHG#,QWHUQHW#3URWRFROV
„
&UHDWLQJ#0XOWLSOH#9LUWXDO#6HUYHUV
„
6LPSOH#0DLO#7UDQVIHU#3URWRFRO
„
3RVW#2IILFH#3URWRFRO#6#2#,QWHUQHW#0DLO#$FFHVV#3URWRFRO#7
„
+\SHUWH[W#7UDQVIHU#3URWRFRO
„
1HWZRUN#1HZV#7UDQVIHU#3URWRFRO
„
6FDOLQJ#WKH#3URWRFRO#6HUYHUVVirtual servers help to reduce your company’s hardware costs and scale your
system to accommodate more users by enabling you to place more than one
mail server on a single computer. You can create, configure, and manage virtual
servers and connect to them using the Internet protocols which Exchange 2000
supports.
At the end of this module, you will be able to:
„#
List the Internet protocols that Microsoft
®

&RQVROH :LQGRZV +HOS
$
FWLRQ 9LHZ )DYRULWHV
7UHH
)DYRULWHV
1RUWKZLQG#7UDGHUV#+([FKDQJH,
*OREDO#6HWWLQJV
5HFLSLHQWV
$GPLQLVWUDWLYH#*URXS
)LUVW#$GPLQLVWUDWLYH#*URXS
6HUYHUV
%5,6%$1'#± 489<$
'(19(5#± 489<$
/,6%21#± 489<$
/21'21#± 489<$
3URWRFROV
+773
,0$37
1173
3236
6073
,5&;
593
0LFURVRIW#07$
,QIRUPDWLRQ#6WRUH
3(57+#± 489<$
9$1&289(5#± 489<$
3ROLFLHV
5RXWLQJ#*URXSV
&KDW#&RPPXQLFDWLRQV

then applies it to IIS on the appropriate server running Exchange 2000.
6OLGH#2EMHFWLYH#
7R#OLVW#WKH#,QWHUQHW#SURWRFROV#
WKDW#([FKDQJH#5333#
VXSSRUWV1#
/HDG0LQ#
([FKDQJH#5333#VXSSRUWV#
PXOWLSOH#SURWRFRO#VHUYHUV1#
1RWH#
# 0RGXOH#;=#0DQDJLQJ#9LUWXDO#6HUYHUV#DQG#3URWRFROV#LQ#([FKDQJH#5333# # 6#
&UHDWLQJ#0XOWLSOH#9LUWXDO#6HUYHUV#
Exchange 2000
Server
Exchange 2000
Server
Clients
Clients
Application
Application
Application
Virtual
Server A
Virtual
Server A
Virtual
Server B
Virtual

7R#VKRZ#DQ#HQYLURQPHQW#LQ#
ZKLFK#\RX#PLJKW#XVH#
PXOWLSOH#YLUWXDO#VHUYHUV1#
/HDG0LQ#
&UHDWLQJ#PXOWLSOH#YLUWXDO#
VHUYHUV#HQDEOHV#\RX#WR#
VXSSRUW#XVHUV#ZLWK#GLIIHUHQW#
FRQILJXUDWLRQ#QHHGV1#
1RWH#
7# # 0RGXOH#;=#0DQDJLQJ#9LUWXDO#6HUYHUV#DQG#3URWRFROV#LQ#([FKDQJH#5333#7\SLFDO#6FHQDULRV#IRU#&UHDWLQJ#0XOWLSOH#9LUWXDO#6HUYHUV#
Consider creating multiple virtual servers for the following reasons:
„#
You want to configure each virtual server to use different authentication
mechanisms.
For example, external users sending messages over the Internet may have all
messages encrypted with Transport Layer Security for additional security,
while users on an internal intranet do not use Transport Layer Security
encryption and do not need to incur the additional cost.
„#
You want to optimize trusted applications.
For example, applications that use Collaboration Data Objects (CDO) to
send SMTP messages can use an SMTP virtual server that is not restricted
by reverse Domain Name System (DNS) lookup or recipient limits.
„#
You want to configure each server on different purposes.
For example, you can connect one virtual server to the Internet, enabling all
users to send and receive messages over the Internet, and configure another

7R#RXWOLQH#6073#WRSLFV1#
/HDG0LQ#
6073#LV#WKH#SULPDU\#
SURWRFRO#IRU#FRPPXQLFDWLQJ#
ZLWK#RWKHU#FRPSXWHUV#
UXQQLQJ#([FKDQJH#53331#
9# # 0RGXOH#;=#0DQDJLQJ#9LUWXDO#6HUYHUV#DQG#3URWRFROV#LQ#([FKDQJH#5333#
6073#6HUYHU#&RQILJXUDWLRQ#
Default SMTP Virtual Sever Properties
General
Access
Messages
Delivery
Default SMTP Virtual Server
IP
address
(All Unassigned)
Limit number of connections to:
Connection time-o
ut (minutes): 10
E
nable logging
Act
ive log format:
Act
ive log format:
W3C Extended Log File Format

those provided by other IIS services. Because many of the properties
available in the IIS log formats do not apply to SMTP, you can customize
the list of properties logged to optimize the logging process.
„#
Connections
By default, the server accepts an unlimited number of SMTP connections.
However, an unlimited number of SMTP connections can use an excessive
amount of resources, which will negatively affect other services, such as the
information store, and could result in a denial of service. You can control
SMTP traffic by configuring a maximum number of concurrent connections
and the time-out for each connection.

6OLGH#2EMHFWLYH#
7R#RXWOLQH#WKH#WDEV#XVHG#WR#
FRQILJXUH#WKH#6073#VHUYHU1#
/HDG0LQ#
8VH#WKH#([FKDQJH#6\VWHP#
0DQDJHU#WR#FRQILJXUH#WKH#
6073#VHUYHU1#
# 0RGXOH#;=#0DQDJLQJ#9LUWXDO#6HUYHUV#DQG#3URWRFROV#LQ#([FKDQJH#5333# # :#$FFHVV#7DE#
If you require a stringent policy for SMTP message transfer, you can use the
Access tab to configure security to the SMTP port, which does the following:
„#
Requires authentication before a message transfer session can be
established.
„#
Associates a certificate with the SMTP server and creates a secure channel.

megabytes (MB) is too restrictive, you can raise the limit, thereby increasing
functionality for the user, but potentially decreasing server performance.
When the system exceeds the number of messages per connection, Exchange
opens an additional connection and sends any remaining messages
simultaneously. While this can improve outbound performance, it must be
balanced with other resource limitations, such as limited network bandwidth.
When there are more recipients in the header of a message than the relative
number configured on the server, Exchange generates multiple messages. For
example, if a message is addressed to 150 recipients, the routing engine will
transfer two messages of the same content, one for the first 100 recipients and
another for the final 50.

If the number of recipients exceeds the limit specified in the global
SMTP settings, the message is not processed.

1RWH#
;# # 0RGXOH#;=#0DQDJLQJ#9LUWXDO#6HUYHUV#DQG#3URWRFROV#LQ#([FKDQJH#5333#)DLOHG#0HVVDJHV#
When the destination for an e-mail address cannot be determined, you can
forward the message to another host for redelivery. If a message is not delivered
successfully, a non-delivery report (NDR) is automatically sent to the sender. If
the NDR is not delivered successfully, a copy of the message is stored in the
Badmail directory.
Exchange 2000 attempts to redeliver failed messages three times, at one minute
intervals, before switching to fifteen minute intervals.
'HOLYHU\#7DE#
The SMTP server will attempt to deliver messages after it determines both the
destination and destination address. When there is a problem with the next-hop

Modifying the sender address in outgoing messages to use a specific domain
called a masquerade domain.
„#
Sending all outgoing SMTP messages to a smart host for delivery. This
offloads message delivery mechanics to the smart host computer; however,
delivery issues are not resolved as quickly because your server is not aware
of delivery problems.
„#
Configuring the SMTP server to perform a reverse DNS lookup for the
sender of the message. If the submitting SMTP client does not belong to the
Domain Name System (DNS) domain of the matching SMTP domain name
specified in the Mail from field, the virtual server rejects the message.
Unfortunately, reverse lookups severely impact the performance of message
transfer and should be tested in the lab before going into production to make
sure the virtual server can handle the necessary messaging traffic with
reverse DNS lookup enabled.

Reverse DNS lookups only provide a partial solution to preventing
junk mail. If you need to verify a message sender’s identity, digital
certificates should be used instead. 1RWH#
43# # 0RGXOH#;=#0DQDJLQJ#9LUWXDO#6HUYHUV#DQG#3URWRFROV#LQ#([FKDQJH#5333#0DQDJLQJ#6073#6HUYHU#6WDWXV#
„
&RQILJXULQJ#'RPDLQV
z

RCPT TO: <USER> would be USER@LOCALDOMAIN
„#
Local (Alias)
Any mail addressed with an alias will be processed by the local computer:
RCPT TO: <USER@ALIASDOM> would be USER@LOCALDOMAIN
„#
Local (Normal/blank)
This is the domain for which Exchange 2000 accepts inbound mail if it is set
up not to relay mail. Normally it would reject the address. If you support users with different domains from the default domain or
users with multiple domains you want to match, you can configure SMTP to
accept them.

6OLGH#2EMHFWLYH#
7R#RXWOLQH#WKH#6073#
GRPDLQV#\RX#FDQ#FRQILJXUH#
DQG#WKH#TXHXHV#\RX#FDQ#
PDQDJH1#
/HDG0LQ#
0DQDJLQJ#6073#VHUYHU#
VWDWXV#UHTXLUHV#FRQILJXULQJ#
WKH#GRPDLQV#WKDW#WKH#VHUYHU#
XVHV#DQG#PDQDJLQJ#
PHVVDJHV#WKDW#DUH#TXHXHG#
IRU#GHOLYHU\1#
1RWH#
# 0RGXOH#;=#0DQDJLQJ#9LUWXDO#6HUYHUV#DQG#3URWRFROV#LQ#([FKDQJH#5333# # 44#


(TURN/ETRN).
Frozen No messages will flow out of the link;
message can be inserted if the Categorizer
is running. 45# # 0RGXOH#;=#0DQDJLQJ#9LUWXDO#6HUYHUV#DQG#3URWRFROV#LQ#([FKDQJH#5333#6073#*OREDO#3DUDPHWHUV#
Inbox
Inbox
InboxExchange 2000 global settings affect all SMTP servers in a company. You can
configure Internet message formats and message delivery parameters.
,QWHUQHW#0HVVDJH#)RUPDWV#
Internet message formats enable you to configure the encoding, format, and
type of messages that you send to a specific domain. The domain can reference
a specific destination, such as microsoft.com, or it can use a wildcard, such as
*.edu to reference a large group of destinations.
0HVVDJH#'HOLYHU\#
Message delivery configuration options include:
„#
Specifying an account to receive messages that are sent to
postmaster@domain.
„#
Specifying default delivery limits for outgoing and incoming message sizes
and the maximum number of recipients for a message.

Server
POP3
Virtual
Server
POP3
Virtual
Server
IMAP4
Virtual
Server
IMAP4POP3 and IMAP4 enable clients, such as Outlook Express, to communicate
with servers. These protocols also enable clients to communicate with virtual
servers as though they were physical servers.
The POP3 and IMAP4 services supported by Exchange 2000 provide the
following new features:
„#
Support for virtual servers. You can now configure servers with separate
names, authentication, and message formatting.
„#
Support for front-end/back-end servers. You can now use a single
namespace with multiple servers. Clients connect to the front-end server,
which looks up the user’s mailbox in the directory, and then proxies the
traffic to the corresponding back-end server. The front-end server also
provides IMAP4 clients access to all public folders, even those folders that
do not exist on your primary public folder server.
„#
IMAP4 support for Request for Comments (RFC 2359). RFC describes how