It'll likely be available late this week or early next week. Here's the release notes:

Fixed issuesBlackBerry Attachment ServiceSDR 78955
Previously, if a user requested an attachment that was larger than the limit you set in the BlackBerry Configuration Panel, the user did not receive an error stating the attachment exceeded the size limit.

SDR 49529
Previously, after you restarted the remote BlackBerry® Attachment Service, the BlackBerry Enterprise Server could not re-establish a connection to the BlackBerry Attachment Service and could no longer convert attachments.

BlackBerry Configuration DatabaseSDR 72825
Previously, if you deleted the bbprofiles database and let the BlackBerry Enterprise Server rebuild it, it was not repopulated correctly from the configuration database.

SDR 66712
Previously, when you tried to update a user PIN to 0 and it coincided with an update of another user to 0, the configuration database would not accept the update.

SDR 55924, SDR 55923
Previously, if the connection to the configuration database was lost during a long database query, it might have affected the ability to administer the BlackBerry Enterprise Server through the BlackBerry Manager.

SDR 48851
Previously, if multiple BlackBerry Enterprise Servers connected to a single configuration database and multiple BlackBerry Routers, the BlackBerry Enterprise Server might have sent incorrect BlackBerry Router information to the BlackBerry devices.

BlackBerry DispatcherSDR 77591
Previously, the connection to the BlackBerry Infrastructure might have initialized incorrectly if certain threads started too early. The BlackBerry Dispatcher might not have been able to connect to the BlackBerry Infrastructure and would reset after 10 failed ping attempts.

SDR 54367
Previously, if the BlackBerry Dispatcher attempted to process incoming data during the shutdown process after the connection to the BlackBerry Infrastructure was closed, the BlackBerry Dispatcher might have stopped responding.

SDR 54142
Previously, if the BlackBerry Dispatcher attempted to use a session that was already deleted during the shutdown process, the BlackBerry Dispatcher might have stopped responding.

BlackBerry ManagerSDR 72254
Previously, when you attempted to clear BlackBerry Mobile Data Service statistics in the BlackBerry Manager, the BlackBerry Manager stopped responding.

SDR 68614
Previously, if you changed the setting in the Smart Dialing Group Options and saved the changes, the changes were not applied.

SDR 67697
Previously, if you had two or more BlackBerry Enterprise Servers sharing a single configuration database, the second BlackBerry Enterprise Server listed under the BlackBerry Domain was unable to send PIN messages on a domain, server, or user level.

SDR 65184
Previously, if you typed an incorrect value when changing IT policy settings, no warning was displayed and the value was saved.

SDR 64876
Previously, when viewing users on a BlackBerry Enterprise Server in the BlackBerry Manager, users might have been sorted by last name only, not first and last name.

SDR 65177
Previously, when you made changes to existing IT policies and clicked Cancel, the IT policy name appeared as Default in the IT Policies window in BlackBerry Manager.

SDR 59290
Previously, when you moved a user to a new IT policy, the BlackBerry Manager showed that the new IT policy was applied successfully before it was sent to the BlackBerry device.

SDR 58017
Previously, if you added a user account that resided on an IBM Lotus Domino Server version 5.0.9 or later to the BlackBerry Enterprise Server using the BlackBerry Manager on an IBM Lotus Domino Server version 5.0.8 or earlier, a Runtime error message appeared.

SDR 52705
Previously, if you turned off TCP/IP on the BlackBerry Configuration Database or connected to a port other than the default port (1433), you could not open the Handheld Configuration Tool.

BlackBerry Messaging AgentSDR 77132, SDR 74570, SDR 73999
Previously, when you removed users from the BlackBerry Enterprise Server, re-added them, and then performed a state database cleanup, the BlackBerry Enterprise Server might have stopped responding.

SDR 77009
Previously, if you deleted a user from the BlackBerry Enterprise Server, the BlackBerry Enterprise Server might have stopped responding during its nightly maintenance process.

