Evening to you from over here as my Saturday comes to a close.

I've updated 1/100 and 1/101 to the latest build and implemented MIS POLL
SEND for both systems when MUTIL tosses mail in and out of each.

So... interesting start for 1/100 I was noticing a number of nodes that were failing during a poll session after MUTIL has processed incoming echomail.

I saw this sort of thing.

--------------------- POLL v1.12 A46 2020/02/29 Sat, Feb 29 2020 (loglevel 2) + 2020.02.29 20:10:39 Sending to all nodes of session type ALL
+ 2020.02.29 20:10:39 Queued 1 files (859 bytes) for 21:1/107
+ 2020.02.29 20:10:39 1-Polling 21:1/107 on slot 1 via BINKP
+ 2020.02.29 20:10:39 Queued 1 files (859 bytes) for 21:1/106
+ 2020.02.29 20:10:39 1-Connecting to bbs.thebytexchange.com on port 24555
+ 2020.02.29 20:10:39 2-Polling 21:1/106 on slot 2 via BINKP
+ 2020.02.29 20:10:39 2-Connecting to blackice.bbsindex.de on port 24555
+ 2020.02.29 20:10:39 Queued 1 files (858 bytes) for 21:1/105
+ 2020.02.29 20:10:39 3-Polling 21:1/105 on slot 3 via BINKP
+ 2020.02.29 20:10:39 3-Connecting to fluph.zapto.org on port 24555
+ 2020.02.29 20:10:39 Queued 1 files (859 bytes) for 21:1/104
+ 2020.02.29 20:10:39 4-Polling 21:1/104 on slot 4 via BINKP
+ 2020.02.29 20:10:39 4-Connecting to shenks.dyndns.org on port 24555
+ 2020.02.29 20:10:39 Queued 1 files (859 bytes) for 21:1/102
+ 2020.02.29 20:10:39 5-Polling 21:1/102 on slot 5 via BINKP
+ 2020.02.29 20:10:39 5-Connecting to error404bbs.ddns.net on port 24555
+ 2020.02.29 20:10:39 Queued 1 files (1,158 bytes) for 21:1/101
+ 2020.02.29 20:10:39 6-Polling 21:1/101 on slot 6 via BINKP
+ 2020.02.29 20:10:39 6-Connecting to 192.168.1.130 on port 24555
+ 2020.02.29 20:10:39 Queued 1 files (858 bytes) for 21:1/110
+ 2020.02.29 20:10:39 7-Polling 21:1/110 on slot 7 via BINKP
+ 2020.02.29 20:10:39 7-Connecting to ftn.amigaxess.de on port 24555
+ 2020.02.29 20:10:39 Queued 1 files (859 bytes) for 21:1/113
+ 2020.02.29 20:10:39 8-Polling 21:1/113 on slot 8 via BINKP
+ 2020.02.29 20:10:39 8-Connecting to alco.bbs.io on port 24555
+ 2020.02.29 20:10:39 Queued 1 files (61,283 bytes) for 21:1/114
+ 2020.02.29 20:10:39 Waiting for available send slot for 21:1/114
+ 2020.02.29 20:10:45 1-Unable to connect
+ 2020.02.29 20:10:45 2-Unable to connect
+ 2020.02.29 20:10:45 3-Unable to connect
+ 2020.02.29 20:10:45 4-Unable to connect
+ 2020.02.29 20:10:45 6-Unable to connect

[snip]

+ 2020.02.29 20:11:40 5-Session ended (1 sent, 0 rcvd, 0 skip)
+ 2020.02.29 20:11:41 4-Session ended (1 sent, 0 rcvd, 0 skip)
+ 2020.02.29 20:11:41 6-System Star Collision BBS
+ 2020.02.29 20:11:41 6-SysOp Zip
+ 2020.02.29 20:11:41 6-Info TIME Sat, 29 Feb 2020 08:11:51 +0100
+ 2020.02.29 20:11:41 6-Mailer Mystic/1.12A45 binkp/1.0
+ 2020.02.29 20:11:41 6-Info BUILD 2020/02/18 21:23:34 Linux/64
+ 2020.02.29 20:11:41 2-Sending: 0000ff98.sad (861 bytes)
+ 2020.02.29 20:11:41 2-Remote Queue: 0 files 0 bytes
+ 2020.02.29 20:11:41 2-Session ended (1 sent, 0 rcvd, 0 skip)
+ 2020.02.29 20:11:41 6-Sending: 0000ff9a.sab (867 bytes)
+ 2020.02.29 20:11:42 6-Remote Queue: 0 files 0 bytes
+ 2020.02.29 20:11:42 8-Unable to connect
+ 2020.02.29 20:11:42 6-Session ended (1 sent, 0 rcvd, 0 skip)
+ 2020.02.29 20:11:42 1-Unable to connect
+ 2020.02.29 20:11:43 Polled 68 systems

[snip]

So I ran FIDOPOLL SEND and saw the same issues

[snip]

Feb 29 20:19:48 Scanning 21:1/107
Feb 29 20:19:48 Queued 1 files (870 bytes) to 21:1/107
Feb 29 20:19:48 Polling BINKP node 21:1/107 (Chad Adams) by IPV4
Feb 29 20:19:48 Connecting to bbs.thebytexchange.com port 24555
Feb 29 20:19:58 Unable to connect
Feb 29 20:19:58 ---
Feb 29 20:19:58 Scanning 21:1/106
Feb 29 20:19:58 Queued 1 files (6439 bytes) to 21:1/106
Feb 29 20:19:58 Polling BINKP node 21:1/106 (Vitus Zeel) by IPV4
Feb 29 20:19:58 Connecting to blackice.bbsindex.de port 24555
Feb 29 20:20:08 Unable to connect
Feb 29 20:20:08 ---
Feb 29 20:20:08 Scanning 21:1/105
Feb 29 20:20:08 Queued 1 files (6435 bytes) to 21:1/105
Feb 29 20:20:08 Polling BINKP node 21:1/105 (Leslie Given) by IPV4
Feb 29 20:20:08 Connecting to fluph.zapto.org port 24555
Feb 29 20:20:18 Unable to connect

[snip]

Then the penny dropped, port 24555 ... I still had many nodes set up in their individual settings for

Use SSL/TLS │ Yes

So had to go though and manually set all 100 + echomail nodes to No just to make sure things would work better.

That solved most of the issues to get polling working again.

So that got me wondering about a use case whereby the echomail node has a domain name with a port appended to it... e.g nodes polling the fsxNet 1/100 HUB will be polling agency.bbs.nz:24556 or an echomail node that I poll here at 1/100 which is 21:2/1202 which uses 24557 in the BinkP hostname settings

So I did a MIS POLL 21:2/1202 with SSL/TLS to No

[snip]

