Downloads
What's New in MagooClient V4
Version 4 provides a signifcant upgrade to MagooClient message handling. Message persistence has been upgraded to allow the client make use of either a local RDEBMS or a central MagooServer message store via secure Web Services. Full details are provided below.
Local RDBMS Message Store
The underlying file-based message store has been superceded by a fully indexed RDBMS capabilty to provide a significantly faster and more scalable persistence mechanism. The client can be configured to use either an embedded HSQL database or an external MySQL instance.
The message store now supports auto-archiving and archive cleanup for deployment scenarios with high message volume requirements.
Folder List Pagination
The view onto folder message lists has been paginated for faster loading and now supports navigation through folders with thousands or even hundreds of thousands of messages.
Upgraded Transports
POP3/SMTP connections can now be encrypted and new transports have been added for native (i.e. non-JMS) connection to RabbitMQ and Websphere MQ
Send Again
Testing can be speeded up through use of a Send Again on the message pop-up menu to allow previously sent messages to be instantly converted to new drafts.
Shared Message Boxes with MagooServer
MagooClient can now be configured to use a central MagooServer message store. This facilitates collaborative message handling across a user group and provides centralized message store management and archiving. Message boxes can be either personal or group (shared) to allow boxes to be configured and structured according to organization hierarchy with access rights secured accordingly. A single message tree view is provided onto all of a user's available message boxes.
Asynchronous Send
Messages are now dispatched asynchronously to allow users to continue working while a message is being sent. Automatic re-try capability will queue and attempt to re-send a message if the initial send attempt fails.
Background Delete
Message clean-up is now run as a background process to allow large folders to be purged with a single delete action.