Hi, new Sysop here. Not sure what is going on, but my echomail isn't being
sent unless I manually run the event "Send outbound echomail" commands at the command line (e.g. ./mutil mailout.ini && ./fidopoll send && ./mutil mailin.ini). Then the mail sends properly.

I've set the echomail node to Export Type: Crash, and Message Settings:
Create Semaphore to Logout. mailout.ini contains ExportEchoMail = true

The event itself is Active, type Semaphore, and set "Yes" to all days of the week.

To test, I post a message in an echomail area, then logoff. About 10 minutes later, the message is still flagged as "Local" and not "Sent."

The only thing I can think of is that somehow the Semaphore isn't being set,
or read, therefore the event never fires (and I've confirmed the event is Active).

Reading mutil logs confirms that it was never run.

I'm running Mystic BBS v1.12 A43 on Linux64 (Xubuntu 19.04).

Any thoughts? Suggestions on debugging? Thanks!

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: Strontium 90 BBS (21:4/158)

I'm running Mystic BBS v1.12 A43 on Linux64 (Xubuntu 19.04).

Forgot to add: running Mystic as "sudo ./mis daemon"

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: Strontium 90 BBS (21:4/158)

The event itself is Active, type Semaphore, and set "Yes" to all days of the week.

I had a similar problem when I first started with Echomail.... I hadn't specified a name in the Semaphore and Kill After fields in the Event Editor. Adding echomail.out|netmail.out to both fields got it working.

I've also had a couple issues on new non-mail related events that they don't seem to 'kick in' until I restart mis.

Just a couple things that I tripped over. Good luck!

Dave

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/32)
* Origin: Blue Northern Software | bnsbbs.ddns.net:23000 (21:4/111)

Hi,

From what I see your configuration is close to mine. And mine works.
Only that I am using "|" between commands instead of "&&".

Are you sure that your system is generating semaphore files correctly? Configure your server to create semaphores right after you finish writing
the message and not after you logout. Then, on a terminal window on your
Linux server monitor the semaphore folder using NC file commander (this is
what I use) to see if ecomail.out is created.

Also a good idea would be to run the ./mis server command in another terminal and look if the system runs the events.

There might be something wrong somewhere in your config.

Andrei
apernevan.tk BBS, Arad RO
Web - https://apernevan.tk
Telnet - telnet://apernevan.tk

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: apernevan.tk BBS | Arad, Romania (21:1/124)

Forgot to add: running Mystic as "sudo ./mis daemon"

you should also check the permissions in the mystic folder. I had a
permissions problem when I fist installed mystic.

Andrei
apernevan.tk BBS, Arad RO
Web - https://apernevan.tk
Telnet - telnet://apernevan.tk

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: apernevan.tk BBS | Arad, Romania (21:1/124)

On 12 Jun 2019, andrei said the following...

Hi,

From what I see your configuration is close to mine. And mine works.
Only that I am using "|" between commands instead of "&&".

^^^^ This right here. I knew his command looked a little off, and that's exactly it.

Mystic wants pipes between commands; linux wants &&. I betcha it works after
he sets his double ampersands to singular pipes. =)

--- Mystic BBS v1.12 A43 2019/02/23 (Raspberry Pi/32)
* Origin: throwbackbbs.com -\- meriden, ct -\- (21:1/114)

yep, this should do the trick if all other settings are ok.

Andrei
apernevan.tk BBS, Arad RO
Web - https://apernevan.tk
Telnet - telnet://apernevan.tk

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: apernevan.tk BBS | Arad, Romania (21:1/124)

I had a similar problem when I first started with Echomail.... I hadn't specified a name in the Semaphore and Kill After fields in the Event Editor. Adding echomail.out|netmail.out to both fields got it working.

Figured it out! Was a really a dumb oversight on my part: in the Event
Editor, I was missing the "./" in front of the shell commands (e.g ./mutil mailout.ini). Finally realized that "res 127" in the mis console when
events fired meant path not found. Fixed! Thanks.

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: Strontium 90 BBS (21:4/158)