When you configure VPIM Networking, you can define the following message delivery options:
To allow the local messaging server to send and receive VPIM messages, enable both outgoing and incoming VPIM messages. The Incoming and Outgoing SMTP/VPIM options are enabled by default, and are cleared only under exceptional circumstances.
You can send outgoing messages directly to the destination
system, or route messages using an e-mail server or proxy server. In most
cases, messages sent to external sites over the Internet are routed through
a mail server or a proxy server. Messages sent to internal sites over
an intranet are not routed in this way.

The open VPIM compose prefix is a number that identifies
a message that is to be delivered to an open site using the VPIM protocol.
When users address a message to an open VPIM site, they enter the compose
prefix before entering the address. Define
the open VPIM compose prefix if any local users want to exchange VPIM
messages with open sites.

Create open VPIM shortcuts to simplify addressing for users who want to send messages to VPIM-compliant sites that are not defined in your network database (open sites).
You can define up to 500 open VPIM shortcuts.
For each shortcut, you must specify both the domain name of the open VPIM-compliant
site, as well as the number you want phoneset users to use when addressing
VPIM messages.

CallPilot uses Simple Mail Transport Protocol (SMTP) to send
VPIM Networking messages between the local CallPilot server and remote CallPilot servers
VPIM Networking messages between the local CallPilot server and remote messaging servers that are VPIM-compliant
CallPilot messages from desktop messaging and My CallPilot clients to the CallPilot server
CallPilot authenticates SMTP connections to prevent denial of service, junk e-mail, and toll fraud. SMTP authentication is performed between
desktop messaging and My CallPilot clients and CallPilot server
the local CallPilot server and voice messaging servers that have been defined as remote sites in the CallPilot network database
For more information, see SMTP security.
Nortel
Networks recommends that you define access restrictions
for unauthenticated users to prevent toll fraud by desktop messaging and My CallPilot users
for unauthenticated servers to prevent denial-of-service attacks and junk e-mail proliferation
For more information, see Setting unauthenticated access restrictions.
CallPilot uses Secure Socket Layer (SSL) encryption to encrypt message transmissions between CallPilot and
desktop and My CallPilot clients
another messaging server
When SSL is used to encrypt message traffic between messaging servers, users are provided with privacy over the network.
Encryption is optional. However, Nortel Networks strongly recommends that you establish a secure (encrypted) session if the User ID and Password authentication method is used. Transmission of the user ID and password in the clear is strongly discouraged.
For more information, see Encryption.