Hello folks. I am sure there is a simple fix for this, BUT, BinkP is polling the following every 2 hours or so,

Jun 04 11:20:49 FIDOPOLL Version 1.12 A33
Jun 04 11:20:49 Scanning 1:266/0
Jun 04 11:20:49 Queued 0 files (0 bytes) to 1:266/0
Jun 04 11:20:49 Polling BINKP node 1:266/0
Jun 04 11:20:49 Connecting to cfbbs.dtdns.net
Jun 04 11:20:49 Connected
Jun 04 11:20:49 OPT MB CRAM-MD5-52fc7a6f90db1e93e83a61f794f9896c
Jun 04 11:20:49 SYS Christian Fellowship
Jun 04 11:20:49 ZYZ Michael Luko
Jun 04 11:20:49 LOC Mt. Ephraim, NJ
Jun 04 11:20:49 NDL CM,INA:cfbbs.dtdns.net,IBN,ITN,IFT
Jun 04 11:20:49 TIME 2017/06/04 11:20:10 -5:00
Jun 04 11:20:49 VER Internet Rex 2.29 Win32 (binkp/1.1)
Jun 04 11:20:49 Session complete (0 sent, 0 rcvd, 0 skip)

I have scoured my configs for a mis-type and cannot find it. Its weird, and
now probably aggravates the poor fellow at 1:266/0

I do poll Tequilamockingbird at 1:266/404 from time to time but not the hub.

Whats do I need to do?

Mick Manning

Central Ontario Remote BBS
Telnet: oxfordmi.synchro.net

--- Mystic BBS v1.12 A33 (Windows/32)
* Origin: Central Ontario Remote | fsxNET 21:1/156 (21:1/156)

On 06/04/17, Mick Manning said the following...

Hello folks. I am sure there is a simple fix for this, BUT, BinkP is polling the following every 2 hours or so,

Sounds like you have a FIDOPOLL command in your events configuration. Check all the active events, hourly, interval, etc.

Hope that helps

Immortal

--- Mystic BBS v1.12 A33 (Linux/32)
* Origin: Lightning BBS -- lightningbbs.com:2400 (21:1/185)

On 06/04/17, Immortal considered the following...

Sounds like you have a FIDOPOLL command in your events configuration. Check all the active events, hourly, interval, etc.

That,s a good suggestion. I have looked at all my events of which I have a
few but 1:266/0 is mentioned nowhere. Because it seems to happen so often, I thought that would be the most reasonable place to start.

I was concerned that maybe my system couldnt reach its destination so was trying it,s hub node by default or something weird.

Cheers!

Mick

Central Ontario Remote BBS
Telnet: oxfordmi.synchro.net

--- Mystic BBS v1.12 A33 (Windows/32)
* Origin: Central Ontario Remote | fsxNET 21:1/156 (21:1/156)

It will only poll what nodes you have setup, since you need login.

Do a fidopoll list command and see if that node is listed.

I suspect so. And if so, you have a script, batch file, or event configure polling that person.



On 08:24 04/06 , Mick Manning wrote:

On 06/04/17, Immortal considered the following...

Sounds like you have a FIDOPOLL command in your events configuration. Check all the active events, hourly, interval, etc.

That,s a good suggestion. I have looked at all my events of which I have a >few but 1:266/0 is mentioned nowhere. Because it seems to happen so often, I >thought that would be the most reasonable place to start.

I was concerned that maybe my system couldnt reach its destination so was >trying it,s hub node by default or something weird.

Cheers!

Mick

Central Ontario Remote BBS
Telnet: oxfordmi.synchro.net

--- Mystic BBS v1.12 A33 (Windows/32)
* Origin: Central Ontario Remote | fsxNET 21:1/156 (21:1/156)

--
yrNews Usenet Reader for iOS
http://appstore.com/yrNewsUsenetReader

--- Mystic BBS/NNTP v1.12 A33 (Linux/64)
* Origin: -=The ByteXchange BBS : bbs.thebytexchange.com=- (21:1/107)

On 06/04/17, Nugax considered the following...

I suspect so. And if so, you have a script, batch file, or event
configure polling that person.

I was hoping so, but no, its not listed. Like I mentioned earlier, I do have 1:266/404 but NOT 1:266/0

Another good place to check though. Just a note, I have deleted the hub from the internal nodelist here, as well as added the url to the badip file etc.
It didn't work either.

Cheers!

Mick

Central Ontario Remote BBS
Telnet: oxfordmi.synchro.net

--- Mystic BBS v1.12 A33 (Windows/32)
* Origin: Central Ontario Remote | fsxNET 21:1/156 (21:1/156)

On 06/04/17, Mick Manning pondered and said...

Hello folks. I am sure there is a simple fix for this, BUT, BinkP is polling the following every 2 hours or so,

