@TID: Mystic BBS 1.12 A48
@MSGID: 2:201/137 136eaa9c
@TZUTC: 0200
@SEEN-BY: 1/123 15/0 90/1 103/705 105/81 106/201 114/705 120/340 123/120 @SEEN-BY: 123/131 124/5016 129/305 330 331 153/757 7715 154/10 201/0 @SEEN-BY: 201/137 203/0 124 218/700 840 220/70 221/0 1 6 242 360 226/17 @SEEN-BY: 226/30 100 227/114 229/110 206 307 317 400 424 426 428 452 @SEEN-BY: 229/550 664 700 230/0 240/5832 250/5 8 266/512 267/800 280/464 @SEEN-BY: 280/5003 282/1038 292/854 8125 298/25 301/1 305/2 3 317/3 @SEEN-BY: 320/219 322/757 335/364 341/66 234 342/200 396/45 423/81 @SEEN-BY: 460/58 633/280 712/848 770/1 2452/250 3634/24 4500/1
@PATH: 201/137 0 203/0 280/464 221/1 6 218/840 770/1 317/3 229/426
...to see if my messages in this echo still do not reach his system for some reason.
Best regards
Björn
--- Mystic BBS v1.12 A48 2022/03/22 (Linux/64)
* Origin: Star Collision BBS, Uppsala, Sweden (2:201/137)
This is what I see & how it reached me:
Both of your test messages reached me via the same path.
Keeping fingers crossed that g00r00 will be able to find out what the cause of the message "loss" could be. Wouldn't want to be without this echo, as it's kind of central for Mystic questions. :-D
I know g00r00 sees my messages. I have a connection to Tommi at 221/6
so I've reconnected this echo with him which should bridge 221/6 -> 229/664 -> 229/426.
Both of your test messages reached me via the same path.
Sysop: | digital man |
---|---|
Location: | Riverside County, California |
Users: | 1,041 |
Nodes: | 17 (1 / 16) |
Uptime: | 07:13:09 |
Calls: | 501,708 |
Calls today: | 1 |
Files: | 104,420 |
D/L today: |
124 files (8,807K bytes) |
Messages: | 298,335 |
Posted today: | 2 |