The CallPilot SMTP server monitors port 25 for non-encrypted SMTP sessions. The CallPilot SMTP server also monitors (and connects to) port 465 for encrypted sessions. Encryption is provided by enabling Secure Socket Layer (SSL), which is also known as Transport Layer Security (TLS).
SSL sessions can be established only when SSL is supported at both ends of the connection.
This topic describes the following:
When SSL is enabled, the CallPilot server listens on port 465 for SSL handshake protocol commands. If the remote host sends a request for a connection to this port but does not provide the SSL handshake commands, the session cannot be established.
Similarly, if SSL is required, the CallPilot SMTP server attempts to
connect to the SSL port on a remote messaging server. The default SSL
port is 465.

The following table describes how SSL and the User ID and Password authentication method work together to guarantee user privacy over the network:
|
IF |
THEN |
|
SSL is enabled on |
message transmission sessions are encrypted.
|
|
SSL is not enabled |
message transmission sessions are not encrypted.
|
|
the SSL connection cannot be established on an incoming connection (encryption fails) |
the CallPilot SMTP server drops the connection. Message transmission does not occur. |
|
the SSL connection cannot be established on an outgoing connection (encryption fails) |
the CallPilot SMTP server drops the connection. CallPilot sends a non-delivery notification (NDN) to the message originator. |
Meridian Mail Net Gateway encryption (using Entrust) is not supported by CallPilot. Therefore, message transmissions between CallPilot and a Meridian Mail Net Gateway system cannot be encrypted.
The SMTP connection is encrypted if
SSL is enabled at both ends
encryption certificates are accepted by each system
Intermediate mail relays and application proxy servers must participate
in the establishment of secure sessions.

SSL encryption (and authentication) works best when messages are transferred point-to-point (for example, within a firewall).
When messages are not transmitted point-to-point, SSL sessions can still
be initiated and authentication can still be performed if the firewalls
are configured appropriately. It may also be possible to initiate SSL
sessions between intermediary mail relays and proxies if those systems
support SSL and are configured appropriately. However, end-to-end authentication
may not be possible.

SSL implementation requires a certificate on the CallPilot server. The CallPilot SMTP server uses the certificate that is provided for Internet Message Access Protocol (IMAP) and Lightweight Directory Access Protocol (LDAP). No specific manual interventions are required by you to create a certificate for SMTP.
Some
third-party VPIM-compliant messaging systems may or may not accept the
CallPilot certificate.
You
may need to use a certificate import feature to import certificates created
from known certificate authorities such as Verisign.
The CallPilot SMTP server accepts all certificates when establishing an SSL session. That is, CallPilot does not verify the digital signature. Therefore, establishing the secure session does not guarantee that CallPilot is actually sending the message to a specific destination.
For example, a tampered router in the network can redirect messages to a server that is pretending to be a known site. CallPilot cannot verify that the certificate presented by the remote site is legitimate, and sends the encrypted message to the rogue server, which can decrypt the message with its master keys.