Mixed authentication mode

In mixed authentication mode, authentication is optional. Authentication is performed only if it is supported at both ends of the connection.

If authentication is not being used, CallPilot may limit the addressing capabilities of the sender, if configured. See Setting unauthenticated access restrictions.

If authentication is being used and it fails, the session is disconnected.

You can independently define authentication options for SMTP and LDAP servers. Connections to the IMAP server must be authenticated. In mixed authenticated mode, CallPilot performs as follows:

Server type

Description

SMTP

If authentication is supported by the remote messaging server or client software sending the message, the CallPilot server verifies the authenticity of the sender before accepting a message.

For SMTP connections that are not authenticated, CallPilot accepts messages without authentication, but may limit the addressing capabilities of the sender.

LDAP

If authentication is supported by the desktop messaging client, the CallPilot server verifies the authenticity of a mailbox owner before allowing access to the CallPilot address book. The LDAP server also permits unauthenticated connections.

This topic describes

Back to top

When to use mixed authentication

Use mixed authentication if your messaging network contains any of the following:

For SMTP connections, CallPilot accepts messages from both authenticated and unauthenticated senders, but restricts the capabilities of senders that are not authenticated.

Caution!  If you are concerned about security, Nortel Networks recommends that you use the authenticated mode only.


Back to top

How mixed authentication affects users

In mixed authentication mode, message receipts (and therefore, user addressing capabilities) are affected as follows:

IF the connection is

THEN

not authenticated

  • incoming messages from remote servers can be blocked by defining the Unauthenticated Server Access Restrictions.

  • incoming messages from desktop messaging or My CallPilot users can be restricted by defining the Unauthenticated Desktop User Restrictions.

See Setting unauthenticated access restrictions.

 

authenticated

incoming messages do not have to be blocked.

The restrictions for users and remote servers are not enforced. However, users are restricted to the capabilities that are allowed in their mailbox class.

Back to top

How to enable mixed authentication

You can enable mixed authenticated mode for communication with SMTP and LDAP servers, or choose different modes for each server, depending on the requirements and configuration of your messaging network.

To enable mixed authenticated mode, choose the appropriate option.

Server type

Description

SMTP

  1. On the Message Delivery Configuration page, choose the Unauthenticated option.

  2. Choose one or both of the following authentication methods:

Note/Tip  By default, the Unauthenticated and Challenge/Response Authentication check boxes are checked when you install your CallPilot server.

How to verify or change the settings.

LDAP

  1. On the Messaging > Internet Mail Clients page, choose the Enable LDAP with Plain Password Authentication option.

  2. Choose the Enable LDAP with No Authentication option.

Note/Tip  By default, both of these check boxes are checked when you install your CallPilot server.

How to verify or change the settings.

 

Back to top


Related Procedures    Overviews    See Also