Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.milw.wisc.edu!cs.utexas.edu!uunet!wugate!wupost!kuhub.cc.ukans.edu!sloane From: SLOANE@kuhub.cc.ukans.edu (Bob Sloane) Newsgroups: news.software.anu-news Subject: Re: Rename newsgroups? Message-ID: <7751@kuhub.cc.ukans.edu> Date: 4 Aug 89 18:11:17 GMT References: <6342@kuhub.cc.ukans.edu> <98@gp.govt.nz> Organization: University of Kansas Academic Computing Services Lines: 24 In article <98@gp.govt.nz>, GPWRDCS@gp.govt.nz (Don Stokes, GPO) writes: > In article <6342@kuhub.cc.ukans.edu>, SLOANE@kuhub.cc.ukans.edu (Bob Sloane) writes: >> >> I haven't actually tried this, but how about creating an alias that maps to >> old group to the new group in NEWS.ALIASES and then doing: >> >> NEWS> CREATE NEWSGROUP new.group/LOCAL >> NEWS> ADD FILE/RETRY NEWS_DEVICE:[old.group]*.ITM >> NEWS> DELETE NEWSGROUP old.group > > We thought that just ADDing [...]*.ITM would fix it, but alas, no. > The message path in the item files *includes* the local node, resulting > in a path loop on every message, and subsequent rejection. That is why I specified /RETRY in the above example. The /RETRY qualifier on the ADD FILE command tells news to ignore Path: header loops when adding the message. I have never had any problems using this procedure, although, as another poster pointed out, the articles may not be added in the exact same order they were in in the original group. +-------------------+-------------------------------------+------------------+ | Bob Sloane \Internet: SLOANE@KUHUB.CC.UKANS.EDU/Anything I said is | | Computer Center \ BITNET: SLOANE@UKANVAX.BITNET / my opinion, not my | | University of Kansas\ AT&T: (913) 864-0444 / employer's. | +-----------------------+-----------------------------+----------------------+