SDR 76792
Previously, when the BlackBerry Messaging Agent resolved addresses, it attempted to determine if the recipient was on IBM Lotus Notes®. The address resolution might have taken longer than in earlier versions of the BlackBerry Enterprise Server software.

SDR 72662
Previously, if the BlackBerry Enterprise Server experienced an exception error while retrieving an address list, a deadlock might have occurred.

SDR 71812
Previously, when the BlackBerry Enterprise Server performed wireless folder management synchronization for folders with a large number of items, delays in message processing might have occurred.

SDR 70284
Previously, if an address book entry had a long company name, the BlackBerry Messaging Agent might have silently stopped responding.

SDR 70207
Previously, users with IBM Lotus Notes version 5 or 6 could not synchronize their address books to their mailboxes using the standard message template.

SDR 69281
Previously, if a user had journal entries with long subject lines, the BlackBerry Enterprise server might have silently stopped responding when it attempted to synchronize the journal entries.

SDR 69133
Previously, if a user performed a global address list look-up on the BlackBerry device, the full street address might not have been returned.

SDR 66686
Previously, the BlackBerry Enterprise Server might have attempted to reconcile a large amount of folder data wirelessly and caused the user’s BlackBerry device to stop responding for several minutes.

SDR 61684
Previously, if you sent an All Points Bulletin (APB) to a user who was outside of a wireless coverage area, the .dat files created by the BlackBerry Messaging Agent and BlackBerry Dispatcher were duplicated. If you restarted the BlackBerry Enterprise Server, the .dat files were duplicated again and the user received multiple copies of the APB.

SDR 58771
Previously, if a user replied to a message from the BlackBerry device and multiple recipients were listed in the cc field, only one recipient was listed in the cc field if the user then checked the sent items in IBM Lotus Notes.

SDR 56421
Previously, in certain circumstances, if you removed a user from the BlackBerry Enterprise Server, the BlackBerry Messaging Agent might have stopped responding.

SDR 55603
Previously, when you turned off wireless email reconciliation globally in BlackBerry Manager and then enabled it, the Reconcile Now option did not appear on the BlackBerry device.

SDR 55305
Previously, if you moved a user from a BlackBerry Enterprise Server version 4.0 or later to an earlier version, the user was removed from the newer BlackBerry Enterprise Server, but not added to the older BlackBerry Enterprise Server.

SDR 55189
Previously, when a message with multiple recipients in the To field was sent to a BlackBerry device, and one of the recipients used Reply to All, the original message was appended to the body of the reply, but only one recipient's name appeared in the To field. However, all intended recipients received the message.

SDR 54068
Previously, if the BlackBerry Messaging Agent attempted to decode MIME messages with attachments that were HUFFMAN encoded, had a HostType of HOST_UNKNOWN, and did not have the FILEFLAG_SIGN flag, the attachment did not open and an error message appeared.

SDR 53892
Previously, the SRP Connection trap did not get logged to the SNMP service.

SDR 43672
Previously, when you used the IBM Lotus Notes Send and File feature for messages sent from Lotus Notes, the message would only be sent to the BlackBerry device Inbox, and not to the folder where you had filed it in Lotus Notes.

SDR 29455
Previously, if a hierarchical name change occurred in the IBM Lotus Domino environment, the update did not populate into the root folder name of the message file in the state database message folder view or in the user information document of a state database.

BlackBerry Mobile Data ServiceSDR 78690
Previously, the BlackBerry Mobile Data Service did not send the proxy-authorization header when it attempted to authenticate through a proxy server.

SDR 78689
Previously, users with the BlackBerry 8700 Series of wireless handhelds might not have been able to browse the web in color.

SDR 71875
Previously, if you attempted to retrieve the status of a certificate that had been revoked and was in the CRL, the BlackBerry Enterprise Server might have stopped responding.

SDR 33227
Previously, SNMP traps for the BlackBerry Mobile Data Service did not appear correctly in an SNMP trap viewer.

