Novell Messenger 3 Support Pack 1

4.1 Messaging Agent Does Not Always Start Automatically

In some cases, the Messaging Agent does not start automatically even when the startup type has been set to Automatic, as described in Windows Server Options for the Windows Messenger Agents in the Novell Messenger 3.0 Installation Guide.

To work around this issue:

4.2 Cannot Search Messenger Archive for a User Whose eDirectory OU Contains the ‘&’ Character

You cannot search the Messenger Archive for conversations based on a user if that user resides in an eDirectory OU that contains the & (and) character.

4.3 ConsoleOne Fails to Start on SLES 12 Because of Missing Dependency

When running Messenger on SLES 12, ConsoleOne fails to start because the following dependency is missing:

libXtst6

Install the libXtst6 package, then proceed to run Messenger.

4.4 Installation Location Cannot Contain Extended or Double-Byte Characters in the Path Name

When installing Messenger, the installation location where you plan to install Messenger cannot contain extended or double-byte characters.

4.5 Extending the eDirectory 8.8.5 Schema When Using LDAP Mode on Linux

When installing Messenger with eDirectory 8.8.5 with LDAP mode on Linux, you must manually extend the eDirectory schema.

How you extend the schema depends on whether eDirectory is installed locally or remotely.

4.6 Library Dependency on SUSE Linux Enterprise Server 11

When running Messenger on SUSE Linux Enterprise Server (SLES) 11, you need to install the libstc++.so.5 or greater library.

4.7 Case-Sensitive Passwords Do Not Work with eDirectory 8.8

If you try to connect to eDirectory 8.8 from Novell Messenger with a case-sensitive password, eDirectory 8.8 might not recognize the case-sensitive password. For information on how to enable case-sensitive passwords in eDirectory 8.8, see “How to Make Your Password Case-Sensitive” in the eDirectory 8.8 What’s New Guide.

4.8 Encrypted Messenger Attributes in eDirectory 8.8

If you are storing any encrypted Novell Messenger attributes in eDirectory 8.8, you cannot see these attributes in ConsoleOne until they are unencrypted.

4.9 Server Object Security Settings

The Messenger install/upgrade now requires Security settings (SSL certificate and key) to be written to the Server object. If you have overwritten these settings on the Agent objects, the Security settings that are set during the install/upgrade will not apply to the Agents. If you want the Server object Security settings to apply to the Agents, go to the Agent object > Security in ConsoleOne and click Reset to Defaults.

5.1 Shared Filr Location for Message History of Multiple Clients Is Not Supported

Messenger does not support storing the history files from multiple clients in a shared Filr storage location. Because Messenger supports simultaneous client connections, storing history information to a single Filr location for multiple clients can result in corrupt history files.

5.2 Changing Owner or Modifying Access Settings When Creating a Chat Room Results in an Error Message

When creating a chat room, changing the owner to someone other than yourself before the chat room is created results in an error message. The chat room is ultimately created, but not all configuration changes are saved. The new owner must then edit the chat room and make the equivalent changes.

6.1 Differences Between How the iOS App and the Android/Blackberry App Connect to the Server

The iOS app and the Android/Blackberry app use different methods to connect to the Messenger server.

The Android/Blackberry app behaves the same way as the desktop clients. It uses a direct internet connection to the server and is in constant contact with the server. If the app cannot connect to the server, it attempts to reconnect in the background. After it reconnects to the server, it pulls down any queued messages.

The Messenger server uses Novell Push Notification Service, which uses Apple Push Notification, to push messages to the iOS app. This does not require the app to have constant communication with the Messenger server. If the iOS app is not used for 24 hours, it times out and you are logged out by the server. You then receive a notification that you have been logged out. If you were only logged into Messenger through the iOS app, you appear offline to others users in the system. To go online and receive messages again, simply open the app and login.