Mail Problem: retry timeout exceeded

[embsupafly]

I have a customer that sent me an email stating that the forwarder he had setup on his domain is not sending mail to the address that it is supposed to forward to and he sent me the error message he got in his inbox:

customers-isp-account-where-mail-sho...@sbcglobal.com
(ultimately generated from forwarder@customers-domain-on-server.com)
retry timeout exceeded

The exim logs show the same thing.

I ran: host sbcglobal.com in the shell and I do get a response, so the route looks ok. Is this a problem on our end or sbcglobal.com's end?

UPDATE: we are now getting a new message:

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

[nettigritty]

I have a customer that sent me an email stating that the forwarder he had setup on his domain is not sending mail to the address that it is supposed to forward to and he sent me the error message he got in his inbox:

customers-isp-account-where-mail-sho...@sbcglobal.com
(ultimately generated from forwarder@customers-domain-on-server.com)
retry timeout exceeded

The exim logs show the same thing.

I ran: host sbcglobal.com in the shell and I do get a response, so the route looks ok. Is this a problem on our end or sbcglobal.com's end?

UPDATE: we are now getting a new message:

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

try restarting bind and exim then try forcing a delivery in the exim mail queue. paste the error if you still get one.

[embsupafly]

Tried restarting exim and bind, does not work..

Still getting this error message:

customers-isp-account-where-mail-sho...@sbcglobal.com
(ultimately generated from forwarder@customers-domain-on-server.com)
retry timeout exceeded

[nettigritty]

what does exim_mainlog show ? any error while sending through smtp?

Make sure you have a reverse DNS PTR record for your servers IP address and that DNS resolvers in /etc/resolv.conf are ok.

[embsupafly]

Yes, we have a reverse PTR record, resolv.conf is ok. All other email accounts (about 600-800 total) on the server are ok.

Exim log shows, "retry timeout exceeded" when sending as well.

[Drew Nichols]

I now have a client getting "retry timeout exceeded" on their messages to a remote domain. Does this indicate the remote domain may be blocking us?

[valpo]

It happens to me the same with an email account:

====================
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:

xxxxxx@xxxxxx.xx
retry timeout exceeded
====================

Somebody has found the solution for this

I have reinitiated Exim, POP and Bind, but the problem continue

That I must do?

Thank

[gahelm]

I am having this problem as well now. I notice it is happening when sending email to any Bellsouth.net domain. Anybody find a solution for this??

[hicom]

I've had this problem with some stupid servers that reject emails temporarily but don't accept a retry until after 12hrs or so. This is their way of combating spam!

To fix it, these are my retry times in exim config fiel:

#Allows server to retry delivery every 1 day
retry_data_expire = 1d

smtp_connect_backlog = 50
smtp_accept_max = 100

# primary_hostname =
deliver_queue_load_max = 6
auto_thaw = 24h
ignore_bounce_errors_after = 12h
timeout_frozen_after = 2d

Mainly, retry_data_expire=1d should help. This may not 100% resolve this issue depending on the receiving server.

[jandafields]

Bellsouth giving me the same problem!!!

[AndyReed]

Yes, we have a reverse PTR record, resolv.conf is ok. All other email accounts (about 600-800 total) on the server are ok.

Exim log shows, "retry timeout exceeded" when sending as well.

In some cases, this error indicates that the disk quota of an email account is either full or exceeded.

[mtindor]

I have a customer that sent me an email stating that the forwarder he had setup on his domain is not sending mail to the address that it is supposed to forward to and he sent me the error message he got in his inbox:

customers-isp-account-where-mail-sho...@sbcglobal.com
(ultimately generated from forwarder@customers-domain-on-server.com)
retry timeout exceeded

The exim logs show the same thing.

I ran: host sbcglobal.com in the shell and I do get a response, so the route looks ok. Is this a problem on our end or sbcglobal.com's end?

UPDATE: we are now getting a new message:

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

An @sbcglobal.com email address is not a valid email address. It is @sbcglobal.NET. sbcglobal.com does not have active MX servers. SBC DSL and dialup customers have @sbcglobal.Net addresses. You're customer gave you the wrong info.

Mike