I am migrating to Exchange 2013 from a mail software that used a blacklist to determine when not to send auto-responses (the Exchange equivalent to OOF messages). Here is what my blakclist looks like: Mailer-Daemon@* bounce@* postmaster@* X-Spam-Flag: YES X-Mailing-List: * Mailing-List: * Precedence: bulk Precedence: list Precedence: junk Return-Path: <> According to this thread, not sending OOF messages when an e-mail contains the "Precedence: bulk" header is built in to Exchange, which is well and good, but I believe we have members on a list that doesn't use that header, but some other one from this list instead. I see enough OOF messages on that list to assume at least part of them come from Exchange, and I don't want to be a part of that problem.

Hi PRDIT, I'm afraid you cannot create custom OOF rule via Exchange native cmdlet Set-MailboxAutoReplyConfiguration http://technet.microsoft.com/en-us/library/dd638217.aspx Maybe you can try to use EWS, for example: Setting OOF Messages http://msdn.microsoft.com/en-us/library/exchange/aa563356(v=exchg.140).aspx I would also suggest you seek the solution in the Development forum: http://social.technet.microsoft.com/Forums/en-US/exchangesvrdevelopment/threads Frank Wang TechNet Community Support

Hi PRDIT, I'm afraid you cannot create custom OOF rule via Exchange native cmdlet Set-MailboxAutoReplyConfiguration http://technet.microsoft.com/en-us/library/dd638217.aspx Maybe you can try to use EWS, for example: Setting OOF Messages http://msdn.microsoft.com/en-us/library/exchange/aa563356(v=exchg.140).aspx I would also suggest you seek the solution in the Development forum: http://social.technet.microsoft.com/Forums/en-US/exchangesvrdevelopment/threads Frank Wang TechNet Community Support

Hi PRDIT, I'm afraid you cannot create custom OOF rule via Exchange native cmdlet Set-MailboxAutoReplyConfiguration http://technet.microsoft.com/en-us/library/dd638217.aspx Maybe you can try to use EWS, for example: Setting OOF Messages http://msdn.microsoft.com/en-us/library/exchange/aa563356(v=exchg.140).aspx I would also suggest you seek the solution in the Development forum: http://social.technet.microsoft.com/Forums/en-US/exchangesvrdevelopment/threads Frank Wang TechNet Community Support

Hi PRDIT, I'm afraid you cannot create custom OOF rule via Exchange native cmdlet Set-MailboxAutoReplyConfiguration http://technet.microsoft.com/en-us/library/dd638217.aspx Maybe you can try to use EWS, for example: Setting OOF Messages http://msdn.microsoft.com/en-us/library/exchange/aa563356(v=exchg.140).aspx I would also suggest you seek the solution in the Development forum: http://social.technet.microsoft.com/Forums/en-US/exchangesvrdevelopment/threads Frank Wang TechNet Community Support

Hi PRDIT, I'm afraid you cannot create custom OOF rule via Exchange native cmdlet Set-MailboxAutoReplyConfiguration http://technet.microsoft.com/en-us/library/dd638217.aspx Maybe you can try to use EWS, for example: Setting OOF Messages http://msdn.microsoft.com/en-us/library/exchange/aa563356(v=exchg.140).aspx I would also suggest you seek the solution in the Development forum: http://social.technet.microsoft.com/Forums/en-US/exchangesvrdevelopment/threads Frank Wang TechNet Community Support

Would a Transport Rule not meet your needs? "Automatic Reply" is a message type one could act on. Mike Crowley | MVP My Blog -- Planet Technologies

Would a Transport Rule not meet your needs? "Automatic Reply" is a message type one could act on. Mike Crowley | MVP My Blog -- Planet Technologies

Would a Transport Rule not meet your needs? "Automatic Reply" is a message type one could act on. I hadn't thought of a transport rule. It sounds like it would, but alas, it won't. The issue with a transport rule is I need to prevent an outbound (OOF) e-mail based on information in the header of the inbound e-mail that triggered it. Best I can tell, there is no way to do that with a transport rule.

Would a Transport Rule not meet your needs? "Automatic Reply" is a message type one could act on. I hadn't thought of a transport rule. It sounds like it would, but alas, it won't. The issue with a transport rule is I need to prevent an outbound (OOF) e-mail based on information in the header of the inbound e-mail that triggered it. Best I can tell, there is no way to do that with a transport rule.

I think there is something like an "In-Reply-To <messageid>" header for email replies. I don't know if the OOF preservs this; never looked. Might be worth thinking through. Mike Crowley | MVP My Blog -- Planet Technologies

I think there is something like an "In-Reply-To <messageid>" header for email replies. I don't know if the OOF preservs this; never looked. Might be worth thinking through. Mike Crowley | MVP My Blog -- Planet Technologies

I think there is something like an "In-Reply-To <messageid>" header for email replies. I don't know if the OOF preservs this; never looked. Might be worth thinking through. I think that would require custom coding of some sort. Thank you for trying to help, but I am going to mark Frank's post as the answer and scratch this off as a "feature" of Microsoft's OOF implementation. Presumably my users could set up rules for their auto-replies, but I don't want to rely on the users. If I am wrong regarding development, or if there is a way to enforce auto-reply rules across a group of users (or an organization), I would appreciate if someone could let me know. Otherwise, I have a couple of bigger fish to fry.

I think there is something like an "In-Reply-To <messageid>" header for email replies. I don't know if the OOF preservs this; never looked. Might be worth thinking through. I think that would require custom coding of some sort. Thank you for trying to help, but I am going to mark Frank's post as the answer and scratch this off as a "feature" of Microsoft's OOF implementation. Presumably my users could set up rules for their auto-replies, but I don't want to rely on the users. If I am wrong regarding development, or if there is a way to enforce auto-reply rules across a group of users (or an organization), I would appreciate if someone could let me know. Otherwise, I have a couple of bigger fish to fry.

I think there is something like an "In-Reply-To <messageid>" header for email replies. I don't know if the OOF preservs this; never looked. Might be worth thinking through. I think that would require custom coding of some sort. Thank you for trying to help, but I am going to mark Frank's post as the answer and scratch this off as a "feature" of Microsoft's OOF implementation. Presumably my users could set up rules for their auto-replies, but I don't want to rely on the users. If I am wrong regarding development, or if there is a way to enforce auto-reply rules across a group of users (or an organization), I would appreciate if someone could let me know. Otherwise, I have a couple of bigger fish to fry.