Unrouteable address

toml said:
First place I would look, is what does your Line 1 look like in /etc/exim.conf
Click to expand...

Hi tom, thanks for helping me (again). Pretty much the same issue but thought it better to sort one of the issues first which is email. I tired this:

http://help.directadmin.com/item.php?id=51

And when copying over the exim.conf it failed and so I was left with a filed message within exim.conf. So I then copy the main file:

http://files.directadmin.com/services/exim.conf

Straight into my exim.conf. This is becoming a nightmare, ive been gone for 2 months and now my server is a mess.
 
Phil_b, you've never answered the question.

Please do the following:

First shell in as root.

Then post for us the output of: ls -al /etc/exim.conf

and the output of: head -10 /etc/exim.conf.

Jeff
 
any why did the download fail? Paste us the output of the wget command. Also run:

df -h

to make sure your / partition isn't full.

Also on a note relating to the original thread, keep everything lower case. A user had an upper case hostname which confused exim.

John
 
spologies for the late reply. I have been looking into the issue.

Then post for us the output of: ls -al /etc/exim.conf
Click to expand...

-rwxr-xr-x 1 root root 0 Nov 9 23:22 /etc/exim.conf

and the output of: head -10 /etc/exim.conf.
Click to expand...

doesnt seem to provide anything. I got exim working in the end and now my mainlog is showing the below:

2006-11-24 21:05:08 1GiYIF-00089e-KW Message is frozen
2006-11-24 21:05:08 1Gjm3t-0004f9-TE Message is frozen
2006-11-24 21:05:09 1GjLmk-00023E-29 Message is frozen
2006-11-24 21:05:09 1GneJI-0006vh-0q Message is frozen
2006-11-24 21:05:09 1GlBlM-0002CV-8A Message is frozen
2006-11-24 21:05:09 1GhYs9-00018W-Do Message is frozen
2006-11-24 21:05:10 1GjaU8-00068b-RS Message is frozen
2006-11-24 21:05:10 1Glc3H-0005Er-Rc Message is frozen
2006-11-24 21:05:10 1GmShw-0004mB-Bk Message is frozen
Click to expand...

I believe somewhere I have about 4 gig worth of 'data'. I checked the logs mainlog.1, mainlog.2 etc and they are only a few hundred meg. Is there anywhere I can get to the source of this issue?

Thanks again.
Phil
 
I made an error in my request :( .

Please try as root:

head -10 /etc/exim.conf

and post the output here.

Check also that you've got workable nameservers in /etc/resolv.conf.

Post also the output of:

head -10 /etc/resolv.conf

Thanks.

Jeff
 
In my /etc/resolv.conf I have the following output:

search 4directadmin.com
nameserver 213.228.193.36
nameserver 213.228.193.110

These two IP's dont relate to my server IP's at all... do these look correct or would I need to change them?


head -10 /etc/exim.conf

The above gives no return. When I try to edit the file by:

nano exim.conf it seems the config file is empty.

Thanks again for your advice on this issue.

Phil
 
Phil_b said:
search 4directadmin.com
nameserver 213.228.193.36
nameserver 213.228.193.110

These two IP's dont relate to my server IP's at all... do these look correct or would I need to change them?
Click to expand...
They should not be your IP#s. They should be the IP#s of working recursive namervers as close as possible (network wise) to your server.

To test them:
Code: 
$ dig @213.228.193.36 aol.com
$ dig @213.228.193.110 aol.com
If both of the above lines give you answers for aol.com, they work, and they're correct.
head -10 /etc/exim.conf

The above gives no return. When I try to edit the file by:

nano exim.conf it seems the config file is empty.
Click to expand...
exim won't run without a config file. For example:
Code: 
# service exim restart
Shutting down exim:
Starting exim: 2006-11-28 09:00:38 non-existent configuration file(s): /etc/exim.conf
                                                           [FAILED]
#
My guess is you've got a bad exim install and that you need to reinstall exim.

Of course you may have been hacked or have had other problems.

But you can try reinstalling exim:
Code: 
# cd /usr/local/directadmin/scripts
# ./exim.sh
Jeff
 
right I see. Seem to be getting somewhere now.

Code: 
Preparing...                ########################################### [100%]
   1:da_exim                ########################################### [100%]
Preparing...                ########################################### [100%]
        package da_vm-pop3d-1.1.7f-2 is already installed
Substitution replacement not terminated at -e line 1.
make: `wrapper' is up to date.
Testing for perl (/usr/bin/perl)...
Configuring scripts...
./install.sh -m 751 -O 102 -g 2 . /etc/virtual/majordomo
./install.sh -m 755 -O 102 -g 2 . /etc/virtual/majordomo/bin
Copying tools to /etc/virtual/majordomo/bin
Copying Majordomo files to /etc/virtual/majordomo
Copying archiving and other tools to /etc/virtual/majordomo/Tools
./install.sh -m 755 -O 102 -g 2 . /etc/virtual/majordomo/Tools
Using installed majordomo.cf
Installing manual pages in /etc/virtual/majordomo/man

To finish the installation, 'su' to root and type:

            make install-wrapper

If not installing the wrapper, type

            cd /etc/virtual/majordomo; ./wrapper config-test

(no 'su' necessary) to verify the installation.
./install.sh -o root -g 2 \
        -m 4755 wrapper /etc/virtual/majordomo/wrapper

To verify that all the permissions and etc are correct,
run the command

             cd /etc/virtual/majordomo; ./wrapper config-test
Starting DA-PopB4Smtp: 
Stopping xinetd: [  OK  ]
Starting xinetd: [  OK  ]
cp: copying multiple files, but last argument `/var/www/html/squirrelmail-1.4.6/data/[email protected]' is not a directory
Try `cp --help' for more information.

In the above everything seems to be fine apart from the last part. It says the firstory does not exist but when I check it in fact does.
 
no, it says it's a file.

I don't know why it's trying to copy it; you might want to check with DA support if exim still isn't working.

Jeff
 
DirectAdmin Support said:
Hello,

Go through this checklist:
http://help.directadmin.com/item.php?id=16

If you get an unrouteable message for the hostname, it means exim has no clue what to do with the message. The hostname is supposed to be local. The way that exim knows that is if it's in the /etc/virtual/domains file. My first guess #2 of that guide. Having the hostname in the domains file is what tells exim, yes this is local, no need to try and route it anywhere.

John
Click to expand...

John can you explain part 1) in your links a bit more.

1) hostname must not match any domain that is being used on the system. Example, if you have a domain called domain.com and you want to recieve mail on [email protected], you must *not* set your hostname to domain.com. We recommend using server.domain.com instead. You must make sure that you add the A record for server.domain.com so that it resolves.
Click to expand...
Why add 'server.' infront of the domain name?
It seems to me this is not in line with the setup info found here http://admin.site-helper.com/settings.html

gs113.gif
 
chartmusic,

What's your server hostname?

Do you have a domain name on the server with exactly the same name?

If so, you have to change it so they're not the same.

One way to do that is to make server.example.com your server hostname.

Jeff
 
Hm, sorry for digging this out, I've read complete thread, followed every advice and nothing happened.

Still have unroutable email address error.
 
MMarko,

There are lots of reasons why an address could be unroutable, and this is your first post to this thread.

We're not mindreaders. Post some of your log snippets and we'll see if we can figure it out.

No more than ten lines or so if you want me to read it :) .

Jeff
 
Thanks for your earlier reply Jeff.
I do understand what to do and it does work, but I just don't understand why. Hence the question about why add 'server.' infront of domain. I tend not to like doing things which I have no understanding of the reason behind it.
 
I thought I made it clear. You're not interested in the domain name; you're interested in the hostname. Which may very well be "server." in front of the domain name.

Jeff
 
I'd like to add to this - I was writing down my problem when I discovered what was wrong!

I sometimes get unroutable address errors at random times and then only for

- external email addresses (hotmail.com, yahoo.com, ligna.nl, etc. - all local addresses are delivered fine);

- sent through one of my mailing lists;

- often between 23.00 and 00.30 at night, but today for example during the day.

Domains resolve fine, all local deliveries work fine, restarting Named does not help and after a while the error disappears again...

The problem was found in /var/log/exim/paniclog:

2007-02-09 14:02:25 1HFVOK-0006WS-7z failed to expand condition "${perl{check_limits}}" for lookuphost router: You (username) have reach your daily email limit of 250 emails
Click to expand...

Because of traffic on the mailinglist the limit I set for mails was actually reached! I am very happy to have found the cause because it was bugging me for a while now :)

The limit is set in /etc/virtual/limit. Now I'll have to research how to set a per-user limit, but I have a recollection that this has been posted on the forum somewhere already.

Logs:

error mail:
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:

ad@ yahoo.com
(generated from yout-out@ sengerema.nl)
Unrouteable address
ben007@ hotmail.com
(generated from yout-out@ sengerema.nl)
Unrouteable address
Click to expand...

Bye,

Harro
 
For me it turned out to be the first nameserver in /etc/resolv.conf was acting up - which was a dc provided recursive nameserver. It would work sometimes and not others... switching it to another nameserver and the problem seems to be gone.
 
You must log in or register to reply here.
Back
Top