Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!lll-crg!lll-lcc!qantel!ihnp4!cbatt!cbosgd!mark
From: mark@cbosgd.UUCP (Mark Horton)
Newsgroups: net.mail
Subject: Re: sendmail configuration ..
Message-ID: <2600@cbosgd.UUCP>
Date: Fri, 19-Sep-86 00:00:15 EDT
Article-I.D.: cbosgd.2600
Posted: Fri Sep 19 00:00:15 1986
Date-Received: Sun, 21-Sep-86 18:23:19 EDT
References: <124@radha.UUCP>
Organization: AT&T Bell Laboratories, Columbus, Oh
Lines: 31
Keywords: arpa+uucp

In article <124@radha.UUCP> sanand@radha.UUCP writes:
>I can't seem to get mail sent internally via ethernet and externally via uucp.

smail, as recently posted to mod.sources, handles this case.
The restriction is that you have to be able to list all the
local host names (as single words) in a file, /etc/hosts.smtp.
If your local net is simple enough (all hosts in /etc/hosts
properly reachable via SMTP) you can just use /etc/hosts.
In particular, this isn't suitable if you're on the ARPA Internet.

The basic technique is to list all the ethernet hosts in a file,
and read them into a class in semdmail.cf with a line such as
	CE/etc/hosts.smtp
Now you can refer to $=E to mean "any local Ethernet host".
It is unfortunate that this mechanism only works as long as
there are no dots in any of the hostnames.

This allows you to use the same syntax to reach both local
hosts and remote hosts, so you can present a consistent user
interface to your users.

The traditional approach is to key on the syntax: send user@host
via Ethernet, and host!user via UUCP.  This is easy to implement,
but harder to use, and things get ugly when your UUCP neighbor
wants to send mail to your Ethernet-only host, since they must
generate a path like
	foo!bar!user@host
which is ambiguous and will probably be parsed differently than
you intended by some site along the path.

	Mark