On my Mystic Pi BBS at bcw142.zapto.org I've noticed a problem with the semaphores: mailin.ini worked, mailout.ini didn't. What I saw:
Sep 24 06:47:52 VER Mystic/1.12A35 binkp/1.0
Sep 24 06:47:52 Recv: ADR 21:1/100@fsxnet 21:1/3@fsxnet 21:1/2@fsxnet 21:1/0@fsxnet 21:0/0@fsxnet
Sep 24 06:47:52 Sent: PWD CRAM-MD5-224f190964ba226f7128e215975c97b2
Sep 24 06:47:52 Authorization State: 5 HH:0 NH:1
Sep 24 06:47:52 Recv: OK secure
Sep 24 06:47:52 Authorization State: 5 HH:1 NH:0
Sep 24 06:47:52 State RxS:1 TxS:1 HH:0 NH:1
Sep 24 06:47:52 Sent: EOB
Sep 24 06:47:53 State RxS:1 TxS:4 HH:0 NH:1
Sep 24 06:47:53 Recv: FILE 0000ffd3.sus 3172 1506295238 0
Sep 24 06:47:53 State RxS:1 TxS:4 HH:1 NH:0
Sep 24 06:47:53 Receiving 0000ffd3.sus (3,172 bytes)
Sep 24 06:47:53 Recv: Data 3,172/3,172

Received, but didn't send anything and there was a 'Mystic Pi Says'
poster.ini that had run at ~2am that wasn't sent till I forced a poll
with my poll script (which forces './mutil mailout.ini'):

Sep 24 07:14:09 Recv: NUL VER Mystic/1.12A35 binkp/1.0
Sep 24 07:14:09 VER Mystic/1.12A35 binkp/1.0
Sep 24 07:14:09 Recv: ADR 21:1/145.5@fsxnet
Sep 24 07:14:09 Sent: PWD CRAM-MD5-b86af884df4ac4363804e7fffe2e4b33
Sep 24 07:14:09 Authorization State: 5 HH:0 NH:1
Sep 24 07:14:09 Recv: OK secure
Sep 24 07:14:09 Authorization State: 5 HH:1 NH:0
Sep 24 07:14:09 State RxS:1 TxS:1 HH:0 NH:1
Sep 24 07:14:09 Sending 00000005.su6 (3,029 bytes)
Sep 24 07:14:09 Sent: FILE 00000005.su6 3029 1506237238 0
Sep 24 07:14:09 Recv: EOB
Sep 24 07:14:09 State RxS:1 TxS:2 HH:1 NH:0
Sep 24 07:14:09 Sent: Data 3,029
Sep 24 07:14:09 State RxS:3 TxS:3 HH:0 NH:1
Sep 24 07:14:09 Recv: GOT 00000005.su6 3029 1506237238
Sep 24 07:14:09 State RxS:3 TxS:3 HH:1 NH:0
Sep 24 07:14:09 State RxS:3 TxS:1 HH:0 NH:1
Sep 24 07:14:09 Sent: EOB
Event Editor shows:
Yes Semaphore Send outbound echomail N/A

Active Yes
Description Send outbound echomail Sun No
Exec Type Semaphore Mon No
Exec Hour 0 Tue No
Exec Min 0 Wed No
Shell ./mutil export.ini|./fidopoll Thu No
Semaphore echomail.out|netmail.out Fri No
Node 0 Sat No
Warning 0

The full Shell line './mutil export.ini|./fidopoll send|./mutil import.ini'. export.ini is linked to mailout.ini and the same setup for import.ini.
cat export.ini shows:

; MUTIL MAILOUT.INI for Mystic Pi BBS bcw142.zapto.org
;
; Configured to put Echo/Netmail out based on 'Mystic Guy' YouTube channel
;
[General] ; list of functions to perform on startup

ExportEchoMail = true

logfile=mutil.log
loglevel = 3
maxlogsize = 1000

[ExportEchoMail]

; Do not export messages from users currently online
; seemed to cause problems

skip_online = false


So what did I miss that caused it not to send? When I looked it was in
the area as 'local' until I forced it, then 'local sent' as it should
have been.

