1. Forum
  2. fsxNet
  3. FSX MYS

  • Local Mail Check Issue

    From TALIADON@21:3/138 to All on Monday, June 27, 2022 13:22:48
    Hi All,

    Regarding Mystic A47 on Linux, can anyone else confirm if they've experienced the following local mail issue:

    When checking for local mail - automatically during login, or manually via the "Check for E-Mail" option - the system correctly acknowledges pending messages with an appropriate message such as that illustrated below:

    You have 1 messages (1 unread). Read them now? Yes No

    When selecting "Yes" however, the system reports:

    You don't have access to read in this base!

    Nonetheless, the messages may be accessed without issue via the "Indexed Message Reader" option.

    As always, all advice is gratefully received.

    ==================================================================
    TALIADON (Lee Westlake) | TALIADON BBS (taliadon.ddns.net:23)
    FidoNet: 2:250/6 | fsxNet: 21:3/138 | Email: taliadon-bbs@mail.com ==================================================================

    --- Mystic BBS v1.12 A47 2021/12/24 (Linux/64)
    * Origin: TALIADON BBS (21:3/138)
  • From Zip@21:1/202 to TALIADON on Monday, June 27, 2022 16:33:32
    Hello TALIADON!

    On 27 Jun 2022, TALIADON said the following...
    When selecting "Yes" however, the system reports:
    You don't have access to read in this base!

    This sounds like an ACS issue for the e-mail message base (ID #1) -- you might wish to double-check that the Read ACS (and Post ACS) don't contain any "g" strings in them -- the reason being that the user might not be standing in that message group when scanning for/reading/posting replies.

    Something like this should work:

    List ACS │ s10g1
    Read ACS │ s10
    Post ACS │
    Sysop ACS │ s255
    List EACS │ %

    (Although I don't recall this being specific to A47 in any way.)

    Best regards
    Zip

    --- Mystic BBS v1.12 A48 2022/04/26 (Linux/64)
    * Origin: Star Collision BBS, Uppsala, Sweden (21:1/202)
  • From TALIADON@21:3/138 to Zip on Monday, June 27, 2022 17:18:42
    Something like this should work:

    List ACS │ s10g1
    Read ACS │ s10
    Post ACS │
    Sysop ACS │ s255
    List EACS │ %

    That's why I love you guys: this was precisely the issue.

    This sounds like an ACS issue for the e-mail message base (ID #1) -- you might wish to double-check that the Read ACS (and Post ACS) don't
    contain any "g" strings in them -- the reason being that the user might not be standing in that message group when scanning for/reading/posting replies.

    That's a great explanation Zip: I had waaaaaaay too many "g" strings. I think I understand the "g" and "z" codes a little better at this point.

    (Although I don't recall this being specific to A47 in any way.)

    Nope, this was all me :)

    Incidentally, what's does the "%" symbol signify under the "List EACS" field? I'm sure I was told this once before, but memory fails to serve in this particular instance.

    Once again, thanks for the superb explanation Zip - it's very much appreciated.

    ==================================================================
    TALIADON (Lee Westlake) | TALIADON BBS (taliadon.ddns.net:23)
    FidoNet: 2:250/6 | fsxNet: 21:3/138 | Email: taliadon-bbs@mail.com ==================================================================

    --- Mystic BBS v1.12 A47 2021/12/24 (Linux/64)
    * Origin: TALIADON BBS (21:3/138)
  • From seeLive@21:2/128 to TALIADON on Monday, June 27, 2022 12:43:26
    Hey TALIADON, I'm running on a pi, but do not see that... i see something similar where already read emails are still listed as unread... I'm not sure if this is why, but g00r00 did confirm that there is a date bug in the rpi version... I think it's where the dos file date is not reporting correctly...

    Not sure if that helps, but that's what I've seen fairly consistently...

    -seeLive

    Re-livin' the dream...

    --- Mystic BBS v1.12 A47 2021/12/24 (Raspberry Pi/32)
    * Origin: oNyX bBs - onyxbbs.mywire.org:2300 (21:2/128)
  • From TALIADON@21:3/138 to seeLive on Monday, June 27, 2022 18:15:31
    Hey TALIADON, I'm running on a pi, but do not see that... i see something similar where already read emails are still listed as unread... I'm not sure if this is why, but g00r00 did confirm that there is a date bug in the rpi version... I think it's where the dos file date is not reporting correctly...

    Not sure if that helps, but that's what I've seen fairly consistently...

    Cheers bud - the info is very much appreciated :)

    Thankfully, Zip has already shown me the error of my ways.

    I had too many group tags within my security descriptors which effectively limited reading/posting to a specific base - I have now placed group tags on the "list" descriptors only.

    See previous post for Zip's beautifully succinct explanation.

    ==================================================================
    TALIADON (Lee Westlake) | TALIADON BBS (taliadon.ddns.net:23)
    FidoNet: 2:250/6 | fsxNet: 21:3/138 | Email: taliadon-bbs@mail.com ==================================================================

    --- Mystic BBS v1.12 A47 2021/12/24 (Linux/64)
    * Origin: TALIADON BBS (21:3/138)
  • From Zip@21:1/202 to TALIADON on Monday, June 27, 2022 19:20:23
    Hello TALIADON!

    On 27 Jun 2022, TALIADON said the following...
    That's why I love you guys: this was precisely the issue.

    Glad to be able to help! :)

    That's a great explanation Zip: I had waaaaaaay too many "g" strings. I think I understand the "g" and "z" codes a little better at this point.

    I also learned this the hard way. :)

    It took me quite some time to get working ACSes for the message bases, as well as a "normal" mail scan during logon. In earlier versions (at least), the mail scan included messages that had already been read, which was confusing to say the least...

    The /YOU flag added to the "(MQ) Message quick scan" and "(MN) Message new scan" functions in A47/A48 helped making things work the way one would expect.

    At the moment I use:

    (MQ) /NOSCAN /NOFOOT /YOU /LIST /NOREAD

    ...for scanning and displaying "new" (unread) messages, and, after (if) answering yes to read them, I use:

    (MN) /P /G /NOLR /NOREAD /YOU

    ...to perform the actual reading (and without "destroying" the last read pointers so that I can still browse through new echomail regardless of reading the "personal" messages).

    The above works for both "e-mails" (private messages) and echomail, and can be used both in the prelogin menu and the personalscan menu.

    If one only wants to scan for new "e-mail":

    (MC) /UNREAD

    ...should suffice (in the prelogin menu as well as the (C) command of the message menu).

    Hope this helps someone. :)

    Best regards
    Zip

    --- Mystic BBS v1.12 A48 2022/04/26 (Linux/64)
    * Origin: Star Collision BBS, Uppsala, Sweden (21:1/202)
  • From seeLive@21:2/128 to TALIADON on Monday, June 27, 2022 21:19:02
    Thankfully, Zip has already shown me the error of my ways.

    Cool, glad you got it sorted...

    Re-livin' the dream...

    --- Mystic BBS v1.12 A47 2021/12/24 (Raspberry Pi/32)
    * Origin: oNyX bBs - onyxbbs.mywire.org:2300 (21:2/128)