How to find what domains an exchange server tries to deliver mail   

I've been getting the below message when trying to send email to domain that 
used to be hosted by our company.  Externaldomain.com was at one time handled 
by our exchange server but is no longer.  I can't find any references to it 
under recipient policies where all the other domains the exchange server 
delivers mail to is listed.  Does anybody have a list of other places I might 
check to see why it is trying to deliver this mail locally instead of 
delivering it to our smtp connector for external delivery?

bob@externaldomain.com on 4/25/2006 10:21 AM
            The e-mail account does not exist at the organization this 
message was sent to.  Check the e-mail address, or contact the recipient 
directly to find out the correct address.
            <myexchangeserver.mydomain.com #5.1.1>

date: Tue, 25 Apr 2006 07:35:02 -0700   author:   Michael Leighty

Re: How to find what domains an exchange server tries to deliver mail   

How about in the user properties?

-- 
--------
Hope It Helps!

dw

_______________________________
Don Wilwol
Distributed Application Technologies.
dwilwol(DELETE)@datbusiness.com
http://spaces.msn.com/members/wilwol/
www.datbusieness.com
www.skyphere.com

"Michael Leighty"  wrote in 
message news:0922D96F-11DA-4836-A77E-BFEA81FF1781@microsoft.com...
> I've been getting the below message when trying to send email to domain 
> that
> used to be hosted by our company.  Externaldomain.com was at one time 
> handled
> by our exchange server but is no longer.  I can't find any references to 
> it
> under recipient policies where all the other domains the exchange server
> delivers mail to is listed.  Does anybody have a list of other places I 
> might
> check to see why it is trying to deliver this mail locally instead of
> delivering it to our smtp connector for external delivery?
>
> bob@externaldomain.com on 4/25/2006 10:21 AM
>            The e-mail account does not exist at the organization this
> message was sent to.  Check the e-mail address, or contact the recipient
> directly to find out the correct address.
>            <myexchangeserver.mydomain.com #5.1.1>
>

date: Tue, 25 Apr 2006 11:06:39 -0400   author:   dw donWilwol@(EMAIL)yahoo.com

Re: How to find what domains an exchange server tries to deliver m   

There aren't any user properties that would affect delivery of messages to an 
entire domain.  Plus it's not just affecting a single user or group of users.

date: Tue, 25 Apr 2006 08:30:02 -0700   author:   Michael Leighty

Re: How to find what domains an exchange server tries to deliver m   

If you had a recipient policy set up, and then unchecked the "allow 
recipient policy to set email" and then removed the policy, the email would 
still be set in the user properties to the old domain. If the users email is 
set incorrectly, email will not be delivered.

-- 
--------
Hope It Helps!

dw

_______________________________
Don Wilwol
Distributed Application Technologies.
dwilwol(DELETE)@datbusiness.com
http://spaces.msn.com/members/wilwol/
www.datbusieness.com
www.skyphere.com

"Michael Leighty"  wrote in 
message news:B9DD0503-EE58-4ED1-8AD5-C45A7184B2AC@microsoft.com...
> There aren't any user properties that would affect delivery of messages to 
> an
> entire domain.  Plus it's not just affecting a single user or group of 
> users.

date: Tue, 25 Apr 2006 13:00:22 -0400   author:   dw donWilwol@(EMAIL)yahoo.com

Re: How to find what domains an exchange server tries to deliver mail   

Check to make sure that you don't have any internal MX records that point 
back to your environment.  Also, look at the address space tabs of any SMTP 
connectors you may have defined.

Eric Bockelman
Principal IT Infrastructure Specialist
Windows Platform Engineering
Symantec Corporation



"Michael Leighty"  wrote in 
message news:0922D96F-11DA-4836-A77E-BFEA81FF1781@microsoft.com...
> I've been getting the below message when trying to send email to domain 
> that
> used to be hosted by our company.  Externaldomain.com was at one time 
> handled
> by our exchange server but is no longer.  I can't find any references to 
> it
> under recipient policies where all the other domains the exchange server
> delivers mail to is listed.  Does anybody have a list of other places I 
> might
> check to see why it is trying to deliver this mail locally instead of
> delivering it to our smtp connector for external delivery?
>
> bob@externaldomain.com on 4/25/2006 10:21 AM
>            The e-mail account does not exist at the organization this
> message was sent to.  Check the e-mail address, or contact the recipient
> directly to find out the correct address.
>            <myexchangeserver.mydomain.com #5.1.1>
>

date: Tue, 25 Apr 2006 13:04:41 -0400   author:   Eric Bockelman

Re: How to find what domains an exchange server tries to deliver m   

Eric,

