Just a heads up FIDOPOLL is going bye bye probably in A46 or if not then A47 for sure.

Its been swallowed by the massive black hole known as MIS112

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

On 29 Feb 2020 at 12:19a, g00r00 pondered and said...

Just a heads up FIDOPOLL is going bye bye probably in A46 or if not then A47 for sure.

Its been swallowed by the massive black hole known as MIS112

where did it go to?! how will we talk fsxNET... oh <GaSP>!

M@STERMiND

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

Its been swallowed by the massive black hole known as MIS112

where did it go to?! how will we talk fsxNET... oh <GaSP>!

I don't know its a mystery what happens to 1s and 0s once they cross the event horizon of MIS112! I guess we'll just have to see what MIS morphs into afterwards! I'll document any findings in whatsnew.txt!

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

On 02-29-20 00:19, g00r00 wrote to All <=-

Just a heads up FIDOPOLL is going bye bye probably in A46 or if not
then A47 for sure.

Its been swallowed by the massive black hole known as MIS112

How do we manually poll nodes after Fidopoll disappears? Just curious, as I will have scripts to change. :)


... "Did you open the Microwave door before the 'ding'"?
=== MultiMail/Win v0.51
--- SBBSecho 3.10-Linux
* Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (21:1/109)

Its been swallowed by the massive black hole known as MIS112

How do we manually poll nodes after Fidopoll disappears? Just curious,
as I will have scripts to change. :)

Its the same, really. I rewrote it to use the same command lines:

fidopoll forced -> mis poll forced
fidopoll send -> mis poll send
fidopoll 1:123/1234 -> mis poll 1:123/1234

You can still do the session/protocol types too like:

mis poll forced ftp

Other than the everything else about it is pretty much new. It can spawn any number of concurrent send processes. My BBS has been running off of it for a day or two now and I have 6 uplinks, all of which poll instantly as soon as I start it up (completes 6 polls in a few seconds).

The log management is better, the UI is better, etc.

But now that the code is baked into the MIS codebase, it also means that it could in theory be triggered by MIS itself and you wouldn't need any sort of event or anything. Echomail can just flow and Mystic will handle it without any human interaction post initial setup (and Mystic's setup is already very minimal compared to others). No events, batch files, nothing.

I'm not heading in that direction yet and I would likely do it optionally (since I still value Mystic's ability to mix and match itself with a wide range of 3rd party mailers or tossers).

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

On 02-29-20 15:20, g00r00 wrote to Vk3jed <=-\

Its the same, really. I rewrote it to use the same command lines:

fidopoll forced -> mis poll forced
fidopoll send -> mis poll send
fidopoll 1:123/1234 -> mis poll 1:123/1234

You can still do the session/protocol types too like:

mis poll forced ftp

Cool, sounds like an easy change on my end, and with some clever rewriting, I can make the switch even easier. :)

Other than the everything else about it is pretty much new. It can
spawn any number of concurrent send processes. My BBS has been running off of it for a day or two now and I have 6 uplinks, all of which poll instantly as soon as I start it up (completes 6 polls in a few
seconds).

Nice, that's more like binkd. :)

But now that the code is baked into the MIS codebase, it also means
that it could in theory be triggered by MIS itself and you wouldn't
need any sort of event or anything. Echomail can just flow and Mystic will handle it without any human interaction post initial setup (and Mystic's setup is already very minimal compared to others). No events, batch files, nothing.

Could be neat. :)

I'm not heading in that direction yet and I would likely do it
optionally (since I still value Mystic's ability to mix and match
itself with a wide range of 3rd party mailers or tossers).

Probably something to make configurable, because the "mix and match" is a valuable asset of Mystic (even though I'm using Mystic as an all in one package).


... Babehart - a cute little pig that slaughters half of Scotland
=== MultiMail/Win v0.51
--- SBBSecho 3.10-Linux
* Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (21:1/109)

On 29 Feb 2020, g00r00 said the following...

Just a heads up FIDOPOLL is going bye bye probably in A46 or if not then A47 for sure.

Oof. I'll need to set myself a little block of free time for this one. lol

Or maybe not. I thought I had crons and scripts setup and all that stuff, but that must have been my last iteration before catching myself up and letting mystic do all the work. ;)

Accession

--- Mystic BBS v1.12 A46 2020/02/29 (Linux/64)
* Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (21:1/200)

Oof. I'll need to set myself a little block of free time for this one.
lol

Or maybe not. I thought I had crons and scripts setup and all that
stuff, but that must have been my last iteration before catching myself
up and letting mystic do all the work. ;)

Well at least I tried to make the conversion pretty ease it'll be the same commands just "mis poll" instead of "fidopoll". Hopefully it won't bother
too many people.

I plan to keep the original fidopoll in there for a while but initial reports have been very positive so far and the only issue I knew about was a display issue that I cleaned up today! Who knows maybe it will go earlier than expected if this new version proves to be as stable as it seems already.

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

On 29 Feb 2020 at 03:20p, g00r00 pondered and said...

fidopoll 1:123/1234 -> mis poll 1:123/1234

I wonder if there should also be an option to force an IPv4 or IPv6 poll?

I did a test poll to Al just now which used the nodelist lookup to find his details as I don't have him defined as an echomail node.

I have both IPv4 and IPv6 connectivity here and the polling defaulted to an IPv6 outgoing connection

mis poll 21:4/106

┌─ Status
────────────────────────────────────────────────────────────────────┐
│ 21:35:11 Poll BINKP node via address lookup: 21:4/106
│
│ 21:35:11 1-Polling 21:4/106 on slot 1 via BINKP
│
│ 21:35:11 1-Connecting to trmb.ca on port 24554
│
│ 21:35:12 1-Connected by IPV6 to 2600:3C04::F03C:92FF:FE69:8DB0
│
│ 21:35:12 1-System The Rusty MailBox
│
│ 21:35:12 1-SysOp Alan Ianson
│
│ 21:35:12 1-Location Penticton, BC Canada
│
│ 21:35:12 1-Info NDL 115200,CM,XW,IBN
│
│ 21:35:12 1-Info TIME Sun, 1 Mar 2020 00:35:13 -0800
│
│ 21:35:12 1-Mailer binkd/1.1a-101/Linux binkp/1.1
│
│ 21:35:13 1-Info TRF 0 0
│
│ 21:35:13 1-Session ended (0 sent, 0 rcvd, 0 skip)
│
│ 21:35:13 Polled 1 systems
│ └─────────────────────────────────────────────────────────────────────────────┘

perhaps

mis poll [node] -4

mis poll [node] -6

or some setting somewhere in MIS config to enable IPV4+IPV6 etc.. like we
have for servers?

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

I did a test poll to Al just now which used the nodelist lookup to find his details as I don't have him defined as an echomail node.

I have both IPv4 and IPv6 connectivity here and the polling defaulted to an IPv6 outgoing connection

When doing a nodelist lookup it will automatically figure out IP options are available for the remote system. It will default to IPV6 when available for the connection.

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

On 29 Feb 2020, g00r00 said the following...

I plan to keep the original fidopoll in there for a while but initial reports have been very positive so far and the only issue I knew about
was a display issue that I cleaned up today! Who knows maybe it will go earlier than expected if this new version proves to be as stable as it seems already.

Did you mention something about either removing or having less need for the event editor? I'm fairly certain that's about the only place I'd have to
really change these commands.

Accession

--- Mystic BBS v1.12 A46 2020/02/29 (Linux/64)
* Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (21:1/200)