Just a sample of the Echomail archive
[ << oldest | < older | list | newer > | newest >> ]
|  Message 126  |
|  Bob Ackley to BOB KLAHN  |
|  Echo Rules  |
|  12 Jan 11 06:57:34  |
 Replying to a message of BOB KLAHN to BOB ACKLEY: 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 BK>>> so 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 BK>>> the elists of the time. He was not listed as moderator. He was BK>>> listed in the *NEXT* elist, not the last one. And you can't see BK>>> the next elist until it's published. BA>> Since that *NEXT* elist hadn't been published, how did you BA>> know the listing had expired? BK> Because it was not in the *LAST* elist. You just finished claiming that watever was or wasn't in the *LAST* elist was irrelevant. Note that Earl posted the ALL-POLITICS entry from the elist preceding your hijack attempt, and Earl is listed as moderator. 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. BK> Try to think. You used to be able to do that. He relisted it BK> *BETWEEN* elist releases. So the elist that was in distribution BK> showed it had expired. The Robot does not read that, but it's BK> 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. BK> And just how do you know that? Oh, and why did he twist the BK> rules so badly, if he picked it up for Alan? Earl said that he did. As to why you'll have to ask Earl. --- FleetStreet 1.19+ * Origin: Bob's Boneyard, Emerson, Iowa (1:300/3) |
[ << oldest | < older | list | newer > | newest >> ]