BlackBerry Policy ServiceSDR 66156
Previously, if a user performed a wireless enterprise activation on a BlackBerry Enterprise Server that did not have S/MIME support enabled, the option to send PGP messages did not appear.

BlackBerry RouterSDR 76907
Previously, if more than 32 messages were sent to a BlackBerry device when it was outside of a wireless coverage area, some messages might have been duplicated if the user synchronized messages through the USB connection to the computer.

BlackBerry Synchronization ServiceSDR 70714
Previously, if a user had more than 5 MB of tasks, the user was not able to synchronize them wirelessly.

SDR 67409
Previously, if the organization name in IBM Lotus Domino contained a special character, tasks could not be synchronized.

Setup programSDR 73897
Previously, after you upgraded the BlackBerry Enterprise Server from version 4.0 SP2 to version 4.0 SP3, the global field mappings reverted to the default settings.

SDR 63556
Previously, when you upgraded from BlackBerry Enterprise Server version 2.2 to version 4.0 or later, the Service Name was not written in the Registry or the configuration database.

SDR 62488
Previously, if your BlackBerry Enterprise Server had a temporary SRP ID, and you specified a permanent SRP ID, the BlackBerry Enterprise Server might not have connected to the BlackBerry Infrastructure using the permanent SRP ID.

SDR 62174
Previously, when you upgraded the BlackBerry Enterprise Server from version 4.0 SP1 to version 4.0 SP2, the setup program did not back up the configuration database when the Backup Database check box was selected.

SDR 61526, SDR 58204
Previously, if you upgraded a BlackBerry Enterprise Server that used a remote BlackBerry Router from version 4.0, or version 4.0 SP1 to version 4.0 SP2, the Router Host field changed to localhost from the remote BlackBerry Router.

SDR 54551
Previously, if you upgraded to BlackBerry Enterprise Server version 4.0 SP1 or later, the settings for the BlackBerry Alert Service might not have been retained.

SDR 40956
Previously, when you upgraded the BlackBerry Enterprise Server, user-defined log levels were not preserved during the upgrade.

SDR 76377, SDR 71107, SDR 67629
Previously, if a meeting organizer made changes to a recurring meeting, the changes might have appeared in all past instances on the BlackBerry device even when the changes only applied to future instances.

SDR 75974
Previously, if an attendee deleted a meeting entry from the BlackBerry device, the change did not synchronize correctly and was not removed from IBM Lotus Notes.

SDR 75608
Previously, if a user selected Don't display new calendar entries and notices in the All Documents view of Mail check box in the calendar preferences for IBM Lotus Notes, it had no effect on calendar items created on the BlackBerry device.

SDR 75353
Previously, when the BlackBerry Enterprise Server received a duplicate calendar synchronization session from a BlackBerry device, the BlackBerry Enterprise Server aborted the second request. This might have resulted in an increased use of system resources.

SDR 74755
Previously, if you turned off wireless calendar synchronization using the Tell BES OTAC off command in the Domino Server Console, the BlackBerry Enterprise Server might have stopped responding.

SDR 73676, SDR 73568
Previously, if the state document for a recurring meeting was deleted, duplicate instances of the meetings might have appeared on the BlackBerry device.

SDR 70562
Previously, when a user performed an initial calendar synchronization, if the BlackBerry Enterprise Server could not find a contact’s SMTP address in the Notes Address Book, it might have caused a general protection fault on the user’s computer.

SDR 69068
Previously, when a user created a meeting using IBM Lotus Notes and an invitee accepted on a BlackBerry device, if the organizer then changed the location for one occurrence and an invitee accepted the change on the BlackBerry device, an error message appeared. The instance was deleted in the invitee’s calendar.

Wireless enterprise activationSDR 61605
Previously, if you used the BlackBerry Manager to perform an enterprise activation on a new user’s BlackBerry device, and the user connected the BlackBerry device to the desktop computer, the BlackBerry Desktop Software prompted the user to generate encryption keys again.

