Question : Action: failed. Status: 4.4.7 (Persistent transient failure - routing/network: delivery time expired)

I began receiving this response when I try to send mail from my personal email server. It has been working fine for at least a year. I first started receiving this response:

Reporting-MTA: dns; mailsitea
Arrival-Date: Sat, 5 Aug 2006 08:58:36 -0400

Final-Recipient: rfc822; K***@t***.com
Action: delayed
Status: 4.4.1 (Persistent transient failure - routing/network: no answer from host)
Will-Retry-Until: Wed, 9 Aug 2006 22:30:22 -0400
and then I receive this resonse


Reporting-MTA: dns; mailsitea
Arrival-Date: Sat, 5 Aug 2006 08:58:36 -0400

Final-Recipient: rfc822; K***@t***.com
Action: delayed
Status: 4.4.1 (Persistent transient failure - routing/network: no answer from host)
Will-Retry-Until: Wed, 9 Aug 2006 22:30:22 -0400

This happens with all mail sent. I can send from my ISP mail account just fine. I even tried to test by sending mail from my branded email to my sp email account with the same results. I don't know where to even begin looking for a solution. It appears that it must be a configuration problem on my end. I know I have the server closed to relaying unless authenticated so I'm not being shut down because of spam. Any thought would be greatly appreciated.

I want to say that I am using this example masked for privacy but I am getting this from all the major ISPs i.e. AOL, earthink, Bell South, Road Runner as well as some TLD email addresses.

Tommy

Answer : Action: failed. Status: 4.4.7 (Persistent transient failure - routing/network: delivery time expired)

All email would indicate a problem at your end.

Email server being used would be handy, as my crystal ball is on the blink (didn't help being dropped this morning).

Try a raw test - see if you can telnet to port 25 of a remote email server.
I tend to use Microsoft's because it is the only one I can remember.

telnet maila.microsoft.com 25

If that fails, then port 25 is being blocked somewhere - firewall ISP etc.
If that works, then you start looking at the server application as being the cause.

Simon.