Distribution lists and automatic replies- Exchange 2013 CU3
Running Exchange 2013 CU3 on a VM running Server 2012.
So... I need a distribution list, say membership@domain.com, to have an automatic reply to every email.
I understand I have several ways of achieving this, but I obviously cannot have the actual distribution list reply, as it is not a mailbox.
So I can have a member of the distribution list have a server-rule to "have server reply....".
The issue is:
On Exchange 2013, by default, automatic replies on distribution lists are disabled. If you enable it then the rule gets applied, but along with it every sender will also receive out-of-office notices from every member of the list. That's a pain.
My question is:
Is there a simple way to have the rule (server reply) applied, but without having out-of-office notices going out to the senders?
Thanks for all replies!
So... I need a distribution list, say membership@domain.com, to have an automatic reply to every email.
I understand I have several ways of achieving this, but I obviously cannot have the actual distribution list reply, as it is not a mailbox.
So I can have a member of the distribution list have a server-rule to "have server reply....".
The issue is:
On Exchange 2013, by default, automatic replies on distribution lists are disabled. If you enable it then the rule gets applied, but along with it every sender will also receive out-of-office notices from every member of the list. That's a pain.
My question is:
Is there a simple way to have the rule (server reply) applied, but without having out-of-office notices going out to the senders?
Thanks for all replies!
Murali Reddy
Did you check transport rules?
ASKER
@tmkreddy - Yes, there's no rule for automatic reply in the transport rules.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Chosen solution is a workaround that I also thought of. But will do the job just fine so I guess there's no point in chasing after the un-achievable.