Wireless PIM synchronizationSDR 58810
Previously, if you changed the PIM Sync Global Field Mapping settings and added a new user, the settings were not applied. When the user created a contact on the BlackBerry device with a field that was mapped globally, that field did not synchronize.

BlackBerry DispatcherSDR 78610
The BlackBerry Dispatcher does not restart after it stops responding. It appears to be processing transactions, but messages are not delivered to or sent from the BlackBerry device.

BlackBerry ManagerSDR 76256
The BlackBerry Manager cannot differentiate between users who have the same mail path file name.

SDR 72019
If you change the SRP ID and, or client access license key in the BlackBerry Manager while the BlackBerry services are stopped, when the BlackBerry services are started, the routing information is not updated in a user’s BlackBerry profiles database.

SDR 69335
If you open the BlackBerry Manager from a remote desktop connection using the same SQL authentication account in the same domain that was used to install the BlackBerry Enterprise Server, the BlackBerry Manager cannot connect to the configuration database. The DB Connection failed error message appears.

SDR 57849
If you add a user to a BlackBerry Enterprise Server, but do not assign a BlackBerry device to the user, the Last forward time, Last contact time, and Last sent time fields show incorrect information.

SDR 50094
You cannot assign separate application policies to additional applications. The BlackBerry Enterprise Server does not allow multiple versions of an application on a BlackBerry device.

SDR 44717
If you use a USB connection to provision a BlackBerry device from a computer running a remote BlackBerry Manager, an error message stating that an error occurred while assigning the BlackBerry device to the user appears.

BlackBerry Messaging AgentSDR 77447
If the BlackBerry Enterprise Server is not running, the profiles database is deleted, and you send a message to a BlackBerry device, when the BlackBerry Enterprise Server is restarted and the profiles database is created, the user’s BlackBerry device activation date is reset to the profiles database creation date and the message is not forwarded to the BlackBerry device.

SDR 77289
In certain circumstances, when the BlackBerry Enterprise Server attempts to remove two different state databases for the same user the BlackBerry Enterprise Server might stop responding.

SDR 77061
In certain circumstances, an issue might occur with one of the threads and the BlackBerry Enterprise Server might stop responding.

SDR 76960
If a user resides on an IBM Lotus Domino server version that is different from the IBM Lotus Domino server on which the BlackBerry Enterprise Server resides, the messaging agent might not flag read or unread messages correctly for wireless folder reconciliation.

SDR 76854
If you send APBs to BlackBerry devices, you can send more than five messages to a user. This sends more than five packets to the BlackBerry Infrastructure, which might increase the load on the BlackBerry Infrastructure.

SDR 76837
If you remove a user from the BlackBerry Enterprise Server, then re-add the user and activate the user’s BlackBerry device wirelessly, the BlackBerry Enterprise Server and the IBM Lotus Domino server might stop responding.

SDR 76190
In certain circumstances, if a user performs a More request on the BlackBerry device, the BlackBerry Enterprise Server might silently stop responding.

SDR 75710
If you forward a message containing an attachment using the BlackBerry device, the BlackBerry Enterprise Server might change a property in the attachment and the recipient might not receive the message successfully.

SDR 75595
When you add a user to the BlackBerry Enterprise Server who has an out of office message turned on, the user’s name in the Subject field of the Out of Office message might be replaced with the user’s common name and organization.

SDR 75170
If you move a user from one BlackBerry Enterprise Server to another that already has a profile document for that user, the BlackBerry Enterprise Server might stop responding.

SDR 75137
If you send out an APB message, then a user sends a message from the BlackBerry device, if the APB and message are assigned the same Tag number, the message is not sent successfully to its recipients.

