I'm wondering if the address they are connecting to could be the problem
(n3.z21.bbs.dege.au)? Only a guess.
I dont think so, that's what everybody else uses:
$ host n3.z21.bbs.dege.au
n3.z21.bbs.dege.au is an alias for clrghouz.bbs.dege.au. clrghouz.bbs.dege.au is an alias for ip4.bbs.dege.au.
ip4.bbs.dege.au has address 139.99.135.199
Like freq was having issues polling on his Pi, I have another new user with the same issue.
--------------------- POLL v1.12 A48 2023/01/15 Sun, Nov 16 2025 (loglevel 3) + 16.11.2025 20:48:07 Polling all nodes of session type ALL + 16.11.2025 20:48:07 Queued 1 files (896 bytes) for 21:3/100
+ 16.11.2025 20:48:07 1-Polling 21:3/100 on slot 1 via BINKP
+ 16.11.2025 20:48:07 1-DEBUG ConnectMode=0
+ 16.11.2025 20:48:07 1-Connecting to n3.z21.bbs.dege.au on port 24554
I'm wondering if the address they are connecting to could be the problem (n3.z21.bbs.dege.au)? Only a guess.
I also change the address to ip:139.99.135.199, same result.
-- SMTP client. No sending of internet emails.
Those two events are off. I can't use the semaphore tricks simply
because the MIS POLL don't work. It don't connect to the node HUB. This
is why i have to use Binkd for that.
I tested changing "MIS POLL SEND" with Binkd in the command line
but it is never executed. I think linux don't like the"|" to separate
the two commands.
Same problem here. Also sometimes ignores stacked commands. Turning on
the ./ prefix doesn't work. I just put it in the command line. Also
the node setup ignores whats in the echomail in and out folder setting
and uses the default.
Mystic do strange things on Pi. Now is on Event config. I do some modifications to one event and after some time, this event resets alone
to the old values.
Same problem here. Also sometimes ignores stacked commands. Turning on
the ./ prefix doesn't work. I just put it in the command line. Also
the node setup ignores whats in the echomail in and out folder setting
and uses the default.
A bug that a have but now it seen to be OK, is on "message Base Editor"
on echomail Bases the option "Export To"
lost this setting
Yeah, in such cases it's usually good to try to figure out what's wrong
in the setup, ask for help if needed, and try to fix things..
Mystic do strange things on Pi. Now is on Event config. I do some modifications to one event and after some time, this event resets alone
to the old values.
At first i liked to use Synchronet software but the installation don't
work very well and i ended using Mystic.
Now, my Mystic is tweated a lot, many hrs lost on that.
Difficult to me to restart again from 0.
I see some Mystic BBS on Pi.But, or they don't use echomail messages, or they use a old dated msgs Base. Is difficult to see if the MIS Polling
is working for they on PI.
But, i'm happy, i found a way to get this working for me! :-)
Mystic do strange things on Pi. Now is on Event config. I do somemodifications to one event and af
ter some time, this event resets alone to
the old values.
Make sure the BBS is down when you make changes like this. I know, it's annoying lol.
The problem is, Mystic/MIS doesn't tell you when this needs to be done
(it probably should), and doesn't /always/ require it. So, the "recommendation" has always been that whenever you make changes in Mystic's configuration, you should restart MIS afterwards.
A bug that a have but now it seen to be OK, is on "message Base Editor"
on echomail Bases the option "Export To" lost this setting and
goes to "0 node". I've to verify (various times) all echomail Bases to
see is this setting is good to "1 node".
| Sysop: | HM Derdoc |
|---|---|
| Location: | SKY NET |
| Users: | 38 |
| Nodes: | 9 (1 / 8) |
| Uptime: | 07:07:21 |
| Calls: | 538 |
| Calls today: | 7 |
| Files: | 2 |
| D/L today: |
3 files (14K bytes) |
| Messages: | 12,563 |