Jun 04 11:20:49 FIDOPOLL Version 1.12 A33
Jun 04 11:20:49 Scanning 1:266/0
Jun 04 11:20:49 Queued 0 files (0 bytes) to 1:266/0
Jun 04 11:20:49 Polling BINKP node 1:266/0
Jun 04 11:20:49 Connecting to cfbbs.dtdns.net
Jun 04 11:20:49 Connected
Jun 04 11:20:49 OPT MB CRAM-MD5-52fc7a6f90db1e93e83a61f794f9896c
Jun 04 11:20:49 SYS Christian Fellowship

Hi :)

Have you ever configured this echo node before?
Does it show in the echo nodes you have set up when running mystic -cfg ?
When you see this behavior happening what files do you observe in the echomail\out\ directory being touched?


Best, Paul

--- Mystic BBS v1.12 A33 (Windows/32)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)

On 06/05/17, Avon considered the following...

Have you ever configured this echo node before?

Never.

Does it show in the echo nodes you have set up when running mystic -cfg ?

No, Never has.

When you see this behavior happening what files do you observe in the echomail\out\ directory being touched?

I never have anything in 'Out', mail is handled almost immediately by Mystic. This is new behaviour as far as I can tell. It seems to poll this node every
2 hours. I have nothing like that scheduled. At first I thought it was his system polling me, but the log shows differently.

Mick

Central Ontario Remote BBS
Telnet: oxfordmi.synchro.net

--- Mystic BBS v1.12 A33 (Windows/32)
* Origin: Central Ontario Remote | fsxNET (21:1/156)

I have scoured my configs for a mis-type and cannot find it. Its weird, and now probably aggravates the poor fellow at 1:266/0

Whats do I need to do?

Sorry but I am not sure what the problem is or what you are trying to do!

Are you saying that you're accidentally polling that address? What is the command line you're using to run FidoPoll?

--- Mystic BBS v1.12 A34 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

It will only poll what nodes you have setup, since you need login.

Do a fidopoll list command and see if that node is listed.

Just a note:

The 1.12 version of fidopoll can read the nodelist and do unsecure mail transactions with anything in the node list.

--- Mystic BBS v1.12 A34 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

On 06/04/17, g00r00 considered the following...

Are you saying that you're accidentally polling that address? What is
the command line you're using to run FidoPoll?

I have re-produced, and removed the problem. I still don't know exactly what the problem is, but I no longer auto-poll the poor hub.

I had an event set-up to poll 1:266/404 for my file-feed, and it was set for
an EXEC type of 'Interval' instead of 'Shell'. For some reason, it would poll their HUB at 1:266/0 instead. I made the event inactive, and the problem went away.

I'll keep an eye on it.

Mick

Central Ontario Remote BBS
Telnet: oxfordmi.synchro.net

--- Mystic BBS v1.12 A33 (Windows/32)
* Origin: Central Ontario Remote | fsxNET (21:1/156)

On 06/04/17, Mick Manning pondered and said...

On 06/04/17, g00r00 considered the following...
I have re-produced, and removed the problem. I still don't know exactly what the problem is, but I no longer auto-poll the poor hub.

I had an event set-up to poll 1:266/404 for my file-feed, and it was set for an EXEC type of 'Interval' instead of 'Shell'. For some reason, it would poll their HUB at 1:266/0 instead. I made the event inactive, and the problem went away.

I'll keep an eye on it.

Mick, was the 'session option' details set correctly for the 1:266/404 node
you saw this strange behavior occurring on?

Because you were saying you were polling this /404 address without issue also
- is that right?

I can't see how interval vs shell would cause that problem. What was/is
listed in the now 'inactive' event on the shell line?

Be curious to try and suss why this one occurred, it's a new one to me.

Best, Paul

--- Mystic BBS v1.12 A33 (Windows/32)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)

The 1.12 version of fidopoll can read the nodelist and do unsecure mail transactions with anything in the node list.

Didn't know this. Looks like a place to start looking!



-Nugax

--- Mystic BBS v1.12 A33 (Linux/64)
* Origin: -=The ByteXchange BBS : bbs.thebytexchange.com=- (21:1/107)

On 06/05/17, Avon considered the following...

Mick, was the 'session option' details set correctly for the 1:266/404 node you saw this strange behavior occurring on?

Hi Paul, Because I don't need to poll for new files every hour or two, I decided to remove the option completely. The only change I made was to switch from session type 'interval' to 'shell'. It seemed to work then, but like I say, I've unactivated it for now, so it would poll 1:266/0 using 'session'
and switch to 1:266/404 using shell. My forte' is Music, not computer programming so much. :-)

Be curious to try and suss why this one occurred, it's a new one to me.

I'm just glad I fixed it, and I'm sure Michael over at 1:266/0 is just
jumping for joy. <grin>

Mick

