Hello g00r00!

When I compare the menu options "G" (Group) and "A" (All Groups) of the mnewscan menu ("N" from the message menu), the difference is the /G data to the (MN) Message new scan function.

According to http://wiki.mysticbbs.com/doku.php?id=menu_commands#message_bases /G should be required to scan messages in all groups.

But both menu options appear to be scanning all areas in all groups (i.e. regardless of /G or not). I can see it scanning "everything" (it lists all areas while scanning).

Is this also so for you?

Thanks in advance!

Best regards
Björn

--- Mystic BBS v1.12 A47 2021/07/23 (Linux/64)
* Origin: Star Collision BBS, Uppsala, Sweden (2:201/137)

But both menu options appear to be scanning all areas in all groups (i.e. regardless of /G or not). I can see it scanning "everything" (it lists
all areas while scanning).

Is this also so for you?

The mnewscan menu works fine for me. I can't really tell you more without seeing your ACS for your message bases, what group you are in and so on. If you have a "global" group make sure you are not in it when you are scanning "current group" because that would obviously scan everything.

... The seminar on time travel will be held two weeks ago

--- Mystic BBS v1.12 A47 2021/07/23 (Windows/64)
* Origin: Sector 7 * Mystic WHQ (1:129/215)

Hello g00r00!

Thank you for your reply!

On 26 Jul 2021, g00r00 said the following...

The mnewscan menu works fine for me. I can't really tell you more
without seeing your ACS for your message bases, what group you are in
and so on. If you have a "global" group make sure you are not in it
when you are scanning "current group" because that would obviously scan everything.

What is a global group? I do have one message area whose List ACS is "any of the Echomail Groups", but that's about it. =)

Anyway, I was standing in FSX_ADS and launching the N G scan:

Group....: fsxNet
Area.....: FSX_ADS: BBS and NETwork Ads
Command (9780 minutes left) -> N

[■] New Scan: (C)urrent Area, (G)roup, (A)ll Groups, (P)ersonal, or (Q)uit? G

Then it began scanning; the last area (among those to be scanned as per the new scan settings) was:

Scanning FIDOTEST: FidoNet TEST echo and malfunction conference...

And that one is not part of the fsxNet group. =)

My message base configurations look like this:

▄▄▄▄▄▄▄▄
█▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀ ID 127 ▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▄ █ Name │ FSX_ADS: BBS and NETwork Ads █ █ Base Type │ Networked Quote Color │ Sample █ █ Newsgroup │ FSX_ADS Text Color │ Sample █ █ QWK Name │ FSX_ADS Tear Color │ Sample █ █ Echo Tag │ FSX_ADS Origin Color │ Sample █ █ File Name │ FSX_ADS Kludge Color │ Sample █ █ Path │ /mnt/bbs/mystic/msgs/fsxnet/ Max Msgs │ 0 █ █ List ACS │ g2 Max Msg Age │ 0 █ █ Read ACS │ New Scan │ No █ █ Post ACS │ s20&!fd QWK Scan │ No █ █ Sysop ACS │ s255 Header │ msghead █ █ List EACS │ g1 R Template │ ansimrd █ █ │ L Template │ ansimlst █ █ Net Address │ 21:1/202 (fsxNet) Real Names │ No █ █ Export To │ 1 node(s) Autosigs │ Yes █ █ Origin │ Private │ No █ █ QWK Network │ None Pvt Reply │ No █ █ QWK Base ID │ 0 Allow ANSI │ Yes █ ▀▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄█

█▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀ ID 61 ▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▄ █ Name │ FIDOTEST: FidoNet TEST echo an █ █ Base Type │ Networked Quote Color │ Sample █ █ Newsgroup │ FIDOTEST Text Color │ Sample █ █ QWK Name │ FIDOTEST Tear Color │ Sample █ █ Echo Tag │ FIDOTEST Origin Color │ Sample █ █ File Name │ FIDOTEST Kludge Color │ Sample █ █ Path │ /mnt/bbs/mystic/msgs/fidonet/ Max Msgs │ 0 █ █ List ACS │ g3 Max Msg Age │ 0 █ █ Read ACS │ New Scan │ No █ █ Post ACS │ s20&!fd QWK Scan │ No █ █ Sysop ACS │ s255 Header │ msghead █ █ List EACS │ g2 R Template │ ansimrd █ █ │ L Template │ ansimlst █ █ Net Address │ 2:201/137 (FidoNet) Real Names │ Yes █ █ Export To │ 1 node(s) Autosigs │ Yes █ █ Origin │ Private │ No █ █ QWK Network │ None Pvt Reply │ No █ █ QWK Base ID │ 0 Allow ANSI │ Yes █ ▀▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄█

