HDTenEightyP/NetNews huggingface dataset:
Newsgroups: news.newsites
Subject: Map update for valinor [u.usa.fl.1]
From: stu@valinor.mythical.com (Stu Labovitz)
Date: Mon, 13 Apr 92 06:55:23 CDT
Distribution: world
Organization: (What? Organized??) - Mythical Computer Systems
Keywords: update,fl,maps

#N	valinor
#F	uunet.uu.net
#S	PC Brand 386/25C; MS-DOS 5.0; WAFFLE v1.64
#O	Mythical Computing Systems
#C	Stuart L Labovitz
#E	valinor!postmaster
#T	+1 904 897 1195
#P	1209 Whitewood Way, Niceville FL 32578-4217
#L	30 31 00 N / 086 28 56 W
#R
#U	uunet
#W	stu@valinor.mythical.com (Stu Labovitz); Mon Apr 13 06:45:34 CDT 1992
#
# 	Running WAFFLE v1.64 for uucp mail and USENET news
# 	Using an Intel 14.4EX V.32/V.32bis/V.42/V.42bis modem
#	Local feeds available: send email for more info
#
valinor =      valinor.mythical.com
valinor        .mythical.com(LOCAL+HIGH)
valinor        uunet(EVENING)
valinor        dayvb(DEAD)


----------------------------------------------------------------------

   Stuart L Labovitz                    Internet:  stu@valinor.mythical.com
    (insert standard disclaimer here)       UUCP:   uunet!valinor!stu

   Duct tape is like the force.  It has a light side, a dark side,
      and it holds the universe together.      --- Carl Zwanzig
=============================================================================
Newsgroups: news.newsites
From: scott@phlpa.UUCP (Scott Scheingold)
Subject: Site Update: phlpa
Organization: Ian's Playhouse
Date: Tue, 07 Apr 1992 13:13:12 GMT
Keywords: site update: phlpa


#N	phlpa
#S	80386 / SCO Xenix 2.3.3
#O	Ians Playhouse
#C	Scott Scheingold
#E	...!jabber!phlpa!root
#T	+1 215 732 7685
#P	1326 Spruce St Apt 906 Phila. Pa. 19107
#L	35 15 N / 072 06 W
#F	cs.widener.edu
#R	Soon to be Ians Playhouse BBS 
#R	Willing to provide E-mail and USENET newsfeed. 
#R	Call or send E-mail for more info.
#U	jabber cpp caligula widener
#W	scott%phlpa@ls.com (Scott Scheingold);  Fri Feb 14 17:47:32 EDT 1992
#
phlpa = phlpa.pha.pa.us
phlpa	cpp(DIRECT),  jabber(HOURLY+FAST), caligula(DIRECT),
	widener(DIRECT)
-- 
Need service? Ask me about USENET news feeds and mail service.
Scott Scheingold sysadmin   Voice   1-215-546-9959
UUCP 	...!{widener|dsinc}!jabber!phlpa!scott  or scott@phlpa.uucp
Compuserve 76057.607@compuserve.com
From: root@next32.isnet.com (Operator)
Newsgroups: news.newsites
Subject: Map update for next32.isnet.com
Date: 4 Apr 92 11:09:06 GMT
Article-I.D.: next32.1992Apr4.110906.10914
Reply-To: root@next32.isnet.com
Distribution: usa
Organization: is a sign of a sick mind...

#N	next32, next32.isnet.com
#S	NeXTStation, 4.3BSD over Mach
#O	Private
#C	Dave Strout
#E	root@next32.isnet.com 
#T	+1 703 385 3250
#P	12162 Penderview Lane apt 1601, Fairfax, Va 22033
#L	38 52 30 N / 77 23 80 W
#R	Custom NeXT Software Available -- NeXT Registered Developer
#	Usenet news feeds are available from next32.isnet.com or
#	ihost.isnet.com.
#	Send email to uucp-request@ihost.isnet.com for further
#	information.
#	We have one T2500 for dialin/out
#U	
#W	next32!root (Dave Strout) Sat Apr  4 06:06:45 GMT-0500 1992
#
next32	ihost(DIRECT+FAST), irscscm(HOURLY), ailanth(HOURLY)
next32 =  next32.isnet.com
From: vern@zebra.UUCP (Vernon C. Hoxie)
Newsgroups: news.newsites
Subject: Revised map info
Date: 9 Apr 92 05:20:01 GMT

