CallPilot authenticates SMTP connections to prevent denial of service, junk e-mail, and toll fraud. SMTP authentication is performed between
desktop messaging users, My CallPilot users and the CallPilot server
voice messaging servers that have been defined as remote sites in the CallPilot network database and the CallPilot server
Two methods of authentication are supported:
SMTP authentication can be configured in one of the following modes on CallPilot:
You can specify the maximum number of failed authentication attempts
that can occur from remote messaging servers, desktop messaging users,
or My CallPilot users.

Messaging > Message Delivery Configuration
Unauthenticated:
Choose this option if you want to accept messages from desktop
messaging and My CallPilot clients and remote servers in your messaging
network without SMTP authentication. This option is checked by default.
When checked, CallPilot accepts messages from unauthenticated desktop
messaging and My CallPilot users and remote servers.
If
unauthenticated mode
will be used, Nortel Networks recommends that you also enable unauthenticated
access restrictions for servers and desktop messaging users.
Challenge/Response
Authentication: Choose this option if you want CallPilot to request
SMTP authentication using the CRAM-MD5 challenge and response algorithm.
This option is checked by default.
User
ID/Password Authentication: Choose this option if you want CallPilot
to request SMTP authentication using the User ID and Password algorithm.
This option is cleared by default.
Nortel
Networks recommends that you also enable
encryption to prevent password transmission in the clear.
SMTP/VPIM
Password for Initiating Authenticated Connections to Remote Servers:
If authentication will be used, type the password that CallPilot should
send when initiating outgoing message transmissions to remote servers.
A blank password means that CallPilot will not attempt to perform SMTP
authentication when connecting to remote servers.
The password should
contain a minimum of 6 characters
be mixed uppercase and lowercase
contain both letters and digits or special characters
Maximum length: 30 alphanumeric characters
Maximum
failed authentication attempts from a remote server: Type a number
to identify how many times a remote server can fail SMTP authentication
before an event is logged.
Default: 4
Action to perform when the maximum has been reached: Choose one of the following options:
Log only: To report an event in the event log only.
Log
and Disable Server: To report an event in the event log and disable
incoming message receipts from the server that failed SMTP authentication.
This option is enabled by default.
When the remote server is disabled, CallPilot rejects all incoming
VPIM messages from that server (both authenticated and unauthenticated).
This prevents hackers from trying all the possible password combinations,
and eventually obtaining the correct password.
If unsuccessful authentication attempts continue, CallPilot reports an event for each time the maximum number of failed attempts is exceeded.
Maximum
failed authentication attempts from a user: This option identifies
how many times a desktop messaging or My CallPilot client can fail SMTP
authentication before an event is logged.
Default: 9 (it cannot be changed)
Action to perform when the maximum has been reached: Choose one of the following options:
Log only: To report an event in the event log only.
Log
and Disable User: To report an event in the event log and disable
the mailbox belonging to the desktop messaging or My CallPilot user that
failed SMTP authentication. This option is enabled by default.
When the user’s mailbox is disabled, CallPilot rejects the following
from the user:
all attempts to log on to the mailbox (including logon attempts from a phoneset)
all incoming VPIM
messages from a desktop messaging or My CallPilot client that is configured
as belonging to the user
This prevents hackers from trying all the possible password combinations,
and eventually obtaining the correct password.
If unsuccessful authentication attempts continue, CallPilot reports an event for each time the maximum number of failed attempts is exceeded.