Using Logical Service Names

Design your deployment around the use of logical names for Communications Suite servers.
You should use logical names even on a single-system deployment, to position
it for ease of future growth and expansion. Using logical names does not impose
any additional deployment setup costs other than populating your DNS.

You can think of these logical names as falling into two categories:
those that affect end users, such as settings in email client programs; and
those affecting back-end administration, such as inbound SMTP servers.

The following tables describes these logical entities.

Table 5–1 User Facing Logical Names

Example

Description

mail.siroe.com

Name of the server from which end users collect their email.

imap.siroe.com

Name of the IMAP server from which end users collect their email.

pop.siroe.com

Name of the POP server from which the end users collect their email.

smtp.siroe.com

Name of the SMTP server users set as outgoing mail server.

webcal.siroe.com or ce.siroe.com

Name of the Communications Express (formerly Calendar Express) server.

Table 5–2 Maintenance Level Logical Names

Example

Description

relay-in.siroe.com

Corresponds to a bank of inbound SMTP servers.

relay-out.siroe.com

Corresponds to a bank of outbound SMTP servers.

mmp.siroe.com

Corresponds to a bank of MMP servers.

storeAA.siroe.com

Back-end message store. Select a naming scheme to work with your topology,
for example, storeAA.siroe.com through storeZZ.siroe.com.

calstoreAA.siroe.com

Back-end calendar store. Select naming scheme to work with topology,
for example, calstoreAA.siroe.com through calstoreZZ.siroe.com.