From: mbs@adastra.cvl.va.us (Michael B. Smith)
Newsgroups: alt.sys.amiga.uucp
Subject: Re: Sendmail routing
Distribution: world
X-NewsSoftware: GRn 1.16f (10.6.92) by Mike Schwartz & Michael B. Smith
Date: 7 Oct 92 18:35:57 EDT
Organization: Well, I haven't decided on a name yet...

In article <BvqtJ3.MIs@icsbelf.co.uk> ianm@icsbelf.co.uk (Ian Moran) writes:
> Michael B. Smith (mbs@adastra.cvl.va.us) wrote:
> : In article <ianm.0332@laghey.UUCP> ianm@laghey.UUCP (Ian Moran) writes:
> : > When sending mail in the following form
> : >  icsbelf!uknet!waspy@cix.compulink.co.uk
> :
> : > this is what ends up in the D* file
> :
> : > C rmail cix.compulink.co.uk!icsbelf!uknet!waspy
> : >
> : > Understandably, this does not make it past icsbelf. How can I persaude
> : > sendmail to leave my address alone. I am using AVM, UUCP1.6D with the
> : > supplied sendmail.

> : If you were trying to use a bang-path style address to get to uknet!waspy,
> : how would you write it? In Internet addresses the '@' takes priority over
> : the '!'.
>
> But that's the point user waspy is not known at uknet, he is known at cix,
> which is known at uknet. I would write a bang path as follows
>
>  uknet!cix!waspy
>
>  I am assuming here that cix is known by uknet, I haven't checked the
>  maps. I must admit to finding the whole business os addressing
>  somewhat confusing. I understand bang paths ok, but when mmixed with
>  % or @ or FQDN then things get interesting. If you can rec any source
>  of reading on this I would be eternally grateful.

I understand your confusion now.

Sendmail in AmigaUUCP interprets those addresses according to RFC976
(a portion of which I have included below). You are using it in reverse
precedence. The portion of the address to the RIGHT of the '@' takes
priority for routing.

I encourage you to become familiar with RFC976 and RFC822.
--
  //   Michael B. Smith
\X/    mbs@adastra.cvl.va.us  -or-  uunet.uu.net!virginia.edu!adastra!mbs

RFC 976                                                    February 1986
UUCP Mail Interchange Format Standard


2.1  Hybrid Addresses

   There are (among others) two major kinds of mailing address syntax
   used in the UUCP world.  The a!b!c!user ("bang paths") is used by
   older UUCP software to explicitly route mail to the destination.  The
   user@domain ("domain") syntax is used in conformance to RFC-822.
   Under most circumstances, it is possible to look at a given address
   and determine which sort of address it is.  However, a hybrid address
   with a ! to the left of an @, such as a!b@c, is ambiguous: it could
   be interpreted as (a!b)@c.d or a!(b@c.d).  Both interpretations can
   be useful.  The first interpretation is required by RFC-822, the
   second is a de-facto standard in the UUCP software.

   Because of the confusion surrounding hybrid addresses, we recommend
   that all transport layer software avoid the use of hybrid addresses
   at all times.  A pure bang syntax can be used to disambiguate, being
   written c.d!a!b in the first case above, and a!c.d!b in the second.
   We recommend that all implementations use this "bang domain" syntax
   unless they are sure of what is running on the next machine.

   In conformance with RFC-822 and the AT&T Message Transfer
   Architecture, we recommand that any host that accepts hybrid
   addresses apply the (a!b)@c.d interpretation.