• Email scan no access

    From bcw142@21:1/145.3 to All on Monday, August 14, 2017 14:10:04
    I know someone had this problem recently, at startup when it shows mail it
    asks Read them now? Yes No
    But then shows "You don't have access to read in this base!" when I'm sysop! Any idea what happened? It's A33 Linux x64 Mystic in this case - it works
    right on A33 on the Pi, but not this Linux system. I noticed the emails themselves under msgs are -rx-r--r-- permissions with me as owner so I don't really get it.

    --- Mystic BBS v1.12 A33 (Linux/64)
    * Origin: Workpoint (21:1/145.3)
  • From Avon@21:1/101 to bcw142 on Tuesday, August 15, 2017 09:42:43


    On 08/14/17, bcw142 pondered and said...

    I know someone had this problem recently, at startup when it shows mail
    it asks Read them now? Yes No
    But then shows "You don't have access to read in this base!" when I'm sysop! Any idea what happened? It's A33 Linux x64 Mystic in this case -
    it works right on A33 on the Pi, but not this Linux system. I noticed
    the emails themselves under msgs are -rx-r--r-- permissions with me as owner so I don't really get it.


    What is the ACS set for in the email base?

    --- Mystic BBS v1.12 A34 (Windows/32)
    * Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)
  • From bcw142@21:1/145.3 to Avon on Tuesday, August 15, 2017 10:11:33
    On 08/15/17, Avon said the following...

    On 08/14/17, bcw142 pondered and said...
    I know someone had this problem recently, at startup when it shows ma it asks Read them now? Yes No
    But then shows "You don't have access to read in this base!" when I'm sysop! Any idea what happened? It's A33 Linux x64 Mystic in this case it works right on A33 on the Pi, but not this Linux system. I noticed the emails themselves under msgs are -rx-r--r-- permissions with me a owner so I don't really get it.

    What is the ACS set for in the email base?

    --- Mystic BBS v1.12 A34 (Windows/32)
    * Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)

    Email is a special case I guess, can't do normal ACS permissions, need to
    leave it to % at the start then nothing till s255 for sysop at the end of permissions. Then it all works as it should. I checked the main BBS (which worked) to see that.

    --- Mystic BBS v1.12 A33 (Linux/64)
    * Origin: Workpoint (21:1/145.3)
  • From Gryphon@21:1/120 to bcw142 on Tuesday, August 15, 2017 23:11:33
    On 08/14/17, bcw142 said the following...

    I know someone had this problem recently, at startup when it shows mail
    it asks Read them now? Yes No
    But then shows "You don't have access to read in this base!" when I'm sysop! Any idea what happened? It's A33 Linux x64 Mystic in this case -
    it works right on A33 on the Pi, but not this Linux system. I noticed
    the emails themselves under msgs are -rx-r--r-- permissions with me as owner so I don't really get it.

    Check the ACS of the message base. I had that happen too. I had it so that the groups were part of the ACS (g3s10) but if you are in a group other than g3, you'll get that error.

    --- Mystic BBS v1.12 A34 (Linux/64)
    * Origin: Cyberia BBS | cyberia.darktech.org | San Jose, CA (21:1/120)
  • From Avon@21:1/101 to bcw142 on Wednesday, August 16, 2017 19:01:57
    On 08/15/17, bcw142 pondered and said...

    Email is a special case I guess, can't do normal ACS permissions, need to leave it to % at the start then nothing till s255 for sysop at the end of permissions. Then it all works as it should. I checked the main BBS
    (which worked) to see that.

    Sounds like my settings, and it's a local base right?

    --- Mystic BBS v1.12 A34 (Windows/32)
    * Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)
  • From bcw142@21:1/145.3 to Gryphon on Wednesday, August 16, 2017 07:24:34
    On 08/15/17, Gryphon said the following...

    On 08/14/17, bcw142 said the following...

    I know someone had this problem recently, at startup when it shows ma it asks Read them now? Yes No
    But then shows "You don't have access to read in this base!" when I'm


    Check the ACS of the message base. I had that happen too. I had it so that the groups were part of the ACS (g3s10) but if you are in a group other than g3, you'll get that error.

    Interesting solution. It shows two interesting things: 1 g3 can be used this way (as local) and 2 it can go first as in g3s10 instead of s10g3 (as is
    normal for Mystic docs. The solution I used was the original default:

    +--------------------------------- ID 1 ------------------------------------+
    | Name | E-mail Quote Color | Sample | | Newsgroup | Email Text Color | Sample | | QWK Name | Email Tear Color | Sample | | Echo Tag | Email Origin Color | Sample | | File Name | email Kludge Color | Sample | | Path | /mystic/msgs/ Max Msgs | 0 | | List ACS | % Max Msg Age | 0 |
    | Read ACS | New Scan | Yes |
    | Post ACS | QWK Scan | Yes |
    | Sysop ACS | s255 Header | msghead |
    | Base Type | Local R Template | ansimrd |
    | Net Address | 0:0/0 (Local Address) L Template | ansimlst | | Export To | 0 node(s) Real Names | No |
    | Origin | WorkPoint Autosigs | No |
    | Sponsor | Private | Yes |
    | QWK Network | None Pvt Reply | No |
    | QWK Base ID | 1 Allow ANSI | Yes |
    | | +---------------------------------------------------------------------------+

    --- Mystic BBS v1.12 A33 (Linux/64)
    * Origin: Workpoint (21:1/145.3)
  • From bcw142@21:1/145.3 to Avon on Wednesday, August 16, 2017 07:26:26
    On 08/16/17, Avon said the following...

    On 08/15/17, bcw142 pondered and said...

    Email is a special case I guess, can't do normal ACS permissions, nee leave it to % at the start then nothing till s255 for sysop at the en permissions. Then it all works as it should. I checked the main BBS (which worked) to see that.

    Sounds like my settings, and it's a local base right?

    --- Mystic BBS v1.12 A34 (Windows/32)
    * Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)

    Yup, local so the final default is:

    +--------------------------------- ID 1 ------------------------------------+
    | Name | E-mail Quote Color | Sample | | Newsgroup | Email Text Color | Sample | | QWK Name | Email Tear Color | Sample | | Echo Tag | Email Origin Color | Sample | | File Name | email Kludge Color | Sample | | Path | /mystic/msgs/ Max Msgs | 0 | | List ACS | % Max Msg Age | 0 |
    | Read ACS | New Scan | Yes |
    | Post ACS | QWK Scan | Yes |
    | Sysop ACS | s255 Header | msghead |
    | Base Type | Local R Template | ansimrd |
    | Net Address | 0:0/0 (Local Address) L Template | ansimlst | | Export To | 0 node(s) Real Names | No |
    | Origin | WorkPoint Autosigs | No |
    | Sponsor | Private | Yes |
    | QWK Network | None Pvt Reply | No |
    | QWK Base ID | 1 Allow ANSI | Yes |
    | |

    +---------------------------------------------------------------------------+

    It might go in the FAQ that way, as it's been asked more than once here.

    --- Mystic BBS v1.12 A33 (Linux/64)
    * Origin: Workpoint (21:1/145.3)
  • From Gryphon@21:1/120 to bcw142 on Wednesday, August 16, 2017 09:58:32
    On 08/16/17, bcw142 said the following...

    On 08/15/17, Gryphon said the following...

    On 08/14/17, bcw142 said the following...

    I know someone had this problem recently, at startup when it sho it asks Read them now? Yes No
    But then shows "You don't have access to read in this base!" whe


    Check the ACS of the message base. I had that happen too. I had it that the groups were part of the ACS (g3s10) but if you are in a grou other than g3, you'll get that error.

    Interesting solution. It shows two interesting things: 1 g3 can be used this way (as local) and 2 it can go first as in g3s10 instead of s10g3
    (as is normal for Mystic docs. The solution I used was the original default:
    List ACS | %
    Read ACS |
    Post ACS |

    I'm a bit unclear on the access that ACS gives if the fields are blank. I
    was also of the understanding that to give implicit access, the '^' character was used. I do know that the order of the various acs types does not make a difference. I do also know that you can use the AND '&' and OR '|' so you
    can do (g1|g2|g3)s10 and it should allow access if you are in group 1, 2 or three and at seclev 10 or higher. but won't allow access if you are in g4.

    --- Mystic BBS v1.12 A34 (Linux/64)
    * Origin: Cyberia BBS | cyberia.darktech.org | San Jose, CA (21:1/120)
  • From bcw142@21:1/145 to Avon on Monday, August 14, 2017 19:11:58
    On 08/15/17, Avon said the following...
    I know someone had this problem recently, at startup when it shows ma it asks Read them now? Yes No
    But then shows "You don't have access to read in this base!" when I'm sysop! Any idea what happened? It's A33 Linux x64 Mystic in this case

    What is the ACS set for in the email base?

    Good thought, I'll check tomorrow when I have access to that one. It's just a point system I have at work behind the firewall there. I guess I should put teamviewer back on it, but I haven't. It still doesn't make sense, as sysop I have the highest ACS (255) so should have access to everything. My main BBS
    is working fine and the work one polls it hourly (as do a couple of others). It's how I figured out how to act as a Hub, playing with the points.

    --- Mystic BBS v1.12 A33 (Raspberry Pi/32)
    * Origin: Mystic Pi BBS bcw142.zapto.org (21:1/145)
  • From Gryphon@21:1/120 to bcw142 on Wednesday, August 16, 2017 10:09:40
    On 08/16/17, bcw142 said the following...

    On 08/16/17, Avon said the following...

    On 08/15/17, bcw142 pondered and said...

    Email is a special case I guess, can't do normal ACS permissions leave it to % at the start then nothing till s255 for sysop at t permissions. Then it all works as it should. I checked the main (which worked) to see that.

    Sounds like my settings, and it's a local base right?

    Yup, local so the final default is:


    I'm curious as to why it being a local base is important.

    --- Mystic BBS v1.12 A34 (Linux/64)
    * Origin: Cyberia BBS | cyberia.darktech.org | San Jose, CA (21:1/120)
  • From bcw142@21:1/145.2 to Gryphon on Wednesday, August 16, 2017 16:34:19
    On 08/16/17, Gryphon said the following...
    Sounds like my settings, and it's a local base right?

    Yup, local so the final default is:


    I'm curious as to why it being a local base is important.

    --- Mystic BBS v1.12 A34 (Linux/64)
    * Origin: Cyberia BBS | cyberia.darktech.org | San Jose, CA (21:1/120)

    Email isn't Netmail, it's local only and both of those have special handling. Basically Email is local, Netmail is external only (I think). Otherwise they are very much the same - one to one mail or echomail. Email has pretty much always existed on most BBS, Netmail is newer and handled quit differently.

    --- Mystic BBS v1.12 A34 (Linux/64)
    * Origin: Mystic AlphaTest bcw142.zapto.org:2323 (21:1/145.2)
  • From Gryphon@21:1/120 to bcw142 on Wednesday, August 16, 2017 16:57:17
    On 08/16/17, bcw142 said the following...

    On 08/16/17, Gryphon said the following...
    Sounds like my settings, and it's a local base right?

    Yup, local so the final default is:


    I'm curious as to why it being a local base is important.

    Email isn't Netmail, it's local only and both of those have special handling. Basically Email is local, Netmail is external only (I think). Otherwise they are very much the same - one to one mail or echomail.
    Email has pretty much always existed on most BBS, Netmail is newer and handled quit differently.

    So you are thinking it's not an ACS issue then? Something internal to the local email base? If it was an ACS issue, then it wouldn't matter if it was local or otherwise.

    --- Mystic BBS v1.12 A34 (Linux/64)
    * Origin: Cyberia BBS | cyberia.darktech.org | San Jose, CA (21:1/120)
  • From Avon@21:1/101 to Gryphon on Thursday, August 17, 2017 12:42:34
    On 08/16/17, Gryphon pondered and said...

    Sounds like my settings, and it's a local base right?

    Yup, local so the final default is:


    I'm curious as to why it being a local base is important.

    It may not be, but given it's not a base you would expect to export, keeping
    it 'local' is the way to go IMHO :)

    --- Mystic BBS v1.12 A34 (Windows/32)
    * Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)
  • From Avon@21:1/101 to bcw142 on Thursday, August 17, 2017 12:45:54

    On 08/15/17, bcw142 pondered and said...

    Email is a special case I guess, can't do normal ACS permissions, need to leave it to % at the start then nothing till s255 for sysop at the end of permissions. Then it all works as it should. I checked the main BBS
    (which worked) to see that.

    I agree the % is the key, need to review the ACS docs to confirm the meaning, but think it's a logical NOT and therefore something that ensures only those who have email addressed to them can see their own. I have a hunch g00r00 updated the coding and privacy around this also in recent alphas? Perhaps I
    am thinking of how Mystic handles netmail... that could be it.

    Best, Paul

    --- Mystic BBS v1.12 A34 (Windows/32)
    * Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)
  • From Avon@21:1/101 to bcw142 on Thursday, August 17, 2017 12:47:54
    On 08/15/17, bcw142 pondered and said...

    On 08/14/17, bcw142 pondered and said...
    I know someone had this problem recently, at startup when it sho it asks Read them now? Yes No
    But then shows "You don't have access to read in this base!" whe sysop! Any idea what happened? It's A33 Linux x64 Mystic in this

    Are you sure it's an email base presenting with this issue, or could it be a base where you have it set to force all users to read the base on new message scan?

    --- Mystic BBS v1.12 A34 (Windows/32)
    * Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)
  • From bcw142@21:1/145.3 to Gryphon on Friday, August 18, 2017 11:03:12
    On 08/16/17, Gryphon said the following...
    So you are thinking it's not an ACS issue then? Something internal to
    the local email base? If it was an ACS issue, then it wouldn't matter
    if it was local or otherwise.

    It's it's own special case, but it was ACS. It's fixed and working fine. 'Email' by the Mystic definition is local, 'Netmail' is external. They are
    both special cases of mail. It could have been handled differently, but
    that's the way it's ended up and it works fine.

    --- Mystic BBS v1.12 A33 (Linux/64)
    * Origin: Workpoint (21:1/145.3)
  • From bcw142@21:1/145 to Gryphon on Wednesday, August 16, 2017 13:37:13
    On 08/16/17, Gryphon said the following...
    default:
    List ACS | %
    Read ACS |
    Post ACS |

    I'm a bit unclear on the access that ACS gives if the fields are blank.
    I was also of the understanding that to give implicit access, the '^' character was used. I do know that the order of the various acs types does not make a difference. I do also know that you can use the AND '&' and OR '|' so you can do (g1|g2|g3)s10 and it should allow access if you are in group 1, 2 or three and at seclev 10 or higher. but won't allow access if you are in g4.

    --- Mystic BBS v1.12 A34 (Linux/64)
    * Origin: Cyberia BBS | cyberia.darktech.org | San Jose, CA (21:1/120)

    The % doesn't really give any access, but if your sender or receiver of email you get access automatically I think. The empty stuff I think either uses the
    % or nothing, not sure. I didn't realize the pipe and & would work there, but it seems I vaguely remember seeing something like that. I would expect local
    to be g0 or g1 not g3 so that seems odd, but it could end up that way after some moving things around ;)

    --- Mystic BBS v1.12 A33 (Raspberry Pi/32)
    * Origin: Mystic Pi BBS bcw142.zapto.org (21:1/145)
  • From g00r00@21:1/108 to bcw142 on Friday, August 25, 2017 12:11:58
    I know someone had this problem recently, at startup when it shows mail
    it asks Read them now? Yes No

    You have an ACS set for your email base, most likely. You should not modify the post/read ACS for the e-mail base.

    --- Mystic BBS v1.12 A35 (Windows/32)
    * Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)
  • From bcw142@21:1/145 to g00r00 on Saturday, August 26, 2017 10:12:01
    On 08/25/17, g00r00 said the following...

    I know someone had this problem recently, at startup when it shows ma it asks Read them now? Yes No

    You have an ACS set for your email base, most likely. You should not modify the post/read ACS for the e-mail base.

    Yup, it was changed, I put it back to % and that fixed it. It was ACS, I must have changed it at some point. Compared it to a working system and set it up like that.

    --- Mystic BBS v1.12 A33 (Raspberry Pi/32)
    * Origin: Mystic Pi BBS bcw142.zapto.org (21:1/145)