1. Forum
  2. SciNet
  3. SCIMYSTIC

  • MUTIL ImportEchoMail: Auto-create Path and List EACS?

    From Zip@77:2/107 to g00r00 on Thu Nov 19 18:22:42 2020
    Hello g00r00!

    Hope all is well with you, and thanks for your continued great work on Mystic!

    I'm wondering if there is any way to set the Path and List EACS of auto-created message areas in mutil.ini?

    Something like:

    path = /mnt/bbs/mystic/msgs
    eacs_list = g1

    ...with per-node overrides such as:

    46:999/999_path = /mnt/bbs/mystic/msgs/scinet
    46:999/999_eacs_list = g6

    I noticed that the Path field gets the (default) Message Base Path and that List EACS is empty, and would love to have those fields populated for new areas if possible.

    Tried to run "strings" on mutil but found nothing matching... =)

    Many thanks in advance!

    Best regards
    Zip

    --- Mystic BBS v1.12 A47 2020/10/31 (Linux/64)
    * Origin: Star Collision BBS, Uppsala, Sweden (77:2/107)
  • From g00r00@77:1/138 to Zip on Thu Nov 19 14:06:48 2020
    I'm wondering if there is any way to set the Path and List EACS of auto-created message areas in mutil.ini?

    The path was intentional because I was planning to remove the path for each individual message base back when I created that function. But the List EACS was just something I just forgot to add in when I added echomail ACS.

    In the next build you will be able to define the echo list ACS as:

    acs_elist =

    (Or should I make it acs_echolist ?)

    Being able to define a path per network for automatic creation will take a little bit more work that I don't want to do until I have more time to test the change. The EACS is a quick change.

    --- Mystic BBS v1.12 A47 2020/11/17 (Windows/64)
    * Origin: Sector 7 | Mystic WHQ (77:1/138)
  • From Zip@77:2/107 to g00r00 on Fri Nov 20 08:51:20 2020
    Hello g00r00!

    On 19 Nov 2020, g00r00 said the following...
    The path was intentional because I was planning to remove the path for each individual message base back when I created that function. But the

    OK! :)

    In the next build you will be able to define the echo list ACS as: acs_elist =

    Thanks a lot!

    (Or should I make it acs_echolist ?)

    I'd suggest eacs_list to match the config screen in the Message Base Editor and since EACS is a term used in the documentation, but probably it doesn't matter. :)

    Best regards
    Zip

    --- Mystic BBS v1.12 A47 2020/10/31 (Linux/64)
    * Origin: Star Collision BBS, Uppsala, Sweden (77:2/107)