--------------------- POLL v1.12 A46 2020/02/29 Sat, Feb 29 2020 (loglevel 2) + 2020.02.29 21:45:06 Poll BINKP node via address lookup: 21:2/1202
+ 2020.02.29 21:45:06 1-Polling 21:2/1202 on slot 1 via BINKP
+ 2020.02.29 21:45:06 1-Connecting to error404bbs.ddns.net on port 24557
+ 2020.02.29 21:45:07 1-Connected by IPV4 to 71.74.66.9
+ 2020.02.29 21:45:07 1-System Error 1202 BBS !
+ 2020.02.29 21:45:07 1-SysOp Solaris
+ 2020.02.29 21:45:07 1-Info TIME Sat, 29 Feb 2020 03:44:51 -0500
+ 2020.02.29 21:45:07 1-Mailer Mystic/1.12A46 binkp/1.0
+ 2020.02.29 21:45:07 1-Info BUILD 2020/02/27 15:54:27 Windows/64
+ 2020.02.29 21:45:08 1-Remote Queue: 0 files 0 bytes
+ 2020.02.29 21:45:08 1-Session ended (0 sent, 0 rcvd, 0 skip)
+ 2020.02.29 21:45:08 Polled 1 systems

[snip]

So far all good, then set SSL/TLS to Yes for this node, and it looks like it allowed the port defined in the BinkP Hostname to take precedence which is
good I think else you might never reach the node.

[snip]

--------------------- POLL v1.12 A46 2020/02/29 Sat, Feb 29 2020 (loglevel 2) + 2020.02.29 21:48:56 Poll BINKP node via address lookup: 21:2/1202
+ 2020.02.29 21:48:56 1-Polling 21:2/1202 on slot 1 via BINKP
+ 2020.02.29 21:48:56 1-Connecting to error404bbs.ddns.net on port 24557
+ 2020.02.29 21:48:56 1-Connected by IPV4 to 71.74.66.9
+ 2020.02.29 21:48:57 1-System Error 1202 BBS !
+ 2020.02.29 21:48:57 1-SysOp Solaris
+ 2020.02.29 21:48:57 1-Info TIME Sat, 29 Feb 2020 03:48:41 -0500
+ 2020.02.29 21:48:57 1-Mailer Mystic/1.12A46 binkp/1.0
+ 2020.02.29 21:48:57 1-Info BUILD 2020/02/27 15:54:27 Windows/64
+ 2020.02.29 21:48:58 1-Remote Queue: 0 files 0 bytes
+ 2020.02.29 21:48:58 1-Session ended (0 sent, 0 rcvd, 0 skip)
+ 2020.02.29 21:48:58 Polled 1 systems

[snip]

Then I removed the additional port info from the BinkP Hostname and left SSL/TLS still set to Yes and saw that MIS POLL 21:2/1202 was now trying to reach the node using port 24555

--------------------- POLL v1.12 A46 2020/02/29 Sat, Feb 29 2020 (loglevel 2) + 2020.02.29 21:51:19 Poll BINKP node via address lookup: 21:2/1202
+ 2020.02.29 21:51:19 1-Polling 21:2/1202 on slot 1 via BINKP
+ 2020.02.29 21:51:19 1-Connecting to error404bbs.ddns.net on port 24555
+ 2020.02.29 21:51:50 1-Unable to connect
+ 2020.02.29 21:51:50 Polled 1 systems

[snip]

All of which raises a few questions for me.

1) If I wanted to poll the node using SSL/TLS on a port that was not 24555
how can I direct Mystic to do so?

2) Because I have a port stated in BinkP Hostname when I have SSL/TLS set to Yes is MIS POLL SEND just going to try and run a SSL session over that port? (in my example it would be trying 24557) ... I'm picking this is a No as I
was able to get a connection to 24557 with SSL/TLS set to Yes but there's nothing setup at that node for SSL/TLS and there's nothing in the poll.txt logging to show anything like that was happening :)

Suggestions:


1) In the poll.txt and in the output of MIS POLL if a SSL/TLS session is being attempted can this be flagged by text/colour to show such a thing? At present
I see..

┌─ Status ─────────────────────────────────────────────────────
│ 21:51:19 Poll BINKP node via address lookup: 21:2/1202
│ 21:51:19 1-Polling 21:2/1202 on slot 1 via BINKP
│ 21:51:19 1-Connecting to error404bbs.ddns.net on port 24555
│ 21:51:50 1-Unable to connect
│ 21:51:50 Polled 1 systems

But think something to say this was an attempted SSL/TLS connection prior to line 3 or on line 3 may be a good move.

2)

If I understand this correct

[snip]

+ Mystic's BINKP server now has an "SSL Port" option which when set to a
non-zero value will also run the BINKP server in direct SSL mode.

[snip]

This is where I could set a SSL port for the 1/100 HUB to be say 24558 and
it's this port that nodes (if they set their Use SSL/TLS = Yes in their echomail node settings for 1/100) would be trying to poll. Right?

But at the moment I don't think they could reach it as I'm fairly sure
there's nowhere to define this port.

I confess it's got me wondering if I should shift Agency BBS off BinkP port 24555 and move it's BinkP server to a higher port just to ensure if nodes do try to reach the port I can at least have 1/100 on it waiting to answer.

3) If the shell line is something like MIS POLL 21:1/200 | MIS POLL 21:2/100 | MIS POLL 21:3/100 etc.

Do you think you could enable some variable to be passed to MIS POLL that
would allow me pass it text file containing the nodes I wanted to POLL? This would shorten the length of the entires typed in the Shell line for starters and perhaps make it much easier for folks to set up some rather cool polling options for nodes they wanted.

Lets assume I have a text file in my data directory called fsxhubs.txt

Inside it you see

21:2/100
21:3/100
21:4/100
21:5/100

And in my Event shell line I have

MIS POLL -T fsxhubs.txt

That would be rather clean / nice :)

Or perhaps there could be some regex or wildcard sort of syntax I could place in the text file for example

21:?/100

Might be all that would be needed to poll all defined echomail nodes in
any Net with Zone of 21 and Node of 100

Just an idea that came to mind :)


Couple of last questions

[snip]

+ Mystic's BINKP server now allows the "Port" option to be set to 0 to
disable non-SSL connections when used in combination with the SSL Port
option, so that Mystic will only accept SSL BINKP connections.

[snip]

Is there a message that MIS will send systems that attempt to connect but cannot because MIS is set to only accept SSL BINKP connections? If not
perhaps a hard coded thing could be added?


▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀ Server BINKP ▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀

Active │ Yes Force CRAM-MD5 │ No
ID │ BINKP Allow UnSecure │ Yes
Adapter Type │ IPV4+IPV6 File Conflicts │ Rename
IPV4 Adapter │ 0.0.0.0 Allow SSL/TLS │ No
IPV6 Adapter │ ::

In the server view what does the Allow SSL/TLS option now do?

If a SSL port is defined does that just enable SSL/TLS or does the Allow SSL/TLS need to be set to Yes also? And does 'Forced' have any relevance now?

Sorry lots of questions and thoughts :)

I'll zip up some logs in the next 12 hours and send them to you so you can
see what the HUB has been up to under the new build.

Best, Paul

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

On 29 Feb 2020 at 10:20p, Avon pondered and said...

