Just a sample of the Echomail archive
Cooperative anarchy at its finest, still active today. Darkrealms is the Zone 1 Hub.
|    MYSTIC    |    Mystic support echo    |    16,010 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 13,976 of 16,010    |
|    deon to Jay Harris    |
|    Re: Dupes?    |
|    13 Oct 21 11:12:38    |
      TZUTC: 1100       MSGID: 2602.fdn_mystic@3:633/509 25cb64a0       REPLY: 1:229/664 517486ae       PID: Synchronet 3.19a-Linux master/8f79438d2 Apr 24 2021 GCC 8.3.0       TID: SBBSecho 3.14-Linux master/8f79438d2 Apr 24 2021 GCC 8.3.0       COLS: 255       BBSID: ALTERANT       CHRS: CP437 2       NOTE: FSEditor.js v1.104        Re: Re: Dupes?        By: Jay Harris to g00r00 on Mon Oct 11 2021 08:20 pm               > Here are two more than came through today. I've turned off my feeds to        > 2:221/6 & 3:770/1 for now and am just hooked up to 1:229/426:        > https://paste.ee/p/hBhCR        > https://paste.ee/p/nN9aV        > Again, the kludges look the same (except for the path and seen-by lines)       but the message body has again been modified. One message has a SLMR line       where the other one doesn't.              Howdy,              For me it looks like three things:              * Your BBS didnt consider it a dupe              * 229/426 didnt consider it a dupe - since it sent it to you twice.              * Somebody after 261/38 modified the message - possibly 301/1, 320/219 or       240/5832, since it looks like 261/38 sent it 2 ways, that end up at 229/426.       So either 301/1 removed the bottom 2 lines, or one of 320/219, 240/5832 added       them.              This could go 2 ways, depending if the authors of the software involved think       they are doing the "right thing" or not.              1) A consistent method to identify a duplicate - which there is an FTS       document that can help here,       2) "Thou should not modify message content" - dont recall if that is an FTS       document somewhere              Fortunately for you, there is some software that handles this situation well,       so even if something upsream is not doing what is expected you can mitigate it       yourself.              Getting popcorn...                     ...лоеп       --- SBBSecho 3.14-Linux        * Origin: I'm playing with ANSI+videotex - wanna play too? (3:633/509)       SEEN-BY: 1/123 90/1 105/81 120/340 123/131 129/305 226/30 227/114       SEEN-BY: 227/702 229/424 426 428 452 550 664 700 981 240/5832 249/206       SEEN-BY: 249/307 317 400 282/1038 292/854 301/1 317/3 322/757 342/200       SEEN-BY: 633/267 280 281 410 412 416 509 640/1384 712/848 770/1       PATH: 633/509 280 229/426           |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca