Just a sample of the Echomail archive
MYSTIC:
[ << oldest | < older | list | newer > | newest >> ]
|  Message 14,686 of 16,009  |
|  Tommi Koivula to Michiel van der Vlist  |
|  Issues with PING functionality  |
|  17 Apr 22 19:07:58  |
 REPLY: 2:280/5555 6257d893 MSGID: 2:221/360 625c3bce TID: GE/2 1.2 CHRS: LATIN-1 2 TZUTC: 0300 * Originally in FIDOTEST * Crossposted in MYSTIC Thursday April 14 2022 10:13, Michiel van der Vlist wrote to Flavio Bessa: MV> No response from your PING robot yet. But I noticed something odd in the via MV> lines of a ping to 464 routed through your system: MV> MV> @Via 2:280/5555 @20220414.073614.608.UTC FMail-W32(Pack) 2.1.3.7-B20170919 MV> @Via 0:0/0 @20220414.043431.UTC Mystic 1.12 A47 MV> @Via 4:90/1 @20220414.043743 FMail/Win32 1.60+ MV> @Via 1:229/426 @20220414.033728 D'Bridge 4 MV> @Via 1:229/426@fidonet @20220414.073729.UTC O/T-Track+ 2.85 MV> @Via 2:280/464 @20220414.074202.227.UTC FMail-lnx64(Toss) 2 1.0.18-B20170815 MV> MV> Note the 0:0/0 in the via line generated by your system. The UTC time stamp is MV> also wrong. I noticed the same thing happening in another Mystic. This one is running A48. === Via 2:221/6.6 @20220417.155028.UTC hpt/w32-wc 1.9 2022-04-14 Via 0:0/0 @20220417.114640.UTC Mystic 1.12 A48 Via 2:221/6 @20220417.155056.UTC hpt/lnx 1.9 2022-02-13 Via 2:221/1 @20220417.155144.UTC O/T-Track+ 2.85 === 'Tommi --- * Origin: * RBB * Lake Ylo * Finland * (2:221/360) SEEN-BY: 1/123 15/0 90/1 105/81 106/201 120/340 123/131 129/305 330 SEEN-BY: 129/331 153/757 7715 154/10 203/0 218/700 840 221/1 6 242 SEEN-BY: 221/360 226/30 227/114 229/110 111 206 307 317 400 424 426 SEEN-BY: 229/428 452 550 664 700 230/0 266/512 280/464 5003 282/1038 SEEN-BY: 292/854 301/1 317/3 320/219 322/757 335/364 341/66 342/200 SEEN-BY: 396/45 423/81 460/58 633/280 712/848 4500/1 PATH: 221/360 1 6 229/664 426 |
[ << oldest | < older | list | newer > | newest >> ]
(c) 1994, bbs@darkrealms.ca