Autoreplies are not working for any users on my Exchange servers. The user can set their OOF message using Outlook 2007, 2010, or OWA without any errors. When I try to send an email to that user in Outlook 2010, I can see the out-of-office message as a mailtip, but I never get the actual out of office message. It isn't working for internal or external senders for any users. I restarted the Microsoft Exchange Mailbox Assistants services on all of my mailbox servers. I tried users on different databases. And I restarted the WWW service on all CAS servers. Correction: It is working for some users and not others. It doesn't seem to matter which database. Some users on a database work and others on that same database don't work. Again, there are no error messages.

Hi, I would like to give some suggestion for you: If you have any anti-virus program please disable it and try. What's your Exchange Version and make sure it is up to date. Verify there's no outlook rule or transport rule can affect this. If all are checked and problem persists please feedback with more information. Thanks.Rowen TechNet Community Support

Hi, I would like to give some suggestion for you: If you have any anti-virus program please disable it and try. What's your Exchange Version and make sure it is up to date. Verify there's no outlook rule or transport rule can affect this. If all are checked and problem persists please feedback with more information. Thanks.Rowen TechNet Community Support

Thanks Rowen. There is no antivirus running on the mailbox servers. We do have antivirus running on the CAS and HUB servers, but on-access scanning is disabled. It only scans inbound email. We are using Exchange 2010 SP1. There are no inbox rules on my test user. After verifying there were no rules, I ran outlook.exe /cleanrules just to be certain. Problem persists this morning.

Thanks Rowen. There is no antivirus running on the mailbox servers. We do have antivirus running on the CAS and HUB servers, but on-access scanning is disabled. It only scans inbound email. We are using Exchange 2010 SP1. There are no inbox rules on my test user. After verifying there were no rules, I ran outlook.exe /cleanrules just to be certain. Problem persists this morning.

Rebooted all mailbox, cas, and hub servers. Still no auto-replies from some users.

Rebooted all mailbox, cas, and hub servers. Still no auto-replies from some users.

Lets check few settings. 1- Setup OOF on a user mailbox 2- Login to that mailbox using Mfcmapi In the main window choose; Session-> Logon and Display Store Table Select the Outlook mail profile to logon to when prompted. If you do not recognize this dialog, simply press OK to load you default Outlook mail profile. Youll now see a list of your configured message stores in your mail profile. Select your mailbox by looking at the Display Name column. In the pane below, some properties will get loaded. Look at the Property Name(s) column and select the entry called; PR_OOF_STATE - See whether its set to false or True To set to True. Double click the entry to Select the check box in front of Boolean. Press OK to close the dialog. Log off your session via; Session-> Logoff 3- Make sure there are no corrupt OOF rule present. 4- Make sure you have the system mailbox and System attendant mailbox as well. 5- Send a test message and see if you receive the OOF message Please 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. Hasnain Shaikh| My blogs: http://messagingserversupport.com

Lets check few settings. 1- Setup OOF on a user mailbox 2- Login to that mailbox using Mfcmapi In the main window choose; Session-> Logon and Display Store Table Select the Outlook mail profile to logon to when prompted. If you do not recognize this dialog, simply press OK to load you default Outlook mail profile. Youll now see a list of your configured message stores in your mail profile. Select your mailbox by looking at the Display Name column. In the pane below, some properties will get loaded. Look at the Property Name(s) column and select the entry called; PR_OOF_STATE - See whether its set to false or True To set to True. Double click the entry to Select the check box in front of Boolean. Press OK to close the dialog. Log off your session via; Session-> Logoff 3- Make sure there are no corrupt OOF rule present. 4- Make sure you have the system mailbox and System attendant mailbox as well. 5- Send a test message and see if you receive the OOF message Please 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. Hasnain Shaikh| My blogs: http://messagingserversupport.com