I checked dns records by doing an nslookup and found their were no mx 
records pointing to back to us.  They point to the external ip address that 
they should.  The address space for the smtp connector is set to * so that 
all mail should be sent to the smart host who delivers the mail.  The mail 
isn't reaching the smart host however because exchange believes it can still 
deliver this mail locally.

Don,

I'm a little confused by your post.  I assume teh check box you are 
referring to is the "automatically update email addresses based on recipient 
policy".  We no longer have any reference to the external domain in our 
recipient policies.  So are you saying that if there is one user who has the 
above box unchecked and still has an address at externaldomain.com that this 
will cause exchange to try and deliver all mail for the entire domain locally 
instead of to the smtp connector to the smarthost.  Because I can make up any 
address joe@externaldomain.com or ted@externaldomain.com and it will still 
try to deliver the mail locally on the exchange server.  Is it really 
possible that one user's properties can affect mail delivery for  the whole 
domain?

date: Tue, 25 Apr 2006 10:21:03 -0700   author:   Michael Leighty

Re: How to find what domains an exchange server tries to deliver m   

Have you verified that your smart host doesn't have a rule that points the 
message right back at you?  (You can telnet to port 25 and craft a message 
to the domain in question, or message track the one you already sent to see 
if it traversed the connector.)


"Michael Leighty"  wrote in 
message news:21DEB3F9-2508-4669-8E2F-32C1A444705F@microsoft.com...
> Eric,
>
> I checked dns records by doing an nslookup and found their were no mx
> records pointing to back to us.  They point to the external ip address 
> that
> they should.  The address space for the smtp connector is set to * so that
> all mail should be sent to the smart host who delivers the mail.  The mail
> isn't reaching the smart host however because exchange believes it can 
> still
> deliver this mail locally.
>
> Don,
>
> I'm a little confused by your post.  I assume teh check box you are
> referring to is the "automatically update email addresses based on 
> recipient
> policy".  We no longer have any reference to the external domain in our
> recipient policies.  So are you saying that if there is one user who has 
> the
> above box unchecked and still has an address at externaldomain.com that 
> this
> will cause exchange to try and deliver all mail for the entire domain 
> locally
> instead of to the smtp connector to the smarthost.  Because I can make up 
> any
> address joe@externaldomain.com or ted@externaldomain.com and it will still
> try to deliver the mail locally on the exchange server.  Is it really
> possible that one user's properties can affect mail delivery for  the 
> whole
> domain?

date: Tue, 25 Apr 2006 13:45:16 -0400   author:   Eric Bockelman

Re: How to find what domains an exchange server tries to deliver m   

No. If the email address in the user properties does not show the old 
domain, and the smtp address is set correctly in the user properties you 
should be ok. What I meant was if all users were updated and then set to not 
update again, they may still have the old properties.

If the users now have mailboxes hosted somewhere else, delete their 
mailboxes off the exchange server and mail should start moving. If users 
have a mailbox, Exchange will assume that's where mail is suppose to go, 
even though the address is wrong. In other words, if you create a mail 
enabled user, and add his real smtp address, exchange will put the mail in 
his mailbox, even though it should go elsewhere.

-- 
--------
Hope It Helps!

dw

_______________________________
Don Wilwol
Distributed Application Technologies.
dwilwol(DELETE)@datbusiness.com
http://spaces.msn.com/members/wilwol/
www.datbusieness.com
www.skyphere.com

"Michael Leighty"  wrote in 
message news:21DEB3F9-2508-4669-8E2F-32C1A444705F@microsoft.com...
> Eric,
>
> I checked dns records by doing an nslookup and found their were no mx
> records pointing to back to us.  They point to the external ip address 
> that
> they should.  The address space for the smtp connector is set to * so that
> all mail should be sent to the smart host who delivers the mail.  The mail
> isn't reaching the smart host however because exchange believes it can 
> still
> deliver this mail locally.
>
> Don,
>
> I'm a little confused by your post.  I assume teh check box you are
> referring to is the "automatically update email addresses based on 
> recipient
> policy".  We no longer have any reference to the external domain in our
> recipient policies.  So are you saying that if there is one user who has 
> the
> above box unchecked and still has an address at externaldomain.com that 
> this
> will cause exchange to try and deliver all mail for the entire domain 
> locally
> instead of to the smtp connector to the smarthost.  Because I can make up 
> any
> address joe@externaldomain.com or ted@externaldomain.com and it will still
> try to deliver the mail locally on the exchange server.  Is it really
> possible that one user's properties can affect mail delivery for  the 
> whole
> domain?

date: Tue, 25 Apr 2006 15:13:30 -0400   author:   dw donWilwol@(EMAIL)yahoo.com