Hi, A customer hosted on our Exchange 2007 Organisation is claiming that they have been able to auto-forward email/calendar invites to an external email address using Outlook rules. In our Exchange org there is only the one ’Default’ remote domain (domain name set to * ) and the options to allow automatic forward is NOT enabled. To backup my argument I require the following information and was hoping that someone could kindly help with this:- 1. Does a message/calendar item that is auto-forwarded by a rule have a specific x-header set in the mail header that will make it distinguishable from other email/calendar items that have been manually forwarded by the user? 2. If the remote domain is set not to allow automatic forwarding and a user attempted to auto-forward outside of the Exchange organisation would the action (block) taken by the Exchange server be in a log file somewhere? 3. Is there a way to report on any attempts to auto-forward outside of the Exchange Organisation? I hope this makes sense, thank you in advance. Andrew

On Wed, 14 Dec 2011 13:29:03 +0000, ahughes76 wrote: > > >Hi, > >A customer hosted on our Exchange 2007 Organisation is claiming that they have been able to auto-forward email/calendar invites to an external email address using Outlook rules. In our Exchange org there is only the one ?Default? remote domain (domain name set to * ) and the options to allow automatic forward is NOT enabled. To backup my argument I require the following information and was hoping that someone could kindly help with this:- > >1. Does a message/calendar item that is auto-forwarded by a rule have a specific x-header set in the mail header that will make it distinguishable from other email/calendar items that have been manually forwarded by the user? No, it's determined by a MAPI property on the message. Which means that if the message is "auto-forwarded" by a rule from a client using something other than OWA or Outlook MAPI/RPC connections it won't be detected as an auto-forward. >2. If the remote domain is set not to allow automatic forwarding and a user attempted to auto-forward outside of the Exchange organisation would the action (block) taken by the Exchange server be in a log file somewhere? I don't recall. Sorry. The message tracking logs would show the message getting only as far as the categorizer, though. >3. Is there a way to report on any attempts to auto-forward outside of the Exchange Organisation? I don't think so. I don't think the message tracking logs would make a distinction as to the reason a message was stopped if it's just dropped. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

On Wed, 14 Dec 2011 13:29:03 +0000, ahughes76 wrote: > > >Hi, > >A customer hosted on our Exchange 2007 Organisation is claiming that they have been able to auto-forward email/calendar invites to an external email address using Outlook rules. In our Exchange org there is only the one ?Default? remote domain (domain name set to * ) and the options to allow automatic forward is NOT enabled. To backup my argument I require the following information and was hoping that someone could kindly help with this:- > >1. Does a message/calendar item that is auto-forwarded by a rule have a specific x-header set in the mail header that will make it distinguishable from other email/calendar items that have been manually forwarded by the user? No, it's determined by a MAPI property on the message. Which means that if the message is "auto-forwarded" by a rule from a client using something other than OWA or Outlook MAPI/RPC connections it won't be detected as an auto-forward. >2. If the remote domain is set not to allow automatic forwarding and a user attempted to auto-forward outside of the Exchange organisation would the action (block) taken by the Exchange server be in a log file somewhere? I don't recall. Sorry. The message tracking logs would show the message getting only as far as the categorizer, though. >3. Is there a way to report on any attempts to auto-forward outside of the Exchange Organisation? I don't think so. I don't think the message tracking logs would make a distinction as to the reason a message was stopped if it's just dropped. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP