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,617 of 16,010    |
|    g00r00 to Bj”rn Wiberg    |
|    Re: Message new scan with and without /G    |
|    28 Jul 21 23:40:04    |
      TID: Mystic BBS 1.12 A47       MSGID: 1:129/215 216802cd       REPLY: 2:201/137 667fc0d3       TZUTC: -0400        BW> Although when I changed the last read date for the MYSTIC echomail area        BW> to two days back and performed the global personal scan, MQ (/NOSCAN        BW> /NOFOOT /NEW /YOU /LIST /NOREAD) acted up and didn't find anything for        BW> some reason. Checked the message list (Read, Forward, scroll to end) and        BW> the messages (some of them from you, to me) were correctly flagged as        BW> "N" (new), and still MQ didn't find them. Changing the LR date worked              When you reset your last scan date it does not reset the flag on each       individual message that determines if you read it before       or not. The /noread option tells Mystic to ignore messages that have been       presented to you once before regardless of what your last read pointer says.              In other words Mystic tracks (for each message) whether or not the "To" user       has seen the message or not. If you have seen it, Mystic will not show it to       you again if /noread is used and your lastread pointer doesn't matter in that       case. If you want it to *only* key off of the last read pointers then you       should remove the /noread option.              Its easy to get lost in all of the options Mystic has for ways to scan. In       the long run its a good thing because the scanning in Mystic is super       flexible, but it can take a bit to sort through it all. Even I have thought       the newscan was bugged and it turned out to be because of /noread in the past       (and I created this mess)!              That said if you feel its not because of /noread let me know because of course       there could always be a bug.               BW> Anyway, I posted two test messages in FSX_TST to myself (both to my        BW> alias and real name) and that worked just fine; they appeared in both MQ        BW> and MN as they should.              Great! Thank you for testing it and following up!               BW> P.S. The comment in whatsnew.txt suggests that it is /G (the global scan        BW> option) that is affected by /YOU, but it really is /P (the personal scan        BW> option) that is affected, right? D.S.              I think technically it will be both, but you're right it should probably have       said personal scan. I'll update that.              I haven't really tested all of the scenarios but technically /YOU should work       in combination with different modes for MN and MR. I'll need to sort out where       it can and can't be used and document it, but feel free to experiment if you       want to! For now just assume its only guarenteed to work in the /P scan!              ... Honk if you love peace and quiet!       --- Mystic BBS v1.12 A47 2021/07/28 (Windows/64)        * Origin: Sector 7 * Mystic WHQ (1:129/215)       SEEN-BY: 1/123 30/0 80/1 90/1 103/705 105/81 120/340 457 616 123/10       SEEN-BY: 123/131 129/215 305 154/10 30 40 50 700 203/0 218/700 220/80       SEEN-BY: 220/90 221/1 6 226/18 30 227/114 201 702 229/101 310 424       SEEN-BY: 229/426 428 452 550 700 981 1016 1017 240/1120 5832 249/206       SEEN-BY: 249/307 317 400 261/38 280/464 282/464 1038 292/854 301/0       SEEN-BY: 301/1 101 113 317/3 322/757 335/364 341/66 342/200 633/280       SEEN-BY: 712/848 770/1 920/1 3634/12 5020/1042 5058/104       PATH: 129/215 154/10 301/1 229/426           |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca