I get FSX_BOT in, but my BOT output no longer gets sent - it shows as local. FSX_BOT on my Pi is at 6 and the .ini file sents it to 6, but it shows as
local only. Even stranger is all new posts come in and this all worked when I first upgraded to the A47 I'm running. Can anyone guess how it has become local?
Hmm, seems I can't upload the .ini here either.

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

`07*** Quoting bcw142 from a message to All ***`07

I get FSX_BOT in, but my BOT output no longer gets sent - it shows as local. FSX_BOT on my Pi is at 6 and the .ini file sents it to 6, but
it shows as local only. Even stranger is all new posts come in and
this all worked when I first upgraded to the A47 I'm running. Can
anyone guess how it has become local? Hmm, seems I can't upload the
.ini here either.

Anything I post with the mutil also says: Stat : Local

Once I run ./mutil mailout.ini it will then say: Stat : Local Sent


Jay

... A truly wise man never plays leapfrog with a unicorn.

--- Telegard v3.09.g2-sp4/mL
* Origin: Northern Realms (21:3/110.1)

On 22 Feb 2021 at 09:28a, Warpslide pondered and said...

Anything I post with the mutil also says: Stat : Local
Once I run ./mutil mailout.ini it will then say: Stat : Local Sent

Jay

Ahhh, I tried that and get Waiting on BUSY nodes. So it's the BUSY issue ;(

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

`07*** Quoting bcw142 from a message to Warpslide ***`07

Ahhh, I tried that and get Waiting on BUSY nodes. So it's the BUSY
issue ;(

./mis poll killbusy

And make sure your mailout.ini file has:

[ExportEchoMail]

; Do not export messages from users currently online
skip_online = false


Jay

... To err is human, but to really foul things up requires a computer.

--- Telegard v3.09.g2-sp4/mL
* Origin: Northern Realms (21:3/110.1)

I followed Avon's old advice on that (Waiting for BUSY nodes)

Chances are you have a ton of unprocessed packets in your BBS inbound.

Check the mutil logs to see if it's reporting things are BUSY so not
processing them.

If this is the case, stop MIS (in my case 'sudo killall mis')
and then run the './mis poll killbusy all' command

Then try your './mutil mailin.ini' (or whatever ini you use)
to see if they process in...

Then restart MIS (in my case 'sudo ./mis daemon')

Note above that './mis poll killbusy all' not just killbusy

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

On 22 Feb 2021, Warpslide said the following...

Once I run ./mutil mailout.ini it will then say: Stat : Local Sent

Jay

Ahh, I think I see the issue: Waiting for BUSY nodes when I do mailout. We're back to the BUSY issue again ;(

--- Mystic BBS v1.12 A47 2021/02/12 (Raspberry Pi/32)
* Origin: Mystic Pi BBS bcw142.zapto.org:23 (21:1/145)