Today the Exchange Team released Rollup 5 for Exchange Server 2007 Service Pack 3 (KB2602324). This update raises Exchange 2007 version number to 8.3.213.1.

Here’s the list of changes included in this rollup:

• 981820  New X-headers of a message item do not appear when the message item is retrieved by IMAP4 or by POP3 in an Exchange Server 2007 SP2 environment
• 2292150  A deleted hyperlink remains in the HTML source of an email message if you create the email message by using OWA in an Exchange Server 2007 environment
• 2411423  The Msftefd.exe process constantly consumes up to 100 percent of CPU resources when your mailbox language is set to German on an Exchange Server 2007 server
• 2450078  The sent time in an email message body is incorrect when you reply or forward the email message by using an EWS application in an Exchange Server 2007 environment
• 2451415  “There was a problem logging onto your mail server” error message when you use a POP3 client to access a mailbox in an Exchange Server 2007 SP3 environment
• 2536652  EdgeTransport.exe randomly stops responding on a Hub Transport server after you configure public folder replication in Exchange Server 2007
• 2536695  “Some items cannot be deleted” error message when you try to delete or modify an email message in a public folder in an Exchange Server 2007 environment
• 2536697  DBCS characters in a rule name are converted to question marks after you move a mailbox from Exchange Server 2003 to Exchange Server 2007
• 2537783  The EdgeTransport.exe process crashes occasionally after you install Update Rollup 2 for Exchange Server 2007 SP3
• 2538958  Extended Protection Warning Displayed in Exchange Management Console and Exchange Management Shell After Installing RU2 for Exchange 2007 SP3
• 2554575  Items accumulate in the MRM submission folder when managed folder assistant journal items in an Exchange Server 2007 environment
• 2556751  The EdgeTransport.exe process crashes when processing certain email messages on an Exchange Server 2007 Hub Transport server
• 2557304  The Store.exe process may consume excessive CPU resources and memory resources intermittently when a user opens a calendar item by using OWA in an Exchange Server 2007 SP3 environment

When running ForeFront Protection for Exchange, make sure you disable ForeFront before installing the rollup and re-enable it afterwards, otherwise the Information Store and Transport services may not start. You can disable ForeFront using fscutility /disable and enable it using the fscutility /enable command.

Note that update rollups are cumulative, i.e. they contain fixes released in earlier update rollups for the same product level (RTM, SPx). This means you don’t need to install previous update rollups during a fresh installation but can start with the latest rollup available right away.

You can download Exchange 2007 SP3 Rollup 5 here.

Today the Exchange Team released Rollup 4 for Exchange Server 2007 Service Pack 3 (KB2509911). This update raises Exchange 2007 version number to 8.3.192.1.

Here’s the big list of changes included in this rollup:

• 2531208  You cannot synchronize a folder hierarchy by using Outlook for Mac 2011 in an Exchange Server 2007 SP3 environment
• 2528437  EWS applications cannot connect to Exchange Server 2007 servers after you make changes on accepted domains
• 2521063  You are incorrectly displayed as a meeting organizer after you synchronize the meeting by using your mobile device in an Exchange Server 2007 environment
• 2517337  You cannot open a mailbox that has a “#” character in the primary SMTP email address by using OWA in an Exchange Server 2007 environment
• 2515428  The MSExchangeMailboxAssistants.exe process crashes when the managed folder assistant tries to journal a message in an Exchange Server 2007 environment
• 2508872  The W3WP.exe process in the Autodiscover application pool on the Exchange Server 2007 Client Access servers consumes excessive CPU resources
• 2507374  “Cannot open this item” error message in Outlook online mode in an Exchange Server 2007 environment
• 2506827  An UM auto attendant times out and generates an invalid extension number error message in an Exchange Server 2007 environment
• 2502276  A meeting request series are deleted unexpectedly from the calendar in an Exchange Server 2007 environment
• 2498924  “Could not connect to a directory server” error message when you click the last page button in the search results in Exchange Server 2007 OWA
• 2498156  OLM/OLD incorrectly runs against databases in a RSG in an Exchange Server 2007 environment
• 2496806  A mobile phone times out when you use ActiveSync to synchronize the calendar on the mobile phone with an Exchange Server 2007 mailbox
• 2543879  A PDF attachment sent from a Mac Mail client does not display when you open the email message by using Outlook 2010 in an Exchange Server 2007 SP3 environment
• 2491751  Spell checking does not function correctly in OWA when an S/MIME control is used and SSL Offloading is enabled in Exchange Server 2007
• 2484147  “HTTP Error 400 Bad Request” error message when you use OWA to log on to a newly created Exchange Server 2007 mailbox
• 2466220  Question mark (?) characters appear in the subject of a reply email message in an Exchange Server 2007 environment
• 2223294  A new feature is available to disable the “No end date” check box in OWA when you create a recurring meeting item in an Exchange Server 2007 environment
• 977906  You receive an error message when you run certain commands in the EMS on an Exchange Server 2007 server
• 2495010  The EdgeTransport.exe process consumes 100% CPU usage on an Exchange Server 2010 Edge Transport server or an Exchange Server 2007 Edge Transport server
• 2484817  A mailbox does not show in certain address lists after you run commands on an Exchange Server 2007 mailbox

When running ForeFront Protection for Exchange, make sure you disable ForeFront before installing the rollup and re-enable it afterwards, otherwise the Information Store and Transport services may not start. You can disable ForeFront using fscutility /disable and enable it using the fscutility /enable command.

Note that update rollups are cumulative, i.e. they contain fixes released in earlier update rollups for the same product level (RTM, SPx). This means you don’t need to install previous update rollups during a fresh installation but can start with the latest rollup available right away.

You can download Exchange 2007 SP3 Rollup 4 here.

Update: Exchange 2007 SP3 Rollup 3 has been re-released. Version 2 of the Rollup can be downloaded here. Rollup 3 version 2 raises Exchange 2007’s version number to 8.3.159.2 (initial release was 8.3.159.0). The related knowledgebase article is kb2530488.

Update: The related knowledgebase article kb2531163 can be found here.

A quick notice on a potential issue with Exchange 2007 SP3 and database corruption after installing Rollup 3. The issue may occurs in the following situations:

• When transaction log replay is performed by the Replication Service as part of ensuring the passive database copy is up-to-date;
• When a database is not cleanly shut down and recovery occurs.

Because of this, Rollup 3 for Exchange 2007 was pulled and you’re advised to uninstall Rollup 3 on Exchange 2007 Mailbox and Transport servers. For more information, consult the post on the Exchange Team’s blog here.

Note that the issue may affect all Mailbox servers, clustered or standalone, so you’re also advised to uninstall RU3 on standalone Mailbox servers. For those with the issue on CCR or SCC setups, it requires reseeding or restoring from backup so plan accordingly.

Looking at the issues with latest Rollups for Exchange 2010 and 2007, it gives to think about the quality control process or if the Exchange team’s priorities perhaps lay somewhere else (Office 365?).