...

 BA>>> He's telling the absolute truth, Klahn.  Everybody that
 BA>>> witnessed your hijinks is aware of what you tried to do.

 BK>>  And they are aware that you are lying here. Your ignorance may
 BK>>  be correctable, but your choice to remain ignorant makes it a
 BK>>  lie.

 BA>>> Not to mention that Earl saved the netmails he got when
 BA>>> Thom's system notified him that somebody was trying to
 BA>>> register HIS echo is someone else's name (yours).  You

 BK>>  Which does not change a thing, as you would know if you were not  so
 BK>> ignorant of how Fido works.

 BA>>> tried the same trick some time back with POL_INC, and Earl
 BA>>> has that netmail too.  Had either echo *really* expired as
 BA>>> you claim, Thom's system would not have rejected your
 BA>>> attempt(s) to claim them.

 BK>>  And that is your ignorance. Thom's system works automatically,
 BK>>  the elist robot. The echo does not have to be in the last issued
 BK>> Elist to be listed, but the next one. I told you before, look  in the
 BK>> elists of the time. He was not listed as moderator. He  was listed in
 BK>> the *NEXT* elist, not the last one. And you can't  see the next elist
 BK>> until it's published.

 BA> Since that *NEXT* elist hadn't been published, how did you
 BA> know the listing had expired?

 Because it was not in the *LAST* elist.

 BK>>  I checked the elist before attempting to list an echo. You
 BK>>  should check it before spouting off on what you don't know.

 BA> Let's take a big leap and assume for a moment that what
 BA> you've posted here is really
 BA> true and not one of your delusions.  Why then, did Thom's
 BA> elist robot (a) reject your
 BA> attempt to list the echo and (b) warn Earl that you were
 BA> trying to steal it? The only
 BA> answer I can think of is that the listing had *NOT* expired
 BA> as you continue to claim.

 Try to think. You used to be able to do that. He relisted it
 *BETWEEN* elist releases. So the elist that was in distribution
 showed it had expired. The Robot does not read that, but it's
 own records.

 BA> When the elist entry for this echo did in fact expire, Earl
 BA> was able to list it in his
 BA> name with no problem, and Alan Hess later thanked him for
 BA> picking it up.

 And just how do you know that? Oh, and why did he twist the
 rules so badly, if he picked it up for Alan?

 BA> Just in case you missed this post to me:

 Since it would be in a just downloaded packet, I have not seen
 it yet. I checked my emails both Fidotel and my regular home
 email and I do not find any mod upd email in that part of Nov
 2010 so I can't check it.

 Notice that Ross did not start his game until Dec 2010. So, I
 would have no reason to consider it before then. Reread Ross'
 msg on that.

 So, whatever happened I filed to relist *MY* echo as recognized
 by every one including you. I was not trying to list an echo,
 but renew my echo. If that happened.

 BA> -----------------------------------------------
BK>> I checked the elist before attempting to list an echo.

 BA> "Warning: bob.klahn@fidotel.com, bob.klahn@sev.org,
 BA> (1:261/1500.0) attempted to modify the record for area
 BA> "ALL-POLITICS", but provided the wrong password."

 BA> That was sent November 12, 2010.  There was no list put out
 BA> in October, but the September list has this entry:

 BA> "ALL-POLITICS
 BA>      All Politics Conference

 BA> And you claim that *I'M* lying?

 Yes. And note that Earl posted one from much earlier.

 And note that I did not have to check the echolist for all
 politics since I was recognized as the moderator by everyone
 until Ross jumped in to play his games.

 At that time no one considered Earl the moderator. Not even you.



BOB KLAHN bob.klahn@sev.org   http://home.toltbbs.com/bobklahn

--- Via Silver Xpress V4.5/P [Reg]
 * Origin: Doc's Place BBS Fido Since 1991 docsplace.tzo.com (1:123/140)