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.
Normally, outgoing messages use port 25 on the server.
However, you can change this number if you have security concerns. To
use another port, specify the port number according to standard convention.

Messaging > Message Delivery Configuration
In the SMTP/VPIM section, choose the VPIM services to provide
Incoming
SMTP/VPIM: Check this option to allow CallPilot to receive messages
from other systems using VPIM Networking. To prevent the server from receiving
messages from any remote systems, clear this option.
This
option is checked by default, and must be enabled if you want to allow
users to send messages with desktop messaging. The Outgoing SMTP/VPIM
option applies to VPIM Networking only and does not affect desktop messaging.
Outgoing
SMTP/VPIM: Check this option to allow CallPilot to send messages
to integrated and open remote systems using VPIM Networking. To prevent
the server from sending messages to any remote systems, clear this option.
This option is checked by default.
To route outgoing messages through an e-mail or
proxy server, type the fully qualified domain name (FQDN)
for the server in the Outgoing SMTP Mail/Proxy
Server box.
Maximum length: 255 alphanumeric characters
Default port number: 25
To
change the port number, type a colon after the FQDN, followed by the port
number.
Click Save.