Change In The Way The 'service.loginseparator' Setting Is Used (Doc ID 2047158.1)

Last updated on AUGUST 28, 2015

Applies to:

Oracle Communications Messaging Server - Version 7.0.4 and later
Information in this document applies to any platform.

Symptoms

Consider an Oracle Communications Messaging Server setup running on 7.0.5.36.0 release, where one would notice a change in the way the service.loginseparator setting is interpreted.

Note: The service.loginseparator setting refers to the character(s) to be used as login separator (between userid and domain)

If service.loginseparator is set to something other than '@' (say for example, '~' ), the new mailbox that is created will have '~' character used in it.

While in the previous versions, the character "@" was always used as a delimiter, no matter what was defined in service.loginseparator.

Example:

Where the 2nd mailbox in the list has been created when the user, usertest1, tried accessing his mail after the service.loginseparator was changed to '~'.

Changes

The service.loginseparator can now contain multiple characters and the first one will be the canonical one.

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