Mail still going to old exchange RRS feed

  • Question

  • For some reason, SOME email still goes to the old exchange server (in a completely different location, different building, etc.) I changed the DNS records, and there is NOTHING pointing to the old server in DNS at all. It has been about a week and a half now. my TTL on the records is a half hour. 


    Any ideas? Thank you

    Wednesday, February 16, 2011 2:10 PM

All replies

  • Can you provide an example scenario? Is this external email, internal email, intermittent? Was the old exchange server split off from the domain etc?
    James Chong MCITP | EA | EMA; MCSE | M+, S+ Security+, Project+, ITIL msexchangetips.blogspot.com
    Wednesday, February 16, 2011 2:42 PM
  • Sure! Whats going on is this.


    Its both internal and external. We just set up an internal exchange server. For the last 10 years we have had our email coming from the boss's friends exchange. I changed all of the DNS records (as mentioned above) to not even attempt to look at his. We still get emails that go straight to his and not ours. An internal billing girl sent me an email (was received by our server). I responded. She responded a few minutes later, it was directed to the other guys server. 


    This is so crazy to me.

    Wednesday, February 16, 2011 4:24 PM
  • So internal user responded to your email and it went to the old Exchange server? Is the old Exchange on your network? Is this Exchange 2007? Can you go into EMC, org config, Hub Transport, Accepted Domains and verify that your domain is set to Authoratative? Also Check the send connector tab to see if you have a send connector going to the other Exchange server?


    James Chong MCITP | EA | EMA; MCSE | M+, S+ Security+, Project+, ITIL msexchangetips.blogspot.com
    Wednesday, February 16, 2011 4:36 PM
  • All of our exchange (ours and his) are 07. The domain is not authoritive anymore on his. All DNS points to ours. Everything is set on ours to be directed only to ours. We can do in all the tabs and were authoritive. No send connnectors are going to his.
    Thursday, February 17, 2011 1:43 PM
  • Was yours and his Exchange server part of the same Domain and Exchange org?
    James Chong MCITP | EA | EMA; MCSE | M+, S+ Security+, Project+, ITIL msexchangetips.blogspot.com
    Thursday, February 17, 2011 3:04 PM
  • are you using outlook? then check your server settings on outlook.

    is this problem happening for random sender? or some particular sender?

    check dns resolution from the sender's computers.

    Saumyarup Sengupta CCNA, CCNP, MCSE, CWNA, CCSP, CCSA Technical Trainer HCL Career Development Center Kolkata
    Friday, February 18, 2011 7:17 AM
  • Hi,


    Is the old Exchange server and the new one in the same domain? Have you migrated all users to the new Exchange server?


    At this stage, I suggest you create a new Send Connecter to check the result.






    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Monday, February 21, 2011 3:26 AM
  • Also check if its happen for some perticular users:

    1: Check Transport rule of your new server

    2: Outlook rule for clients

    3: Mailbox dlivery property in mailbox

    Monday, February 21, 2011 2:57 PM
  • This may have been covered, but you mention all of your DNS records point to your server, I am assuming you only have 1 MX Record and have that MX record pointing to the IP address that routes into your internal Exchange server? If those are OK you shouldn't have any issues, you can verify there are no additional MX records by doing a lookup at www.mxtoolbox.com. I'd also check your send connectors to make sure you aren't routing through his server as a smarthost.

    Jorge R. Diaz, PMP, CCNA, MCSA, MCSE, MCTS

    Senior Microsoft Consultant

    Planet Technologies, Inc.

    Check out My Blog!

    Monday, February 21, 2011 3:42 PM
  • Your DNS has been refreshed, but what about the server of the person sending.  If they have been sending for years, but don't refresh their DNS often, they could be holding onto the old route. 
    Wednesday, June 20, 2012 9:26 PM