Gary,

        The problem is with exim which thinks that mach1 is your entire
domain name. Here is a snippet from the "ROUTERS CONFIGURATION" section of
exim.conf :

#
#  Lets deliver mail to remote users on the megadodo.umb domain
#
qualify :
        driver = domainlist
        route_list = "^[A-Za-z0-9]*$ $domain.megadodo.umb"

local_net :
        driver = domainlist
        domains = "*.megadodo.umb"
        transport = local_net_smtp
        route_list = * $domain byname
        host_find_failed = fail_soft
        self = send

        The 'qualify' router takes a single component domain name and
replaces it with <single component>.megadodo.umb . It does no deliver
since there is no transport specified, so exim takes this converted domain
down to the 'local_net' router. 

        The 'local_net' router uses the 'domains' keyword to filter out
all non megadodo.umb hostnames. This is essential because if I want to
send mail to [EMAIL PROTECTED], I do _not_ want the 'local_net' router
acting on it. 

        Note the 'route_list' keyword. It tells the router to verify the
hostname via DNS. Since my DNS server only provides lookups for my local
network (*.megadodo.umb), it will fail on all non-local addresses. The
'host-find-failed' option now tells exim to pass it onto the next router,
rather than failing the routing process. What you do in the next router is
whatever you need to do to deliver internet mail.

HTH,
Jor-el  

The price of greatness is responsibility.

On 25 Jul 1999, Gary L. Hennigan wrote:

> I'm in the process of getting a little home network set up. One of the
> hosts, call it mach2, won't have a connection to the internet, just
> to other hosts on my home network. The other host, call it mach1, will
> occasionally connect to the internet via dialup. I have mach1 all set
> up but can't seem to get mach2 to forward all the mail to mach1. In
> fact I can't get mach2 to deliver mail directly to mach1 at all.
> 
> What I want to do is set mach2 so that it uses mach1 as a smarthost. I
> think I got that right in my exim.conf (configuration 2 from the
> debian installation) but I can't seem to make it work. When I send
> email to, for example, [EMAIL PROTECTED] I get this in my exim mainlog:
> 
> 1999-07-25 10:38:36 118R4n-0000B0-00 == [EMAIL PROTECTED] routing defer 
> (-32): retry time not reached
> 
> or
> 
> 1999-07-25 10:39:47 118R4n-0000B0-00 == [EMAIL PROTECTED] R=smarthost defer 
> (-1):
> 
> I get the same thing if I send the email to [EMAIL PROTECTED]
> 
> Also, something's not quite right with mach1. If I connect manually,
> eg., telnet mach1 smtp
> 
> and type rcpt to: [EMAIL PROTECTED]
> 
> I get:
> 
> 550 relaying to <[EMAIL PROTECTED]> prohibited by administrator
> 
> but if I do rcpt to: [EMAIL PROTECTED]
> 
> it works.
> 
> Any ideas?
> 
> Thanks,
> Gary
> 
> 
> -- 
> Unsubscribe?  mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
> 
> 

Reply via email to