#N	zebra
#S	AT&T 3B1; UNIX Sys V, ver. 3.51m
#O	very little
#C	Vernon C. Hoxie
#E	zebra!vern
#T	+1 303 455 2670
#P	3975 W. 29th Ave., Denver, Colo., 80212
#L	39 46 5.2 N / 105 2 19 W
#R	Unix-pc SIG local 
#U	scicom yonder
#W	zebra!vern (Vernon C. Hoxie); Wed Apr 8 23:15 MDT 1992
#
zebra = zebra.denver.co.us
zebra = zebra.alphacdc.com
zebra	scicom(DIRECT)

-- 
Vernon C. Hoxie                            {ncar,boulder}!scicom!zebra!vern
3975 W. 29th Ave.                                   
Denver, Colo., 80212        voice: 303-477-1780          uucp: 303-455-2670
From: jerry@strobe.ATC.Olivetti.Com (Jerry Aguirre)
Newsgroups: news.admin
Subject: 5 Meg article on the loose
Date: 9 Apr 92 03:28:50 GMT

I notice that many of my NNTP neighbors are refusing connections, usually
because their spool is full.  The volume has been on its usualy upswing
so that explains part of it.

But, while checking my space I found a article of size 5720333.  Yes,
thats right it is nearly 6 Meg for one article.  Apparently it is
someones runaway news stat posting.  You may want to look for it on your
system (it was in my junk) and delete it to free space.

The article header is:
Path: olivea!spool.mu.edu!sol.ctr.columbia.edu!usc!hacgate!news
    From: news@hacgate.UUCP
    Newsgroups: la.news,hac.usenet
    Subject: Weekly USENET Report for hacgate.scg.hac.com
    Message-ID: <21096@hacgate.UUCP>
    Date: 1 Apr 92 23:20:17 GMT
    Sender: news@hacgate.UUCP
    Lines: 635333
    Posted: Wed Apr  1 17:20:17 1992

Interestingly I am not supposed to be getting either la.news or
hac.usenet distributions.  Time to complain to my feed.
Xref: sparky news.admin:3608 alt.tv.tiny-toon:2221
From: klein@kira.egr.msu.edu (Jeffrey Klein)
Newsgroups: news.admin,alt.tv.tiny-toon
Subject: Re: Newgroup Forged
Date: 17 Apr 92 19:39:34 GMT
Article-I.D.: msuinfo.1992Apr17.193934.5383
Organization: Michigan State University College of Stunt Piloting

It seems that my efforts to rmgroup "rec.arts.tv.tiny-toon" aren't
going through...if anyone can send an rmgroup, I'd be grateful.

Oh, and THANK YOU MR. FORGER JERK AT PSINNTP!!!
-- 
Jeff Klein                  | "One of you is a Charlie Brown mutant,
                            |  and the other has a hand growing out  
klein@kira.egr.msu.edu      |  of his(?) head!" - Blue Bunny
Xref: sparky news.admin:3607 alt.tv.tiny-toon:2215
From: klein@kira.msu.edu (Jeffrey Klein)
Newsgroups: news.admin,alt.tv.tiny-toon
Subject: Newgroup Forged
Date: 17 Apr 92 17:21:57 GMT
Organization: Michigan State University College of Stunt Piloting
Originator: klein@kira.egr.msu.edu

Recently a newgroup command has been sent to newgroup "rec.arts.tv.tiny-toon".

It was in my name, but it was a forgery.  The header follows:
From: klein@kira.egr.msu.edu (Jeffrey Klein)
Newsgroups: alt.tv.tiny-toon
Subject: Another Henny Youngman Day Bit.
Date: 13 Apr 92 23:05:00 GMT
Control: newgroup rec.arts.tv.tiny-toon
Organization: Michigan State University College of Stunt Piloting


The Path: goes from "kiro-matsu" to psinntp.  The machine I post from is
kira, and posts through msuinfo.  Some jerk whose machine connects
through psinntp posted the original newgroup.  An rmgroup has been 
issued.

Also, about 20 old articles from alt.tv.tiny-toon have been reposted
to a.t.t-t and r.a.t.t-t, through psinntp.
-- 
Jeff Klein                  | "One of you is a Charlie Brown mutant,
                            |  and the other has a hand growing out  
klein@kira.egr.msu.edu      |  of his(?) head!" - Blue Bunny
Xref: sparky news.admin:3469 news.config:141
From: trev@hubcap.clemson.edu (Trevor Bauknight)
Newsgroups: news.admin,news.config
Subject: So how long are the old articles going to be puked back up?
Date: 8 Apr 92 04:23:33 GMT
Distribution: usa
Organization: Jes Grew Carriers -- Metaphysical Bunko Squad

Usually, it doesn't last this long.  Can't some news expert figure out 
where the old articles are being re-sent from?  My kill/select file
is getting tired of doing the same ol' articles over and over again.

Please.

 
Trevor Bauknight         trev@hubcap.clemson.edu    ...gatech!hubcap!trev
 
                                                     +-----------+
                                                     | _> ###    |
                  clownhead                          |     |     |
                                                     +-----------+
From: tinsel@uiuc.edu (Thomas Aaron Insel)
Newsgroups: news.admin
Subject: Re: Automatic disclaimers on outbound postings from a corporation
Date: 16 Apr 92 19:40:13 GMT
Reply-To: tinsel@uiuc.edu
Organization: {not speaking for the} University of Illinois at Urbana
Originator: tai50080@uxa.cso.uiuc.edu

rickert@mp.cs.niu.edu (Neil Rickert) writes:

>   Anybody reading usenet should already be assuming that postings are the
> individual poster's rantings and ravings.  Do you have to rub it in?

Yes, but most sites do exactly the opposite, and include an Organization:
header that seems to imply that the poster is representing the organization
in some capacity.
-- 
Thomas Aaron Insel (tinsel@uiuc.edu)
  I speak for myself, and not for the State or University of Illinois.
  "We must not confuse dissent with disloyalty." -- Edward R. Murrow
From: gritton@altar.caedm.byu.edu (Jamie Gritton)
Newsgroups: news.admin
Subject: Re: (yet another) sendsys alternative
Date: 7 Apr 92 16:02:41 GMT
Article-I.D.: altar.GRITTON.92Apr7110241
	<1992Apr7.133221.19856@unhtel.unh.edu>
Reply-To: gritton@byu.edu
Organization: Brigham Young University, Provo UT USA

paul@unhtel.unh.edu (Paul S. Sawyer) writes:

>That might be a good idea;  why not just put it into the maps as "#U"
>lines?  Many would be something like:

Usenet isn't the same as the UUCP net. Particularly, there are us Internet
news sites who don't have entries in the maps. I wouldn't mind publishing
my sys file, but I don't want to bother making a "fake" UUCP map for my site.
--
James Gritton - gritton@byu.edu - I disclaim
From: mrapple@quack.sac.ca.us (Nick Sayer)
Newsgroups: news.admin
Subject: Re: I've forged a cancel of a sendsys
Date: 9 Apr 92 14:55:19 GMT
Organization: The Duck Pond public unix: +1 408 249 9630, log in as 'guest'.

ckd@eff.org (Christopher Davis) writes:

