From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=5.0 tests=DKIM_INVALID,DKIM_SIGNED, HTML_MESSAGE,MAILING_LIST_MULTI,RCVD_IN_DNSWL_NONE autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 17391 invoked from network); 1 Apr 2021 12:29:08 -0000 Received: from minnie.tuhs.org (45.79.103.53) by inbox.vuxu.org with ESMTPUTF8; 1 Apr 2021 12:29:08 -0000 Received: by minnie.tuhs.org (Postfix, from userid 112) id 89A649C82B; Thu, 1 Apr 2021 22:29:07 +1000 (AEST) Received: from minnie.tuhs.org (localhost [127.0.0.1]) by minnie.tuhs.org (Postfix) with ESMTP id 629689C63E; Thu, 1 Apr 2021 22:28:14 +1000 (AEST) Authentication-Results: minnie.tuhs.org; dkim=fail reason="signature verification failed" (1024-bit key; secure) header.d=mxes.net header.i=@mxes.net header.b="ZUi/uStw"; dkim-atps=neutral Received: by minnie.tuhs.org (Postfix, from userid 112) id D84BF9C63E; Thu, 1 Apr 2021 22:28:11 +1000 (AEST) X-Greylist: delayed 415 seconds by postgrey-1.36 at minnie.tuhs.org; Thu, 01 Apr 2021 22:28:10 AEST Received: from fbo-3.mxes.net (fbo-3.mxes.net [198.205.123.65]) by minnie.tuhs.org (Postfix) with ESMTPS id EC2A09C63D for ; Thu, 1 Apr 2021 22:28:10 +1000 (AEST) Received: from smtp-out-4.mxes.net (smtp-out-4.mxes.net [198.205.123.69]) by fbi-3.mxes.net (Postfix) with ESMTP id 4FB2ND2cGTz3c9P for ; Thu, 1 Apr 2021 08:21:15 -0400 (EDT) Received: from Customer-MUA (mua.mxes.net [10.0.0.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 4FB2N93sSbz3cC0 for ; Thu, 1 Apr 2021 08:21:13 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mxes.net; s=mta; t=1617279674; bh=ytuJ1pSXqzzaEmIGU4yOr25i+KW9NosDkGv4YKPPOxk=; h=From:To:Subject:Date:Message-Id:Reply-To:Mime-Version: Content-Type; b=ZUi/uStw5IJdXIVZPTL7+mitg76QfqRKK0dO49/KOJgLAFG0LAIBkR/I2TNurV9au iYiXpW6tuw1NoUQdvOB0/Tn2FoU40pqqEGrv9trl5pAXDfC/4DFXgkAn/hFa/NJLUb yF5E2X00cDd8ZwQWS4ruetcbpthTEV3qMk9kcuYg= From: "Ron Natalie" To: "The Unix Heritage Society mailing list" Date: Thu, 01 Apr 2021 12:21:10 +0000 Message-Id: User-Agent: eM_Client/8.1.1083.0 Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="------=_MB62039111-C9F2-4200-BD56-BDA8685F92D3" X-Sent-To: Subject: [TUHS] 30th Anniversary of most epic netnews post X-BeenThere: tuhs@minnie.tuhs.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: The Unix Heritage Society mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Ron Natalie Errors-To: tuhs-bounces@minnie.tuhs.org Sender: "TUHS" --------=_MB62039111-C9F2-4200-BD56-BDA8685F92D3 Content-Type: text/plain; format=flowed; charset=utf-8 Content-Transfer-Encoding: quoted-printable >From spaf@cs.purdue.EDU Thu Apr 4 23:11:22 1991=0APath: ai-lab!mintaka!mit= -eddie!wuarchive!usc!apple!amdahl!walldrug!moscvax!perdue!spaf=0AFrom: spaf= @cs.purdue.EDU (Gene Spafford)=0ANewsgroups: news.announce.important,news.a= dmin=0ASubject: Warning: April Fools Time again (forged messages on the loo= se!)=0AMessage-ID: <4-1-1991@medusa.cs.purdue.edu>=0ADate: 1 Apr 91 00:00:0= 0 GMT=0AExpires: 1 May 91 00:00:00 GMT=0AFollowup-To: news.admin=0AOrganiza= tion: Dept. of Computer Sciences, Purdue Univ.=0ALines: 25=0AApproved: spaf= @cs.purdue.EDU=0AXref: ai-lab news.announce.important:19 news.admin:8235=0A= =0AWarning: April 1 is rapidly approaching, and with it comes a USENET=0Atr= adition. On April Fools day comes a series of forged, tongue-in-cheek=0Ames= sages, either from non-existent sites or using the name of a Well Known=0AU= SENET person. In general, these messages are harmless and meant as a joke,= =0Aand people who respond to these messages without thinking, either by fla= ming=0Aor otherwise responding, generally end up looking rather silly when= the=0Aforgery is exposed.=0A=0ASo, for the few weeks, if you see a message= that seems completely out=0Aof line or is otherwise unusual, think twice be= fore posting a followup=0Aor responding to it; it's very likely a forgery.= =0A=0AThere are a few ways of checking to see if a message is a forgery. Th= ese=0Aaren't foolproof, but since most forgery posters want people to figur= e it=0Aout, they will allow you to track down the vast majority of forgerie= s:=0A=0A o Russian computers. For historic reasons most forged messages hav= e=0A as part of their Path: a non-existent (we think!) russian=0A compu= ter, either kremvax or moscvax. Other possibilities are=0A nsacyber or wo= begon. Please note, however, that walldrug is a real=0A site and isn't a= forgery.=0A=0A o Posted dates. Almost invariably, the date of the posting i= s forged=0A to be April 1.=0A=0A o Funky Message-ID. Subtle hints are oft= en lodged into the=0A Message-Id, as that field is more or less an unpars= ed text string=0A and can contain random information. Common values inclu= de pi,=0A the phone number of the red phone in the white house, and the= =0A name of the forger's parrot.=0A=0A o subtle mispellings. Look for sub= tle misspellings of the host names=0A in the Path: field when a message i= s forged in the name of a Big=0A Name USENET person. This is done so that = the person being forged=0A actually gets a chance to see the message and = wonder when he=0A actually posted it.=0A=0AForged messages, of course, a= re not to be condoned. But they happen, and=0Ait's important for people on= the net not to over-react. They happen at this=0Atime every year, and the f= orger generally gets their kick from watching the=0Anovice users take the p= osting seriously and try to flame their tails off. If=0Awe can keep a level = head and not react to these postings, they'll taper off=0Arather quickly a= nd we can return to the normal state of affairs: chaos.=0A=0AThanks for you= r support.=0A=0AGene Spafford, Net.God (and probably tired of seeing this m= essage) --------=_MB62039111-C9F2-4200-BD56-BDA8685F92D3 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable =0A=0A=0A=0A
From spaf@cs.purdue.EDU Thu Apr  4 23:11:22 1=
991=0APath: ai-lab!mintaka!mit-eddie!wuarchive!usc!apple!amdahl!walldrug!mo=
scvax!perdue!spaf=0AFrom: spaf@cs.pur=
due.EDU (Gene Spafford)=0ANewsgroups: news.announce.important,news.admi=
n=0ASubject: Warning: April Fools Time again (forged messages on the loose!=
)=0AMessage-ID: <4-1-19=
91@medusa.cs.purdue.edu>=0ADate: 1 Apr 91 00:00:00 GMT=0AExpires: 1=
 May 91 00:00:00 GMT=0AFollowup-To: news.admin=0AOrganization: Dept. of Comp=
uter Sciences, Purdue Univ.=0ALines: 25=0AApproved: spaf@cs.purdue.EDU=0AXref: ai-lab news.announce.importan=
t:19 news.admin:8235=0A=0AWarning: April 1 is rapidly approaching, and with =
it comes a USENET=0Atradition. On April Fools day comes a series of forged=
, tongue-in-cheek=0Amessages, either from non-existent sites or using the n=
ame of a Well Known=0AUSENET person. In general, these messages are harmles=
s and meant as a joke,=0Aand people who respond to these messages without t=
hinking, either by flaming=0Aor otherwise responding, generally end up look=
ing rather silly when the=0Aforgery is exposed. =0A=0ASo, for the few weeks=
, if you see a message that seems completely out=0Aof line or is otherwise=
 unusual, think twice before posting a followup=0Aor responding to it; it's=
 very likely a forgery.=0A=0AThere are a few ways of checking to see if a me=
ssage is a forgery. These=0Aaren't foolproof, but since most forgery poster=
s want people to figure it=0Aout, they will allow you to track down the vas=
t majority of forgeries:=0A=0A	o Russian computers. For historic reasons mo=
st forged messages have=0A	  as part of their Path: a non-existent (we thin=
k!) russian=0A	  computer, either kremvax or moscvax. Other possibilities a=
re=0A	  nsacyber or wobegon. Please note, however, that walldrug is a real=
=0A	  site and isn't a forgery.=0A=0A	o Posted dates. Almost invariably, th=
e date of the posting is forged=0A	  to be April 1. =0A=0A	o Funky Message-=
ID. Subtle hints are often lodged into the=0A	  Message-Id, as that field i=
s more or less an unparsed text string=0A	  and can contain random informat=
ion. Common values include pi,=0A	  the phone number of the red phone in th=
e white house, and the =0A	  name of the forger's parrot.=0A=0A	o subtle mi=
spellings. Look for subtle misspellings of the host names=0A	  in the Path: =
field when a message is forged in the name of a Big=0A	  Name USENET perso=
n. This is done so that the person being forged=0A	  actually gets a chance =
to see the message and wonder when he=0A	  actually posted it.=0A=0AForged =
messages, of course, are not to be condoned. But they happen, and=0Ait's i=
mportant for people on the net not to over-react. They happen at this=0Atim=
e every year, and the forger generally gets their kick from watching the=0A=
novice users take the posting seriously and try to flame their tails off. I=
f=0Awe can keep a level head and not react to these postings, they'll taper =
off=0Arather quickly and we can return to the normal state of affairs: cha=
os.=0A=0AThanks for your support.=0A=0AGene Spafford, Net.God (and probably =
tired of seeing this message)
=0A --------=_MB62039111-C9F2-4200-BD56-BDA8685F92D3--