home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.bbs.waffle:5441 comp.mail.uucp:2388
- Newsgroups: comp.bbs.waffle,comp.mail.uucp
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!uwm.edu!linac!att!mcdchg!chinet!les
- From: les@chinet.chi.il.us (Leslie Mikesell)
- Subject: Re: Mixed format addresses
- Message-ID: <BzMpx5.D00@chinet.chi.il.us>
- Organization: Chinet - Public Access UNIX
- References: <1992Dec8.190000.21254@nwnexus.WA.COM> <KGmNrAOCBh107h@boombox.apana.org.au> <BzMIIu.Lnp@cs.psu.edu>
- Date: Mon, 21 Dec 1992 21:48:40 GMT
- Lines: 14
-
- In article <BzMIIu.Lnp@cs.psu.edu> fenner@postscript.cs.psu.edu (Bill Fenner) writes:
- >|The problem with smarthost: hishost!bighost is that mail for myneighbor
- >|(ie: myhost!hishost!myneighbor!user) goes up to bighost.
-
- >Only if you don't have your PATHS file set up properly.
-
- But it will still force mail to direct neighbors of hishost to go to
- bighost and back unless you also maintain path entries for those machines.
- If the mailer on hishost is smart enough to resolve what it can and
- pass the rest on to bighost then you are better off using hishost as
- your smarthost instead of hishost!bighost.
-
- Les Mikesell
- les@chinet.chi.il.us
-