home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!ukma!darwin.sura.net!zaphod.mps.ohio-state.edu!menudo.uh.edu!nuchat!rivdell!elrond
- From: elrond@freeside.com (SysAdmin)
- Newsgroups: comp.bbs.waffle
- Subject: Re: Address Munging
- Keywords: UUCP, Bitnet, mailing list
- Message-ID: <bp4BrA8EBh107h@freeside.com>
- Date: Mon, 16 Nov 92 06:47:39 -0600
- References: <syV7TB4w165w@ncc1701e.uucp>
- Organization: Rivendell BBS / Hou, TX. / +1 713 941 2236
- Lines: 33
-
- In <syV7TB4w165w@ncc1701e.uucp> the_sage@ncc1701e.uucp (Jerome Grimmer) writes:
-
- >The other problem I forsee with this address munging is when there are no
- >'@' characters in the From: header. For example, suppose I get a message
- >from somebox!somewhere!foo!user, and the system foo is not in the UUCP
- >maps (this is obviously a UUCP address). Would it be appropriate to munge
- >this address to somewhere!foo!user@uunet.uu.net so that it would be
- >distributable from a Bitnet Listserv? (Assuming the system somewhere is in
- >the maps.)
-
- The problem you'll run into here is the needless routing of mail local to
- a group of systems to uunet.
-
- ie.
- system foobar.UUCP
-
- feeds sites ex1.UUCP
- and ex2.UUCP
-
- user1 on ex1 sends mail to user2 on ex2 addressed as:
-
- foobar!ex2!user2
-
- your method would cause this to be routed back to uunet for absolutely no
- reason, increasing transmission time, and wasting bandwith on systems that
- needn't be involved. Best bet is to leave bang paths alone, they are
- *usualy* the best or most reliable path to use.
-
- --
- +-------------------------+---------------------+-------------------------+
- | God is Real... | elrond@freeside.com | Pull up a dick and have |
- | Unless declared integer | Stephen L. Palmer | a seat. (Chong) |
- +-------------------------+---------------------+-------------------------+
-