On Mon, 6 Sep 1999, Jonathan Allen wrote:
> However, my problem is with mail from a UUCP node to this
> machine. All the addresses are bang-path addresses like this:
> From: bilge!alice
> To: mirror!jonathan
!!Ack!! Who on earth is still using bang paths? stop!please
> Now, the central machine knows that it is 'mirror', and is
> master for that domain, so that part isn't a problem. It is the
> 'bilge' part that causes the named call. I don't think I can
> put 'bilge' in the /etc/hosts with a suitable dummy address
> (e.g. 192.168.1.200) because it is a UUCP connection and not
> Internet or LAN - or can I without disturbing sendmail ?
Maybe have bilge identify itself as mirror!bilge?
If you really want to fix this properly, stop using bang paths,
have your ISP set up MX records pointing to itself for all the
machines you serve, have the ISP's sendmail forward all such mail
to uucp for holding, set up mirror's uucp to grab the mail
periodically, and set up mirror's sendmail to distribute the mail.
Not so hard, really, you just need some cooperation from the ISP.
Oh, and set up you local named on your 192.168.x.x net with MX
records at higher priority than those of the ISP, otherwise mail
from one machine on your net to another might end up going through
the ISP.
> More sad (or perhaps providentially depending on how you look at
> it) is that my ISP actually has another client (like me) with a
> machine called 'bilge' on it, so that after doing the named call
> referral to the ISP it quietly delivers it to me locally after
> all.
Using Internet-style addresses would solve this problem (or would
at least force you to deal with it properly by changing one
machine's name :-)
Ed
--
Ed Doolittle <mailto:[EMAIL PROTECTED]>
"Everything we do, we do for a reason." -- Peter O'Chiese
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
