Just trying to poll some data to narrow this down...
grep -r yahoo /var/log/exim_mainlog | grep retry
grep -r yahoo.com /var/spool/exim/input | grep From: | wc -l
The way cpanel has exim configured out of the box, it has a very generic,
probably overlooked retry configuration, basically it will retry every 15
minutes for 2 hours. The problem here is graylisting is getting popular.
You end up with something like this :
2006-10-23 08:47:11 1Gc08F-0002d2-0c == [email protected] R=lookuphost
T=remote_smtp defer (-53): retry time not reached for any host
2006-10-23 09:07:12 1Gc08F-0002d2-0c == [email protected] R=lookuphost
T=remote_smtp defer (-53): retry time not reached for any host
2006-10-23 10:23:05 1Gc08F-0002d2-0c == [email protected] R=lookuphost
T=remote_smtp defer (-53): retry time not reached for any host
The issue here is, with graylisting, you should retry at least once,
initially, almost immediately. For whatever reason, exim isn't allowing
itself to retry properly.
It's something to look at, since yahoo implemented graylisting 2 days ago,
we've had hundreds of customers complaining, because their email are being
rejected, and for whatever reason, since the retry times aren't optimized,
it's taking at least 15 minutes, often a few hours, to retry.
Any thought on this? The other issue is the queue runner by default only runs every hour.
You can set a specific retry interval for the 451 error, which is what should be done (rcpt_451) something such as :
* rcpt_451 F,1m,3s; F,1h,5m; F,3h,30m;
lemme know.
grep -r yahoo /var/log/exim_mainlog | grep retry
grep -r yahoo.com /var/spool/exim/input | grep From: | wc -l
The way cpanel has exim configured out of the box, it has a very generic,
probably overlooked retry configuration, basically it will retry every 15
minutes for 2 hours. The problem here is graylisting is getting popular.
You end up with something like this :
2006-10-23 08:47:11 1Gc08F-0002d2-0c == [email protected] R=lookuphost
T=remote_smtp defer (-53): retry time not reached for any host
2006-10-23 09:07:12 1Gc08F-0002d2-0c == [email protected] R=lookuphost
T=remote_smtp defer (-53): retry time not reached for any host
2006-10-23 10:23:05 1Gc08F-0002d2-0c == [email protected] R=lookuphost
T=remote_smtp defer (-53): retry time not reached for any host
The issue here is, with graylisting, you should retry at least once,
initially, almost immediately. For whatever reason, exim isn't allowing
itself to retry properly.
It's something to look at, since yahoo implemented graylisting 2 days ago,
we've had hundreds of customers complaining, because their email are being
rejected, and for whatever reason, since the retry times aren't optimized,
it's taking at least 15 minutes, often a few hours, to retry.
Any thought on this? The other issue is the queue runner by default only runs every hour.
You can set a specific retry interval for the 451 error, which is what should be done (rcpt_451) something such as :
* rcpt_451 F,1m,3s; F,1h,5m; F,3h,30m;
lemme know.