fsxNet is Message Group 2 (g2) and Echomail Group 1 (g1).
FidoNet is Message Group 3 (g3) and Echomail Group 2 (g2).
My user account has s255 (could that affect things?).

Other than that, my Message Settings look like this:

█▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀ Message Settings ▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▄
█ █
█ List Compression │ Yes Quote Color │ Sample █
▄▄ █ List Columns │ 1 Text Color │ Sample █gj!
███ Show Message Header │ Yes Tear Color │ Sample █▄▄
░██ Bases in Group List │ Yes Origin Color │ Sample ██▒■ ▀ ▓█ Max AutoSig Lines │ 4 Kludge Color │ Sample ████ ▓ ▒█ Force NL Match │ Yes Netmail Crash │ No █░ ▓ ▀ ██ Extended Reply ACS │ Netmail Hold │ No █░ ▓ ░░▓█ Attachment ACS │ s255 Netmail Killsent │ No █▄▄█ ▄▄■█ Msg Upload ACS │ Netmail Direct │ No ██░░
█ Add [ANSI] Prefix │ Echo Only Create Semaphore │ MsgPost █▀▄
█ Add Re: Prefix │ Yes Ask Message Post │ No █
█ Default Origin │ Star Collision BBS, Uppsala, Sweden █
█ █
▀▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄█

I've also double-checked the G action in the mnewscan menu and it looks OK:

█▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀ Command ID 2: scbbs_en.mnewscan ▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▄ █ █ █ Display Text │ █ █ LightBar OFF │ █ █ LightBar ON │ █ █ LightBar X Y │ 0 0 █ █ Hot Key │ G ┌ GRID MENU JUMPS ─────── █ █ Access String │ │ Up 00 Escape 00 █ █ Display When │ User has access │ Down 00 Tab 00 █ █ Redraw After │ Yes │ Left 00 PageUp 00 █ █ Execute Timer │ 0 │ Right 00 PageDn 00 █ █ Timer Type │ Every <timer> interval │ Home 00 End 00 █ █ █ █ Action List ────────────── Access ───── Data ───────────────────────────── █ █ (GT) Display line of text % |CL ░ █ (MN) Message new scan ░ █ (GO) Go to new menu message ░ █ ▓ █ ░ █ ░ ▀▄▄▄▄▄▄▄▄▄▄▄▄▄ (TAB) Switch Focus (/) Commands ▄▄▄▄▄▄▄▄▄▄▄▄▄█

...i.e. it does not have /G in the data field.

Can you spot anything strange among those settings?

Many thanks in advance!

Best regards
Björn

--- Mystic BBS v1.12 A47 2021/07/23 (Linux/64)
* Origin: Star Collision BBS, Uppsala, Sweden (2:201/137)

What is a global group? I do have one message area whose List ACS is
"any of the Echomail Groups", but that's about it. =)

Anyway, I was standing in FSX_ADS and launching the N G scan:

█ Read ACS │ New Scan │ No

So it looks like in this case you don't have READ access for that base assigned to any group, which means it will show up in every group when performaing a read function.

If you want to restict reading the base to only group 2 for example you'd set Read ACS to "g2". So you'd probably want something like:

List ACS: g2
Read ACS: g2
Post ACS: g2
Sysop ACS: s255g2

This way you can only see, read, post, or perform SysOp stuff on that message base when you are in group 2. Generally speaking you want to put the group into all of the access strings as shown above.

Hope that makes sense.

... As I said before, I never repeat myself

--- Mystic BBS v1.12 A47 2021/07/23 (Windows/64)
* Origin: Sector 7 * Mystic WHQ (1:129/215)

Hello g00r00!

Thank you for your reply!

On 26 Jul 2021, g00r00 said the following...

So it looks like in this case you don't have READ access for that base assigned

Ah -- that must be it, yes! Thanks!

But, speaking of those ACSes, won't...

Read ACS: g2
Post ACS: g2

