The method used to perform SMTP authentication on a remote server or desktop messaging or My CallPilot client depends on what is supported by both the sending and receiving systems. If User ID and Password authentication is used, Nortel Networks recommends that you use Secure Socket Layer (SSL) to encrypt the session. SSL encryption prevents password transmission in the clear, and ensures content privacy while the message is in transit.
See Encryption.
Authentication
of remote servers can occur only if the remote server is defined in the
CallPilot network database. Open VPIM sites
cannot be authenticated.

In
CallPilot, the component that implements SMTP is known as the Internet
Mail Agent.
The sending system (remote server or desktop messaging
or My CallPilot user) connects to the CallPilot Internet Mail Agent (SMTP
server) through either the SMTP port or the SSL port.
By
default, 465 is defined as the SSL port that listens for encrypted sessions.
Port 25 listens for unencrypted
sessions.
The
CallPilot SMTP server does not require SSL on incoming transmissions,
but does support it. On outgoing sessions, SSL must be enabled if User
ID and Password authentication is being used.
CallPilot advertises that it supports User ID and Password authentication.
One of the following occurs:
|
IF the sending system |
THEN |
|
supports User ID and Password authentication |
the sending system requests authentication. |
|
does not support User ID and Password authentication |
authentication fails. See SMTP authentication failures. |
CallPilot requests the user ID.
The sending system responds with the user ID:
For a desktop messaging or My CallPilot client, the user ID is the user’s public switch telephone network (PSTN) number (SMTP/VPIM shortcut and mailbox number)
For a remote messaging server, the user ID is the remote server’s fully qualified domain name (FQDN).
CallPilot requests the password.
The sending system responds with the password.
CallPilot verifies the User ID and Password.
For a desktop messaging or My CallPilot client, the mailbox and user password are obtained from the user database.
For a remote messaging server, the remote server’s FQDN and SMTP/VPIM password are obtained from the network database.
|
IF the user ID and password |
THEN |
|
match |
the sending system is authenticated and message transmission continues. |
|
do not match |
authentication fails. See SMTP authentication failures. |