home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!wupost!darwin.sura.net!gatech!swrinde!elroy.jpl.nasa.gov!decwrl!decwrl!infopiz!mccall!ipmdf-newsgate!list
- From: ned@innosoft.com (Ned Freed)
- Newsgroups: vmsnet.mail.pmdf
- Subject: RE: UUCP bang style addresses
- Message-ID: <01GO2LODJE1O94E2EJ@INNOSOFT.COM>
- Date: 27 Aug 92 17:55:01 GMT
- Organization: The Internet
- Lines: 15
- Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
- Resent-Date: 27 Aug 1992 09:55:01 -0800 (PST)
- Resent-From: epmdf@YMIR.CLAREMONT.EDU
- Errors-To: epmdf@YMIR.CLAREMONT.EDU
- Resent-Message-ID: <01GO2LSVCC7M95OE2Z@YMIR.CLAREMONT.EDU>
- X-Vms-To: IN%"gdha@se.alcbel.be"
- X-Vms-Cc: IPMDF
- Mime-Version: 1.0
- Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
- Content-Transfer-Encoding: 7BIT
-
- The $! control sequence has nothing at all to do with UUCP paths. It
- is used to extract a part of a domain specification.
-
- The handling of bang paths is detailed in section 3.2.4.1 of the
- manual (page 3-10). This is simply part of the overall strategy PMDF
- uses to handle addresses; there is no special facility for handling these
- sorts of addresses.
-
- If you have a specific goal in mind (rather than the intent to use some
- particular feature) please explain it in greater detail. Bang path
- addresses work just like any other address format in PMDF; unless you're
- trying to produce them for a UUCP connection there should be no reason
- to handle them specially.
-
- Ned
-