sanand@radha.UUCP (Sanand Patel) (09/17/86)
A while ago (2 months ?) someone asked for help is using sendmail to
send both arpa/ethernet and uucp/serial lines. I would also like help
in the same area.
We use ethernet internally (ultrix1.1), but we connect to external sites
via uucp. At the moment we also use uucp internally as well --- for mail.
I can't seem to get mail sent internally via ethernet and externally via
uucp. If I use the 'generic arpa' sendmail.cf, then uucp mail gets dropped.
If I use the 'generic uucp' sendmail.cf, then all mail goes by uucp, and
the ethernet is never used. What I need are the changes required to
sendmail.cf that will choose the best way to mail -- local=arpa_style,
otherwise use uucp. If anyone can offer help, I would appreciate it.
---
--- {ihnp4,decvax}!utzoo!dciem!radha!sanand
--- seismo!mnetor!radha!sanand
--- 416-293-9722 ext248mark@cbosgd.UUCP (Mark Horton) (09/19/86)
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