Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!zaphod.mps.ohio-state.edu!unix.cis.pitt.edu!dsinc!netnews.upenn.edu!msuinfo!midway!clout!chinet!les
From: les@chinet.chi.il.us (Leslie Mikesell)
Newsgroups: comp.mail.uucp
Subject: Re: address re-writing in smail 3.1.18
Message-ID: <1991Jun05.151833.25405@chinet.chi.il.us>
Date: 5 Jun 91 15:18:33 GMT
References: <1991Jun2.165657.16810@unixland.natick.ma.us> <1991Jun2.182421.11107@Firewall.Nielsen.Com> <1991Jun2.231207.19164@unixland.natick.ma.us>
Organization: Chinet - Chicago Public Access UNIX
Lines: 23

In article <1991Jun2.231207.19164@unixland.natick.ma.us> bill@unixland.natick.ma.us (Bill Heiser) writes:

>How do I make all outbound addresses carry FQDN's (I do ONLY UUCP, no
>SMTP)?  If I send out stuff like "user@host", it's going out with an
>incomplete address!  That causes problems:  For example, if I send to
>user@abc, meaning one system, but my mail host also has a host named
>"abc", it'll end up bouncing from his machine with a "no such user"
>error.  In order to avoid that confusion, the outbound mail needs to
>be fully qualified (unless there's another way I don't know about).

Do you have a "qualify" file?  If you do, smail3 should use it to
fully qualify the addresses (including To: and Cc:, etc.) on mail
that originates locally with a remote destination.  This does not
affect the envelope-to (the address in the uux'd rmail command),
though, so it doesn't solve the problem you mention.  If you maintain
your own paths file you would be resolving the route to abc.uucp yourself
so this wouldn't happen.  A work-around might be to hand-build a paths
file that includes:
  abc  mailhost!abc.uucp!%s
for any known conflicts.

Les Mikesell
  les@chinet.chi.il.us