Just a sample of the Echomail archive
Cooperative anarchy at its finest, still active today. Darkrealms is the Zone 1 Hub.
|    AFTERSHOCK    |    The Aftershock software client    |    1,212 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 1,030 of 1,212    |
|    John Dovey to Alan Ianson    |
|    Dupes and Deletions    |
|    23 Nov 22 12:48:27    |
      REPLY: 1:153/757.0 1c7690a6       MSGID: 4:920/1.1 637e5ceb       TZUTC: -0500       CHRS: CP437               >>> My first problem is that FIDO-REQ is generating hundreds of dupes in        >>> Aftershock and I have no idea why. Normally SBBSEcho handles dupes        >>> perfectly, but not for that echo.               >> What is FIDO-REQ? Regular echo? I need to subscribe to it for problem        >> investigation. I do not see this echo in Areafix of Ward. Will ask him        >> if it possible to make this echo available for me.               AI> This is a bit complicated.               AI> A node in Z1 is posting very big messages, over 400k. Those messages are        AI> tossing OK here but when they pass through some nodes that don't support        AI> messages over a certain size (64k, I think) they can get mangled. I see        AI> two mangled messages without correct header info or MSGID. For every good        AI> message I see here I see two mangled messages also. This issue will reveal        AI> itself differently at different nodes with different tossers.               AI> If I read the situation correctly that nodes "New file Announcement" keeps        AI> growing every day because the already announced files are not being        AI> cleared so they get announced again day after day. The message size grows        AI> a little every day.               AI> That node seems to be on auto pilot so that will keep on happening until        AI> he gets in front of his keyboard again.               AI> His packets are valid, just quite large and growing every day.                     Thanks Alan. Yes, the dupes are from one particular node. I couldn't figure       out why they weren't being picked up as dupes, but this would make sense.        Do you think it's something we should ask Digital Man to take a look at, or is       it too specific?              JD       --- AfterShock/Android 1.6.8        * Origin: FireCat Mobile (4:920/1.1)       SEEN-BY: 1/21 123 3/1 15/0 90/1 92/0 1 103/705 105/81 106/201 114/705       SEEN-BY: 120/340 123/120 131 129/305 153/757 7715 154/10 218/700 840       SEEN-BY: 220/70 221/1 6 226/17 30 227/114 229/110 111 112 113 114       SEEN-BY: 229/206 317 424 426 428 470 550 664 700 240/1120 250/5 8       SEEN-BY: 266/512 267/800 282/1038 298/25 301/1 113 305/3 317/3 320/219       SEEN-BY: 322/757 335/364 341/66 234 342/200 396/45 633/280 712/848       SEEN-BY: 770/1 920/0 1 69 4500/1 5020/1042       PATH: 920/1 92/1 301/1 221/6 218/840 770/1 317/3 229/426           |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca