Xref: utzoo news.admin:15466 comp.mail.misc:5780
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!ncar!news.miami.edu!mthvax!wb8foz
From: wb8foz@mthvax.cs.miami.edu (David Lesher)
Newsgroups: news.admin,comp.mail.misc
Subject: Re: Bogus .UUCP addresses, was: Is UUNET going to upgrade?
Message-ID: <1991Jun23.135640.24068@mthvax.cs.miami.edu>
Date: 23 Jun 91 13:56:40 GMT
References: <9106151249.48@rmkhome.UUCP> <1991Jun21.025904.3563@osh3.OSHA.GOV> <1991Jun21.214642.8746@mthvax.cs.miami.edu> <1991Jun22.173931.19979@agate.berkeley.edu>
Reply-To: wb8foz@mthvax.cs.miami.edu (David Lesher)
Distribution: na
Organization: NRK Clinic for habitual NetNews Abusers
Lines: 25

>  An Internet host doesn't have to
>deal with .UUCP addresses, though, particularly since the "user@host.UUCP"
>construct has no official standing -

Yep, that's true. Instead of fixing your system to handle addresses of
non-royal peerage, encourage your users that have tried to mail to
those addresses, and failed, to use the alternative approach.  Just
have them POST their mail, several times maybe, with world-wide
distribution.  That will work, and who could possibly complain about
it, right?

Suppose ATT said: We won't bother sending calls to those folks in GTE
land. We've always hated GTE, and they're a pain, so to hell with
them.  Or the USPS said: Why should we bust our gut sending mail to
Canada - those damn Canadians don't buy our stamps.
[sarcasm mode, note no smily.]

After all, this IS the net, where being Politically Correct is
everything, and cooperation is nothing.

-- 
A host is a host from coast to coast.....wb8foz@mthvax.cs.miami.edu 
& no one will talk to a host that's close............(305) 255-RTFM
Unless the host (that isn't close)......................pob 570-335
is busy, hung or dead....................................33257-0335