Last updated on AUGUST 26, 2017
Applies to:
Oracle Communications Messaging Server - Version 7.0.5 to 7.0.5 [Release 7.0.0]Information in this document applies to any platform.
Symptoms
Post upgrade of the Message Store to Oracle Communications Messaging Server 7.0.5.35 (from say, version 6.3), one would notice a changed behavior with the parameters:
sasl.default.ldap.searchfilter
sasl.default.ldap.searchfordomain
For instance, with the setting as shown here to allow users to authenticate with their Radius username instead of <uid>@<domain>
sasl.default.ldap.searchfordomain=0
and
sasl.default.ldap.searchfilter='(&(objectclass=inetmailuser)(radiusLogin=%o))'
For Example:
1. When using Messaging server 7.0.5.35.0 with
sasl.default.ldap.searchfordomain=1
and
sasl.default.ldap.searchfilter not set.
Logging into IMAP with <uid@domain> is successful and the correct mailbox is accessed on SELECT.
Changes
In older versions (since at least Messaging Server version 5.x), the above setting would work fine - the user would log into POP/IMAP with the Radius credentials and get to his / her '<uid@domain>' mailbox.
However, in version 7.0.5.x, the behavior has changed. User logs in successfully to IMAP or POP, but the services then try accessing a non-existent mailbox with user's unqualified name, as if the user belonged to the default domain.
Cause
Sign In with your My Oracle Support account |
|
Don't have a My Oracle Support account? Click to get started |
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms