>
> Awhile back, I setup a Linux box here at home that's connected to my own
> FreeBSD box. (as well as a couple of windows95 computers that my wife
> and kids use) It's been nice to be able to simulate situations here,
> without loosing any production time. :)
>
> Anyway, I setup Exim on the two Unix-like machines here, and thought I
> had it going... I was passing mail just fine between the two computers,
> but the rotten thing... If I telnet to work and use Pine to write a mail
> to a test user here, and that test user is in the alias file to be sent
> to box2, it won't forward the mail, but instead writes an autoresponse
> back saying 'no such mail domain', or something like that.
Ah! That is because it finds no such domain in DNS. Try this in the routers
section of your exim.conf:
box2:
domains=box2.your-domain.dom,
transport=smtp,
driver=domainlist;
route_list="box2.your-domain.dom box2.your-domain.dom byname"
modemask=002
and make sure that you have box2.your-domain.dom in the /etc/hosts file and
kill and restart exim.
>
> If I write a mail from myself to the test user locally, it does just
> fine using gethostbyname in the /etc/hosts file, why not from a remote
> host?
Because it can not find box2.your-domain.dom in DNS. It will try to find an MX
record for it, that is why I mentioned putting an MX record for box2 that points
to box2. If you can also add an A record for box2 in your local DNS, change
the byname to bydns_a in the route_list entry and you can remove the host from
/etc/hosts.
>
> --
>
> ------------------------
> Dana Booth <dana@???>
> ------------------------
>
> --
> *** Exim information can be found at http://www.exim.org/ ***
>
>
--
*** Exim information can be found at
http://www.exim.org/ ***
