• Default List EACS for auto-created message areas?

    From Zip@21:1/101 to All on Sat Dec 28 08:32:34 2019
    Hello everyone!

    Does anyone know if there is some config file directive for the MUTIL ImportEchoMail stanza which allows you to specify the default List EACS for auto-created message areas?

    Something similar to:

    21:1/202_acs_list = g2

    ...but that one is for "List ACS", not "List EACS"!

    Thanks in advance!

    Best regards
    Zip

    --- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From Avon@21:1/101 to Zip on Sat Dec 28 21:25:57 2019
    On 28 Dec 2019 at 08:32a, Zip pondered and said...

    Does anyone know if there is some config file directive for the MUTIL ImportEchoMail stanza which allows you to specify the default List EACS for auto-created message areas?

    There is not one to my knowledge as the whole EACS system was being implemented incrementally by g00r00 when 1.12 A37 came out first with a focus on echomail.

    [snip]

    + The beginning of Echomail node security is here! The easiest way to think
    about how this system works is to relate an Echomail node to the way
    security works for a user in your BBS. Each node will have a security
    level, access flags, and can be a member of many Echomail groups (up to
    65000 echomail groups can be defined).

    Different functions throughout the echomail system will eventually have
    "Echo ACS" strings which work just like the user ACS strings that we're
    familiar with. For example, you might have "Hatch File EACS" in a file
    base
    where you could say that you wanted only echomail nodes within a particular
    group to be able to hatch files, or a particular security level or access
    flag(s), or even by static echomail node ID. For example:

    Hatch File EACS: g2|s255|fH|u10

    The above would say that any echomail node that is a member of Echomail
    group 2, OR any node that has a security level of 255 OR any Echomail node
    that has flag H can hatch files to that file base. The Echomail node
    with the ID of #10 can also hatch.

    This is a very powerful system for managing an Echomail network, and EACS
    strings will be added to various functions in the future as seen fit.

    [snip]

    Then when A39 came out some focus was given to file bases

    [snip]

    + File Bases now have an "List EACS". This Echomail ACS works identically
    to the Message Base version, allowing hubs to define which nodes have
    access to list, subscribe, and receive get files from an echoed file base

    [snip]

    ..and that's where things got to..

    I agree that having those equivalent switches in the [ImportEchoMail] and [FileToss] stanzas would be a good move.

    But they are not there as yet.

    Best, Paul

    --- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From Zip@21:1/202 to Avon on Sat Dec 28 11:52:14 2019
    Hello Avon!

    On 28 Dec 2019, Avon said the following...
    I agree that having those equivalent switches in the [ImportEchoMail] and [FileToss] stanzas would be a good move.

    But they are not there as yet.

    Thanks for all the info!

    Not a big deal as I don't have any downlinks, but would be nice. We'll see
    what happens in the future. :)

    Thanks again!

    Best regards
    Zip

    --- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
    * Origin: Star Collision BBS, Uppsala, Sweden (21:1/202)