Exchange 2007 Out Of Office (OOF) Not working

H G

unread,

Aug 30, 2010, 8:16:06 PM8/30/10

to

I have a win2k3x64 server SP2 / Exchange 2007 fully updated, and cannot get oof to work.

First off let me say that it did work temporarily, but one day just stopped in during one persons absence. The user goes in and creates their message with no errors (via OWA or Outlook 07). But on a test message, I get no response. On login to OWA, I get the message that OOF is on and do I want to turn it off?

Remote Domains OOF properties are set to allow external & 2003, but I've tired all of them.

Verified it with Shell:

Name DomainName AllowedOOFType
---- ---------- --------------
Default * ExternalLegacy

I don't see any errors in the event viewer, and I've searched all over this site and google with no ideas on what the problem is.

Submitted via EggHeadCafe - Software Developer Portal of Choice
Composite UI Pattern and RAD Development for Data Entry Applications, Part 1
http://www.eggheadcafe.com/tutorials/aspnet/a119aebe-7478-4aaa-b415-12786ec5cf90/composite-ui-pattern-and-rad-development-for-data-entry-applications-part-1.aspx

iann

unread,

Aug 31, 2010, 7:38:24 AM8/31/10

to

> Composite UI Pattern and RAD Development for Data Entry Applications, Part 1http://www.eggheadcafe.com/tutorials/aspnet/a119aebe-7478-4aaa-b415-1...

Can you look at the message tracking logs to see if anything was
actually sent out of the users mailbox. Message tracking is turned on
by default unless you switch it off manually. Does it not work for
only 1 person or for all?

H G

unread,

Aug 31, 2010, 3:11:11 PM8/31/10

to

This happens for any user. I even tested by creating a new user. Here is a copy of the log after I sent a test message:

2010-08-31T19:02:37.324Z,192.168.0.3,DC2,,DC2,"MDB:0754ecd6-a74f-44b9-973f-089be36ad410, Mailbox:b797917f-5024-4b78-b671-6fdbbd0fef4a, Event:248351, MessageClass:IPM.Note.Rules.OofTemplate.Microsoft, CreationTime:2010-08-31T19:02:36.683Z, ClientType:Transport",,STOREDRIVER,SUBMIT,,<8FD55C04967B50488134F...@dc2.guard.corp>,,,,,,,Out of Office: test,<>,,
2010-08-31T19:02:38.120Z,192.168.0.3,DC2,,DC2,"MDB:0754ecd6-a74f-44b9-973f-089be36ad410, Mailbox:b797917f-5024-4b78-b671-6fdbbd0fef4a, Event:248354, MessageClass:IPM.Note.Rules.ExternalOofTemplate.Microsoft, CreationTime:2010-08-31T19:02:36.995Z, ClientType:Transport",,STOREDRIVER,SUBMIT,,<8FD55C04967B50488134F...@dc2.guard.corp>,,,,,,,Out of Office: test,<>,,

Submitted via EggHeadCafe - Software Developer Portal of Choice

Make The WebClient Class follow redirects and get Target Url
http://www.eggheadcafe.com/tutorials/aspnet/70511872-c3aa-4e92-a7d7-dd4b09881af5/make-the-webclient-class-follow-redirects-and-get-target-url.aspx

iann

unread,

Sep 1, 2010, 10:30:27 AM9/1/10

to

On Aug 31, 3:11 pm, H G <hgol...@yahoo.com> wrote:
> This happens for any user. I even tested by creating a new user. Here is a copy of the log after I sent a test message:
>

> 2010-08-31T19:02:37.324Z,192.168.0.3,DC2,,DC2,"MDB:0754ecd6-a74f-44b9-973f-089be36ad410, Mailbox:b797917f-5024-4b78-b671-6fdbbd0fef4a, Event:248351, MessageClass:IPM.Note.Rules.OofTemplate.Microsoft, CreationTime:2010-08-31T19:02:36.683Z, ClientType:Transport",,STOREDRIVER,SUBMIT,,<8FD55C04967B50488134F78C2CE7F837D24A6A3...@dc2.guard.corp>,,,,,,,Out of Office: test,<>,,
> 2010-08-31T19:02:38.120Z,192.168.0.3,DC2,,DC2,"MDB:0754ecd6-a74f-44b9-973f-089be36ad410, Mailbox:b797917f-5024-4b78-b671-6fdbbd0fef4a, Event:248354, MessageClass:IPM.Note.Rules.ExternalOofTemplate.Microsoft, CreationTime:2010-08-31T19:02:36.995Z, ClientType:Transport",,STOREDRIVER,SUBMIT,,<8FD55C04967B50488134F78C2CE7F837D24A6A3...@dc2.guard.corp>,,,,,,,Out of Office: test,<>,,

>
> Submitted via EggHeadCafe - Software Developer Portal of Choice

> Make The WebClient Class follow redirects and get Target Urlhttp://www.eggheadcafe.com/tutorials/aspnet/70511872-c3aa-4e92-a7d7-d...

It looks like the OOF message is being generated. In the log, does it
show that the sender received the OOF message? It seems as if these
messages are being caught somewhere. Was anything changed on your Hub
servers or anything at all relating to email? Usually when something
goes from working to not working, there was a change that caused it.