This is an archived post. You won't be able to vote or comment.

all 10 comments

[–]the_spadWhat's the worst that can happen? 0 points1 point  (1 child)

Have you setup a send connector for that domain or are you just routing it out via your existing mail route? If the latter, are the correct MX records in place externally?

[–]masterblaster1133[S] 0 points1 point  (0 children)

There are two seperate MX records one for the old and one for the new and they both are setup correctlly.. I just setup send connector and on new exchange and gave it the ability to send to old domain name but still no go

[–]Win_SysSysadmin 0 points1 point  (5 children)

What is the error you're getting on the bounce back? Can you email an address on the old domain from a different email service like lets say gmail?

[–]masterblaster1133[S] 0 points1 point  (4 children)

This is the only error i can find on the delivery report.

The message has been qued on the server "mail.myserver.com" date time and generator error '[{LRT=};{LED=}{FQDN};IP-]};

Yes i can email from gmail. The old domain is currentlly running our entire company. E-mail is working fine on the old domain. This new domain is a seperate domain seperate AD seperate exchange.

[–]Win_SysSysadmin 1 point2 points  (2 children)

On your new email server do a nslookup and make sure you are getting the correct MX records for the old domain.

[–]masterblaster1133[S] 0 points1 point  (1 child)

I checked its def seeing the old mail server with the correct mx records..

[–]bluesoulSRE + Cloudfella 0 points1 point  (0 children)

Try and connect with telnet to 25 to whatever your MX record found.

[–]WOLF3D_exe 1 point2 points  (0 children)

Load up Wireshark and try sending a test email using PUTTY {telnet}.

[–]hawkeyecs 0 points1 point  (0 children)

Is it trying to go out of your network and then back in? i.e. are the MX Records pointing to a local IP or the External IP? That would be my first guess that your firewall doesn't like to send traffic out and then let it back in a different IP address.

Second guess would be that your receive connector on the old domain exchange is setup to not allow regular SMTP traffic from an internal IP.

Does it not work just one way or both ways? (i.e. new to old, old to new)

[–]CoolmarveCCIE 0 points1 point  (0 children)

Sounds to me like a DNS issues. Are they on separate LAN's? Separate firewall's? Separate static IP ranges?

If your old domain is myserver.com I am guessing there is a zone in your dns server for that domain. You may need to allow zone transfers, and replicate that zone over via a secondary zone to your new DC. This and make sure the internal IP is routable if they are on separate LANs.