It is not usenet. It is commercial property of MS. They allow usenet type
servers to take feeds.
Geez... what a dummy. Looking at your own header (shown below) for
this post shows even you yourself have accessed this newsgroup via
Usenet. Are you learning yet? Again you try to argue the absurd. Of
course Microsoft set up this newsgroup and hundreds of others like it
as a "service" to their customers to have a place to discuss various
Microsoft applications. That isn't the point you blithering doofus.
They don't "own" the groups as some other blockheads have suggested
which would incorrectly imply they could control the content or knock
off certain posters regardless where such poster's originates his
posts from. ANYBODY running a news server could use commands to
selectively delete posts FROM THEIR news server if they took the time
to bother. They could even use some abscure cancel commands that may
or may not be accepted by other news servers, but I'm sure Microsoft
employees have better things to do with their time.
Since there are hundreds, perhaps thousands of news servers all over
the world even down under when <.> is posting from Microsoft has no
control over any of them.
For those interested, you read the last four lines (below) backwards,
right to left to trace how any post reached YOUR news server or how
YOU accessed this newsgroup. To do that you need to make what's called
the "header" visible. Not all news readers make it easy to view. The
tool I use, Agent, does make it simple. All the names are different
news servers or routers on the path from where <.> originated his
post, in Australia to travel to my news sever usenetserver.com that is
located in Florida.
That information doesn't mean I live in Florida, only that's the
location of the "copy" of <.>'s post I'm accessing. As any fool can
see for themselves usenetserver com is NOT part of Microsoft's empire,
rather it is one of the larger third party news server providers
anybody can subscribe to for a fee.
In a similar vain just because <.> posted to a news server in
Australia doesn't mean he lives there. However using a whois that I
posted the results of the other day showed who is behind the IP
address 202.155.163.22. A few clicks later then name using simple
search tools on the web strongly suggest who <.> actually is because
he is reckless in is feeble attempt to try to hide, assuming he's
trying, it much more seems likely he is just delusional.
From: <.>
References: <
[email protected]>
<#
[email protected]>
<
[email protected]> <S7UKh.765$yj7.741@trnddc02>
<#
[email protected]>
<
[email protected]>
In-Reply-To: <
[email protected]>
Subject: Re: WHINE, WHINE, WHINE
Date: Mon, 26 Mar 2007 20:37:30 +1000
Lines: 35
MIME-Version: 1.0
Content-Type: text/plain;
format=flowed;
charset="iso-8859-1";
reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Windows Mail 6.0.6000.16386
X-MimeOLE: Produced By Microsoft MimeOLE V6.0.6000.16386
Message-ID: <
[email protected]>
Newsgroups: microsoft.public.windows.vista.general
NNTP-Posting-Host: 202-155-163-22.chilli.net.au 202.155.163.22
Path:
beO3!out02b.usenetserver.com!news.usenetserver.com!in02.usenetserver.com!
news.usenetserver.com!in03.usenetserver.com!news.usenetserver.com!hwmnpeer01.
phx!news.highwinds-media.com!newsfeed.news2me.com!newshub.sdsu.edu!msrtrans!
msrnewsc1!TK2MSFTFEEDS01.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP03.phx.gbl