Central Ontario Remote BBS
Telnet: oxfordmi.synchro.net

--- Mystic BBS v1.12 A33 (Windows/32)
* Origin: Central Ontario Remote | fsxNET (21:1/156)

On 06/04/17, Mick Manning said the following...

On 06/04/17, Nugax considered the following...

I suspect so. And if so, you have a script, batch file, or event configure polling that person.

I was hoping so, but no, its not listed. Like I mentioned earlier, I do have 1:266/404 but NOT 1:266/0

Another good place to check though. Just a note, I have deleted the hub from the internal nodelist here, as well as added the url to the badip file etc. It didn't work either.

Thats weird. As far as I know, mystic will only connect to systems that you have configured. It needs to know the address:port and password, etc. It doesn't read this from the nodelist.

Immortal

--- Mystic BBS v1.12 A33 (Linux/32)
* Origin: Lightning BBS -- lightningbbs.com:2400 (21:1/185)

On 06/05/17, Nugax said the following...

The 1.12 version of fidopoll can read the nodelist and do unsecure ma transactions with anything in the node list.

Didn't know this. Looks like a place to start looking!

Me neither but good to know!

Immortal

--- Mystic BBS v1.12 A33 (Linux/32)
* Origin: Lightning BBS -- lightningbbs.com:2400 (21:1/185)

On 06/04/17, g00r00 said the following...

The 1.12 version of fidopoll can read the nodelist and do unsecure mail transactions with anything in the node list.

That's awesome! I didn't know it did that. Of course I had to try it out. :)


---

Dan Richter
aka Black Panther
Sysop - Castle Rock BBS (RCS)
telnet://castlerockbbs.com
The sparrows are flying again...

--- Mystic BBS v1.12 A33 (Windows/64)
* Origin: Castle Rock BBS - castlerockbbs.com (21:1/186)

I had an event set-up to poll 1:266/404 for my file-feed, and it was set for an EXEC type of 'Interval' instead of 'Shell'. For some reason, it would poll their HUB at 1:266/0 instead. I made the event inactive, and the problem went away.

Okay thanks for the update. What happens when you do a "fidopoll search 1:266/404"?

If you are polling an address that is not configured in your echomail nodes, then Mystic is doing an unsecured poll based on address and nodelist look up.

I think if 1:266/404 is not found, then 1:266/0 would be the fallback if you were trying to send an unsecured netmail to net 266. This may or may not be intended behavior ;)

I want to make sure there isn't some sort of bug with the nodelist lookup in fidopoll.

--- Mystic BBS v1.12 A34 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

The 1.12 version of fidopoll can read the nodelist and do unsecure ma transactions with anything in the node list.

That's awesome! I didn't know it did that. Of course I had to try it
out. :)

Yep and I am probably going to get off my butt and get that IPV6 in there too hopefully very soon. I think it was on my immediate todo list before I had
to take some time off.

--- Mystic BBS v1.12 A34 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

On 06/06/17, g00r00 said the following...

Yep and I am probably going to get off my butt and get that IPV6 in
there too hopefully very soon. I think it was on my immediate todo list before I had to take some time off.

I just recently started looking into getting a IPV6 tunnel set up over here.
I don't have native available. When I tried setting up via he.net, I ended up messing up my wife's system. (she works from home utilizing VOIP and WYSE systems)

I may have to hold off on that for now... :(


---

Dan Richter
aka Black Panther
Sysop - Castle Rock BBS (RCS)
telnet://castlerockbbs.com
The sparrows are flying again...

--- Mystic BBS v1.12 A33 (Windows/64)
* Origin: Castle Rock BBS - castlerockbbs.com (21:1/186)

g00r00 wrote to Black Panther <=-

Yep and I am probably going to get off my butt and get that IPV6 in
there too hopefully very soon. I think it was on my immediate todo
list before I had to take some time off.

That would be awesome for us IPv6 natives. :-)


... If you try to fail, and succeed, which have you done?
--- MultiMail/Win32 v0.49
* Origin: Freeway BBS - freeway.apana.org.au (21:1/109)

On 06/06/17, g00r00 considered the following...

Okay thanks for the update. What happens when you do a "fidopoll search 1:266/404"?

It shows up as expected. As I have this node listed in the config as my file feed, this is good behavior. Of course, 1:266/0 also list as per the nodelist.

I want to make sure there isn't some sort of bug with the nodelist
lookup in fidopoll.

Not sure, but possibly. Since 1:266/404 is now set here as 'HOLD' and not 'CRASH' the problem with polling 1:266/0 is gone. Therefore, there is peace again, in Central Ontario.

Cheers!

Mick

Central Ontario Remote BBS
Telnet: oxfordmi.synchro.net

--- Mystic BBS v1.12 A33 (Windows/32)
* Origin: Central Ontario Remote | fsxNET (21:1/156)