Article View: microsoft.public.security.homeusers
Article #45Re: Very Dangerous post
From: BD
Date: Sat, 23 Jan 2010 23:15
Date: Sat, 23 Jan 2010 23:15
86 lines
4997 bytes
4997 bytes
On 22/01/2010 23:35, John Eddy wrote: > Uh, no. I was laid off because it was decided that my job would be > outsourced. I had never received a complaint from any manager > regarding my treatment of you. > > And, frankly, if you think I based all my decisions on MVPs, you don't > know me. > > So, who in my management chain did you speak to, hmm? > > What tracks do you even think I needed to cover? > > I'm willing to post using MY real name, maybe you should do the same. > Hello John, I raised this matter in 'alt.computer.security' newsgroup - here's a copy of the thread:- ************* > "Mike Easter" wrote: to > | David H. Lipman >>> Filters on the MS New Server do NOT like the alt.* >>> hierarchy. >>> Thus the news group... alt.windows7.general >>> Was most likely the trigger that casued the post to be blocked from >>> being posted. > > | Such a filter would be really weird and inappropriate and tending > toward > | reckless behavior. > > | Are you suggesting that you think that the msnews filter would filter > | your post and this one of mine? > > > Well if it was x-posted from Usenet at large to the MS News Server, yes. Let's be clear that we are talking about such a string occurring in the body, not cross-posted with alt groups in the Newsgroups line. > For example a post made from usenet at large via... > alt.comp.virus,alt.comp.anti-virus,microsoft.public.security.virus > > Would NOT be found on the MS News Server in the > microsoft.public.security.virus group. Those lines are saying crossposted; not about the body only. > Likewise I have posted to the MS News Server and have suggested the > use of alt.comp.virus & alt.comp.anti-virus and the posts get blocked. Those lines appear to be saying in the body only. > However if I obfuscate it as; alt. comp.virus & alt. > comp.anti-virus the post will go through and not be blocked. Obfuscated body string works. > I don't know all the 'rules' applied but there is indeed much rules > based filtering on the Microsoft News server. My limited observation shows it to appear to have been a poorly admin/ed newsserver in the past - notwithstanding whether or not some of your friends may have been involved with its admin. Trying to auto-moderate a news server which is feeding and being fed by news servers worldwide is a whacky idea. The perils of trying to have a news server integrated with a web system are also well established and practically impossible to solve smoothly. - Mike Easter ********************** I'd be most interested to hear what you might have to say in regard to Mikes final paragraph -- Dave (Sometimes man stumbles over the truth ...... Sir Winston Churchill)
Technical Details
Message-ID:
<IbydnQcnBdOzHsbWnZ2dnUVZ8kednZ2d@bt.com>Path:
arc1-ca.pugleaf.net!g2news1.google.com!news1.google.com!Xl.tags.giganews.com!border1.nntp.dca.giganews.com!nntp.giganews.com!local2.nntp.dca.giganews.com!nntp.bt.com!news.bt.com.POSTED!not-for-mailReferences:
<DBCAAD85-FE46-4A45-82C2-6008223E2E79@microsoft.com> <Or$RHcmmKHA.1824@TK2MSFTNGP04.phx.gbl> <O22yQIqmKHA.1824@TK2MSFTNGP04.phx.gbl> <NcednTQbJL00_8XWnZ2dnUVZ8qxi4p2d@bt.com> <O9#Ia6smKHA.3128@TK2MSFTNGP02.phx.gbl> <n9adnWyYptyqcMXWnZ2dnUVZ8kNi4p2d@bt.com> <On9GgtvmKHA.5840@TK2MSFTNGP05.phx.gbl> <4b5909e2$0$9979$88263eea@blocknews.net> <ZM-dnSykXtHBKcTWnZ2dnUVZ8m6dnZ2d@bt.com> <4b59c2f5$0$26713$88263eea@blocknews.net> <egAnO73mKHA.3888@TK2MSFTNGP06.phx.gbl> <4b59f0a4$0$8553$88263eea@blocknews.net> <uY#Wcx6mKHA.5524@TK2MSFTNGP05.phx.gbl> <eqaDB96mKHA.5520@TK2MSFTNGP05.phx.gbl> <4b5a2a7b$0$8151$88263eea@blocknews.net> <8260d6eb-e604-4775-9a56-e8403a678a1a@f12g2000yqn.googlegroups.com>Show Full Headers
Complete Article Headers
X-Google-Thread: 4e777fa27a,d0399fc3995e38e7,start X-Google-Attributes: gid4e777fa27a,public,usenet X-Google-NewGroupId: yes X-Google-Language: ENGLISH,ASCII-7-bit Path: arc1-ca.pugleaf.net!g2news1.google.com!news1.google.com!Xl.tags.giganews.com!border1.nntp.dca.giganews.com!nntp.giganews.com!local2.nntp.dca.giganews.com!nntp.bt.com!news.bt.com.POSTED!not-for-mail NNTP-Posting-Date: Sat, 23 Jan 2010 17:15:58 -0600 Date: Sat, 23 Jan 2010 23:15:58 +0000 From: ~BD~ <BoaterDave@hotmail.co.uk.> User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.7) Gecko/20100111 Thunderbird/3.0.1 MIME-Version: 1.0 Newsgroups: microsoft.public.security.homeusers,24hoursupport.helpdesk Subject: Re: Very Dangerous post References: <DBCAAD85-FE46-4A45-82C2-6008223E2E79@microsoft.com> <Or$RHcmmKHA.1824@TK2MSFTNGP04.phx.gbl> <O22yQIqmKHA.1824@TK2MSFTNGP04.phx.gbl> <NcednTQbJL00_8XWnZ2dnUVZ8qxi4p2d@bt.com> <O9#Ia6smKHA.3128@TK2MSFTNGP02.phx.gbl> <n9adnWyYptyqcMXWnZ2dnUVZ8kNi4p2d@bt.com> <On9GgtvmKHA.5840@TK2MSFTNGP05.phx.gbl> <4b5909e2$0$9979$88263eea@blocknews.net> <ZM-dnSykXtHBKcTWnZ2dnUVZ8m6dnZ2d@bt.com> <4b59c2f5$0$26713$88263eea@blocknews.net> <egAnO73mKHA.3888@TK2MSFTNGP06.phx.gbl> <4b59f0a4$0$8553$88263eea@blocknews.net> <uY#Wcx6mKHA.5524@TK2MSFTNGP05.phx.gbl> <eqaDB96mKHA.5520@TK2MSFTNGP05.phx.gbl> <4b5a2a7b$0$8151$88263eea@blocknews.net> <8260d6eb-e604-4775-9a56-e8403a678a1a@f12g2000yqn.googlegroups.com> In-Reply-To: <8260d6eb-e604-4775-9a56-e8403a678a1a@f12g2000yqn.googlegroups.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Message-ID: <IbydnQcnBdOzHsbWnZ2dnUVZ8kednZ2d@bt.com> Lines: 86 X-Usenet-Provider: http://www.giganews.com X-AuthenticatedUsername: NoAuthUser X-Trace: sv3-yFdXHtX0IEMZR4/q/jRLkj7vIB9zbsLNQUE6UnG5XR50Sn9hS6Hkrpf5D9JHKxllq4lEHfr/Y0x8f6Y!l5t6MeUL2UB0adZuHVz2EYvMMyEiTTRGNyd5b1E3LradcSrZzc1OUxmuvvgt0cEsBrqQAnyeSOLU X-Complaints-To: abuse@btinternet.com X-DMCA-Complaints-To: abuse@btinternet.com X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly X-Postfilter: 1.3.40