--- Mystic BBS v1.12 A35 (Raspberry Pi/32)
* Origin: Mystic Pi BBS bcw142.zapto.org (21:1/145)

On 09/24/17, bcw142 pondered and said...

On my Mystic Pi BBS at bcw142.zapto.org I've noticed a problem with the semaphores: mailin.ini worked, mailout.ini didn't. What I saw:

There's a lot of info in that post.

So firstly are you having issues in general getting message out?

Looking at the thread I am also confused as to why you run different ini
files that seem to do the same thing? e.g. mailout.ini and a export.ini

I would change the SHELL line to point to one of them and remove the other.

Active Yes
Description Send outbound echomail Sun No
Exec Type Semaphore Mon No
Exec Hour 0 Tue No
Exec Min 0 Wed No
Shell ./mutil export.ini|./fidopoll Thu No
Semaphore echomail.out|netmail.out Fri No
Node 0 Sat No
Warning 0

None of the days, are set to YES

Best, Paul

--- Mystic BBS v1.12 A35 (Windows/32)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)

On 09/25/17, Avon said the following...

On 09/24/17, bcw142 pondered and said...

On my Mystic Pi BBS at bcw142.zapto.org I've noticed a problem with t semaphores: mailin.ini worked, mailout.ini didn't. What I saw:

There's a lot of info in that post.

Yes, I wasn't sure what was needed and so included everything that should be reliant.

So firstly are you having issues in general getting message out?

Yes, but messages were coming in OK.

Looking at the thread I am also confused as to why you run different ini files that seem to do the same thing? e.g. mailout.ini and a export.ini

Just an effort to use G00r00's examples as much as possible. I had mailin.ini and mailout.ini already made from your YouTube examples and just linked them
to what G00r00 had called them, so to make it easier without modifying the names. In Linux we often do such things, treating them like aliases. It could be a problem, but since mailin.ini works and mailout.ini doesn't I doubted that as the cause.

I would change the SHELL line to point to one of them and remove the other.

Worth a shot, even though I doubted it should matter - it could. Links are
not always followed in Linux. They are a kind of cheat that doesn't always work.

None of the days, are set to YES

As stated above, I don't think days are reliant to semaphores any more than time is, as shown by G00r00's examples in the events table when we start.
From the examples I assumed Time and Days aren't reliant to semaphore
triggered events.

--- Mystic BBS v1.12 A35 (Raspberry Pi/32)
* Origin: Mystic Pi BBS bcw142.zapto.org (21:1/145)

From what I've found time and date aren't used for semaphores as I had stated before, but the Linux links were a problem for sending messages. It didn't
seem to work and changing export.ini from a link to mailout.ini seems to have fixed that issue. Why import.ini as a link seemed to work I don't know. With Linux links are often like that, even with Windows not all 'shortcuts' as Windows calls them work.
EchoMail seems to send quickly now from the main BBS, we'll see what happens here on .2 AlphaTest ;)
PS. Well, it didn't send after I left it and check the semaphores, No idea
what it's up to, but my hourly forced poll should send it. Edited this in to the message after checking Events and seeing it didn't send. ;(

..The best laid plans of mice and men. [What have men got to do with it?]

--- Mystic BBS v1.12 A35 (Linux/64)
* Origin: Mystic AlphaTest bcw142.zapto.org:2323 (21:1/145.2)

On 09/25/17, bcw142 pondered and said...

stated before, but the Linux links were a problem for sending messages.
It didn't seem to work and changing export.ini from a link to
mailout.ini seems to have fixed that issue. Why import.ini as a link seemed to work I don't know. With Linux links are often like that, even

I'm not familiar with links such as that but agree it best to let Mystic run off one version of the ini files and make them the authoritative source.

EchoMail seems to send quickly now from the main BBS, we'll see what happens here on .2 AlphaTest ;)
PS. Well, it didn't send after I left it and check the semaphores, No
idea what it's up to, but my hourly forced poll should send it. Edited this in to the message after checking Events and seeing it didn't send.

So this is a Linux powered version also? I'm loosing track :)

--- Mystic BBS v1.12 A35 (Windows/32)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)