Janis Kracht wrote in a message to Thom LaCosta:

 JK> Hello Thom,

> Are you saying you saw the cooking echo announcement or not?

> If not, it left here on 11/7

>> Perhaps responses from others will help identify the broken link.

> I'm still not clear what you saw and didn't see and when....might
> help if we
> had more detail.

 JK> I did not see it.  The last message posted in the echolist echo was
 JK> this one one Oct. 19th:

 JK> fido.ECHOLIST message #62276 from Echolist to All.
 JK>    Entered on 19th October, 2007 at 06:43, 24 lines.

 JK> Subject: Update - SPITFIRE
 JK> ==========================

Well...

 JK> -{at}-SEEN-BY: 1/21 10/345 106/1 1010 124/5025 130/803 142/928 143/2
 JK> 261/38 1352 -{at}-SEEN-BY: 267/169 396/45 397/1
 JK> -!-PATH: 1/21 261/1352 106/1 261/38

It would appear the problem is at or between 1:106/1 and you...since I saw
it connect to him...and there is now one between you and him.

And if others didn't see it...then it may be between him and them.

Or at least I think that's how all this echomail stuff works.

It would be interesting if you and Dale both submitted and update for one
of your echoes and let me know:

A. Did you get the ACK(if you submitted via email, you get it back that
way, if via netmail, it goes from here to 1:106/1

B. Did you see the announcement (They go from here to 1:106/1

Thanks for the heads up.

cya,
thom
http://www.tlchost.net/echolist/ 
--- GEcho 1.20/Pro