Hello i have an exchange 2010 envrioment and one of the managers who is assigned to a BCC transport rule to be included in every email sent/recieved... now anyone that sends to someone in our organization is getting the auto response from the manager on vacation... how do we prevent this ?

Other than disabling the OOF message? If the manager really wants to see all these messages, I would BCC them to a shared mailbox or mail-enabled PF instead of his main mailbox.

If the motive is to have every email copy with manager you can consider creating a Journal rule. I would recommend creating a separate shared mailbox for journaling all these emails and provide manager access to that mailbox.

hi, I also recommend that you should use shared mailbox. Then you can use another transport rule to prevent the oof message. The rule should like this: sent to "your shared mailbox" and if the message type is "auto reply" delete the message hope can help you thanks, CastinLu TechNet Community Support

The manager's dont want to have another mailbox they need to check its been working this way for a while only since 2003 -> 2010 migration has this been an issue :S cant disable the OOF cause clients email her on a daily basis and cant add a shared mailbox or mail-enabled PF cause they dont want to change the way things are... must be another work around to delete the OOF message that is not sent directly to her

The manager's dont want to have another mailbox they need to check its been working this way for a while only since 2003 -> 2010 migration has this been an issue :S cant disable the OOF cause clients email her on a daily basis and cant add a shared mailbox or mail-enabled PF cause they dont want to change the way things are... must be another work around to delete the OOF message that is not sent directly to her But it is directly sent to her - via the BCC.

is there a way to make a rule saying that anything thats not sent directly to her meaning TO: Manager and not using BCC. Is this possible?

How did you accomplish this in Exchange 2003?

I didn't a previous company took care of it and it hasn't been an issue (from what i was told) only after i did the migration and set up all the requested rules that i found this happening