My compagny have multiple exchange server, front-end and back-end server. We are owning our domain name "abc.com" we have setup our exchange servers to anwser abc.com (primary address) and abc.local. Every user is getting this setting when we create a new mailbox. Everything work fine. Few month ago, we've start a project with google mail, to transfere our mail system to their system. We are now using Exchange 2003 for most of the internal user and google mail on some specific user for test purpose. What we've done for user that have been migrate to Google Mail, we have create a new contact and setup the forward option in the user exchange setting. The contact point to the google mail address user@gm.abc.com. The mx record gm.abc.com pointing to google mail servers, which means that google mail hosting this domain name. From their, we dont have lot of problem. but few weeks ago, our architec decide to change the way to create user in the AD, instend of using contact to forward mail to google, i've put the gm.abc.com directly in the user smtp address field. What I want to know is, by doing this we doing Spoofing are worst right ? Can someone confirm my thinks that causing us lot of internal and external problems. Thanks folk sorry for the long description i want to be clear

I dont think that this scenario is working. I would suggest to configure the forwarding attribute in Exchange Console - Recipient configuration.regards Thomas Paetzold visit my blog on: http://sus42.wordpress.com

Not spoofing, but you may be running into an old sender ID issue when you Exchange does forwarding to external contacts. What specific issues are you running into? Messages that are sent through Exchange 2003 to an external messaging server are blocked by Sender ID checking http://support.microsoft.com/kb/915863James Chong MCITP | EA | EMA; MCSE | M+, S+ Security+, Project+, ITIL msexchangetips.blogspot.com

Not spoofing, but you may be running into an old sender ID issue when you Exchange does forwarding to external contacts. What specific issues are you running into? Messages that are sent through Exchange 2003 to an external messaging server are blocked by Sender ID checking http://support.microsoft.com/kb/915863 James Chong MCITP | EA | EMA; MCSE | M+, S+ Security+, Project+, ITIL msexchangetips.blogspot.com Two issue that we have: 1- Sometime, a user that is using outlook with exchange account, send e-mail to users that is configured with the smtp address "user@gm.abc.com" fall in the exchange queue the delivery faild and our server try, retry and retry to send this email... in vain. Next time we try to send to same recipents it work perfectly. 2- our spam report are sent by mcafee@mcafee.com to user@abc.com hit our exchange server, the user have a forwarding contact to user@gm.abc.com but stay in mail queue till the mail expires. i hope it's clair. Actually, my first concern is that enter a public SMTP Address, we don't own, into the user smtp address is insane.

On Fri, 25 Feb 2011 18:24:40 +0000, Zyaldo wrote: > > >Not spoofing, but you may be running into an old sender ID issue when you Exchange does forwarding to external contacts. What specific issues are you running into? > >Messages that are sent through Exchange 2003 to an external messaging server are blocked by Sender ID checking http://support.microsoft.com/kb/915863 >James Chong MCITP | EA | EMA; MCSE | M+, S+ Security+, Project+, ITIL msexchangetips.blogspot.com > >Two issue that we have: > >1- Sometime, a user that is using outlook with exchange account, send e-mail to users that is configured with the smtp address "user@gm.abc.com" fall in the exchange queue the delivery faild and our server try, retry and retry to send this email... in vain. Next time we try to send to same recipents it work perfectly. Have a look at your SMTP send protocol log and see what the receiving server is sending as a status. Knowing what's going on will help you discover why your e-mail is not being delivered. >2- our spam report are sent by mcafee@mcafee.com to user@abc.com hit our exchange server, the user have a forwarding contact to user@gm.abc.com but stay in mail queue till the mail expires. > >i hope it's clair. > >Actually, my first concern is that enter a public SMTP Address, we don't own, into the user smtp address is insane. Insane? Maybe. But it's not that uncommon. It sure a heck makes delivering NDRs to the sender almost impossible. :-) --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

Hi, Please understand that the contact object is different from the mailbox enabled user, the contact object uses the targetAddress to route the email. For the mailbox enabled user which stamped with the public email address, it will be recongized as the internal user. Thanks AllenAllen Song