We cannot email vendors and customers using message labs. Our domain is adveng.com One vendor is ra.rockwell.com.
Generating server: Artemis.adveng.com
Receiving server: cluster6a.us.messagelabs.com (184.108.40.206)
Remote Server at cluster6a.us.messagelabs.com (220.127.116.11) returned '400 4.4.7 Message delayed'
1/7/2019 10:39:15 PM - Remote Server at cluster6a.us.messagelabs.com (18.104.22.168) returned '451 4.4.0 Primary target IP address responded with: "421 4.4.1 Connection timed out." Attempted failover to alternate host, but that did not succeed. Either there are no alternate hosts, or delivery failed to all alternate hosts. The last endpoint attempted was 22.214.171.124:25'
We are not on spam lists.
Thank you for your help on this matter.
If you haven't done so already submit a sample of an email that's blocked to:
Links for reference:
This is the first place to start until someone from Symantec can review this thread and remediate.
Sent one this morning. Thank you.
We are also facing the same issue. Our mail server IP is 126.96.36.199. The error message is "Remote Server at cluster9a.us.messagelabs.com (188.8.131.52) returned '400 4.4.7 Message delayed'
Please help to unblock as we have a few customers using messagelabs and we cannot send to all of them.
I had just send an email regarding this to firstname.lastname@example.org. Hope we get the reply the soonest.
If you were to enable logging on your send connector in Exchange and view the logs, is there anything about SSL Certificate, or invaled message/token?
We receive the exact same error message later in the Logs right after the STARTTLS command where we exchange certificates in the logs
We also have issues sending to the ra.rockwell.com domain.
For now we setup a free SocketLabs account and are sending to that smarthost for the domains that are using Symantec
We are having the same issues. Users sending to multiple recipients all going through MessageLabs and all being delayed with response:
421 4.4.1 Connection timed out.
Please advise. We are not blacklisted on any services. Also tried sending request to email@example.com but that was rejected saying user doesn't exist.
Can you please let me know what IP you are connecting from so that I can check to ensure that it is not being throttled?
We're having this same issue.
My sending host is: remote.airbearings.com (184.108.40.206)
mail domain is: airbearings.com
Sending to corning.com and ajg.com. (MessageLabs clients)
Remote Server at cluster4a.us.messagelabs.com (220.127.116.11) returned '441 4.4.1 Error encountered while communicating with primary target IP address: "421 4.4.2 Connection dropped due to ConnectionReset." Attempted failover to alternate host, but that did not succeed. Either there are no alternate hosts, or delivery failed to all alternate hosts.
If I create a DNS zone for corning.com and ajg.com, I can force the MX records to resolve without the "a" (cluster4.us.messagelabs.com), and get email delivered to corning.com or ajg.com.
When I let the DNS queries resolve naturally, the messages eventually timeout, and an NDR is issued to the sending user.
Please check my IP for throttling/blocking, and assist if you can.
I have checked your IP address; however, no configuration that may cause slow connection to our towers was found. Could you kindly check if there is any hop causing the connection timeout by running tcptraceroute on port 25 to our MX record?
As Asked here is the TraceTCP on port 25.
The last two domains we cannot send email to without using smart host. (Rb.com, ra.rockwell.com)
If you can send mails using smart host, Symantec infrastrcuture is not blocking connection from the IP address. Please provide the output from tcptraceroute on port 25 to see which hop is causing the issue.
We are facing hige delay in incoming mails from different domains and as per MXTOOLBOX header analyzer, the delay is happening From messaglabs.
Please find below header info.
The mail header indicates that the mail was queued in the delivery tower for 3 hours. It could be any 400 error. I would be able to check the cause if you can provide me more details to locate the log. (e.g. domain, MX record)