>     
 >  > From Newsgroup: alt.bbs.synchronet
 > 
  To: Carol Shenkenberger
 >  > .,: This is something about Circular Path,
 >  Carol Shenkenberger said it to MRoblivious1bmf on Fri Jan 02 2009 12:11 am 
 Ca--ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ-ÄÄÄÄ---ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ---ÄÄÄÄÄÄÄÄÄ--ÄÄÄÄÄÄÄÄ

 > Path from us is clean BTW, you to 10/1 to Janis to Bob Seaborn then me). 
 > Neither Bob nor Janis have the QWK based SBBS sysop echo.

 >  > 
 >  >  > Can do.  I'm not ruling out it being something here too.
 >  > 
 >  >  > Now, if my areas.bbs is dead on, and i import it, nothing can be 
 >  >  > wrong le any internal settings here right? xxcarol
 >  > 
 >  > i'm not ftn expert even though i've set it up a few times in the recent 
 >  > years.
 > 
 > Well, testing on my end is now kinda hard.  Tom nuked his Fidonet base out 
 > the reimported his areas.bbs.  No more circular logic since then but he 
 > hasnt sent a message yet either.

 >  > if there's a problem that just cropped up, i would say systematically go 
 >  > through each change to  catch the problem.
 >  > checkout your areas.bbs, echocfg and scfg's settings.
 > 
 >  > eliminate all the posibilities and whatever is left, no matter how 
 >  > inconceiveable, is the issue.
 > 
 > I just removed all references to his old point address everyplace.  The 
 > only t railer was it still accepted inbound connections via Argus for it.  
 > This was last night, before he nuked the bases to start over.  SBBSECHO 
 > didnt know anything about his old address as of 2 days ago.

 > scfg, any ideas of where to look there?  I see nothing.  areas.bbs and 
 > echocfg are clear of any references to him as other than 1:123/160.

 > Grin, if I were a meamie, I'd just 'assume' it was all him, but I know 
 > better and that sometimes it's the uplink (me).

 > Next step BTW is to vet out my settings for this echo.  It's possible I am 
 > the one crosslinking the 2.
            xxcarol

 > --- SBBSecho 2.12-Win32