Xref: utzoo news.admin:11667 news.software.b:6526
Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!cs.utexas.edu!wuarchive!uunet!olivea!olivey!jerry
From: jerry@olivey.olivetti.com (Jerry Aguirre)
Newsgroups: news.admin,news.software.b
Subject: Re: Is the "ME:" entry in news/sys really needed?
Summary: !to,to.ME is wrong!
Message-ID: <50061@olivea.atc.olivetti.com>
Date: 3 Jan 91 21:11:20 GMT
References: <3131@papaya.bbn.com> <1990Dec28.072258.28739@zoo.toronto.edu> <1991Jan02.002015.17758@quest.UUCP>
Sender: news@olivea.atc.olivetti.com
Followup-To: news.admin
Organization: Olivetti ATC; Cupertino, CA
Lines: 31

In article <1991Jan02.002015.17758@quest.UUCP> ssb@quest.UUCP (Scott Sheldon Bertilson) writes:
>
>  I'm using "ME:" under C news and B news, but have a tendency to
>want to be able to say:
>	ME:all,!to,to.ME/all:

I think that this is incorrect.  Unlike the feed entries the "ME" entry
must have just "to", not "to.ME".  While this won't cause problems for
most sites consider what happens if you post to "to.neighbor" to send
something just to that site.  Because "to.neighbor" is blocked by the
"ME" entry the posting will, or at least should, be rejected locally.
Thus you might as well scrap your "to.neighbor" distributions in the
other "sys" entries.  You won't be able to use them.

This is a, perhaps, unfortunate side effect of the way the software
functions.  It can not send an article to a neighbor without storing
and processing it locally.  Thus a sendsys, directed to a neighbor
site, will return not only the neighbors sys file but your own as well!

While it is possible that a "to.bogus" might reach your site and be
acted apon I don't think it is something you should be worried about
blocking.  I suppose you could use:

	!to,to.ME,to.neighbor1,to.neighbor2,...

At least you would only have to do it on the ME line.

Is there documentation somewhere that recomends using "to.myname"
on the "ME" line?

					Jerry Aguirre