I'll zip up some logs in the next 12 hours and send them to you so you
can see what the HUB has been up to under the new build.

I figured I'd send you what I have now before I hit the sack..

look for net1-hub-logs.zip and inside you will find a sub dir called 'first tests' which contain the logging after I first started up the new system and noted those issues I wrote about when outbound polling was mysteriously
failing as many echomail nodes still had their SSL/TLS settings set to Yes.

Hope this helps, makes for interesting reading.

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

So... interesting start for 1/100 I was noticing a number of nodes that were failing during a poll session after MUTIL has processed incoming echomail.

Use SSL/TLS │ Yes

So had to go though and manually set all 100 + echomail nodes to No just to make sure things would work better.

Yes, this unfortunately is an artifact of not having step-up SSL like we used to have, so it can't decide on the fly if SSL is going to be used or not. If you have SSL = Yes, then it better be an SSL BINKP server on the other end or it won't work.

So that got me wondering about a use case whereby the echomail node has a domain name with a port appended to it... e.g nodes polling the fsxNet

The port is always the port. If you say the port is 12345 it will always use that port regardless of the SSL setting.

So far all good, then set SSL/TLS to Yes for this node, and it looks
like it allowed the port defined in the BinkP Hostname to take
precedence which is good I think else you might never reach the node.

Correct. You define the port. If you don't then Mystic will impose reasonable default ports. In other words if you just type a hostname and do not tell it what port to use, then by default:

BINKP = Port 24554
BINKP SSL = Port 24555

(There is no default SSL port for BINKP that I know of so I made one up)

1) If I wanted to poll the node using SSL/TLS on a port that was not
24555 how can I direct Mystic to do so?

Configure it as "hostname:port" and set Use SSL/TLS to Yes

2) Because I have a port stated in BinkP Hostname when I have SSL/TLS
set to Yes is MIS POLL SEND just going to try and run a SSL session over that port?

Yes.

Its not nearly as seamless as Mystic's old opportunistic SSL since that could just decide for you the best option and only needed one port. But it will
have to do for now since that is how BINKD tunnels it and how Synchronet does it.

--- Mystic BBS v1.12 A46 2020/02/29 (Windows/64)
* Origin: Sector 7 (21:1/108)

On Sat, 29 Feb 2020 16:50:17 +0700
"g00r00 -> Avon" <0@108.1.21> wrote:

So far all good, then set SSL/TLS to Yes for this node, and it
looks like it allowed the port defined in the BinkP Hostname to
take precedence which is good I think else you might never
reach the node.

Correct. You define the port. If you don't then Mystic will impose reasonable default ports. In other words if you just type a hostname
and do not tell it what port to use, then by default:

BINKP = Port 24554
BINKP SSL = Port 24555

(There is no default SSL port for BINKP that I know of so I made one
up)

There was some agreement on port 24553 and it seems that is what most people use. Someone already filed an application
to get 24553 in IANA's service an port registration database. I don't know if it will get accepted.

---
* Origin: (21:1/151)

There was some agreement on port 24553 and it seems that is what most people use. Someone already filed an application
to get 24553 in IANA's service an port registration database. I don't
know if it will get accepted.

Thank you, I have updated the default to 24553 here too.

--- Mystic BBS v1.12 A46 2020/02/29 (Windows/64)
* Origin: Sector 7 (21:1/108)

On Sat, 29 Feb 2020 19:10:27 +0700
"g00r00 -> Oli" <0@108.1.21> wrote:

There was some agreement on port 24553 and it seems that is
what most people use. Someone already filed an application
to get 24553 in IANA's service an port registration database. I
don't know if it will get accepted.

Thank you, I have updated the default to 24553 here too.

:)

Looks like the request has already been rejected:

Ticket Number Queue Created Status
V1158485 IANA-Ports 2019-12-14 20:37:13 GMT Rejected

https://tools.iana.org/public-view/viewticket/1158485

Anyway, port 24553 is still unassigned / free and is not used by any node in the Fidonet and fsxnet nodelist (for non-TLS connections).

---
* Origin: REPLY (21:1/151)

Looks like the request has already been rejected:

Ticket Number Queue Created Status
V1158485 IANA-Ports 2019-12-14 20:37:13 GMT Rejected

Thats too bad! Maybe the link explains it (I didn't look yet) but I wonder what the criteria is for approval? I would assume its just not widely used enough?

Anyway, port 24553 is still unassigned / free and is not used by any
node in the Fidonet and fsxnet nodelist (for non-TLS connections).

Seems like a good candidate so I will keep it at 24553 in Mystic as well.

--- Mystic BBS v1.12 A46 2020/02/29 (Windows/64)
* Origin: Sector 7 (21:1/108)

On 29 Feb 2020 at 04:50p, g00r00 pondered and said...

1) If I wanted to poll the node using SSL/TLS on a port that was not 24555 how can I direct Mystic to do so?

Configure it as "hostname:port" and set Use SSL/TLS to Yes

2) Because I have a port stated in BinkP Hostname when I have SSL/TLS set to Yes is MIS POLL SEND just going to try and run a SSL session o that port?

Yes.

So nodes polling the 1/100 HUB (for example) are then going to be trying to connect on port 24556 for SSH if they have SSL/TLS set to Yes - right?

How can the HUB offer SSL and non SSL connections on the same port to nodes polling it? I suspect it cant?

... and yet by default NET 1 nodes in fsxNet are all going to have their BinkP Hostname set for agency.bbs.nz:24556 to reach the current server they connect with.

I'm just trying to figure out how best to work this from a HUB and node point of view :)

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

So nodes polling the 1/100 HUB (for example) are then going to be trying to connect on port 24556 for SSH if they have SSL/TLS set to Yes - right?

If you want to open your server up for BINKP SSL then go into the Server configuration for BINKP and set the SSL port to 24553. When you start the BINKP server up next it will listen on that port for SSL connections.

I have changed the default port in Mystic POLL for SSL to be 24553 based on Oli's feedback (instead of 24555). Its up to you whether you want to use them.

If a node wants to switch to SSL they will need to turn on SSL in their echomail node for you and if they don't already have the port configured to something else, it will default to 24553 as of the next build that I will release today ish. Otherwise if you use a different SSL port they'll have to put that port in the hostname.

How can the HUB offer SSL and non SSL connections on the same port to nodes polling it? I suspect it cant?

You can't unfortunately. You COULD before we removed opportunistic SSL.

This is why the opportunistic SSL approach that Mystic did previously was better because it can do SSL over the default BINKP port and fallback to non-SSL when the client can't do SSL - all transparent to existing systems/configurations. The nodelist also has no way to specify a node as SSL to my knowledge which means there is no real clean way to do SSL at the moment unless its opportunistic.

Implementing BINKP SSL the way everyone else (and now Mystic) is doing it is a mistake. (imo of course).

... and yet by default NET 1 nodes in fsxNet are all going to have their BinkP Hostname set for agency.bbs.nz:24556 to reach the current server they connect with.

