Article View: news.admin
Article #3273Re: New sendsys bomb
From: John De Armond
Date: Mon, 09 Nov 1992 09:15
Date: Mon, 09 Nov 1992 09:15
56 lines
3247 bytes
3247 bytes
rick@rgb.com (Rick Davis) writes: >We received a simalar message from the same individual. I have sent >mail to him requesting that he cease and desist. Yeah, this is the idiot who sent me mail accusing me of breaking into his system by virtue of his getting the famous "remain calm" message with my name on it in response to the sendsys. I was impressed at his complete ignorance of how a news system operates. I never thought he would go public with his stupidity. The most amazing part is that he'd actually think someone would want is little bitty sys file. Ha! Rick, Just in case you didn't get my mail, here's what I sent you: --------------------------------------------------- From jgd Fri Nov 6 17:34:20 1992 Subject: Re: Sendsys: Why? To: rgbsys!rick (Rick Davis) Date: Fri, 6 Nov 92 17:34:20 EST In-Reply-To: <9211061650.AA14216@rgbsys.rgb.com>; from "Rick Davis" at Nov 6, 92 8:50 am X-Mailer: ELM [version 2.3 PL11] >I sent you my piss-test list entry in good faith there; the list is >a fine use of net resources. Now it seems you are pilfering sys files >on the net. I have changed my sys file and told my contacts to do >the same. Now get the hell out of my system! Pardon my french, but you are really a dumb f*ck. On two accounts. First, the sendsys facility is designed PRECISELY to make your sys file publicly available. If you'd ever read any of the news.admin groups, or even the man pages for your news software, you'd know that AND you'd know how to set up your system NOT to respond to sendsys requests. Secondly, that sendsys was a forgery designed to try and overflow my system with mail from the thousands of systems that still respond to sendsys commands. This is a common prank pulled by the net.children against someone who says something they don't like. In anticipation of you not knowing what a sendsys control message is, I've included a copy of the forgery at the end of this message. Observe carefully the NNTP-Posting-Host: field. That should give even you a clue as to where the message actually came from. Frankly, my dear, I couldn't give a f*ck less what is in your sys file. It, along with several thousand others went directly to the bitbucket without my ever having looked at it. You really ought to learn a few things about running a news system before opening your mouth. Try and buy a clue if you can. John -------------------------------- end mail ------------------------------------ -- John De Armond, WD4OQC |Interested in high performance mobility? Performance Engineering Magazine (TM) | Marietta, Ga |Interested in high tech and computers? jgd@dixie.com |Write me about PE Magazine Need Usenet public Access in Atlanta? Write Me for info on Dixie.com.
Technical Details
Message-ID:
<g-aqtjr@dixie.com>Path:
arc1-ca.pugleaf.net!sparky!uunet!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!emory!rsiatl!jgdReferences:
<1992Nov6.193710.14566@rgb.com>Show Full Headers
Complete Article Headers
Newsgroups: news.admin Path: arc1-ca.pugleaf.net!sparky!uunet!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!emory!rsiatl!jgd From: jgd@dixie.com (John De Armond) Subject: Re: New sendsys bomb Message-ID: <g-aqtjr@dixie.com> Date: Mon, 09 Nov 92 09:15:26 GMT Organization: Dixie Communications Public Access. The Mouth of the South. References: <1992Nov6.193710.14566@rgb.com> Lines: 56