Remote Server returned '400 4.4.7 Message delayed' (Full Version)

All Forums >> [Microsoft Exchange 2013] >> Message Routing



Message


risingflight143 -> Remote Server returned '400 4.4.7 Message delayed' (8.Jun.2015 2:51:42 PM)

I am facing issue with my exchange server i am not able to send emails to few domains, I am using Exchange 2013 CU7. I doubt it can be spf record issue but not sure, Experts do guide me. Do i need to create SPF record at the ISP or on my server?

Delivery is delayed to these recipients or groups:
myemailid@gmail.com (myemailid@gmail.com)
Subject: test to gmail
This message hasn't been delivered yet. Delivery will continue to be attempted.
The server will keep trying to deliver this message for the next 1 days, 19 hours and 50 minutes. You'll be notified if the
message can't be delivered by that time.


Diagnostic information for administrators:
Generating server: myex2013server@mydomain.com
myemailid@gmail.com
Remote Server returned '400 4.4.7 Message delayed'
Original message headers:

Received: from myex2013server@mydomain.com (192.168.1.50) by myex2013server@mydomain.com
(192.168.1.50) with Microsoft SMTP Server (TLS) id 15.0.1044.25; Mon, 8 Jun
2015 13:44:49 +0300
Received: from myex2013server@mydomain.com ([fa80::7138:18d2:2659:cb80]) by
myex2013server@mydomain.com ([fa80::7138:18d2:2659:cb80%13]) with mapi id
15.00.1044.021; Mon, 8 Jun 2015 13:44:49 +0300
From: Test User <myid@mydomain.com>
To: "myid@mydomain.com" <myemailid@gmail.com>
Subject: test to gmail
Thread-Topic: test to gmail
Thread-Index: AQHQodgkHkkk3HcAkkSgLfZzGIp2XA==
Date: Mon, 8 Jun 2015 10:44:49 +0000
Message-ID: <67a93669353544e48a7b99b964277c86@myex2013server@mydomain.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.10.10.25]
Content-Type: multipart/alternative;
boundary="_000_67a93669353544e48a7b99b964277c86myex2013server@mydomain.com_"
MIME-Version: 1.0




nuggetfarm -> RE: Remote Server returned '400 4.4.7 Message delayed' (10.Jun.2015 3:45:54 AM)

SPF records are never bad to create. I would advise to do so. But if it's delayed it's mainly related to a local virusscanner or spamfilter interfering with your transmission stacks.

The virusscanner / antispam solution generally does not have to run on the Exchange server(s) to cause your transmission stacks to crash. If you have deployed DAG in your organization it could be some relay problem between the servers. Though the safest bet is SPF. virusscanner, antispam solution first.

Also what are the costs on your send connectors, try 1.

Regards,

Nugget.




Page: [1]