I'm just trying to figure out how best to work this from a HUB and node point of view :)

Each configuration will have to choose SSL or not and configure their echonode entry for you to point to the proper port based on that decision.

--- Mystic BBS v1.12 A46 2020/02/29 (Windows/64)
* Origin: Sector 7 (21:1/108)

On 01 Mar 2020 at 08:27a, g00r00 pondered and said...

Each configuration will have to choose SSL or not and configure their echonode entry for you to point to the proper port based on that
decision.

OK thanks for the info. I am pondering shifting 1/100 to accept 24554 and
24553 as it's ports for std and SSL respectively. But to do so will require some rejigger at this end as I have other services I will need to shift
namely a Fido HUB :)

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

Re: Re: MIS POLL
By: g00r00 to Avon on Sat Feb 29 2020 04:50 pm

Its not nearly as seamless as Mystic's old opportunistic SSL since that could just decide for you the best option and only needed one port. But it will
have to do for now since that is how BINKD tunnels it and how Synchronet does it.

I would have happily implemented support for Opportunistic TLS for BinkP in BinkIT, but I've never seen a spec for it (FTSC or otherwise).

digital man

This Is Spinal Tap quote #34:
We'd love to stand around and chat, but we've gotta sit down in the lobby Norco, CA WX: 61.6°F, 20.0% humidity, 6 mph SW wind, 0.00 inches rain/24hrs
--- SBBSecho 3.10-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (21:1/183)

I noticed that my events are not running, specifically for the ./mis poll events. I looked at the logs and the last time they ran was 11/7. I manually ran ./mis poll forced today (11/10) to get it to update.

any ideas?π

--- Mystic BBS v1.12 A47 2020/10/23 (Raspberry Pi/32)
* Origin: Pweck's Retreat BBS (21:3/113)

On 10 Nov 2020, pweck said the following...

I noticed that my events are not running, specifically for the ./mis poll events. I looked at the logs and the last time they ran was 11/7. I manuallyran ./mis poll forced today (11/10) to get it to update.

any ideas?π

I have trouble running any events using Mystic to schedule them. I've since scheduled all my events in chrontab (fcrontab is what I use). Works fine that way.

-=- Gary aka HSM -=-
-=Mystic.BBSGameTime.com=-

--- Mystic BBS v1.12 A47 2020/10/20 (Linux/64)
* Origin: BBS GameTime - mystic.BBSGameTime.com:23 (21:2/162)

On 10 Nov 2020, pweck said the following...

I noticed that my events are not running, specifically for the ./mis poll events. I looked at the logs and the last time they ran was 11/7. I manuallyran ./mis poll forced today (11/10) to get it to update.

I had to change the events to include the full path:

e.g:
/home/pi/mystic/mis poll forced

Then it seemed to work for me.

Jay

... What do you call a dinosaur with one eye? A do-you-think-he-saur-us.

--- Mystic BBS v1.12 A47 2020/10/23 (Raspberry Pi/32)
* Origin: Northern Realms (21:3/110)

On 10 Nov 2020 at 01:49p, pweck pondered and said...

I noticed that my events are not running, specifically for the ./mis poll

do you run something like

./mis poll 21:1/100

if it's just ./mis poll then that's not enough.

events. I looked at the logs and the last time they ran was 11/7. I manually ran ./mis poll forced today (11/10) to get it to update.

the fact that this line ran OK makes me wonder if you had not specified a
node to poll?

I usually set up events to poll a HUB from Agency BBS and just put the HUB address in the line e.g. ./mis poll 21:1/100

I tend to stay clear of the 'forced' switch as I like the idea of more
granular control over which echomail node(s) I want to poll and when.

Using 'forced' will force a poll to all echomail nodes regardless of if there is mail at your end to send etc. or not.

--- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

On 10 Nov 2020 at 03:21p, HSM pondered and said...

I have trouble running any events using Mystic to schedule them. I've since scheduled all my events in chrontab (fcrontab is what I use).
Works fine that way.
--- Mystic BBS v1.12 A47 2020/10/20 (Linux/64)

It's probably a pathing issue often using ./mis poll [address] works well for me... the error code mystic returns will also help you debug if ever
interested in looking into it again :) The result code should be 0 if it's
127 or similar then it's more likely the path issue I refer to.

--- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

Re: MIS POLL
By: pweck to All on Tue Nov 10 2020 01:49 pm

I noticed that my events are not running, specifically for the ./mis poll events. I looked at the logs and the last time they ran was 11/7. I manually ran ./mis poll forced today (11/10) to get it to update.

I noticed that too a version or three ago.

It looks like you are running the prealpha so I'd recommend updating to the latest prealpha release and see if that makes a difference.

Ttyl :-),
Al

... When I am right nobody remembers - When I am wrong nobody forgets!
--- SBBSecho 3.11-Linux
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106.1)

do you run something like
./mis poll 21:1/100

if it's just ./mis poll then that's not enough.

Is this a fact? I believe I only run ./mis poll... I haven't NOTICED not getting any network activity - but....

What should I change it to? ./mis forced??

Ugh - I wanna make sure I'm getting everything.
Seems to work under Linun @ ./mis poll...



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

--- Mystic BBS v1.12 A47 2020/10/23 (Raspberry Pi/32)
* Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (21:2/150)

Re: Re: MIS POLL
By: paulie420 to Avon on Tue Nov 10 2020 05:23 pm

Is this a fact? I believe I only run ./mis poll... I haven't NOTICED not getting any network activity - but....

What should I change it to? ./mis forced??

I use ./mis poll send

That will send out whatever is waiting in the outbound.

Ttyl :-),
Al

... I couldn't repair the brakes.. So I made your horn louder!
--- SBBSecho 3.11-Linux
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106.1)

I noticed that my events are not running, specifically for the ./mis events. I looked at the logs and the last time they ran was 11/7. I manuallyran ./mis poll forced today (11/10) to get it to update.

I had to change the events to include the full path:

e.g:
/home/pi/mystic/mis poll forced

Then it seemed to work for me.

Thanks for the suggestion. As I am running *nix it would be ./home/pi/mystic/mis poll forced
correct?

--- Mystic BBS v1.12 A47 2020/10/23 (Raspberry Pi/32)
* Origin: Pweck's Retreat BBS (21:3/113)

I noticed that my events are not running, specifically for the ./mis

do you run something like

./mis poll 21:1/100

Yes. That is how it is in events and tested command line as well.Since I forced it on a command line this afternoon, it did not run. As well it seems I had to run ./mutil mailin too....

Av> if it's just ./mis poll then

that's not enough. Av>

events. I looked at the logs and the last time they ran was 11/7. I manually ran ./mis poll forced today (11/10) to get it to update.

the fact that this line ran OK makes me wonder if you had not specified a node to poll?

--- Mystic BBS v1.12 A47 2020/10/23 (Raspberry Pi/32)
* Origin: Pweck's Retreat BBS (21:3/113)

