On 05/19/16, Paul Hayton said the following...

This next message is to report the prior message seemed to trigger a fidopoll that sent a large amount of messages (16) out to a number of nodes once the HUB had processed the previous message.

I also see logging ocurring in the HUB again.

The spooky thing is I ran a fidopoll send that did log and did not send anything... then after the prior message was posted and the HUB
processed it I noted some nodes were being polled with much larger data packets than others... checking a node /123 I can see 16 new messages
had arrived when I knew by logging in 10 mins prior that 99% of what should have been there was not.

I'm wondering if the inability (if that's what it is) of fidopoll to
send is based on the logging issue I discovered or ??

I'll have to keep an eye on things but calling a few BBS and seeing what they are getting from the HUB vs what I see here.

Is it a binkp issue or maybe a tosser issue. Do you stay logged into your
BBS? Do you have skip_online = true in your mutil.ini [ExportEchoMail] section? If so, that will hold up processing. I found that out the hard way.

"No matter where you go, there you are!" - Buckaroo Bonzai

--- Mystic BBS v1.12 A14 (Raspberry Pi)
* Origin: Cyberia BBS | Cyberia.Darktech.Org | Kingwood, TX