Thanks, Hasnain. I started Outlook using /cleanrules and /cleanserverrules. I checked PR_OOF_STATE using mfcmapi, and it was already set to True. I changed it to false and back to true again, just to be sure. It still doesn't work. Then I logged into Outlook 2010 and turned my oof rule off and turned it back on again. Made sure it was on for internal and external. Still doesn't work.

Hello, I think you need to check your configuration for OOF messages, Open Exchange Management Console, expand Organization configuration then click on Hub Transport then on Right hand side click on Remote domains-> right click Default & click properties, see what OOF settings you have enabled. looks like you need to change them. let me know, Sandeep

Hello, I think you need to check your configuration for OOF messages, Open Exchange Management Console, expand Organization configuration then click on Hub Transport then on Right hand side click on Remote domains-> right click Default & click properties, see what OOF settings you have enabled. looks like you need to change them. let me know, Sandeep

Thanks, Sandeep. I don't think my OOF configuration is the problem. OOF replies works for most of my users and worked for all of them until just recently. The title of my post is misleading. I initially thought the problem was with *all* users, but it turns out that OOF is not working for only some of the users. I went ahead and double-checked the OOF setting on the default Remote domain anyway, and it is correctly set.

Thanks, Sandeep. I don't think my OOF configuration is the problem. OOF replies works for most of my users and worked for all of them until just recently. The title of my post is misleading. I initially thought the problem was with *all* users, but it turns out that OOF is not working for only some of the users. I went ahead and double-checked the OOF setting on the default Remote domain anyway, and it is correctly set.

I have enabled/disabled the oof rules on one broken user, moved the mailbox to a different DB, moved the DB to a different server, sent from external and internal addresses, and none of that has had an effect. I'm pretty sure that if I deleted the mailbox and created a new one, the OOF would start working. I've created several new accounts and OOF works for all of them. This isn't a practical solution, however. It would create too much havoc for my end users. Any other ideas out there?

I have enabled/disabled the oof rules on one broken user, moved the mailbox to a different DB, moved the DB to a different server, sent from external and internal addresses, and none of that has had an effect. I'm pretty sure that if I deleted the mailbox and created a new one, the OOF would start working. I've created several new accounts and OOF works for all of them. This isn't a practical solution, however. It would create too much havoc for my end users. Any other ideas out there?

I also deleted all oof rules using mfcmapi, re-created the auto-reply, and ran start-managedfolderassistant against a broken mailbox. Still no go.

I also deleted all oof rules using mfcmapi, re-created the auto-reply, and ran start-managedfolderassistant against a broken mailbox. Still no go.

Hi You can try run a New-MailboxRepairRequest against the broken mailbox. This is like running isinteg but only the single mailbox needs to be offline, the rest of the database stays online. Details and instructions here: http://eightwone.com/2010/06/14/goodbye-isinteg-hello-new-mailboxrepairrequest/ Cheers, Steve

Hi You can try run a New-MailboxRepairRequest against the broken mailbox. This is like running isinteg but only the single mailbox needs to be offline, the rest of the database stays online. Details and instructions here: http://eightwone.com/2010/06/14/goodbye-isinteg-hello-new-mailboxrepairrequest/ Cheers, Steve

Thanks, Steve. I haven't seen that command before. I ran it against my mailbox and found the "online integrity check for request....completed successfully" entry in the event log. Still not working. I disabled/enabled the oof and sent emails from internal and external. No auto-replies.

Thanks, Steve. I haven't seen that command before. I ran it against my mailbox and found the "online integrity check for request....completed successfully" entry in the event log. Still not working. I disabled/enabled the oof and sent emails from internal and external. No auto-replies.

No worries, it was worth a shot I guess.

No worries, it was worth a shot I guess.

Got it! Note the database on which the broken mailbox resides and note the server on which that database is mountedDisable (rt-click --> "Disable", not "Remove") the mailbox in EMC.Run Clean-MailboxDatabase <database>Go to disconnected mailboxes and connect to the appropriate serverReconnect the mailbox to the user accountTurn the auto-reply off and back on Viola! It works again!

Thanks Reprac, it worked

Thanks Reprac, it worked