Upgraded to exim 4.34, now getting "Unrouteable address"

[113345]

Upgraded to exim 4.34 from http://files.directadmin.com/services/freebsd4.8/da_exim-4.34-1.tgz, now getting "Unrouteable address"

from /var/log/exim_mainlog:
2004-07-19 21:50:01 1Bme9B-000LZ5-B3 <= root@www1.web49.net U=root P=local S=3398 T="test" from <root@www1.web49.net> for cust@domain.com
2004-07-19 21:50:01 1Bme9B-000LZ5-B3 **
cust@domain.com F=<root@www1.web49.net>: Unrouteable address
2004-07-19 21:50:01 1Bme9B-000LZC-Bm <= <> R=1Bme9B-000LZ5-B3 U=mail P=local S=4200 T="Mail delivery failed: returning message to sender" from <> for root@www1.web49.net

after adding the "#web49#" in exim.conf:

lookuphost:
driver = dnslookup
domains = ! +local_domains
ignore_target_hosts = 127.0.0.0/8
#web49# condition = "${perl{check_limits}}"
transport = remote_smtp
no_more

everything works again:
from /var/log/exim_mainlog:
2004-07-19 22:40:01 1BmevZ-000LyU-2C <= root@www1.web49.net U=root P=local S=3399 T="test" from <root@www1.web49.net> for cust@domain.com
2004-07-19 22:40:01 1BmevZ-000LyU-2C => cust@domain.com F=<root@www1.web49.net> R=lookuphost T=remote_smtp S=3613 H=reit.pair.com [209.68.1.225] C="250 ok 1090269601 qp 54197"
2004-07-19 22:40:01 1BmevZ-000LyU-2C Completed

What does:
condition = "${perl{check_limits}}"
do?

I am using FreeBSD 4.9 + DA v1.22.2

[DirectAdmin Support]

Hello,

There is no MX record for www1.web49.net. Go into the Admin Panel -> Dns Administration, and add www1.web49.net 217.148.168.21 .. As for cust@domain.com, make sure there is an MX for it as well, and that the IP being return is "real".

condition = "${perl{check_limits}}"
is defined in the /etc/exim.pl. It's used to count email bandwidth and the number of email sent by the user. (/etc/virtual/usage/*)

If /etc/virtual/limit is set to a number other than zero, the /etc/virtual/usage/user file might be hitting that limit, thus stopping the outgoing email.

John

[113345]

Hi,

I am sending mail from root@www1.web49.net to a user@web49.com.
www1.web49.net is hosted on a different server than web49.com.


web49.com. 3600 IN MX 50 reit.pair.com.
www1# nslookup web49.com
Server: localhost.web49.net
Address: 127.0.0.1

Non-authoritative answer:
Name: web49.com
Address: 216.92.76.166
However, reverse lookup gives:
www1# nslookup 216.92.76.166
Server: localhost.web49.net
Address: 127.0.0.1

Name: web49.net
Address: 216.92.76.166

This could be a problem when exim does a reverse lookup?

The receiving machine has a MX record.
I don't think the sending machine needs a MX record?

I don't understand why not using this: condition = "${perl{check_limits}}"
would make a difference?

I will sleep on it (getting late here 1:15 AM).

[DirectAdmin Support]

It would only really make a different if you have an email limit setup. Check to see if /etc/virtual/usage/* exists.. and try removing all files in the usage directory.

John

[urgido]

error:


This message was created automatically by mail delivery software.
A message that you sent has not yet been delivered to one or more of its
recipients after more than 24 hours on the queue on blazer.ttlwebtim2.com.

The message identifier is: 1NIpOQ-0004AM-Ej
The date of the message is: Thu, 10 Dec 2009 15:13:42 -0500

The address to which the message has not yet been delivered is:

usuario@etb.net.co

No action is required on your part. Delivery attempts will continue for
some time, and this warning may be repeated at intervals if the message
remains undelivered. Eventually the mail delivery software will give up,
and when that happens, the message will be returned to you.


this error is the first time that appears and showing after the upgrade process.
this happens with any mail like userdomain.com userdomain2.com etc...

[cachorroyayo]

this works for me.

Today I have the same problem but I could do it



It would only really make a different if you have an email limit setup. Check to see if /etc/virtual/usage/* exists.. and try removing all files in the usage directory.

I do:



cd /etc/virtual/usage
mv * /home/users/USAGE

And we don't see anymore th problem of UNROUTEABLE ADDRESS