
In the BlackBerry Enterprise Server for Microsoft Exchange, in high availability configurations, if the SCS Worker thread entered
into a hung state while executing mailbox commands, all messaging servers were not reported as unhealthy so no failover
took place. (DT 486948)
When a user sent a email message with a large attachment, it caused hung threads in the BlackBerry Messaging Agent
instances of the user and recipients. (DT 454903)
In the BlackBerry Enterprise Server for Microsoft Exchange, in certain circumstances, after you configured users to synchronize
with public folder contacts and then failed over the BlackBerry Enterprise Server to another high availability pair, the BlackBerry
Messaging Agent stopped responding. (DT 451637)
In the BlackBerry Enterprise Server for Microsoft Exchange, after a primary BlackBerry Enterprise Server failed over to a standby
BlackBerry Enterprise Server and then became the primary BlackBerry Enterprise Server again, the BlackBerry Messaging
Agent no longer monitored started threads for hung threads. (DT 403681)
If a user had the Editor permissions for the user's mail file and set the out-of-office option using a device, the device displayed
an error message and the user could not change the out-of-office option. (DT 403667)
In certain rare circumstances, users could not view unencoded attachments contained in incoming MIME messages on their
devices. The attachments were encoded into the text of the message body instead of being rendered as an attachment. (DT
400597, SDR 232290)
This issue is resolved in IBM® Lotus® Domino® 7 or later
If a large number of users used BlackBerry® Desktop Manager at the same time to synchronize messages, the BlackBerry
Enterprise Server might not have performed as expected. (DT 395450)
In some circumstances, cached attachment images were incorrectly displayed in email messages on a user's device. (DT
395218)
If a meeting organizer of a recurring meeting added a user to a future instance of the meeting, and the user accepted the
meeting invitation from a device, the device only displayed past occurrences of the meeting. (DT 360960)
Paraguay Standard Time, Kamchatka Standard Time, and UTC time zones were not supported and resulted in errors logged
by the BlackBerry Messaging Agent when running on Windows Server® 2008. (DT 358985)
If you configured a global email filter for sensitivity, any email message that met the requirements of the email filter was sent
to the device without applying the rules within the email filter. (DT 339518)
Release Notes
BlackBerry Messaging Agent issues fixed in this release
15
Commentaires sur ces manuels