It's probably a pathing issue often using ./mis poll [address] works
well forme... the error code mystic returns will also help you debug if everinterested in looking into it again :) The result code should be 0
if it's127 or similar then it's more likely the path issue I refer to.

Where would I see the error code? Thanks

--- Mystic BBS v1.12 A47 2020/10/23 (Raspberry Pi/32)
* Origin: Pweck's Retreat BBS (21:3/113)

I noticed that my events are not running, specifically for the ./mis events. I looked at the logs and the last time they ran was 11/7. I manuallyran ./mis poll forced today (11/10) to get it to update.

any ideas?π

I have trouble running any events using Mystic to schedule them. I've sincescheduled all my events in chrontab (fcrontab is what I use).
Works fine thatway.

Ya my .nix skills are lacking so far to do that. More reading...lol

--- Mystic BBS v1.12 A47 2020/10/23 (Raspberry Pi/32)
* Origin: Pweck's Retreat BBS (21:3/113)

I noticed that too a version or three ago.

It looks like you are running the prealpha so I'd recommend updating to thelatest prealpha release and see if that makes a difference.

thanks, yes i have the latest release. maybe i need to re-install...ugh

--- Mystic BBS v1.12 A47 2020/10/23 (Raspberry Pi/32)
* Origin: Pweck's Retreat BBS (21:3/113)

Re: Re: MIS POLL
By: pweck to Al on Tue Nov 10 2020 10:54 pm

thanks, yes i have the latest release. maybe i need to re-install...ugh

Yeah, in the case of the prealphas it's a good idea to keep up to date with what g00r00 is up to. I see there is a newer one (11/06) that I have to catch up with too.

Ttyl :-),
Al

... You can name your salary here, I call mine fred.
--- SBBSecho 3.11-Linux
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106.1)

On 10 Nov 2020 at 05:23p, paulie420 pondered and said...

do you run something like
./mis poll 21:1/100

if it's just ./mis poll then that's not enough.

Is this a fact? I believe I only run ./mis poll... I haven't NOTICED not getting any network activity - but....

I'm running the current public release, if you type mis poll you get

POLL SEND - Only send/poll if node has new outbound messages
POLL FORCED [Type] - Poll/send to all nodes of session [Type] (Blank/All)
POLL [Address] - Poll/send echomail node [Address] (ex: 46:1/100)

So I suggest use the last option in your shell line and plug in an address to poll.

--- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

On 10 Nov 2020 at 07:49p, Al pondered and said...

I use ./mis poll send

That will send out whatever is waiting in the outbound.

This is the shell line I use when running mailout.ini

--- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

On 10 Nov 2020 at 09:28p, pweck pondered and said...

./mis poll 21:1/100

Yes. That is how it is in events and tested command line as
well.Since I forced it on a command line this afternoon, it did not
run. As well it seems I had to run ./mutil mailin too....

So ./mis poll 21:1/100 from the command line did not poll the node?

--- Mystic BBS v1.12 A47 2020/10/23 (Raspberry Pi/32)
* Origin: Pweck's Retreat BBS (21:3/113)

Have you compiled your nodelist?

--- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

On 10 Nov 2020 at 09:46p, Al pondered and said...

Yeah, in the case of the prealphas it's a good idea to keep up to date with what g00r00 is up to. I see there is a newer one (11/06) that I
have to catch up with too.

:) Have fun with that.

--- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

Re: Re: MIS POLL
By: Avon to Al on Wed Nov 11 2020 07:14 pm

Yeah, in the case of the prealphas it's a good idea to keep up to
date with what g00r00 is up to. I see there is a newer one (11/06)
that I have to catch up with too.

:) Have fun with that.

It's actually quite mellow these days.. one or two updates a week. I remember a time when there was one or two a day!

Ttyl :-),
Al

... Help! I've fallen and can't reach my beer!
--- SBBSecho 3.11-Linux
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106.1)

On 10 Nov 2020 at 10:36p, Al pondered and said...

It's actually quite mellow these days.. one or two updates a week. I remember a time when there was one or two a day!

Great software, does cool things. That said, after the events of the year the fun of it has rather left the building for me. I just don't get as in to it as much as I once did because of this. Nuff said.

--- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

On 10 Nov 2020, pweck said the following...

Thanks for the suggestion. As I am running *nix it would be ./home/pi/mystic/mis poll forced
correct?

No, you only include the period if you're executing from the current
directory.

So if mis was located in /home/pi/mystic you could execute it with ./mis provided you were in that directory. Or from anywhere else you provide the full path /home/pi/mystic/mis

I'm running on a Raspberry Pi, here is how I have my two events setup:

Active │ Yes
Description │ Toss incoming echomail
Event Type │ Semaphore
Exec Hour │ 0
Exec Min │ 0
Shell │ /home/pi/mystic/mutil mailin.ini
Semaphore │ echomail.in|netmail.in
Kill After │ echomail.in|netmail.in


Active │ Yes
Description │ Poll echomail
Event Type │ Interval
Exec Hour │ 1
Exec Min │ 0
Shell │ /home/pi/mystic/mis poll forced|/home/pi/mystic/mutil mailin.ini
Semaphore │
Kill After │

Hope this helps.

Jay

... The male pig puts everyone to sleep. You might say he's quite a boar.

--- Mystic BBS v1.12 A47 2020/10/23 (Raspberry Pi/32)
* Origin: Northern Realms (21:3/110)

Yes. That is how it is in events and tested command line as well.Since I forced it on a command line this afternoon, it did not run. As well it seems I had to run ./mutil mailin too....

So ./mis poll 21:1/100 from the command line did not poll the node?

yes it works when I manually run it from a command prompt. automated seems hit and miss

Have you compiled your nodelist?

i have an event that compiles it daily (merge_node.ini) but looking at logs, it has not been running...<sigh>

--- Mystic BBS v1.12 A47 2020/10/23 (Raspberry Pi/32)
* Origin: Pweck's Retreat BBS (21:3/113)

Yeah, in the case of the prealphas it's a good idea to keep up to dat with what g00r00 is up to. I see there is a newer one (11/06) that I have to catch up with too.

thanks, yes it appears I am behind now too...

--- Mystic BBS v1.12 A47 2020/10/23 (Raspberry Pi/32)
* Origin: Pweck's Retreat BBS (21:3/113)

./home/pi/mystic/mis poll forced
correct?

No, you only include the period if you're executing from the current directory.

Thanks for clarification. So it looks like mystic is in /mystic, not /home/pi/mystic... is this a problem?

Wa>

So if mis was located in /home/pi/mystic you could execute it with ./mis provided you were in that directory. Or from anywhere else you provide thefull path /home/pi/mystic/mis

thanks, I will remove the period and try again

I'm running on a Raspberry Pi, here is how I have my two events setup:

Active │ Yes
Description │ Toss incoming echomail
Event Type │ Semaphore
Exec Hour │ 0
Exec Min │ 0
Shell │ /home/pi/mystic/mutil mailin.ini
Semaphore │ echomail.in|netmail.in
Kill After │ echomail.in|netmail.in

