Subj : RE: ERRORS in Route List! To : Carl Austin Bennett From : Andrea Santos Date : Tue May 08 2001 09:30 am On May 08, 2001 10:33am, CARL AUSTIN BENNETT wrote to ANDREA SANTOS: AS>> Gee Carl, but if we had "millions" of sysops and users, you might AS>> have a point. But since we don't, the routelist isn't of much concern. CAB> So how does keeping outdated routing info help us get back our lost CAB> userbase? A routelist has very little, if anything to do with our users. How many of them do you suppose pick this thing up? Shoot, I moderate 3 echos which actually have traffic in them and I don't use the list. CAB> If anything, a Fido that can't reliably fetch mail will only lose more CAB> users. Think you need to clarify what you are talking about. Users are barely using routed echomail. The routelist details ERN, no? AS>> Haven't bothered to pick one up yet. Also can't remember the last AS>> time I sent someone a Moderator message via Netmail. CAB> The moderator "take it to netmail" demand is a common way to try to CAB> move a flame thread out of an echo. If you were a big, important CAB> moderator like Bobby, you'd need to be able to do this quite often. Really? Perhaps some moderators have thin skin. Last I looked, at least per one hub's stats, I moderate an echo which is in the top 10 in traffic. I also don't send netmail. ;-) CAB>> NC's have been known to disappear without warning; that at least two CAB>> NC's in Region 14 alone answer voice as wrong numbers, two more are CAB>> numbers that are out of service and a few others just don't answer at CAB>> all isn't news to anyone. AS>> What's this have to do with a routelist? CAB> If we're depending on the *C's to provide info for the *EC-generated CAB> lists and treating info from hubs and reverse-engineered paths as CAB> unofficial, then the missing NC's will result in both nodelist and CAB> routelist info being wrong. I'll let you worry about this. If you're so concerned about Region 14, start calling all the nodes and report the no answers to RC14. If that gets you nowhere, send the info to the Z1C. AS>> How about a better method which is to inform the *C above of the AS>> problem so the node in question can be removed from the nodelist? CAB> When that *C tries to put what's left of the net back together, the CAB> information regarding all feeds into it is needed. And what if "all feeds" no longer exist based on what's left? AS>> So how much netmail are you or your Region members trying to send to AS>> Nets with AWOL NCs in Region 14? CAB> Of the two sysops that I'd normally try to reach in region fourteen, CAB> both are *C's so my odds ought to be, in theory, better than average. You didn't answer the question. How much routed mail are you and members of Region 12 trying to send Nets with AWOL NCs in Region 14? CAB> As for the live nodes with dead NC's (Jerry Olney, Timothy Trace, Lee CAB> Lefler, Dan Rosenthal, Scott Heider, Kevin McVay, Robert Pederson and CAB> Greg Thornhill) I doubt I'd even try to use this broken excuse for a CAB> network to write to them, even though I do know Greg from my othernet CAB> days where he ran a fine BBS. Okay, but you aren't sending ERN to these people. CAB> Andrea, I do realise the problems go beyond the routelist. After Ray CAB> Brown's system went down for the count in Y2K (and yes, Foxy still CAB> shows a route to him via the new RC14), I don't know what the routelist shows, but Ray Brown and Net 286 have been removed from the Nodelist. Whoever attended to that forgot to attend to Ray's Fido help node number, 1:1/117, which also needs to be removed. Per your mention of Robert Pederson, it's Gary Petersen who is still listed as NC290, yet he's been out of Fidonet for over a year and notified ALL of his departure in various places. Net 290 doesn't exist. I've verified that Robert is up and running with a mailer, but he's the only node left in 290 and needs to be incorporated in another R14 net or be assigned an RIN. CAB> In the meantime, if Bobby or anyone else has info on any route into CAB> any node that hasn't already been reported, I would strongly encourage CAB> them to publish it. And what if it's not confirmable or, in the end, not wanted? --- Platinum Xpress/Win/Wildcat5! v3.0pr3 * Origin: Platinum Xpress Support 305-248-7815 (1:135/382) .