SDR 74645
If you create a global filter that prevents users from receiving messages on the BlackBerry device, when the BlackBerry Enterprise Server filters a message, “[40043] (12/02 14:19:34):{0xDDC} FILTERS match found [Server: ???????????????, Message: B1E, User: ?????????????????????, Filter: New Filter, Action: DO NOT FORWARD]” is written to the messaging agent log and the BlackBerry Enterprise Server name and user name are not logged correctly.

SDR 73461
If the BlackBerry Enterprise Server is low on memory and tries to allocate memory, the BlackBerry Enterprise Server might stop responding.

SDR 72335
If you remove a user from a BlackBerry Enterprise Server version 2.2, then add the user to a BlackBerry Enterprise Server version 4.0 and implement a BlackBerry device, duplicate folder IDs occur in the state database. Visit http://www.blackberry.com/technicalk...ecenter/public to read article KB-04381 for more information.

SDR 71283
If a user deletes messages from a BlackBerry device, the messages are removed individually instead of together in a batch process, which might result in a slow deletion process on the BlackBerry device.

SDR 69748
If an exception occurs while the BlackBerry Enterprise Server checks for messages and the BlackBerry Enterprise Server cannot process a message, an APB might not be sent.

SDR 69468
If you add a user to the BlackBerry Enterprise Server, then rename the user on the messaging server, when you activate the BlackBerry device wirelessly, messages are not prepopulated to the BlackBerry device.

SDR 69131
If a user deletes a message from IBM Lotus Notes before it is delivered to the BlackBerry device, the BlackBerry Enterprise Server removes the message entry from the state database and the message is not removed from the BlackBerry device.

SDR 68368
In certain circumstances, if the BlackBerry Enterprise Server receives several large wireless folder management requests (for example, when users move a large number of messages in IBM Lotus Notes), the requests might consume increased processing resources, causing other BlackBerry functions, such as message redirection, to perform slower than normal.

Workaround: See the BlackBerry Enterprise Server Administration Guide for information on turning off APBs.

SDR 50370
If you add a user to an IT policy containing the Disable Wireless Calendar IT policy rule, the synchronization setting does not synchronize to the user’s BlackBerry device.

SDR 50160
If a user’s person document is set to the Prefers MIME format preference for incoming messages, and the user forwards a message including an attachment from the BlackBerry device, the recipient cannot open the attachment on the BlackBerry device.

Workaround: Turn off MIME on the BlackBerry Enterprise Server.

SDR 47020
After you remove a user from the BlackBerry Enterprise Server, the Messaging Agent and console logs continue to show transaction errors for that user.

SDR 46710
In certain circumstances, while you are rebuilding the folder view, the BlackBerry Enterprise Server might silently stop responding.

BlackBerry Mobile Data ServiceSDR 69404
If the connection to the configuration database is lost, the BlackBerry Mobile Data Service might stop responding.

SDR 67424
The version number of the BlackBerry Mobile Data Service does not display in the logs.

BlackBerry Policy ServiceSDR 80928
If you change the encryption algorithm from Triple DES to AES, the BlackBerry Policy Service does not automatically regenerate the encryption key for the BlackBerry device.

Workaround: The user must generate the encryption key on the BlackBerry device.

SDR 77282
If the BlackBerry Policy Service cannot connect to the configuration database, it might stop responding.

SDR 74440
If you start the BlackBerry Policy Service and it cannot locate MSXML 4.0, a “5003” error message appears.

SDR 61188
When polling users for missing programs, the BlackBerry Policy Service writes an extraneous log line for all users after it writes a log line for a specific user.

IT policySDR 74622
If you change the IT policy name and resend the IT policy to a BlackBerry device, the updated IT policy name does not display on the BlackBerry device.

SDR 58618
If you create and assign an IT policy with the Do not save sent items rule set to false, in the user’s desktop manager, the rule is set correctly, but the rule is set to true in the BlackBerry Manager.

SDR 50370
If you add a user to an IT policy containing the Disable Wireless Calendar IT policy rule, the synchronization setting does not synchronize to the user’s BlackBerry device.