Active │ Yes
Description │ Poll echomail
Event Type │ Interval
Exec Hour │ 1
Exec Min │ 0
Shell │ /home/pi/mystic/mis poll forced|/home/pi/mystic/mutil mailin.ini Semaphore │
Kill After │

Thank you!

--- Mystic BBS v1.12 A47 2020/10/23 (Raspberry Pi/32)
* Origin: Pweck's Retreat BBS (21:3/113)

Thanks for clarification. So it looks like mystic is in /mystic, not /home/pi/mystic... is this a problem?

Not a problem, you just need to spell out the absolute path like

"/mystic/mis poll force" or whatever the syntax is.

--- Mystic BBS v1.12 A46 2020/08/06 (Linux/64)
* Origin: monterey bbs (21:1/168)

On 11 Nov 2020, pweck said the following...

Thanks for clarification. So it looks like mystic is in /mystic, not /home/pi/mystic... is this a problem?

Yup, if you have mystic installed in /mystic, you'd just update the full path to be /mystic/mis poll forced or /mystic/mis poll send, whatever the case may be.

Jay

... I'm positive I just lost an electron. Better keep an ion that.

--- Mystic BBS v1.12 A47 2020/10/23 (Raspberry Pi/32)
* Origin: Northern Realms (21:3/110)

Thanks for clarification. So it looks like mystic is in /mystic, not /home/pi/mystic... is this a problem?

Yup, if you have mystic installed in /mystic, you'd just update the full pathto be /mystic/mis poll forced or /mystic/mis poll send, whatever the case maybe.

Thanks I figured. Ok, will try and see if it solves the problems..

--- Mystic BBS v1.12 A47 2020/10/23 (Raspberry Pi/32)
* Origin: Pweck's Retreat BBS (21:3/113)

Is this a fact? I believe I only run ./mis poll... I haven't NOTICED getting any network activity - but....

I use ./mis poll send
That will send out whatever is waiting in the outbound.
Ttyl :-),
Al

You know, when I posted this it was more for the wondery of if I needed full paths or not; I actually do run ./mis send, too... and ./mis poll for another event...

If I were a betting man, I think I'd say that under Linux, you can still just call it with ./ ... that is basically 'a full path' as long as mis runs in /mystic...

I think for the Windows users maybe they are the ones that need to modify the commands when upgrading to a47... (With full pathnames; I know we all have to modify to mis...)



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

--- Mystic BBS v1.12 A47 2020/10/23 (Raspberry Pi/32)
* Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (21:2/150)

Thanks for the suggestion. As I am running *nix it would be ./home/pi/mystic/mis poll forced

/home/pi/mystic/./mis poll



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

--- Mystic BBS v1.12 A47 2020/10/23 (Raspberry Pi/32)
* Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (21:2/150)

On 10 Nov 2020, pweck said the following...

It's probably a pathing issue often using ./mis poll [address] works well forme... the error code mystic returns will also help you debug everinterested in looking into it again :) The result code should be if it's127 or similar then it's more likely the path issue I refer to

Where would I see the error code? Thanks

In your mis WFC screen, go to events and if theres a '0' next to them there was no errors on the last run.



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

--- Mystic BBS v1.12 A47 2020/10/23 (Raspberry Pi/32)
* Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (21:2/150)

Re: Re: MIS POLL
By: pweck to Al on Tue Nov 10 2020 10:54 pm

thanks, yes i have the latest release. maybe i need to re-install...u

Yeah, in the case of the prealphas it's a good idea to keep up to date withwhat g00r00 is up to. I see there is a newer one (11/06) that I have to catchup with too.

Ttyl :-),
Al

Hey Al, thanks for posting this... I upgraded to a47 - are you stating that he continues to modify the a47 prealpha and a sysOp would be best served by updating the update every couple week?

I'm familiar with how Synchronet does it - and you just pull the github and get a newer build... but I was under the impression that I just upgrade to a47 and thats THE prealpha release.

Are you stating that he continues to modify that a47 build and I should check back to make sure I'm on the newest date??



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

--- Mystic BBS v1.12 A47 2020/10/23 (Raspberry Pi/32)
* Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (21:2/150)

I'm running the current public release, if you type mis poll you get

POLL SEND - Only send/poll if node has new outbound messages POLL FORCED [Type] - Poll/send to all nodes of session [Type] (Blank/All)POLL [Address] - Poll/send echomail node [Address] (ex: 46:1/100)

So I suggest use the last option in your shell line and plug in an
address topoll.

Ok - I'm running the most current release too - am I correct in thinking that I should use my hub, as that address ... to poll?



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

--- Mystic BBS v1.12 A47 2020/10/23 (Raspberry Pi/32)
* Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (21:2/150)

Have you compiled your nodelist?

Sorry for all the questions - but, is 'compiling your nodelist' running my mergenodelist.ini ??

I always add the newest nodelists to my /mystic/nodelists directory... and I run ./mutil mergonodelists.ini - which... merges all those nodelists. Are my nodelists 'compiled'???



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

--- Mystic BBS v1.12 A47 2020/10/23 (Raspberry Pi/32)
* Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (21:2/150)

Great software, does cool things. That said, after the events of the
year thefun of it has rather left the building for me. I just don't get
as in to it asmuch as I once did because of this. Nuff said.

Not starting any drama or debate; but this statement, by you, is really a downer for... me. Just hope that you know that PLENTY of folks in this BBS community both appreciate, count on and know what YOU do for this scene.

I can understand the reasoning, and wish that you received the appreciation that you so duly DESERVE.

I'd be much happier to hear that you love this hobby and all the moving parts within it- I've probably already said too much.. we appreciate YOU.



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

--- Mystic BBS v1.12 A47 2020/10/23 (Raspberry Pi/32)
* Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (21:2/150)

I'm running on a Raspberry Pi, here is how I have my two events setup:

Active │ Yes
Description │ Toss incoming echomail
Event Type │ Semaphore
Exec Hour │ 0
Exec Min │ 0
Shell │ /home/pi/mystic/mutil mailin.ini
Semaphore │ echomail.in|netmail.in
Kill After │ echomail.in|netmail.in

Active │ Yes
Description │ Poll echomail
Event Type │ Interval
Exec Hour │ 1
Exec Min │ 0
Shell │ /home/pi/mystic/mis poll forced|/home/pi/mystic/mutil mailin.ini Semaphore │
Kill After │

Hope this helps.

Jeez - people are posting such good information over the past day. Can I ask you, what are the 'semaphore' and 'kill after' lines? Mine are null, and ... while my setup works, I'd like to understand exactly whats going on or whats possible...

I don't have semaphore or kill after set to anything; should I?



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

--- Mystic BBS v1.12 A47 2020/10/23 (Raspberry Pi/32)
* Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (21:2/150)

Thanks for clarification. So it looks like mystic is in /mystic, not /home/pi/mystic... is this a problem?

Not a problem, you just need to spell out the absolute path like

"/mystic/mis poll force" or whatever the syntax is.

"/mystic/./mis poll force"

the "./" always goes right before the command you are running; in standard linux, ubuntu, whatever flavor...