...make it impossible to read a message during new e-mail scan in the prelogin menu (or global personal message scan which I have added right after it, to also catch echomails addressed to the user as part of the mail scanning during login) unless you are standing in that group?

And/or impossible to (R)eply to such a message unless you are standing in that group?

And/or impossible to forward a message to another message (B)ase in another group (which one might want to do sometimes when cross-posting)?

I think I stumbled upon some of these, and that's why I left the Read/Post ACSes empty...

Best regards
Björn
--- Mystic BBS v1.12 A47 2021/07/23 (Linux/64)
* Origin: Star Collision BBS, Uppsala, Sweden (2:201/137)

But, speaking of those ACSes, won't...
...make it impossible to read a message during new e-mail scan in the prelogin menu (or global personal message scan which I have added right after it, to also catch echomails addressed to the user as part of the mail scanning during login) unless you are standing in that group?

No, it won't. Thats what the global options are for - they cause the group to be ignored temporarily when doing whatever function you've selected the global option for.

... You can learn many things from children... like how much patience you have

--- Mystic BBS v1.12 A47 2021/07/23 (Windows/64)
* Origin: Sector 7 * Mystic WHQ (1:129/215)

Hello g00r00!

Thank you for your reply!

On 27 Jul 2021, g00r00 said the following...

No, it won't. Thats what the global options are for - they cause the group to be ignored temporarily when doing whatever function you've selected the global option for.

Thanks! I'll try re-adding those g entries to the List/Read ACSes then. =)

Best regards
Björn

--- Mystic BBS v1.12 A47 2021/07/23 (Linux/64)
* Origin: Star Collision BBS, Uppsala, Sweden (2:201/137)

On 27 Jul 2021, Björn Wiberg said the following...

Thanks! I'll try re-adding those g entries to the List/Read ACSes then.

Of course I meant the Read/Post/Sysop ACSes... =)

Best regards
Björn

--- Mystic BBS v1.12 A47 2021/07/23 (Linux/64)
* Origin: Star Collision BBS, Uppsala, Sweden (2:201/137)

Hello again, g00r00!

I have now added the group requirement to all my message areas, including the local ones. For my Private Messages local area, I have:

█ Name │ Private Messages (PMs) █
█ Base Type │ Local Quote Color │ Sample
█
█ Newsgroup │ LOC_PRIVMSGS Text Color │ Sample
█
█ QWK Name │ LOC_PRIVMSGS Tear Color │ Sample
█
█ Echo Tag │ Origin Color │ Sample
█
█ File Name │ LOC_PRIVMSGS Kludge Color │ Sample
█
█ Path │ /mnt/bbs/mystic/msgs/local/ Max Msgs │ 0
█
█ List ACS │ g1 Max Msg Age │ 0
█
█ Read ACS │ g1 New Scan │ Forced
█
█ Post ACS │ g1&!fa QWK Scan │ Forced
█
█ Sysop ACS │ s255g1 Header │ msghead
█
█ List EACS │ % R Template │ ansimrd
█
█ │ L Template │ ansimlst
█
█ Net Address │ 0:0/0 (Local Address) Real Names │ No
█
█ Export To │ 0 node(s) Autosigs │ Yes
█
█ Origin │ Private │ Yes
█
█ QWK Network │ None Pvt Reply │ No
█
█ QWK Base ID │ 0 Allow ANSI │ Yes
█

In my prelogin menu, and for (C)heck E-Mail in the Messages Menu, I have:

Command: (MC) Check e-mail
Data: /UNREAD

When it checks for e-mails, I get:

┌─────────────────────────────────────────────────────────────────────────────┐ │ ▒ PMs │ └─────────────────────────────────────────────────────────────────────────────┘
###### From Subject Date
─────────────────────────────────────────────────────────────────────────────
1 Zip Test 1 07/27/21
─────────────────────────────────────────────────────────────────────────────
[■] You have 27 PMs (1 unread). Read them now? Yes No

...but when selecting "Yes", I get:

You don't have access to read in this message area!

End of messages.

...apparently because I was currently standing in:

Group....: FidoNet
Area.....: MYSTIC: Discussion and chat about the Mystic BBS software

I tried adding /G or /GROUP to (MC), but it didn't appear to have any effect, so probably those flags do not exist for (MC). I couldn't find anything affirmative on the wiki or in whatsnew.txt regarding such flags either.

Is there some way to make this work, allowing it to display new e-mails regardless of the current area?

Or should I skip using the (MC) function and instead rely on my global personal scan instead, i.e.:

Command: (MN) Message new scan
Data: /P /G /NOLR /NOREAD

...as that one appears to have no problems reading the messages (thanks to /G)?

Thanks in advance!

Best regards
Björn

--- Mystic BBS v1.12 A47 2021/07/23 (Linux/64)
* Origin: Star Collision BBS, Uppsala, Sweden (2:201/137)

Hello again, g00r00!

On 27 Jul 2021, Björn Wiberg said the following...

Or should I skip using the (MC) function and instead rely on my global personal scan instead, i.e.:

Command: (MN) Message new scan
Data: /P /G /NOLR /NOREAD

...however that is not a drop-in replacement, I have noticed.

/P will make it find any new messages from me (e.g. an unread echomail message from me to you), which isn't what I'm looking for in this case.

And adding /NOFROM to "cure" that causes any messages from myself to myself, such as new user registration notices, to go unnoticed.

Perhaps it would be an idea to add more alternatives to /P for the "(MN) Message new scan" function, such as:

/ONLYTO (only show messages addressed *to* the user)
/ONLYFROM (only show messages *from* the user)
/NOTO (exclude any messages addressed *to* the user)

Of course /ONLYTO and /ONLYFROM would be mutually exclusive; same thing for /NOFROM and /NOTO. If one combines those you simply get no results.

Just a thought. :)

Best regards
Björn
--- Mystic BBS v1.12 A47 2021/07/23 (Linux/64)
* Origin: Star Collision BBS, Uppsala, Sweden (2:201/137)

Hello g00r00!

I hope I'm not confusing you too much. :)

I just wanted to say that it appears that:

(MQ) Message quick scan
/NOFOOT /NEW /YOU /LIST /NOREAD

...appears to list only messages *to* me, i.e. /YOU appears to mean only "to me" (contrary to how I interpret the description of /YOU on http://wiki.mysticbbs.com/doku.php?id=menu_commands#message_bases), whereas:

(MN) Message new scan
/P /G /NOLR /NOREAD

...appears to list messages both from me *and* to me (just as /P on http://wiki.mysticbbs.com/doku.php?id=menu_commands#message_bases says it should).

Not sure if this is intended to be so?

Just wanted to point it out while experimenting before I forget. :)

Best regards
Björn
--- Mystic BBS v1.12 A47 2021/07/23 (Linux/64)
* Origin: Star Collision BBS, Uppsala, Sweden (2:201/137)

I have now added the group requirement to all my message areas,
including the local ones. For my Private Messages local area, I have:

Okay so let me recap:

The first thing you mentioned was bases showing up in a group scan. That was happening because you didn't have your message base in a group, so it shows up in all groups.

Next I believe you mentioned wanting to do a global scan of personal messages. There is a personalscan menu that comes with the default installation that does a global scan of message bases for new personal unread messages. The personalscan sounds exactly what you want! Give that a look and let me know if there is something you want to change and I can walk you through it.

In this message it looks like you're showing the e-mail base settings and you are trying to change e-mail access? You'd almost never want to change the e-mail access or settings (outside of visual stuff). The e-mail system is not a message base.

Is there some way to make this work, allowing it to display new e-mails regardless of the current area?

It already does that as e-mail has nothing to do with the current message area or group. Email is not a message base, it is its own separate thing. The reason its not working now is because you changed the access to e-mail to require group 2 so e-mail will never work unless they're in group 2.

I'm not very clear on what exactly you're trying to do with the e-mail base/access but once I understand everything I can walk you through how to do it.

... Youth is glorious, but it isn't a career
--- Mystic BBS v1.12 A47 2021/07/23 (Windows/64)
* Origin: Sector 7 * Mystic WHQ (1:129/215)

Hello g00r00!

Thank you for your reply and for the clarifications!

On 27 Jul 2021, g00r00 said the following...

unread messages. The personalscan sounds exactly what you want! Give that a look and let me know if there is something you want to change and
I can walk you through it.

Thanks, yes, that's the one I copied to my theme and modified slightly.

I added /NOSCAN and /NEW to MQ -- to skip displaying area names during the actual scanning, and to skip areas with nothing new in them. That appears to work just fine.

I also added /NOLR to MN, as I do not want to update last read pointers (I want to be able catch up on echomails afterwards, which would be ruined otherwise).

All this works fine, *except* that if MQ finds something (again, the MQ output is perfectly fine!), so that one gets the choice of running the MN, the MN *might* find slightly *more* messages (namely new messages from me to others, not only from me to me or from others to me). So that's the only "oddity"
with all this.

If there were an MN option to exclude messages that are *not* to me, i.e. to narrow /P to messages that *are* to me, the global personal scan would
function just as I would expect it to. So it's very close. =)

and you are trying to change e-mail access? You'd almost never want to change the e-mail access or settings (outside of visual stuff). The
e-mail system is not a message base.

That explains a few things. =)

