This topic describes
SMTP authentication can fail in the following situations:
SMTP/VPIM passwords are not configured correctly in CallPilot Manager for the local CallPilot server and the remote messaging server.
The user’s user ID, password, or both are not configured correctly in the desktop messaging or My CallPilot client.
The requested authentication method is not supported
at both ends of the connection.
This can occur under the following circumstances:
A desktop messaging or My CallPilot user is using a desktop messaging client or web browser that does not support SMTP authentication at all.
The desktop messaging or My CallPilot user is using a client or web browser that does not support the SMTP authentication method requested by CallPilot.
The remote messaging server does not support SMTP authentication.
The remote messaging server does not support the SMTP authentication method requested by CallPilot.
CallPilot cannot receive messages when authenticated mode only is used and authentication fails. If mixed authentication is being used on CallPilot, a message transmission can still occur without authentication.
For incoming messages from desktop messaging or My CallPilot users, the message must leave the desktop messaging or My CallPilot user’s outbox and be received by the CallPilot server before CallPilot can send the message to the receiving destination.
|
IF CallPilot is configured to use |
THEN |
|
authenticated mode only, and authentication fails for an incoming message from a desktop messaging or My CallPilot user |
the message remains in the user’s outbox in the desktop messaging client or web browser. A non-delivery notification (NDN) is not required because the user can immediately determine that the message was not sent. |
|
mixed authentication, and authentication fails for an incoming message from a desktop messaging or My CallPilot user |
the message remains in the user’s outbox in the desktop messaging client or web browser. A non-delivery notification (NDN) is not required because the user can immediately determine that the message was not sent. |
|
mixed authentication, and authentication is not attempted for an incoming message from a desktop messaging or My CallPilot user |
CallPilot accepts the message without authentication. Unauthenticated user restrictions are enforced. |
|
IF CallPilot is configured to use |
THEN |
|
authenticated mode only, and authentication fails for an incoming VPIM Networking message transmission |
CallPilot drops the connection. The sender may receive an NDN if the remote server supports NDNs. |
|
mixed authentication, and authentication fails for an incoming VPIM Networking message transmission |
CallPilot drops the connection. The sender may receive an NDN if the remote server supports NDNs. |
|
mixed authentication, and authentication is not attempted for an incoming VPIM Networking message transmission |
CallPilot accepts the message without authentication. Unauthenticated Server Restrictions are enforced. |
When an initiating SMTP password is defined on your CallPilot server, SMTP authentication is performed on outgoing sessions to remote servers. If authentication is attempted and fails, CallPilot will still attempt to send the message. If the advertised authentication method is not supported, CallPilot will attempt to send the message without authentication.
If the outgoing message was initiated by a desktop messaging or My CallPilot user, Unauthenticated user restrictions are enforced.
If the remote server rejects any SMTP commands, and the message cannot be sent after several attempts, CallPilot sends a non-delivery notification (NDN) to the sender and logs an event.
You can specify the maximum number of failed authentication attempts that can occur from remote messaging servers and desktop messaging or My CallPilot users, and what action to perform when the limit is exceeded. You can choose to
report the event in the event log and generate an alarm
disable the remote messaging server in your network
database and report the event
When the remote server is disabled, the following events occur:
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.
disable the user’s mailbox and report the event
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. CallPilot also reports an event for each time the maximum number of failed attempts is exceeded.
To allow CallPilot to receive incoming messages again, you must
enable the Receive messages from this server option on the Remote Server Properties page