Setup programSDR 58916
When you install the BlackBerry Enterprise Server, if XML Core Services (MSXML) 4.0 is not installed on the computer, the policy service fails to start and displays an error message.

SDR 50610
If you upgrade from BlackBerry Enterprise Server version 2.2 SP5 or version 2.2 SP6 to version 4.0, the BlackBerry Mobile Data Service configuration settings and Notes.ini file are not retained and are set to the default settings.

SDR 49465
If you attempt to install BlackBerry Enterprise Server version 4.0 HF1 or HF 2 using an account different from the one you used to install the BlackBerry Enterprise Server, an error message appears.

Workaround: Use an account that has full system administration privileges.

SDR 40179, SDR 40078
If you upgrade the BlackBerry Enterprise Server from version 2.2, users who were deleted from IBM Lotus Domino still appear in the BlackBerry Manager user list and the BlackBerry Enterprise Server attempts to repeatedly initialize them.

Workaround: Before you upgrade, remove the deleted users from the Profiles database. In the x.Deleted\Accounts view, delete all documents.

SDR 40144
If a user’s account is not enabled in the BlackBerry Manager, and you upgrade from the BlackBerry Enterprise Server version 2.2 SP3, the user's status shows that redirection is not enabled in the BlackBerry Manager.

SDR 38542
After you install the BlackBerry Enterprise Server, attachment conversion errors are logged to the Event Viewer application log.

SDR 38043
If you install and configure the BlackBerry Enterprise Server, but do not start the IBM Lotus Domino server, the BlackBerry Dispatcher and the BlackBerry Controller generate warnings in the Event Viewer log.

Wireless calendar synchronizationSDR 76571
If wireless calendar synchronization is turned off for a user and then enabled while the BlackBerry Enterprise Server is disconnected from the configuration database, wireless calendar synchronization is turned off for the user when the connection to the configuration database is restored.

Workaround: Turn off wireless calendar synchronization, and then enable it again for the user.

SDR 75959
If a meeting organizer updates a meeting entry and sends an update, if an attendee declines the update on the BlackBerry device, the meeting organizer does not receive the decline and the entry is not removed from the attendee’s BlackBerry device.

SDR 66727
If you create a recurring meeting with the absolute rescheduling option selected, and you change the meeting time to an instance of the meeting series, then update the meeting time for the meeting series (for example, one hour earlier than the original time), the first instance that was changed displays off by the time changed to the meeting series (for example, one hour earlier than the changed time) on the attendee’s BlackBerry device.

SDR 66616
If a meeting organizer’s delegate updates an instance of a recurring meeting, then the meeting organizer updates another instance of the recurring meeting, the invitee cannot accept the second meeting update from the BlackBerry device and the message body displays “The meeting may have been updated or deleted since this message was sent. The single instance trying to be updated will be removed from the device's calendar until you accept the changes in Notes.”

SDR 66586
If a delegate updates an instance of a recurring meeting for the meeting organizer, the entire meeting series is updated on the invitee’s BlackBerry device.

SDR 63797
If wireless calendar synchronization is turned off on a BlackBerry device, when the BlackBerry Device Software is upgraded, wireless calendar synchronization is enabled on the BlackBerry device.

SDR 58690
If you turn off wireless calendar synchronization on the BlackBerry device then enable wireless calendar synchronization, it might take the BlackBerry Enterprise Server a long time to enable the user for wireless calendar synchronization.

Wireless enterprise activationSDR 61290
When you generate and send a wireless enterprise activation password to a user, the ETP message is not removed from the user’s desktop messaging program and the message is synchronized to the BlackBerry device after the BlackBerry device is implemented.

SDR 37897
In certain circumstances, if you assign and activate two different users on separate BlackBerry Enterprise Servers that both use the same configuration database, the user’s PIN might not synchronize correctly between the desktop computer and the configuration database.

__________________In the beginning the Universe was created. This has made a lot of people very angry and is widely regarded as a bad move.