On 25 Jan 2021 at 10:47p, Nuke pondered and said...
Under events editor for echomail, do those need to be modified prior to activating? With Avon's advice on mailout.ini / mailin.ini - I wasn't sure if the original commands using "import.ini" apply?
I did try to modify to what I thought it should be and activing these events appear to lock up MIS (it shows "Starting Events" but never seems to finish.
A lot of the events in the stock install refer to files not created.
I'd start with two semaphore events to listen for incoming and outgoing echomail/netmail.
I'd also have an interval event set to poll your hub(s) and a nightly maintenance event to run an .ini that calls the maintenance you want done.
--- Mystic BBS v1.12 A46 2020/08/26 (Linux/64)
* Origin: Westwood BBS II (21:1/999)
You will want to ensure your shell commands are set for linux pathing so something like
./mutil mailin.ini (assuming you have an ini set up to process echomail and files etc. called mailin :)
--- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)