Xref: utzoo news.admin:11594 comp.mail.misc:4603
Path: utzoo!mnetor!geac!torsqnt!news-server.csri.toronto.edu!math.lsa.umich.edu!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: Bogus addresses
Keywords: some deliberate
Message-ID: <1990Dec24.025350.26945@mthvax.cs.miami.edu>
Date: 24 Dec 90 02:53:50 GMT
Reply-To: wb8foz@mthvax.cs.miami.edu (David Lesher)
Distribution: na
Organization: NRK Clinic for habitual NetNews Abusers
Lines: 23

I've got a couple bogus address questions:

I've been seeing posts from people with valid FQDN From: headers, but
then an added Reply-To: foobar.UUCP header too!

Now I know the bogus .UUCP cruft in the From: headers typically comes
outdated versions of 'rn,' but what is adding the Reply-To: errors? I
see too many to think they are being done by hand.

Secondly, one site on the net seems to be deliberately BREAKING
outgoing addressing by making all postings and mail come from:
	nobody@XXXXX.com
and doing the same with the Reply-To: line, too.

This seems to be some internal dispute in the company. My question is:
what do the RFC's say about generating unusable addresses?


-- 
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