One of my OWA (2007) users is trying to configure out-of-office replies, but no replies were being generated on incomming e-mail regardless of the source. Now he may not be the only person having issues, just the only one I know of right now. OOF has worked for our users in the past. The only other thing which I know stopped working is that my standard https re-direct for OWA no longer works but I have no clue if this is related. I tested it using my own account and found that mine also wasn't generating responses to incomming e-mails. I ran into a brick wall trying to troubleshoot it, so I simply rebooted the Exchange server and it seemed to work. However, this user has since complained that OOF replies don't work. I tested this for myself and found it true. I disabled his OOF and then re-enabled it; replies were then generated. The next day, no replies again -- testedit myself using an MSN e-mail account I had never once used to e-mail him, but I know from another MSN account I used that the replies were not being filtered. Is there any troubleshooting process I can go through to get to the bottom of this behavior? I haven't found a thing that's useful.

Hi, In Exchange 2007, Administrators can choose to control external OOF capabilities at a per-domain and per-user level. The ExternalOofOptions parameter specifies the option for sending an Out of Office message to external senders. You can use the following values: External/ InternalOnly. The AllowedOOFType parameter can specify which domains type receive out-of-office messages OWA May Disable External Out of Office Rules http://support.microsoft.com/kb/309219 Besides, please note that OOF will check the below scenario before it being sent out. 1. OOF messages will not be sent out in response to server-detected Junk E-mail. If Exchange 2007 detects a message as Junk or if the message sender is in the user's block list, no OOF response is sent. 2. OOF messages are not sent as responses to Internet mailing lists. Exchange 2007 does not send OOF responses for incoming messages with the Precedence:bulk header set. However, if this header is missing, it is possible that OOF responses may be sent out because there is no reliable way of determining that the message was sent to a mailing list. OOF messages are also not sent as responses for incoming messages with the X-Auto-Response-Suppress: OOF header. For OOF troubleshootings,below four possibility may cause the issue. 1. Wrong Autodiscover Service settings. 2. Wrong certificate. 3. Wrong permission settings on the EWS virtual directory. 4. Logged on with another user account. For detail troubleshooting steps you can refer to the below article: http://www.proexchange.be/modules.php?name=News&file=article&sid=686 More information share with you: Prohibit Send in ESM http://support.microsoft.com/kb/248987/en-us Exchange Server 2007 Out of Office (OOF) http://msexchangeteam.com/archive/2006/10/06/429115.aspx Legacy client and Out of Office (OOF) interoperability http://msexchangeteam.com/archive/2007/04/04/437544.aspx