On 09 Apr 2023 at 10:39a, SIRRONMIT pondered and said...
Ever since upgrading to the latest verison of Mystic, my BULLETINS fail
to notify anyone of "NEW". Even when visiting the "S"ystem Bulletins
menu, still shows none.
I made sure I recomposed the latest .mpx and the command is still "bulletin bulletin bullet check" (if I remember off the top of my head).
I'd check if the script has not changed in some fashion, perhaps do a plain install of mystic in another directory of your system and manually copy the script across to the scripts directory of your BBS (take a backup first ;)) then recompile.
Also check the plain install of Mystic to check the syntax of how the script is being called in case that's changed.
FSX net seems to all stay LOCAL instead of NETWORK. I can see my
messages on other networks, so not sure what is going on. I also saw
that latest post from WebMistress, but my node is not listed there -- could be THE reason I haven't been getting any replies to my questions
for the past few months.
I checked HUB 2 as a starter for you. It seems you are polling in hourly and collecting packets
+ 2023.04.09 18:35:13 BINKP > Connect on slot 1/10 (67.3.184.95)
+ 2023.04.09 18:35:13 BINKP 1-HostName 67-3-184-95.omah.qwest.net
+ 2023.04.09 18:35:13 BINKP 1-System Files 4 Fun BBS
+ 2023.04.09 18:35:13 BINKP 1-SysOp SirRonmit
+ 2023.04.09 18:35:13 BINKP 1-Mailer Mystic/1.12A48 binkp/1.0
+ 2023.04.09 18:35:14 BINKP 1-Queued 1 files for 21:2/120@fsxnet
+ 2023.04.09 18:35:14 BINKP 1-Sending: 0000ffec.suf (1,819 bytes)
+ 2023.04.09 18:35:14 BINKP 1-Remote Queue: 0 files 0 bytes
+ 2023.04.09 18:35:14 BINKP 1-Waiting for sent confirmation
+ 2023.04.09 18:35:14 BINKP 1-Sent: 0000ffec.suf (1,819 bytes in 0.20s)
+ 2023.04.09 18:35:14 BINKP 1-Session ended (1 sent, 0 rcvd, 0 skip)
But I can also confirm the HUB is unable to poll you. Is your domain and IP correct? .. and do you have your port 24554 open to the internet?
--------------------- POLL v1.12 A48 2023/01/15 Sun, Apr 09 2023 (loglevel 1) + 2023.04.09 19:12:53 Poll BINKP node via address lookup: 21:2/120
+ 2023.04.09 19:12:53 1-Polling 21:2/120 on slot 1 via BINKP
+ 2023.04.09 19:12:53 1-DEBUG ConnectMode=0
+ 2023.04.09 19:12:53 1-Connecting to F4FBBS.COM on port 24554
+ 2023.04.09 19:12:53 1-Using address 192.64.150.45
+ 2023.04.09 19:12:59 1-Unable to connect
+ 2023.04.09 19:13:00 Polled 1 systems
As for your BBS, check things like
Level 3 MUTIL logs to see if there's an issue processing inbound packets
Your echomail\in directory to see if there's a bunch of unprocessed packets Your echomail node settings for your HUB (which I think will be correct as you are polling in etc. now)
Your fsxNet echos are linked to export to your echomail node HUB for fsxNet
Let me know how you get on.
We'll get you sorted :)
Best,Paul
Kerr Avon [Blake's 7] 'I'm not expendable, I'm not stupid and I'm not going' avon[at]bbs.nz | bbs.nz | fsxnet.nz
--- Mystic BBS v1.12 A48 (Linux/64)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)