Xref: utzoo comp.sys.ibm.pc:12494 comp.binaries.ibm.pc:399
Path: utzoo!mnetor!uunet!seismo!sundc!pitstop!sun!decwrl!labrea!agate!pasteur!ames!hao!gatech!purdue!i.cc.purdue.edu!j.cc.purdue.edu!pur-ee!iuvax!bsu-cs!dhesi
From: dhesi@bsu-cs.UUCP (Rahul Dhesi)
Newsgroups: comp.sys.ibm.pc,comp.binaries.ibm.pc
Subject: Re: ROGUE FORWARDER
Message-ID: <2217@bsu-cs.UUCP>
Date: 27 Feb 88 00:35:45 GMT
References: <2145@bsu-cs.UUCP> <479@ruby.TEK.COM>
Reply-To: dhesi@bsu-cs.UUCP (Rahul Dhesi)
Followup-To: comp.sys.ibm.pc
Organization: CS Dept, Ball St U, Muncie, Indiana
Lines: 27
Summary: Solved

In article <479@ruby.TEK.COM> rjg@ruby.UUCP (Richard J. Greco) writes:
>I think the problem is harder then you think.  On my news feed SOME of
>the posted binaries wind up in comp.sys.ibm.pc and some of them wind
>up in the binaries group.

The problem has been located.  When Brandon Alberry stepped down as
moderator of comp.binaries.ibm.pc, he asked the backbones to make
"comp.binaries.ibm.pc" an alias to "comp.sys.ibm.pc".  Apparently this
alias still existed on some sites.  Articled posted to
comp.binaries.ibm.pc, when they passed through such sites, moved to
comp.sys.ibm.pc.

Depending on speed of propagation, an article might move through such a
site first, or through a different site first.  So it would appear in
one or the other newsgroup depending on the path it took getting to
you.  This is possible because there is some redundancy in the
network.

The backbones were sent a message by hao!woods (Greg Woods) requesting
that the alias be removed.  The problem should be fixed already.

This article is cross-posted to both comp.binaries.ibm.pc and
comp.sys.ibm.pc.  If it appears only in comp.sys.ibm.pc when you see
it, then the problem is still not fixed.  (However, follow-ups are
directed to comp.sys.ibm.pc only.)
-- 
Rahul Dhesi         UUCP:  <backbones>!{iuvax,pur-ee,uunet}!bsu-cs!dhesi