>The major problem with the "don't send to sendsys@site.UUCP" scheme is
>that there are a fair number of MXed domains out there; a friend of mine
>got sendsys-bombed a while back, and though he was on a domainified
>site, it wasn't a "real" Internet site.

I think you're missunderstanding my proposal. All I said was to
reject/autocancel sendsys news messages not directed to 'sendsys@[anything]'.
That's really the only change necessary to Usenet. With this fix,
it is impossible to bomb people's mailboxes and it is impossible to
bomb a site that gets mail with smtp. It is still possible to bomb a
uucp site. The fix for that is for that site's uucp feed to reject any
mail for 'sendsys@site.uucp'. It's an individual decision for that feed
site to make. And it gets around the whole issue of mx records, since
that feed site is going to have to send it to a uucp mailer. That mailer
then looks to see if the destination address is 'sendsys' and if so, drops
it on the floor.

There's nothing wrong with a sendsys whose destination is
'sendsys@foobar.uucp'. It's up to foobar's feed site to either allow
or disallow that mail.

-- 
Nick Sayer <mrapple@quack.sac.ca.us> | "Do you know how lucky you are we
N6QQQ @ N0ARY.#NOCAL.CA.USA.NA       | even HAVE cereal?! Why, when I was
37 19 49 N / 121 57 36 W             | your age, we ate wood and rocks!"
+1 408 249 9630, log in as 'guest'   | 		  -- Ren
From: hennebry@plains.NoDak.edu (Michael J. Hennebry)
Newsgroups: news.admin
Subject: Re: I've forged a cancel of a sendsys
Date: 6 Apr 92 16:27:01 GMT
Article-I.D.: plains.16486
Organization: North Dakota State University, Fargo, ND

In article <8_9He$ae6@cs.psu.edu> dsbarr@cs.psu.edu writes:
<In article <ivlimr8@fido.asd.sgi.com> dauber@sgi.com (Jeff Dauber) writes:

<>How about sendsys with an acknowledge, where it sends a message to the
<>person who the sendsys will reply to.  If that person does not respond,
<>the sendsys will not happen.
<
<Huh?  So instead of N sys files being sent back to the victim, we have N
<acknowlegements getting sent back.  How does this improve anything?

Not quite. If the sendsys does not get propagated, then requests for
confirmation will be reduced. Leakage may be a problem, especially to
start with.

<What's worse, if it is legit, we now have to have N confirmation messages
<sent out to the respective machines, who then send N sys files back.
<Great, we just increased the mail traffic by 3 times.

Depends on the relative size of handshaking and sendsys files.

A way to cure the leakage problem is to regard a failure to handshake
as permission to "forge" a cancel. I suppose one could put something in
the header for news admins who object to that sort of thing and do not
want to propagate it. One way to reduce the handshaking volume is to
forgo it when the sendsys comes from a site known to do handshaking.

--
Mike   hennebry@plains.NoDak.edu
"To telephone Valhalla from the Taunton area one must go
through the operator, and the process can take a long time." -- Tom Holt
From: dylan@ibmpcug.co.uk (Matthew Farwell)
Newsgroups: news.admin
Subject: Re: 1st (?) senduuname bomb, and a fast fix
Date: 7 Apr 92 10:11:18 GMT
Organization: The IBM PC User Group, UK.

In article <1992Apr3.211011.26956@zoo.toronto.edu> henry@zoo.toronto.edu (Henry Spencer) writes:
>In article <1992Mar31.163334.9545@ukw.uucp> lupe@ukw.uucp (Lupe Christoph) writes:
>>Geoff, Henry, what is your opinion to implement an authentication
>>mechanism in CNews for automated replies, addgroups, rmgroups, etc ?
>>I.e. you send mail to the news user. If it should be processed,
>>he will forward it with a password to some mail alias.
>We'd much rather have something that works even if the news admin is on
>vacation, sick, or simply not paying attention.

We've been having problems with our newsfeed recently, so sorry if this
is the second time you've seen this:

Can anyone give me a good reason not to disable senduuname?

There are various arguments about whether or not sendsys is a good
thing, but I cannot really see any valid reason for senduuname.  There
are sites which have different uucp names than news names (two of my
downstream feeds for a start), there are sites which don't have a uuname
command, and there are sites which may not want to advertise a
particular link (my uucp files contain numbers for anomaly & osu-cis,
which are anonymous uucp sites - I'd hardly call those links, but they
show up in uuname).

Might it be a good idea to drop it from the Son-of-RFC 1036 altogether?

Dylan.
-- 
'If there is a hung parliament, and John Major and Neil Kinnock have
both been hung, then I am willing to take over.  Vote Insanity - you
know it makes sense' - Screaming Lord Sutch
From: gritton@alaska.caedm.byu.edu (Jamie Gritton)
Newsgroups: news.admin
Subject: results of usa.* test, and "usa" vs "us"
Date: 13 Apr 92 04:20:04 GMT
Reply-To: gritton@byu.edu
Organization: Brigham Young University, Provo UT USA


   My recent test post to usa.config (carried along by news.admin) indicates
(to me at least) that the usa.* hiearchy, namewise, is feasable.

I got "test" reflections from:
uop.uop.edu
HARPERVM.BITNET

   I've sent mail to both of these, but got no reply. Anyway, these are a
bother only to potential posters, not to "innocents," and I don't see them
lasting long once things really get going.

The post showed up on these mailing lists:
minix-l@plains.nodak-edu
hp48@seq.uncwil.edu
hp48-sys@seq.uncwil.edu
info-minix@udel.edu
amiga-programmer-relay@udel.edu
net-people@cs.rutgers.edu
advanced-dist@cs.rutgers.edu

   Here also, I've not had the best of luck with getting replies. I talked to
the maintainer of the hp48 lists, and he changed his sys file to stop the
leak. This prophesies good fortune if only I can contact the other
maintainers. With the limited number of lists, I expect this can be done
soon. The advanced-dist list, and perhaps net-people, may be Rutgers-only
lists.

   There were a few other cases of the post showing up in peoples' mail
and them not knowing why. These may be harder to trace, but seem few enough.
My recent mass mailing to news sites whose sys files I checked may plug
many of these "mystery" holes, incluing the postings going to UUCP map
readers, which should just discard them anyway (or do they complain loudly?).

   I've also gotten a few reminders from those who have to pay for their news
that the hiearchy would profoundly increase their traffic. These would mostly
be sites that have a few groups they're interested in and get the usa
distribution. Were we to try to act to prevent this on the many sites
it will affect, we might as well give up on the name "usa" now. But as this
requires only a change to their feeds' sys files, and the ones impacted are
the administrators themselves, I'm ignoring this problem, figuring that once
they notice it (or before if they're followng what's going on here), the
admins of the sites affected will fix their own problems soon enough.
Particularly, if the large feeder sites (i.e. UUNET) default to not
propagating the hiearchy unless asked for, this will become a non-issue
to many sites.

   I wouldn't really mind seeing the hiearchy's name change to "us". It's
the ISO name, and the same as the US's DNS name, plus it's that much shorter.
The only advantage to "usa", and it's big enough to sway me, is that "usa"
already exists as a distribution. I.e. it has usage behind it. That's the
same attribute that others see as "usa"'s big disadvantage. Were the hiearchy
to be called "us" instead, a "us" distribution would soon follow, both from
people's perception of the name space and from existing software's workings.
Thus there would be two distributions for one region, which opens its own
can of worms. The question: which problem is worse?
--
James Gritton - gritton@byu.edu - I disclaim
Newsgroups: news.admin
From: henry@zoo.toronto.edu (Henry Spencer)
Subject: Re: 1st (?) senduuname bomb, and a fast fix
Date: Fri, 10 Apr 1992 23:02:52 GMT
Organization: U of Toronto Zoology

