-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 A long time ago, in a galaxy far, far way, someone said...
> What I can't figure out is how to configure Exim to send mail from one > machine to the other on the LAN. And I suspect there is some basic > fundamental of email/networking that I don't understand that is blocking > the way. > > My home network setup is very simple: > - I call the network 'home' (192.168.1.0) > - each host obviously has it's own hostname > - so I have newdebian.home and olddebian.home > - and those names/addresses are in /etc/hosts on each machine > - I don't run a local name server - I use my IPS's name servers > - and those IP addresses are in /etc/resolv.conf. > - other services such as telnet, ftp, ping work fine using hostnames > > But I can't get email to work between the two hosts. When I try, Exim > just returns it to the same machine, with this message included: > > A message that you sent could not be delivered to one or more of its > recipients. The following address(es) failed: > > [EMAIL PROTECTED]: > unrouteable mail domain "newdebian.home" ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ You need to get exim to know about the "newdebian.home" name. > The problem based on the error message, is that Exim doesn't know about > *.home hostnames. My question is: How do I get it to know about them? You need to run a private DNS server on one of your Linux systems. Both of your Linux systems needs to use your private DNS server for *all* name lookups. As me or on the mailing list if you need help setting that up. When delivering email, SMTP systems tend to use what's called the "MX record" for a certain DNS name (whether it's tux.creighton.edu or creighton.edu) to know what host should be handling that email. I have yet to find a SMTP agent that can use just the straight /etc/hosts file. > I have run eximconfig on both machines, choosing option #1 which is > "Internet machine". That sets up 2 default router entries in > /etc/exim.config as shown at the end of this post. I understand that for > non-local mail, a router has to be configured in /etc/exim.conf, which > then hands it off to a transport, which I assume would be "remote-smtp". > Or no? Close. This is what I do to my exim config at home to make this work (obviously the values you use will be different): 1) set "local_domains" to be the domains you want to route. I have "local_domains = /etc/exim/local-domains"; /etc/exim/local-domains is a file that contains: localhost kaitain.brutsche.com brutsche.com druid.obix.com kaitain.obix.com giedi.obix.com arrakis.obix.com fury.obix.com aeryn.obix.com 2) create transport definitions to define how to get mail to the destination. I have in the Transports configuration: druid_smtp: driver = smtp hosts = druid.brutsche.com giedi_smtp: driver = smtp hosts = giedi.brutsche.com arrakis_smtp: driver = smtp hosts = arrakis.brutsche.com fury_smtp: driver = smtp hosts = fury.brutsche.com aeryn_smtp: driver = smtp hosts = aeryn.brutsche.com 3) create directors to do the actual routing. I have in the Directors configuration: druid: driver = smartuser transport = druid_smtp domains = druid.obix.com no_more giedi: driver = smartuser transport = giedi_smtp domains = giedi.obix.com no_more arrakis: driver = smartuser transport = arrakis_smtp domains = arrakis.obix.com no_more fury: driver = smartuser transport = fury_smtp domains = fury.obix.com no_more aeryn: driver = smartuser transport = aeryn_smtp domains = aeryn.obix.com no_more > I've been going through the Exim documentation, but it sorely lacks for > some SFE (Simple F**king Examples) for those of us with simple needs. Tell me about it... It took me a week or two to figure out how to do just this much :) > Any pointers in the right direction would be much appreciated, as would > anyone who can straighten out any misunderstanding(s) I have that are > obvious from reading this post <BG>. Thanks. What I typed out above should be incredibly helpful :) - -- - ---------------------------------------------------------------------- Phil Brutsche [EMAIL PROTECTED] GPG fingerprint: 9BF9 D84C 37D0 4FA7 1F2D 7E5E FD94 D264 50DE 1CFC GPG key id: 50DE1CFC GPG public key: http://tux.creighton.edu/~pbrutsch/gpg-public-key.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE6FCtV/ZTSZFDeHPwRAoEWAJwOnY4OHiCGqv2Fb4ATJLTQqPjyLgCg1n+l h8LRjprS0ZjfI1vbBf1Cf54= =EdrT -----END PGP SIGNATURE-----