Exchange 2013 auto responder for public folder

I need to configure autoresponders for several public folders within our organization (like the usual 'your mail has been received by our mail server...'). I found some useful information on how to do, and I just configured an autoresponder template and rule in the public folder's properties. Then I read that this isn't enough - I'd have to enable automatic responses in general somewhere within our server configuration.
I found some articles describing that for Exchange < 2013, but I can't find any help for doing this in 2013 ECP :-(
So how (and where) can I enable that feature?

Any help is greatly appreciated.

Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Will SzymkowskiSenior Solution ArchitectCommented:
What you'll need to do is setup theAuto Reply using the Folder Assistant via Outlook Public Folders. You will also not be able to do this via Transport Rules the way you might want to. The closest you will be able to get it Creating a "Reject' rule with a explaination, which does not look very professional.

Those are your options.

You can also check out CodeTwo which has an auto reply tool to accomplish what you are looking for.

Ultimately if none of these are suitable, just delete the public folder and create a mailbox and use the Set-MailboxAutoReplyConfiguration and thats it.


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
mkmkoAuthor Commented:
what I tried to accomplish are hints from some forums and people seem to get it working. I just don't know if it's Exchange 2013 there...
My main problem is that I can't 'convert' the public folder into mail user because of the functionality our users need. With older Exchange versions which have a non-ECP management software, there was a global setting, and I don't find it in 2013.
When I set up the rule on my public folder and write a mail to it, the originating sender will get a '550 5.7.1 RESOLVER.RST.NotAuthorized; not authorized' error instead of the expected auto response.
I think it should work, but there's a setting somewhere which prevents Exchange from autoresponding. A setting I'm unable to find until now.

Will SzymkowskiSenior Solution ArchitectCommented:
Ahh..ok. I get where you are coming from. For this you need to use Get-RemoteDomain | fl *auto*

That will show you if you are allowing forwarding to remote domains.

If the settings are false then you need to use the Set-RemoteDomain cmdlet to change the value.

mkmkoAuthor Commented:
I checked what you suggested. It gives me true for both settings, AutoReplyEnabled and AutoForwardEnabled.

Although, it doesn't work as expected. Maybe I missed something in setting up my autoresponder...

What I did so far:
- Create an e-mail enabled public folder
- Open its properties in Outlook, then folder assistant (sorry, have to translate it freely because I'm on a german Outlook)
- Create a new rule, left all conditions blank (so the rule's applied to 'all')
- Configure a 'reply with template' and wrote a small template, only filling subject and mail body

Outlook then asks me if I'd like to do this for all incoming mails - I answer 'yes'. The rule is listed with 'Status: checked', 'Conditions: All messages' and 'Actions: Reply'.
Folder permissions are set 'as usual', additionally I set the permission for Anonymous to allow creation of elements (as suggested by another forum hint).

What am I missing here?

mkmkoAuthor Commented:
Finally, I didn't get an answer on how to do it natively with Exchange (thus rating this solution as 'B'). So I followed your suggestion and started to test CodeTwo Exchange Rules Pro, which could possibly solve our problem.

Thanks for all suggestions.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.