In article <1992Apr07.101118.12652@ibmpcug.co.uk> dylan@ibmpcug.co.uk (Matthew Farwell) writes:
>... but I cannot really see any valid reason for senduuname.  There
>are sites which have different uucp names than news names (two of my
>downstream feeds for a start), there are sites which don't have a uuname
>command, and there are sites which may not want to advertise a
>particular link ...
>
>Might it be a good idea to drop it from the Son-of-RFC 1036 altogether?

I am inclined to agree with this (although in practice this means mentioning
it as obsolete, rather than omitting it entirely -- the intent is to describe
existing practice rather than some mythical ideal wherever possible).  Does
anybody disagree?
-- 
GCC 2.0 is to C as SVR4 is to Unix.     | Henry Spencer @ U of Toronto Zoology
                             -Dick Dunn |  henry@zoo.toronto.edu  utzoo!henry
From: kherron@ms.uky.edu (Kenneth Herron)
Newsgroups: news.admin
Subject: Non-compliant articles, week ending 12 April 92
Date: 12 Apr 92 11:44:32 GMT
Organization: University Of Kentucky, Dept. of Math Sciences


         Invalid Headers, week ending 12 April 92

    The following is a list of Message IDs of articles which were dropped
    by the news software here for a non-compliant header.  If a message ID
    from your site is on this list, your news software is probably out of 
    compliance with the RFCs on netnews articles and should be fixed.

Header contains non-header line:
	<3302@daily-planet.concordia.ca> `Keywords:VALID, EDIF'
	<14161@claris.com> `Organization:'
	<35040@nntpd.lkg.dec.com> `Summary:'
	<1992Apr6.122902.21854@e2big.mko.dec.com>
		`Keywords:flourescent light, ballast'
	<1992Apr9.144026.16886@ryn.mro4.dec.com>
		`Summary:what axe does the cat play?'
	<7707@travis.csd.harris.com> `Distribution:'
	<2102@transfer.stratus.com> `atus Computer, Inc.'
	<1520@tymix.Tymnet.COM> `Distribution:na'
	<83493@bu.edu> `Keywords:'
	<83802@bu.edu> `References:'
	<1992Apr08.212906.31040@slate.mines.colorado.edu>
		`Summary:Arafat made it again (thank God)'
	<STEVELA.92Apr10161217@beach.csulb.edu> `27@syma.sussex.ac.uk>'
	<2257@news.duke.edu> `Cc:'
	<1992Apr6.193831.3332@cfa.harvard.edu>
		`Reply-To:meleedy@cfa.harvard.edu'
	<43958@mentor.cc.purdue.edu> `ummary:'
	<1992Apr7.085558.5920@noose.ecn.purdue.edu> `Distribution:usa'
	<1992Apr7.090213.6204@noose.ecn.purdue.edu> `Distribution:usa'
	<12033@ucdavis.ucdavis.edu> `Expires:'
	<1992Apr9.150509.24628@eng.ufl.edu> `Subject:Liquid Sky '
	<2830@ub.d.umn.edu>
		`Sender:dratliff@ub.d.umn.edu, dratliff@va.d.umn.edu, drat...'
	<2833@ub.d.umn.edu> `Summary:A discussion of all aspects dealing with.'
	<2848@ub.d.umn.edu> `Sender:cwischne@ub.d.umn.edu   (Curt Wischnewski)'
	<11193@borg.cs.unc.edu> `Keywords:'
	<11209@borg.cs.unc.edu> `Followup-To:'
	<11213@borg.cs.unc.edu> `Keywords:'
	<11225@borg.cs.unc.edu> `Followup-To:'
	<122068@lll-winken.LLNL.GOV>
		`References:<26623@ursa.UUCP> <3APR92084945@b56vxg.kp01.ko...'
	<8862@alvin.mcnc.org> `Distribution:na'
	<220@mnopltd.UUCP> `Distribution:'
	<221@mnopltd.UUCP> `Distribution:'
	<222@mnopltd.UUCP> `Distribution:'
	<223@mnopltd.UUCP> `Distribution:'
	<224@mnopltd.UUCP> `Distribution:'

Unapproved article in moderated group:
	<1992Apr8.193035.16352@ms.uky.edu> `rec.guns'

