Just a heads up. I have been working with 'directory' style transfers between two Mystic systems on the same Windows PC. What I have noticed is that during
a Fidopoll between the two systems the usual echomail.in semaphore is not
being created by the receiving system during a Fidopoll from a sending system.

My theory is that semaphores seem to be the domain on BinkP sessions only, so
I switched over and started running BinkP between the two systems and that solved the issue. Thinking here is that the BinkP server creates the semaphores.

But in cases of Fidopoll 'directory' style sessions it would be good if MIS
or MIS2 could monitor the known inbound directory and create a semaphore when
a file appears.

Best, Paul

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

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

But in cases of Fidopoll 'directory' style sessions it would be good if MIS or MIS2 could monitor the known inbound directory and create a semaphore when a file appears.

Right now if I am right MIS is the only one which can monitor semaphores via the event editor, MIS2 can not do this yet why we are all running MIS/MIS2. :P

Cheers!
Pequito

--- Mystic BBS v1.12 A35 (Linux/32)
* Origin: Twinkle BBS # (21:1/126)

On 09/26/17, Pequito pondered and said...

Right now if I am right MIS is the only one which can monitor semaphores via the event editor, MIS2 can not do this yet why we are all running MIS/MIS2. :P

Yep you're correct - I was just future proofing :)

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

Right now if I am right MIS is the only one which can monitor semaphores via the event editor, MIS2 can not do this yet why we are all running MIS/MIS2. :P

ok that answers why my events weren't working. danke for the 411 on that
one.

cheers,

-tMt

--- Mystic BBS v1.12 A34 (Windows/32)
* Origin: the facility bbs (21:1/172)

Just a heads up. I have been working with 'directory' style transfers between two Mystic systems on the same Windows PC. What I have noticed
is that during a Fidopoll between the two systems the usual echomail.in semaphore is not being created by the receiving system during a Fidopoll from a sending system.

Yes, there is no "server" receiving any files so there is nothing there to create incoming semaphores.

But in cases of Fidopoll 'directory' style sessions it would be good if MIS or MIS2 could monitor the known inbound directory and create a semaphore when a file appears.

Maybe there can be a configuration option for the echomail node that
specifies the path to create the semaphores, and then FidoPoll will create them. Otherwise, you could do a check with a batch file (not tested example below) or just whatever calls FIDOPOLL can also put the semaphore there.

REM IF ANY FILE EXISTS IN INCOMING DIRECTORY CREATE SEMAPHORE

IF EXIST "C:\BBS\ECHO\IN\*" (
ECHO Incoming mail>> C:\BBS\SEMAPHORE\ECHOMAIL.IN
)

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

On 10/22/17, g00r00 pondered and said...

Just a heads up. I have been working with 'directory' style transfers between two Mystic systems on the same Windows PC. What I have notice is that during a Fidopoll between the two systems the usual echomail. semaphore is not being created by the receiving system during a Fidop from a sending system.

Yes, there is no "server" receiving any files so there is nothing there
to create incoming semaphores.

Fair enough, what I'm hoping to do is automate a mailin.ini using Mystic semaphore events system much like the BinkP server does.

Maybe there can be a configuration option for the echomail node that specifies the path to create the semaphores, and then FidoPoll will
create them. Otherwise, you could do a check with a batch file (not tested example below) or just whatever calls FIDOPOLL can also put the semaphore there.

True, either option would work but I like the elegance of your first
suggestion in that it's more baked in to the Mystic DNA :)

Best, Paul

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