SMTP authentication failures

This topic describes

Why SMTP authentication failures occur

SMTP authentication can fail in the following situations:

What happens when SMTP authentication fails

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.

Authentication failures for incoming messages from desktop messaging or My CallPilot users

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.

Authentication failures for incoming messages from remote servers

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.

Back to top

Authentication failures for outgoing messages to remote messaging servers

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.

What happens when there are too many failed authentication attempts

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

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

Back to top