What would the recommended ACS fields be for a local private area (local "PMs" between users), and a local non-private area (local "conference"), respectively?

Right now I have adjusted to (for a local "private" area):

Name │ Private Messages (PMs)
Base Type │ Local
List ACS │ g1
Read ACS │
Post ACS │ !fa
Sysop ACS │ s255g1
List EACS │ %
Private │ Yes

...and (for a local "conference"):

Name │ General Messages
Base Type │ Local
List ACS │ g1
Read ACS │
Post ACS │ s20&!fb
Sysop ACS │ s255g1
List EACS │ %
Private │ No

(The fa and fb flags are to be able to disable posting by "troublesome"
users, if needed.)

Thanks in advance!

Best regards
Björn
--- Mystic BBS v1.12 A47 2021/07/23 (Linux/64)
* Origin: Star Collision BBS, Uppsala, Sweden (2:201/137)

If there were an MN option to exclude messages that are *not* to me,
i.e. to narrow /P to messages that *are* to me, the global personal scan would function just as I would expect it to. So it's very close. =)

It sounds to me like you may want:

Command: MN (Message New Scan)
Data: /P /G /NOFROM /NOLR /NOREAD

This will do a newscan of personal messages (/P) in all groups (/G) so only messages from or to YOU. But then it will exclude messages FROM you (/NOFROM), exclude messages you've already read once before (/NOREAD), and then it will not update your last read pointers afterwards (/NOLR).

What would the recommended ACS fields be for a local private area (local "PMs" between users), and a local non-private area (local "conference"), respectively?

Name │ Private Messages (PMs)
List ACS │ g1
Read ACS │
Post ACS │ !fa
Sysop ACS │ s255g1

I think it looks pretty good now but you'd probably want to remove the "g1" from SysOp ACS because it means you'll only be able to edit, delete (etc) e-mails if you are in group 1 (which I am guessing you don't want considering you can read from any group).

You're on the right track now though. Private Messages will show up as a message base when users are in group 1 and do an area list. Users who do not have flag A cannot send e-mail at all. Anyone can read at all times which means MC menu command will work in any situation.

... Just another prisoner of gravity!

--- Mystic BBS v1.12 A47 2021/07/27 (Windows/64)
* Origin: Sector 7 * Mystic WHQ (1:129/215)

Hello g00r00!

Thank you for your reply!

On 27 Jul 2021, g00r00 said the following...

It sounds to me like you may want:
Command: MN (Message New Scan)
Data: /P /G /NOFROM /NOLR /NOREAD

Thanks, I'm adding /NOFROM to my flags now!

Although "not from me" (/NOFROM) is not the same as "only to me" (a suggested /ONLYTO) -- as /NOFROM would miss any messages from myself to myself, e.g. test messages to myself in an echomail area -- it'll have to do for now.

And if you would happen to implement an /ONLYTO flag in the future, please let me know and I'll happily try it out. :)

What would the recommended ACS fields be for a local private area (lo "PMs" between users), and a local non-private area (local "conference respectively?

I think it looks pretty good now but you'd probably want to remove the "g1" from SysOp ACS because it means you'll only be able to edit, delete (etc) e-mails if you are in group 1 (which I am guessing you don't want considering you can read from any group).

Thanks! I'll adjust the Sysop ACS for the local message areas.

Again, thank you for your help -- it is much appreciated! Trying to get most things "right" here. :)

I spent yesterday editing prompts etc., and am now thinking of perhaps using theme colors for menu buttons and prompts in my theme... we'll see. :)

Best regards
Björn
--- Mystic BBS v1.12 A47 2021/07/23 (Linux/64)
* Origin: Star Collision BBS, Uppsala, Sweden (2:201/137)

Thanks, I'm adding /NOFROM to my flags now!

Although "not from me" (/NOFROM) is not the same as "only to me" (a suggested /ONLYTO) -- as /NOFROM would miss any messages from myself to myself, e.g. test messages to myself in an echomail area -- it'll have
to do for now.

I see what you're saying. You get a choice of "From and To" and "To not from" but no option for just a "To" check.

I have just added in a /YOU option to both the MN and MR commands to better go along with the quick scan /YOU so hopefully that will work better for you. I am working on compiling that build right now so you should be able to download it by the time you see this. If you test it please let me know if it works for you.

Again, thank you for your help -- it is much appreciated! Trying to get most things "right" here. :)

No problem! You're welcome.

I spent yesterday editing prompts etc., and am now thinking of perhaps using theme colors for menu buttons and prompts in my theme... we'll
see. :)

