troubleshooting Question

Delayed delivery and failed delivery email

Avatar of FEI Webmaster
FEI Webmaster asked on
11 Comments5 Solutions931 ViewsLast Modified:
We have begun receiving quite a few of the following queue errors:

451 4.4.0 Primary target IP address responded with "421 4.2.1 Unable to connect." Attempted failover to alternate host, but that did not succeed. Either there are no alternate hosts or delivery failed to all alternate delivery hosts.

The email status in the queue are:

400 4.4.7 Message delayed.

- We use Postini for inbound email.
- We have our own server we use for all outbound email (which are the ones generating these errors).
- I am able to connect directly to the MX servers that are generating these errors via telnet and send email.
- Our reverse DNS lookup for our email server resolves properly.
- Our SPF record tests successfully.
- We can receive email from the domains in question.
- We do not filter outbound email traffic.
- We are no appearing on any blacklists (both the postini mx records and our internal exchange mx record).
- DNS ONLY shows MX records for the postini servers, not the internal server.
- The internal server domain does NOT match the external DNS or RDNS FQDN ( vs.

Any help would be greatly appreciated.
Join the community to see this answer!
Join our exclusive community to see this answer & millions of others.
Unlock 5 Answers and 11 Comments.
Join the Community
Learn from the best

Network and collaborate with thousands of CTOs, CISOs, and IT Pros rooting for you and your success.

Andrew Hancock - VMware vExpert
See if this solution works for you by signing up for a 7 day free trial.
Unlock 5 Answers and 11 Comments.
Try for 7 days

”The time we save is the biggest benefit of E-E to our team. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange.

-Mike Kapnisakis, Warner Bros