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.
--- Mystic BBS v1.12 A46 2020/08/26 (Linux/64)
* Origin: Westwood BBS II (21:1/999)
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.
I think this is an area that trips a lot of people up (me included). As this is of concern for fsxNet sysops running echomail properly w/Mystic, wonder if we could create a documentation page on the fsxNet wiki
I think this is an area that trips a lot of people up (me included). As this is of concern for fsxNet sysops running echomail properly w/Mystic, wonder if we could create a documentation page on the fsxNet wiki
showing recommended echomail setups? I've actually scrubbed your videos multiple times looking at events.At one point, I gave up on Mystic
events and switched to cron jobs, not realizing you had to restart the
mis server for them to take effect... Also, there's the difference
between Windows and Linux events, no more fidpoll, etc.
mailout.ini and maint.ini, as well as the fidopoll, but had to watch through one of the Windows videos to figure out events.
Sysop: | Eric Oulashin |
---|---|
Location: | Beaverton, Oregon, USA |
Users: | 97 |
Nodes: | 16 (0 / 16) |
Uptime: | 00:05:12 |
Calls: | 4,613 |
Calls today: | 7 |
Files: | 8,491 |
Messages: | 349,784 |