Very new to Mystic, so apologies for struggling with the basics.

Raspberry Pi using the latest Mystic download.

Echomail in and out seems to work fine if I manually run fidopoll and mutil, but so far it seems like I have to manually run the import.ini in order to
toss the mail, both when it polls and when the semaphore triggers.

The shell field of the event is the default:
fidopoll forced|mutil import.ini

The mis.log shows that both commands run with Res 127 after them (I don't
know what that means).

Is there a way to force debug-level logs on mis? Is there something I'm
missing with the event?


Thanks,
Andre

--- Mystic BBS v1.12 A45 2020/02/18 (Raspberry Pi/32)
* Origin: Runaan BBS (21:3/117)

On 24 Jul 2020, Andre said the following...

Echomail in and out seems to work fine if I manually run fidopoll and mutil, but so far it seems like I have to manually run the import.ini in order to toss the mail, both when it polls and when the semaphore triggers.

Figured this one out... The "shell" field of the events wants something in
the $PATH, but I don't want /mystic in the path. So I just called each
command explicitly.

Instead of:
fidopoll forced|mutil import.ini

I changed it to:
/mystic/fidopoll forced|/mystic/mutil import.ini


When I made those changes to the relevant events, everything worked find.

If anyone knows how to make the mis.log more of a 'debug' level, I still
would like that info.


- Andre

--- Mystic BBS v1.12 A45 2020/02/18 (Raspberry Pi/32)
* Origin: Runaan BBS (21:3/117)

Re: Re: Import not triggering on event but not doing anything
By: Andre to Andre on Fri Jul 24 2020 07:00 pm

Hey Andre,

Figured this one out... The "shell" field of the events wants something in the $PATH, but I don't want /mystic in the path. So I just called each command explicitly.
Instead of:
fidopoll forced|mutil import.ini
I changed it to:
/mystic/fidopoll forced|/mystic/mutil import.ini

Yeah, this is a known hurdle with Mystic. Many just ./ the commands.

...ëîåï

... What is moral is what you feel good after.
--- SBBSecho 3.11-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)

/mystic/fidopoll forced|/mystic/mutil import.ini

If anyone knows how to make the mis.log more of a 'debug' level, I still would like that info.

Edit that import.ini file, and in there somewhere is a log level line...
there are like 3 or 4 options and you just change the number to verbose. If you're not working with a notated .ini, and it doesn't like what the #s mean you can find a notated mystic .ini file in a clean/stock install of mystic,
or on the mystic wiki...



|07p|15AULIE|1142|07o
|08.........

--- Mystic BBS v1.12 A45 2020/02/18 (Raspberry Pi/32)
* Origin: American Pi BBS (21:2/150)

On 24 Jul 2020, paulie420 said the following...

Edit that import.ini file, and in there somewhere is a log level line... there are like 3 or 4 options and you just change the number to verbose. If you're not working with a notated .ini, and it doesn't like what the

That seems to for anything that mutil is doing, but I was wondering about
mis. I assume if there was a debug-level log it would have told me the error with the events.

- Andre

--- Mystic BBS v1.12 A45 2020/02/18 (Raspberry Pi/32)
* Origin: Runaan BBS (21:3/117)

On 25 Jul 2020, Andre said the following...

On 24 Jul 2020, paulie420 said the following...

Edit that import.ini file, and in there somewhere is a log level line there are like 3 or 4 options and you just change the number to verbo If you're not working with a notated .ini, and it doesn't like what t

That seems to for anything that mutil is doing, but I was wondering about mis. I assume if there was a debug-level log it would have told me the error with the events.

- Andre

Sorry, I read it as you wanted debug logs in mutil... I don't have the data
you need, sir. :O



|07p|15AULIE|1142|07o
|08.........

--- Mystic BBS v1.12 A45 2020/02/18 (Raspberry Pi/32)
* Origin: American Pi BBS (21:2/150)