🚀 go-pugleaf

In article <1tg6kaINNql3@au-ns.american.edu>, Jim McIntosh <jim@american.edu> writes:
> 
> If no significant objection is heard, a NEWGROUP control message will be
> sent out for the new group. Two days later the gateway will be moved to
> the new group. Two days after that a RMGROUP control message will be sent
> out for the old group.

I think your timeline is a little too compressed; On the USENET side both 
the NEWGROUP and RMGROUP messages may take a little time to propigate; May
I suggest that you issue the NEWGROUP and then send articles out cross-posted
to both the old and the new group for a period of time, then send out the
RMGROUP and finally after a second period remove the cross-post;

I would suggest that the cross-post occur for at least two weeks (and a month
is actually better) before issuing the RMGROUP. In USENET, when a group is
superceeded there will be a period of almost two months. 

I don't know if this is practical since you would have to handle the problem
of duplicates and the like but somehow you need to take into account the time
lag required for reorganizations to take place on the USENET side.
-- 
Richard H. Miller                 Email: rick@bcm.tmc.edu
Asst. Dir. for Technical Support  Voice: (713)798-3532
Baylor College of Medicine        US Mail: One Baylor Plaza, 302H
                                           Houston, Texas 77030