The information in this Readme file pertains to Novell Messenger 3 Support Pack 1.
Novell Messenger 3 Support Pack 1 offers enhanced functionality over prior Messenger versions:
SSL Connection Requirements: Messenger now requires all communications except those to eDirectory to be secure. You can either use a publicly signed cert or Messenger will create the server certificate during the installation. For more information about using certificates in Messenger, see Messenger System Security in the Novell Messenger 3.0 Installation Guide.
PIN Support for iOS and Andriod Apps: The Messenger app can now be locked with a PIN so only you can access it. Along with using the PIN, you can also used iOS TouchID to unlock the app. For more information, see Turning on the Passcode in the Novell Messenger 3 Service Pack 1 Mobile Quick Start.
Custom Status Support for iOS and Andriod Apps: You can now edit and create custom status’ inside the apps. For more information, see Creating a Custom Status in the Novell Messenger 3 Service Pack 1 Mobile Quick Start.
Novell Messenger 3.0 system requirements (including requirements for mobile devices) are listed in Novell Messenger 3.0 Installation Guide.
Complete installation instructions are available in the Novell Messenger 3.0 Installation Guide.
In some cases, the Messaging Agent does not start automatically even when the startup type has been set to Automatic, as described in Novell Messenger 3.0 Installation Guide.
To work around this issue:
On the Windows server where the Messaging Agent is running, launch the Run application.
Type services.msc, then press Enter.
Right-click, then click .
On thetab, in the drop-down list, select .
In thedrop-down list, select .
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.
When running Messenger on SLES 12, ConsoleOne fails to start because the following dependency is missing:
Install the libXtst6 package, then proceed to run Messenger.
When installing Messenger, the installation location where you plan to install Messenger cannot contain extended or double-byte characters.
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.
When running Messenger on SUSE Linux Enterprise Server (SLES) 11, you need to install the libstc++.so.5 or greater library.
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.
If you are storing any encrypted Novell Messenger attributes in eDirectory 8.8, you cannot see these attributes in ConsoleOne until they are unencrypted.
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 >in ConsoleOne and click .
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.
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.
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.
IMPORTANT:The third-party messenger systems discussed in this section do not support the simultaneous client connections available with Messenger 3.0.
The Adium instant messaging application for Mac OS X is available at the Adium website.
The Pidgin (formerly Gaim) open source instant messaging connector is available at the Pidgin website.
The Kopete open source instant messaging plug-in is available at the Kopete website.
The following sources provide information about Novell Messenger 3.0:
Online product documentation: Novell Messenger 3.0 Documentation website .
Product documentation included within Novell Messenger:
Help System: Click themenu in the upper-right corner of the Messenger client.
Novell, Inc. makes no representations or warranties with respect to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to revise this publication and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes.
Further, Novell, Inc. makes no representations or warranties with respect to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to make changes to any and all parts of Novell software, at any time, without any obligation to notify any person or entity of such changes.
Any products or technical information provided under this Agreement may be subject to U.S. export controls and the trade laws of other countries. You agree to comply with all export control regulations and to obtain any required licenses or classification to export, re-export or import deliverables. You agree not to export or re-export to entities on the current U.S. export exclusion lists or to any embargoed or terrorist countries as specified in the U.S. export laws. You agree to not use deliverables for prohibited nuclear, missile, or chemical biological weaponry end uses. See the Novell International Trade Services website for more information on exporting Novell software. Novell assumes no responsibility for your failure to obtain any necessary export approvals.
Copyright © 2007-2015 Novell, Inc. All rights reserved. Permission is granted to copy, distribute, and/or modify this document under the terms of the GNU Free Documentation License (GFDL), Version 1.2 or any later version, published by the Free Software Foundation with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the GFDL can be found at http://www.fsf.org/licenses/fdl.html.
For Novell trademarks, see the Novell Trademark and Service Mark list.
All third-party trademarks are the property of their respective owners.