CallPilot uses Simple Mail Transport Protocol (SMTP) to send
VPIM Networking messages between remote CallPilot servers and the local CallPilot server
VPIM Networking messages between remote messaging servers that are VPIM-compliant and the local CallPilot server
CallPilot messages from desktop messaging and My CallPilot clients to the CallPilot server
To secure transmissions in your messaging network, you can enable the following:
CallPilot authenticates SMTP connections to prevent denial of service, junk e-mail, and toll fraud. The CallPilot server authenticates message transmission sessions from
desktop messaging and My CallPilot clients
voice messaging servers that have been defined as remote sites in the CallPilot network database
This topic introduces the following:
Go to task list.
SMTP authentication can be configured in one of the following modes on CallPilot:
unauthenticated
mode
Consider
the following for unauthenticated connections:
To prevent denial-of-service attacks and junk e-mail proliferation, Nortel Networks recommends that you define access restrictions for unauthenticated servers.
To prevent toll fraud by desktop messaging and My CallPilot users, Nortel Networks recommends that you define access restrictions for unauthenticated users.
CallPilot supports two methods of authentication:
When
defining the SMTP authentication settings, remember that the settings
also affect the addressing capabilities of desktop messaging or My CallPilot
users who want to compose messages.
SMTP authentication can fail for a variety of reasons. CallPilot cannot
receive messages when authentication fails in authenticated mode only.
If mixed authentication is used on CallPilot, a message transmission can
still occur without authentication. See SMTP
authentication failures for more details.

Optionally, you can use encryption to secure all message traffic. Encryption prevents
password transmission in the clear
eavesdroppers from gaining access to the contents of the message (thereby guaranteeing user privacy)
Encryption is available for CallPilot Networking, desktop messaging,
and My CallPilot. It is enabled and configured independently from SMTP
authentication configuration.

The SMTP authentication and encryption settings are defined in the following areas:
|
Where |
Task | |
|
Local server’s SMTP settings |
Message Delivery Configuration |
Configure
the authentication mode and settings. |
|
Remote server’s SMTP settings |
Message Network Configuration |
|
|
Desktop messaging and My CallPilot clients |
client software Internet Mail Clients |
Ensure that the client software for desktop messaging and My CallPilot supports the SMTP authentication and encryption options that you choose. You must enable the same options that you enable on the server. For client-specific security options, refer to the online Help for the web browser or e-mail client.
|