just like when yer IN /mystic and you type "./mystic -cfg" to load up the config...

you always type "./" before the command you want to run..

~/mystic/./mplc myfile.mps

or whatever..



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

--- Mystic BBS v1.12 A47 2020/10/23 (Raspberry Pi/32)
* Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (21:2/150)

Re: Re: MIS POLL
By: paulie420 to Al on Wed Nov 11 2020 05:57 pm

You know, when I posted this it was more for the wondery of if I needed full paths or not; I actually do run ./mis send, too... and ./mis poll for another event...

WHen I first started using linux this all caused me lots of wonder too.. :)

./ means current directory. Linux never looks for binary files to run in your current directory the way other OSs do, it only looks in the path. That's why you always need to add the ./ if you want to run a binary in your current directory.

"./mis poll send" will send any mail in your outbound but will do nothing if there is nothing to go.

"./mis poll 21:1/100" will poll 21:1/100 even if the outbound is empty.

If I were a betting man, I think I'd say that under Linux, you can still just call it with ./ ... that is basically 'a full path' as long as mis runs in /mystic...

Only if the file you want to run is in your current directory.

It doesn't hurt to use a full path either, /mystic/mis poll send" or whatever the path is.

I think for the Windows users maybe they are the ones that need to modify the commands when upgrading to a47... (With full pathnames; I know we all have to modify to mis...)

On Windows, DOS and OS/2 the ./ isn't needed because those OSs will run a command in your current directory before looking in the path.

Ttyl :-),
Al

... Software means never having to say you're finished.
--- SBBSecho 3.11-Linux
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106.1)

Re: Re: MIS POLL
By: paulie420 to Al on Wed Nov 11 2020 06:01 pm

Hey Al, thanks for posting this... I upgraded to a47 - are you stating that he continues to modify the a47 prealpha and a sysOp would be best served by updating the update every couple week?

Yes, Mystic 1.12A46 is released. It's a done deal now. 1.12A47 is still a work in progress and there will likely be many new ones (prealphas) before A47 is released.

Are you stating that he continues to modify that a47 build and I should check back to make sure I'm on the newest date??

Yes, once he has done what he wants to do and tested that things are working according to plan he'll release an A47. At some point he'll release a 1.12 final but that may take a while.

Ttyl :-),
Al

... Proofread carefully to see if you any words out
--- SBBSecho 3.11-Linux
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106.1)

On 11 Nov 2020 at 06:02p, paulie420 pondered and said...

Ok - I'm running the most current release too - am I correct in thinking that I should use my hub, as that address ... to poll?

Yep, and you can also set up multiple selected polls if you wanted to on the one shell line if you wished.

e.g.

mis poll 21:1/100 | mis poll 3:770/1

--- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

On 11 Nov 2020 at 06:04p, paulie420 pondered and said...

Sorry for all the questions - but, is 'compiling your nodelist' running
my mergenodelist.ini ??

sorry for my language, In this case yes that's what I am referring to.

I always add the newest nodelists to my /mystic/nodelists directory...
and I run ./mutil mergonodelists.ini - which... merges all those nodelists. Are my nodelists 'compiled'???

You can do this automatically such that your nodefile statement points to the file base directory your nodelist file sits in. Here's my current example at Agency

nodefile=c:\bbs\files\fsx\fsx_node\fsxnet

--- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

On 11 Nov 2020 at 06:08p, paulie420 pondered and said...

I'd be much happier to hear that you love this hobby and all the moving parts within it- I've probably already said too much.. we appreciate YOU.

Thanks for the kind words. I do love this hobby and am not planning on
leaving it anytime soon.

I think for all of us in this crazy world it's been a hell of a year with COVID-19 and other things. When I posted the last post I was feeling a bit
down but honestly I don't know many of us that aren't having a few ups and downs during 2020.

I'll get there. I hope you and yours are safe and well too.

Best, Paul

--- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

You know, when I posted this it was more for the wondery of if I needed fullpaths or not; I actually do run ./mis send, too... and ./mis poll
for anotherevent...

If I were a betting man, I think I'd say that under Linux, you can still justcall it with ./ ... that is basically 'a full path' as long as mis runs in/mystic...

that could be, but until i entered full paths, events were not working...i dunno, it could have been something else, but all works now. however, originally it did run with a problem as ./ ...

--- Mystic BBS v1.12 A47 2020/10/23 (Raspberry Pi/32)
* Origin: Pweck's Retreat BBS (21:3/113)

everinterested in looking into it again :) The result code shoul if it's127 or similar then it's more likely the path issue I ref

Where would I see the error code? Thanks

In your mis WFC screen, go to events and if theres a '0' next to them there wasno errors on the last run.

ok thanks, i'll check that

--- Mystic BBS v1.12 A47 2020/10/23 (Raspberry Pi/32)
* Origin: Pweck's Retreat BBS (21:3/113)

withwhat g00r00 is up to. I see there is a newer one (11/06) that I h to catchup with too.

looks like pi didn't get the most recent update...yet

--- Mystic BBS v1.12 A47 2020/10/23 (Raspberry Pi/32)
* Origin: Pweck's Retreat BBS (21:3/113)

sorry for my language, In this case yes that's what I am referring to.

Yer fine - I thought I understood what you were saying. :P

You can do this automatically such that your nodefile statement points
to thefile base directory your nodelist file sits in. Here's my current example atAgency

nodefile=c:\bbs\files\fsx\fsx_node\fsxnet

Ah ha; lol, I was going to set my fsxNet file base to /mystic/nodelists ... but I get it - I get it... I will set each FTN to the file BASE location and that'll be much cleaner. :P Got it!! :P



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

--- Mystic BBS v1.12 A47 2020/10/23 (Raspberry Pi/32)
* Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (21:2/150)

Yeah, in the case of the prealphas it's a good idea to keep up t withwhat g00r00 is up to. I see there is a newer one (11/06) tha to catchup with too.

looks like pi didn't get the most recent update...yet

Thanks for that; I guess since I went to a47 I need to checkup on these releases. Next time I'm going to stick with the alpha... lol; for a user like me who doesn't want to keep upgrading with every small change, I should stick on the last 'complete' version. In this case a46....?? LOL.

With other github projects, theres just a stable version, that doesn't change. And a bleeding edge, or alpha - that does get updates. :/ Hard to understand, with so many developers and the ways the describe their releases.



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

--- Mystic BBS v1.12 A47 2020/10/23 (Raspberry Pi/32)
* Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (21:2/150)

On 11 Nov 2020, paulie420 said the following...

Just hope that you know that PLENTY of folks in this BBS community both pa> appreciate, count on and know what YOU do for this scene.

I'd be much happier to hear that you love this hobby and all the moving parts within it- I've probably already said too much.. we appreciate YOU.

Couldn't agree with this more. I got back into the BBS scene because of covid (wanted something familiar and that made me feel good).

That's when I discovered Mystic and by extension the Mystic Guy's videos on YouTube. Safe to say I wouldn't be on here without Paul & everything he does for the community.

