[snip]

Event Type: Semaphore
Semaphore: (echomail.in|netmail.in)!fidopoll.bsy
Kill After: echomail.in|netmail.in

The above example says to trigger the event if echomail.in OR netmail.in
exists but NOT if fidopoll.bsy exists. The result would be that the
command line would run when there is incoming net/echomail but it'd also
wait for fidopoll to finish running (if it is) before kicking off.

[snip]

Tested this at 1/100 and the system is not firing the shell line to process incoming packets when I updated the Semaphore line as per example above.

Test was conducted using an event with a valid (prior working ID) with just
the Semaphore line changed out.

Fidopoll was not running when the packet came in via MIS BinkP and an echomail.in semaphore has been created and is now sitting untouched in the semaphore directory.

Closing down the MIS server and restarting had no effect on this and the inbound packet remains unprocessed.

I'm going to send this second packet now to confirm it's still not budging
then will revert to original Semaphore line.

--- Mystic BBS v1.12 A39 2018/03/29 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

On 03/31/18, Avon pondered and said...

I'm going to send this second packet now to confirm it's still not
budging then will revert to original Semaphore line.

Yep confirmed, all is working again now I am using

Event Type: Semaphore
Semaphore: echomail.in|netmail.in
Kill After: echomail.in|netmail.in

So something is broken there...

--- Mystic BBS v1.12 A39 2018/03/29 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

Yep confirmed, all is working again now I am using

Event Type: Semaphore
Semaphore: echomail.in|netmail.in
Kill After: echomail.in|netmail.in

So something is broken there...

I've fixed it so far as I can tell and I am going to send you new pre-alphas now.

--- Mystic BBS v1.12 A39 2018/03/30 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

On 04/01/18, g00r00 pondered and said...

I've fixed it so far as I can tell and I am going to send you new pre-alphas now.

Thanks! these are now up on the mystic.bbs.nz site and I am working on
updating 1/100 before I go to bed. Will test in the morning and update 1/101 then also.

Best, Paul

--- Mystic BBS v1.12 A39 2018/03/29 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

On 04/01/18, Avon pondered and said...

I've fixed it so far as I can tell and I am going to send you new pre-alphas now.

Thanks! these are now up on the mystic.bbs.nz site and I am working on

I have added a release.txt file to the /pre directory which contains the
output of mystic -ver for the pre-release I have uploaded. Hopefully this
helps others if/when they pull a copy from this server so they know which
build they are getting :)

Best, Paul

--- Mystic BBS v1.12 A39 2018/04/01 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)