Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Tuesday, March 27, 2018 1:14 PM
Hi All,
As I found out recently my company OOF doesn't work externally. I can see the internal OOF when sending emails ok in Outlook.
I've checked 'remotedomain' settings and these were not set, I've updated, AutoReplyEnabled and AutoForwardEnabled to True. AllowedOOFtype is set to ExternalLegacy. After updating these settings, oof still doesn't work. Do I need to restart exchange for these updates to work? Any specific service?
Microsoft Analyzer passes all tests under Synchronization, Notification, Availability, and Automatic Replies.
Not sure where to look now. Its a fairly fresh setup, recently upgraded from 2003(where oof worked fine), no global rules and everything else works fine. Cant see anything stuck in the queue viever, if I run Get-MessageTrackingLog I can see the Automatic Reply under EventId - Receive and Source - Mailboxrule.
I cant see anything obvious in the logs, but there is so many of them that I might be missing something here.
I've tried sending email to myself from 4 different external email accounts, including gmail and didn't receive oof to any of them.
Any ideas?
All replies (5)
Friday, May 4, 2018 4:56 PM âś…Answered
Finally solved it and this was a permissions issue and kinda MS bug. This, as far as I know, only applies to scenarios where exchange was updated from exchange 2003 to 2013/2016 which was exactly what happened in our case. I've upgraded exchange 2003 to 2016 last year.
Permissions needs changing on all receive connectors in adsiedit. Under security on each receive connector I had to deselect Deny on 'Accept Forest Headers and Accept Organization Headers' for ExchangeLegacyInterOp group which are needed for OOF to work. As soon as I did that and restarted Exchange Transport Service, OOF started to work.
Hope this helps someone! :)
Wednesday, March 28, 2018 8:39 AM
Hi Katar,
Have you tried using OWA to send external OOF message ? If still no work, try to check the following:
Please run the following command to set the AllowedOOFType parameter of your domains to External:
Get-RemoteDomain | Set-RemoteDomain -AllowedOOFType External
Then, run the following command to check your EWS settings on Exchange servers:
Get-WebServicesVirtualDirectory |fl Name,Server,*ternalUrl
Meantime, in outlook, test E-mail AutoConfiguration (Hold "Ctrl" and Right Click Outlook-icon in the taskbar), check OOF URL record whether it shows the externalURL in EWS settings.(If externalUrl is null, it will show internalURl instead)
Best Regards,
Niko Cheng
Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact [email protected].
Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.
Thursday, March 29, 2018 8:47 AM
Hi Niko,
I've changed ooftype to external - still not working. The external EWS wasn't setup so I've updated it(same as internal) and its now available externally and I can access it ok. Shows correctly within test e-mail autoconfiguration utility too.
Completely lost here :)
One thing I've noticed though, if I check messagetrackinglog all the visible auto replies are under source mailboxrule so I've tried creating an oft template file and set a rule that upon receiving an email from my external email I'd send an automatic email back. I get an error straight away 'Rules in Error - Cannot reply to message' so I think this could be somehow related, just not sure how.
If I set oof from OWA it still doesn't work.
Tuesday, April 3, 2018 3:05 AM
if I run Get-MessageTrackingLog I can see the Automatic Reply under EventId - Receive and Source - Mailboxrule.
Hi Katar,
As you mentioned above, it seems there is a mailbox inbox rule that participates in an automatic reply process. Please check the inbox in OWA and see if there is such a rule, if so, disable the rule and check again.
Best Regards,
Niko Cheng
Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact [email protected].
Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.
Thursday, October 4, 2018 1:47 PM
Hi Can you give me the procedure on where to find this Permissions to change receive connector in adsiedit?
Some images or links to very useful to try
Permissions needs changing on all receive connectors in adsiedit. Under security on each receive connector I had to deselect Deny on 'Accept Forest Headers and Accept Organization Headers' for ExchangeLegacyInterOp group which are needed for OOF to work. As soon as I did that and restarted Exchange Transport Service, OOF started to work.
Regards
Sathish