Jay

... I went to bed with my contact lenses in. My dreams have never been clearer

--- Mystic BBS v1.12 A47 2020/10/23 (Raspberry Pi/32)
* Origin: Northern Realms (21:3/110)

On 11 Nov 2020, paulie420 said the following...

Jeez - people are posting such good information over the past day. Can I ask you, what are the 'semaphore' and 'kill after' lines? Mine are null, and ... while my setup works, I'd like to understand exactly whats going on or whats possible...

A semaphore is a file created in the mystic/semaphore directory. When echomail is received by the bink server Mystic will create an echomail.in file in the semaphore directory. Likewise when you post a message in a message base Mystic will create an echomail.out file.

If you have an event monitor for these semaphores (I believe Mystic checks the directory once a minute) then you can have things run more often, almost in real time.

e.g.

You post a message here in this message base. Mystic creates mystic/semaphore/echomail.out

You have an event looking for echomail.out which runs:
mutil mailout.ini|mis poll send

The kill after line deletes that semaphore so the event won't run continuously.

So the way I have Mystic setup, each time I post a message it's sent out usually within a minute, rather than waiting for an event to run every so often to collect mail and send it out.

Jay

... There was a kidnapping at school yesterday. Don't worry though, he woke up

--- Mystic BBS v1.12 A47 2020/10/23 (Raspberry Pi/32)
* Origin: Northern Realms (21:3/110)

"/mystic/./mis poll force"

This is incorrect. If you use absolute path, you don't put the '.' character
in there. I.e., you just use "/mystic/mis poll force". If you want to run a binary from the current directory you are in, you then put the '.' character, i.e. if your present working directory is /mystic/ already, you just use
"./mis poll force".

the "./" always goes right before the command you are running; in
standard linux, ubuntu, whatever flavor...

Only if you are trying to run a binary in the directory that you are
currently in.

you always type "./" before the command you want to run..

~/mystic/./mplc myfile.mps

Negative. :) _ONLY_ put the '.' if you're trying to run a binary from your current directory.

--- Mystic BBS v1.12 A46 2020/08/06 (Linux/64)
* Origin: monterey bbs (21:1/168)

On 11 Nov 2020, Al said the following...

... Proofread carefully to see if you any words out

I read this fine the first time, but then I saw proofread carefully...

Jay

... Is your iPad making you fall asleep? I can help, there's a nap for that

--- Mystic BBS v1.12 A47 2020/10/23 (Raspberry Pi/32)
* Origin: Northern Realms (21:3/110)

paulie420 wrote to Avon <=-

nodefile=c:\bbs\files\fsx\fsx_node\fsxnet

Ah ha; lol, I was going to set my fsxNet file base to /mystic/nodelists ... but I get it - I get it... I will set each FTN to the file BASE location and that'll be much cleaner. :P Got it!! :P

Just remember it is case sensitive! If the nodelist is in caps, you will need:

nodefile=/home/mystic/fsx/fsx_node/FSXNET

(Yes, I'm speaking from experience on this one... ) ;)


... "Hex Dump" - Where Witches put used Curses?
___ MultiMail/Linux v0.52.1(RCS)

--- Mystic BBS/QWK v1.12 A47 2020/11/06 (Linux/64)
* Origin: Castle Rock BBS - bbs.castlerockbbs.com (21:1/186)

On 12 Nov 2020 at 12:48p, Black Panther pondered and said...

Just remember it is case sensitive! If the nodelist is in caps, you will need:

nodefile=/home/mystic/fsx/fsx_node/FSXNET

I think this is no longer a problem... from memory James did set it to look
for both upper and lower cases when it scanned... mostly due to feedback
about this very niggle in the past :)

--- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

On 13 Nov 2020, 11:21a, Avon said the following...

nodefile=/home/mystic/fsx/fsx_node/FSXNET

I think this is no longer a problem... from memory James did set it to lookfor both upper and lower cases when it scanned... mostly due to feedbackabout this very niggle in the past :)

Ooops. I missed that one. I just verified it is no longer case sensitive. :)


---

Black Panther(RCS)
aka Dan Richter
Castle Rock BBS
telnet://bbs.castlerockbbs.com
http://www.castlerockbbs.com
http://github.com/DRPanther
The sparrows are flying again...

--- Mystic BBS v1.12 A47 2020/11/06 (Linux/64)
* Origin: Castle Rock BBS - bbs.castlerockbbs.com (21:1/186)

I'd be much happier to hear that you love this hobby and all the movi parts within it- I've probably already said too much.. we appreciate

Couldn't agree with this more. I got back into the BBS scene because of covid(wanted something familiar and that made me feel good).

That's when I discovered Mystic and by extension the Mystic Guy's videos onYouTube. Safe to say I wouldn't be on here without Paul & everything he doesfor the community.

Jay

... I went to bed with my contact lenses in. My dreams have never been

LOL - Weird; for some reason I thought you have been around much longer. With a name like warpslide, I guess it makes you instantly uber cool. w00t w00t, daddio!!!



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

--- Mystic BBS v1.12 A47 2020/10/23 (Raspberry Pi/32)
* Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (21:2/150)

A semaphore is a file created in the mystic/semaphore directory. When echomailis received by the bink server Mystic will create an echomail.in file in thesemaphore directory. Likewise when you post a message in a message base Mysticwill create an echomail.out file.

If you have an event monitor for these semaphores (I believe Mystic
checks thedirectory once a minute) then you can have things run more often, almost inreal time.

e.g.

You post a message here in this message base. Mystic creates mystic/semaphore/echomail.out

You have an event looking for echomail.out which runs:
mutil mailout.ini|mis poll send

The kill after line deletes that semaphore so the event won't run continuously.

So the way I have Mystic setup, each time I post a message it's sent out usually within a minute, rather than waiting for an event to run every
so oftento collect mail and send it out.

Jay

Great explanation - copied to my mystic_txt folder.



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

--- Mystic BBS v1.12 A47 2020/10/23 (Raspberry Pi/32)
* Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (21:2/150)

Re: Re: MIS POLL
By: Warpslide to Al on Thu Nov 12 2020 11:59 am

... Proofread carefully to see if you any words out

I read this fine the first time, but then I saw proofread carefully...

Yep, that's a tricky one! ;)

Ttyl :-),
Al

... Put on your seatbelt - I'm gonna try something new!
--- SBBSecho 3.11-Linux
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106.1)

On 12 Nov 2020, paulie420 said the following...

LOL - Weird; for some reason I thought you have been around much longer. With a name like warpslide, I guess it makes you instantly uber cool. pa> w00t w00t, daddio!!!

LOL, well I DID run a Telegard BBS back in the late 90's but I honestly don't remember which handle I used back then. It wasn't until I moved out of my parent's house & got my first DSL connection that I started using Warpslide around 2001.

Jay

... How do you invite a dinosaur for lunch? Tea, Rex?

--- Mystic BBS v1.12 A47 2020/10/23 (Raspberry Pi/32)
* Origin: Northern Realms (21:3/110)