Article by Pascal L’Huriec, Senior Premier Field Engineer. I recently faced an issue with Out-of-Office (OOF) replies not working properly under Exchange 2007 SP3 with RU3 which was not easy to identify, and I thought it was interesting enough to share with you, along with the associated solution.
The OOF doesn’t trigger for all mailboxes located on a server. Only one server was impacted in a large organization, it was running Exchange 2007 SP3 with RU3 with CAS, Hub and Mailbox roles.
When we moved the impacted mailboxes to another server the OOF worked fine. However, when we moved the mailboxes back to the original impacted server, the OOF worked the first time, but as soon as the client turned-off their OOF, and later turned it on, the OOF stopped triggering.
In addition to that, when turning on or off the OOF from the Outlook 2010 or OWA client, the MAPI property PR_OOF_STATE did not toggle to True or False, as it should.
You can check the PR_OOF_STATE property using MFCMAPI (the Microsoft Exchange Server MAPI Editor) against a mailbox:
You also need to increase diagnostic logging for the following categories and check the application event viewer:
In my situation the following event was reported:
Source: MSExchangeIS Mailbox Store Event ID: 1033 Task Category: Rules Level: Warning Keywords: Classic User: N/A Description: The rule (MSFT:TDX OOF Rules) with sequence number 50 is being ignored because it is disabled.
Source: MSExchangeIS Mailbox Store
Event ID: 1033
Task Category: Rules
The rule (MSFT:TDX OOF Rules) with sequence number 50 is being ignored because it is disabled.
We ran Test-MAPIConnectivity against all mailboxes on that impacted server, as follows:
Get-Mailbox –Server servername | Test-MapiConnectivity (with | fl and | more if you want)
The test was failing for one of the mailboxes. As this mailbox was not needed anymore, we deleted it. Recycle the “Microsoft Exchange Mailbox Assistants” and all OOFs started working fine.
So in this case, a single logon failure on one mailbox caused all OOFs on the server not to trigger. Good reason to clean-up un-needed mailboxes!
Hope you found this helpful!