Xref: utzoo news.admin:15443 comp.mail.misc:5778
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!mips!spool.mu.edu!agate!eris.berkeley.edu!wisner
From: wisner@mica.Berkeley.EDU (Bill Wisner)
Newsgroups: news.admin,comp.mail.misc
Subject: Re: Bogus .UUCP addresses, was: Is UUNET going to upgrade?
Message-ID: <1991Jun22.173931.19979@agate.berkeley.edu>
Date: 22 Jun 91 17:39:31 GMT
References: <9106151249.48@rmkhome.UUCP> <1991Jun21.025904.3563@osh3.OSHA.GOV> <1991Jun21.214642.8746@mthvax.cs.miami.edu>
Sender: usenet@agate.berkeley.edu (USENET Administrator)
Distribution: na
Organization: Amnesia International
Lines: 13
Originator: wisner@eris.berkeley.edu

>Comment: If your mailer is too stupid to handle MX's and .UUCP
>addresses, it should at least be smart enough to pass the job off to a
>site that can do the job.

This is true for MX records, since proper handling of MXes is virtually 
mandatory for an Internet mail host.  An Internet host doesn't have to
deal with .UUCP addresses, though, particularly since the "user@host.UUCP"
construct has no official standing -- it's as much an underground hack as
% notation.  If you want to make it easy on your users, fine -- configure
your mailer to punt .UUCP addresses to a gateway.  But don't think it's
required.

Bill Wisner <wisner@mica.Berkeley.EDU> Gryphon Gang Saratoga CA 95070