Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.2 9/12/84; site desint.UUCP Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxt!houxm!vax135!cornell!uw-beaver!tektronix!hplabs!sdcrdcf!trwrb!desint!geoff From: geoff@desint.UUCP (Geoff Kuenning) Newsgroups: net.sources,net.news Subject: Re: about cmsg cancel Message-ID: <137@desint.UUCP> Date: Sat, 2-Nov-85 20:21:48 EST Article-I.D.: desint.137 Posted: Sat Nov 2 20:21:48 1985 Date-Received: Tue, 5-Nov-85 09:13:54 EST References: <134@desint.UUCP> <319@Glacier.ARPA> Reply-To: geoff@desint.UUCP (Geoff Kuenning) Distribution: net Organization: SAH Consulting, Manhattan Beach, CA Lines: 18 Xref: watmath net.sources:3810 net.news:4258 In article <319@Glacier.ARPA> reid@Glacier.UUCP (Brian Reid) writes: >It seems only appropriate to say this in net.sources, which is obviously >the wrong group. I have just run a series of tests of control messages >and cancelling. A properly-formed control message will not show up in >the newsgroup whose message it is cancelling. In other words, if you >read a "cmsg cancel" message in net.sources, that means it didn't work. >Properly-formed control messages get shunted to group "control". Brian is right that a properly-formed control message should be invisible, and we can be thankful the intruder made a formating error. However, on my machine (2.10.2 news with most patches), the damn things still seem to cancel articles successfully. At least, my investigations have shown "cancelled" messages in my history file for some of these articles. -- Geoff Kuenning {hplabs,ihnp4}!trwrb!desint!geoff