I very under utilized feature! :)

... 640K ought to be enough for anybody. -Bill Gates, 1981.
--- Mystic BBS v1.12 A47 2021/07/27 (Windows/64)
* Origin: Sector 7 * Mystic WHQ (1:129/215)

Hello g00r00!

Thank you for your reply!

On 28 Jul 2021, g00r00 said the following...

I have just added in a /YOU option to both the MN and MR commands to better go along with the quick scan /YOU so hopefully that will work better for you. I am working on compiling that build right now so you should be able to download it by the time you see this. If you test it please let me know if it works for you.

Thanks a lot! Seems to be working just as intended!
(I replaced /NOFROM with /YOU for my MN.)

Although when I changed the last read date for the MYSTIC echomail area to two days back and performed the global personal scan, MQ (/NOSCAN /NOFOOT /NEW /YOU /LIST /NOREAD) acted up and didn't find anything for some reason. Checked the message list (Read, Forward, scroll to end) and the messages (some of them from you, to me) were correctly flagged as "N" (new), and still MQ didn't find them. Changing the LR date worked fine yesterday to force your replies to me to reappear in MQ (and the subsequent MN), but not this time. Really strange...

Anyway, I posted two test messages in FSX_TST to myself (both to my alias and real name) and that worked just fine; they appeared in both MQ and MN as they should.

Thanks again for the rapid add of the /YOU flag!

P.S. The comment in whatsnew.txt suggests that it is /G (the global scan option) that is affected by /YOU, but it really is /P (the personal scan option) that is affected, right? D.S.

Best regards
Björn

--- Mystic BBS v1.12 A47 2021/07/28 (Linux/64)
* Origin: Star Collision BBS, Uppsala, Sweden (2:201/137)

Although when I changed the last read date for the MYSTIC echomail area
to two days back and performed the global personal scan, MQ (/NOSCAN /NOFOOT /NEW /YOU /LIST /NOREAD) acted up and didn't find anything for some reason. Checked the message list (Read, Forward, scroll to end) and the messages (some of them from you, to me) were correctly flagged as
"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.

Anyway, I posted two test messages in FSX_TST to myself (both to my
alias and real name) and that worked just fine; they appeared in both MQ and MN as they should.

Great! Thank you for testing it and following up!

P.S. The comment in whatsnew.txt suggests that it is /G (the global scan option) that is affected by /YOU, but it really is /P (the personal scan 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)

Hello g00r00!

Thank you for your reply!

On 28 Jul 2021, g00r00 said the following...

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.

Ah, thanks -- I vaguely remember noting in the past that "new" and "read" is not the same thing, and you confirmed this. :)

By the way, is there a way to un-read a message by editing it?

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

I think it's all working perfectly fine now. :)

My prelogin now consists of an e-mail scan -- to ensure that new, unread e-mails will always be found regardless of users' message scan settings (even though I *do* have set Private Messages to New Scan: Forced and QWK Scan: Forced, because I think that area should always be scanned) -- and a global personal scan.

to experiment if you want to! For now just assume its only guarenteed
to work in the /P scan!

Yep!

Many thanks!

Best regards
Björn
--- Mystic BBS v1.12 A47 2021/07/28 (Linux/64)
* Origin: Star Collision BBS, Uppsala, Sweden (2:201/137)