So a weird issue just started where all my users in my organization can set their OOF but no replies are sent either internally or externally. No Updates have been rolled out recently and all other Exchange Services are running great. Here is a general idea of my environment Win2k3, R2 64-Bit SP2 Exchange 2007 Enterprise, SP2 Clients running Outlook 03 and 07 OWA, Autodiscover and OAB configured and checked/verified SMTP Smarthost (checked logs to make sure emails aren't in queue. I have verified that all users that have Turned on OOF are getting email to their mailbox before and after setting OOF. I have reset /clientrules and /serverrules as well and even used MFCMapi on a test mailbox to try to fix the problem if it was client related with no avail. This environment was transitioned from 03 to 07 and I have recently noticed undelivarable mail in the 'unreachable domain' from publicfoldersdatabase@contoso.com with "no route to mailbox database" in the NDR referencing the old 03 Exchange server. I don't think that would effect OOF but just adding that info. Any ideas where I should start..? I have browsed the web and even this forum this Post: Exchange 2007 Out of office not sending mails (internal and ... but my issue seems different than most OR the suggestions have not worked or don't apply. Thanks, Dee

I spole too son. This post post below turned me in the right direction for my issue: ---------------------- Well it's finally solved, I called MS tech support and logged a ticket. What we did is created a new mailbox datastore and moved all the mailboxes to the new store. After that, we removed the old mailbox store. It appears Exchange verifies and fixes any corrupt attributes on the mailbox, or so I was told. Hope it helps someone else! Thanks for all that tried to help" ----------------------- I tried this on a test mailbox that was having issues and was in an original datastore. Once I created a new store, turned OOF off on the mailbox, moved said mailbox and then turned OOF back on, I began to get OOF messages again. This is bitter sweet news as I'm stoked that it worked but now I have to think about moving hundreds of mailboxes over to 4 seperate stores. Here is another question. Does anyone know what attribute gets corrupt in the mailbox to cause this? It would be great to be able to run a script and fix it that way rather than create new stores and migrate mailboxes for hundreds of user. Any data/attribute cleaning tools that can automate this on exchange Dee

Hi, As I understand, Storage Group is just a container. I think the real corruption is on database. So I suggest you doing a database repair with Eseutil tool. For Exchange 2007, by default, Eseutil is located in is C:\Program Files\Microsoft\Exchange Server. However, you can just open a Command Prompt window and type Eseutil. To repair a corrupted or otherwise damaged database, run Eseutil with the /P switch. For example , to repair a database called Mailbox Database.edb located in E:\Program Files\Microsoft\Exchange Server\Mailbox\First Storage Group. You would need to type: Eseutil /P “E:\Program Files\Microsoft\Exchange Server\Mailbox\First Storage Group\Mailbox Database.edb” More information about Eseutil http://technet.microsoft.com/en-us/library/aa998249(EXCHG.80).aspxPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

ESEUTIL is your absolute last tool you should use. doing a repair you must first take the DB offline and it will cause interuption for users for as long you run eseutil (it could take many hours or even days) And you'renot sure the repair will do any good either. lasse at humandata dot se, http://anewmessagehasarrived.blogspot.com