Exchnage 2013 - "Accepted Domains" email isnt coming through !!!!!

[burgemaster]

Hi,

 

We have two additional domains along side our normal @worcstershire.worcs.sch.uk email addresses. WCC control the DNS for these and have pointed the MX record to the IP of our mail server.

Everything was working perfectly with exchange 2007, but since we have migrated to exchange 2013 none of the additional accepted domains are working externally. I have double check with WCC and they have checked the MX record still points to the correct IP. They are getting "Connection Timed Out" and we are getting emails bounced back when sent from external. I have checked that the accepted domains migrated across and have even tried recreating them in the ECP.

 

Can anyone please shed any light onto this or point us in the right direction?

 

Thanks in advance!

[FN-GM]

Are the addresses assigned to users in the Address Policy?

[burgemaster]

Hi FN-GM,

 

There wasn't a policy set-up, but for the staff that wanted these additional (shorter!) alias`s we added them manually.

I have setup a policy wit the accepted domains, but am i right in thinking this just adds the additional email addresses to user accounts? or is it needed?

 

Thanks

Tim

[burgemaster]

Here is the bounce:

 

This message was created automatically by mail delivery software.

 

A message that you sent could not be delivered to one or more of its

recipients. This is a permanent error. The following address(es) failed:

 

[email protected]

retry time not reached for any host after a long failure period

 

------ This is a copy of the message, including all the headers. ------

 

Return-path:

Received: from mailgate2.networcs.net ([192.168.1.62] helo=mc2.networcs.net)

by mailrouter2.networcs.net with smtp (Exim 4.63)

(envelope-from )

id 1XYYsg-0003lN-QJ

for [email protected]; Mon, 29 Sep 2014 12:12:38 +0100

Received: from mc2.networcs.net (localhost.localdomain [127.0.0.1])

by localhost (Email Security Appliance) with SMTP id 677EE8931BF_4294133B

for ; Mon, 29 Sep 2014 11:23:31 +0000 (GMT)

Received: from DUB004-OMC1S29.hotmail.com (dub004-omc1s29.hotmail.com [157.55.0.228])

by mc2.networcs.net (Sophos Email Appliance) with ESMTP id 2D128892FD0_4294133F

for ; Mon, 29 Sep 2014 11:23:31 +0000 (GMT)

Received: from DUB130-W53 ([157.55.0.237]) by DUB004-OMC1S29.hotmail.com with Microsoft SMTPSVC(7.5.7601.22724);

Mon, 29 Sep 2014 04:13:53 -0700

X-TMN: [apxgWAKlu7+mHieFZanqQBfBgWiWHebXqEoW++Vr0TQ=]

X-Originating-Email: [[email protected]]

Message-ID:

Content-Type: multipart/alternative;

boundary="_2e419f50-bd41-41bd-b2c7-52cf2f1d675d_"

From: tim burgess

To: "[email protected]"

Subject: kljj

Date: Mon, 29 Sep 2014 12:13:52 +0100

Importance: Normal

MIME-Version: 1.0

X-OriginalArrivalTime: 29 Sep 2014 11:13:53.0072 (UTC) FILETIME=[73E22B00:01CFDBD6]

X-Sophos-ESA: [mc2.networcs.net] 3.8.0.1, Antispam-Engine: 2.7.2.1390750, Antispam-Data: 2014.9.29.110319

[howartp]

I just tried an MX lookup against wcess.org.uk - it failed four times before finding four networcs.net results.

 

If mail servers are also failing, then your mail won't arrive. That's the same as what your error is implying.

[cscc]

Do an inbound and outbound SMTP test from this link:

 

https://testconnectivity.microsoft.com/

 

Should allow you to identify where the issue lies.

 

I see they have updated your DNS but could also be a NAT/firewall issue - pointing SMTP rules to the old IP address (assuming its changed)

Edited September 29, 2014 by cscc

[howartp]

Just googled the error about long reply times - that seems to be an error that is specific to Exim. All google results mention Exim and a number point to this solution:

 

http://tomyates.co.uk/2012/05/02/exim-retry-time-not-reached-for-any-host-after-a-long-failure-period/

 

Not sure if it's you or WCC that run Exim but might be worth a try?

[burgemaster]

Hi howartp,

It must be county. The thing is our normal mail is working perfectly. Its just these accepted domains that have stopped working.

All the tests from exchangeconnectivity are passing.

 

County are saying that the mail is passing fine all the way through their servers but is getting rejected by our mail server.

[burgemaster]

This is now sorted.

 

After the migration, to save time getting external DNS records changed we changed the IP of the new mail server to the IP of the old mail server.

For whatever reason the old IP just stopped accepting mail on port 25. We changed the IP back to the original IP and asked county to change the MX records. All mail is now coming through on all domains!

What a nightmare. Maybe that original IP is written in the domain structure somewhere that you cant get to with the ECP..

 

Thanks for the help.