No @ in Message ID:
	8003 
	<1991Dec2509:00:00> 

No From: header:
	<1992Apr9.220721.8488@iscnvx.lmsc.lockheed.com> 
	<1992Apr11.144855.19790@sparc4.ncu.edu.tw> 

No Date or unparsable Date:
	<glock.11@glock.chip.cba.ufl.edu> `<glock.11@glock.chip.cba.ufl.edu>'
	<glock.14@glock.chip.cba.ufl.edu> `<glock.14@glock.chip.cba.ufl.edu>'
	<jcy.1@eng.ufl.edu> `<jcy.1@eng.ufl.edu>'
From: paul@unhtel.unh.edu (Paul S. Sawyer)
Subject: Re: (yet another) sendsys alternative
Organization: UNH Telecommunications and Network Services
Date: Tue, 7 Apr 1992 13:32:21 GMT

In article <9917095@tronix.SignalPath.on.ca> louis@tronix.SignalPath.on.ca (Louis Bertrand) writes:
>There seems to be a wish to map the net on an
>occasional basis (2-3 months), and the sendsys
>mechanism is not a Good Thing anymore.
>
>The uucp maps provide the information needed
>to map the uucp net for mailing, and the distribution
>of maps occurs regularly via the *.maps newsgroups.
>
>I propose that sendsys and senduuname be permanently disabled
>and replaced it with a regular publishing of the sys files 
>in a new newsgroup.  If the volume is too large, the sysfile 
>newsgroup could be made regional (e.g. ont.sysfiles, tx.sysfiles).
> ...

That might be a good idea;  why not just put it into the maps as "#U"
lines?  Many would be something like:

...
#U	ME:all
#U	myfeed:all/all,!local:f:
...
-- 
Paul S. Sawyer    - University of New Hampshire CIS - paul@unhtel.unh.edu
Telecommunications and Network Services             - VOX: +1 603 862 3262
Durham, New Hampshire  03824-3523                   - FAX: +1 603 862 2030
From: pfalstad@phoenix.Princeton.EDU (Paul Falstad)
Newsgroups: news.admin
Subject: Re: Sendsys police
Date: 5 Apr 92 18:38:01 GMT
Organization: League For Fighting Chartered Accountancy
Originator: news@ernie.Princeton.EDU

kaminski@netcom.com (Peter Kaminski) wrote on 3 Apr 92 23:58:04 GMT:
>A few volunteer (preferably backbone) sites can refuse to propagate
>and automatically forge a cancel (or a duplicate-ID post) for any
>sendsys articles, unless they originate from someone on a list of
>validated sendsys requestors.
>
>Said list would be maintained by a sendsys "moderator," who would
>handle validating the requestor (just by emailing back "Did you really
>want to sendsys?"), and who would send updated lists to the volunteer
>sites whenever appropriate.

Yes, this sounds like a good idea.  And it probably should be done
automatically.  Just have a number of backbone sites automatically forge
cancels for all sendsys's they get that are not "validated".  The
validation would have to be done ahead of time; there isn't enough time
to email back to the person "Did you really want to sendsys?" before the
victim's mailbox fills up.  Whenever someone wants to do a sendsys, they
just send mail to the police, who will add the user to the validation lists
temporarily.

The time delay is probably a better idea, but it's harder to implement.
This could be done now.  Plus, a time delay could be added to this scheme
to make sendsys-bombs even less effective.

-- 
Paul Falstad, pfalstad@phoenix.princeton.edu | 10 PRINT "PRINCETON CS"
[Your blood pressure just went up.]          | 20 GOTO 10