Sorry about posting this here, but I just happen to notice that a few of the people that I've been feeding fidonet FTN/FDN have developed a problem
showing up in my fidopoll.log (Zero Reader and Caphood) Carlos is not having any issues though. Anyway here is the recent log..

Jan 16 15:47:55 Polling BINKP node 1:135/369
Jan 16 15:47:55 Connecting to blackflag.acid.org
Jan 16 15:47:55 Connected
Jan 16 15:47:55 Authorization State: 1 HH:0 NH:1
Jan 16 15:47:55 Sent: NUL SYS flupH
Jan 16 15:47:55 Sent: NUL ZYZ Leslie Given
Jan 16 15:47:55 Sent: NUL VER Mystic/1.12A31 binkp/1.0
Jan 16 15:47:55 Sent: ADR 1:275/91@fidonet
Jan 16 15:47:55 Authorization State: 2 HH:0 NH:1
Jan 16 15:47:55 Invalid data frame
Jan 16 15:47:55 Recv: NUL
Jan 16 15:47:55 Remote disconnect
Jan 16 15:47:55 Authorization failed
Jan 16 15:48:56 Polling BINKP node 1:123/525
Jan 16 15:48:56 Connecting to alco.bbs.io
Jan 16 15:48:56 Connected
Jan 16 15:48:56 Authorization State: 1 HH:0 NH:1
Jan 16 15:48:56 Sent: NUL SYS flupH
Jan 16 15:48:56 Sent: NUL ZYZ Leslie Given
Jan 16 15:48:56 Sent: NUL VER Mystic/1.12A31 binkp/1.0
Jan 16 15:48:56 Sent: ADR 1:275/91@fidonet
Jan 16 15:48:56 Authorization State: 2 HH:0 NH:1
Jan 16 15:49:26 Session timeout
Jan 16 15:49:26 Authorization failed

Maybe you both might see this post here, then pvt message me on facebook so we can sort out the problem of what happened, strange that it has been working fine for months if not years (:

Üܲ±ßÞÜÝ ÞÜÜ Ü²Þ²ÜÜ ÜÝ °Ü Ý ! b7 member board
Þ²ÜÜÜ Þ² ÜÞ²Ý Þ²ÝÞÝ޲ݰÜÜ²Ý ÜÜ dA flupHly squirrel ate my nuts!
Þ²Ý ß߲ܲÝßÛܲÝÞ²Ýßß Þ²ÝÞ²Ý²Ý @ http://fluph.bbsnexus.com

--- Mystic BBS v1.12 A31 (Windows)
* Origin: flupH | fluph.darktech.org (21:1/105)

On 01/16/17, Skuz pondered and said...

Sorry about posting this here, but I just happen to notice that a few of the people that I've been feeding fidonet FTN/FDN have developed a
problem showing up in my fidopoll.log (Zero Reader and Caphood) Carlos
is not having any issues though. Anyway here is the recent log..

I would suspect your IP has been auto blocked... I'd check that first :)

Best, Paul

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

On 01/16/17, Skuz said the following...

Sorry about posting this here, but I just happen to notice that a few of the people that I've been feeding fidonet FTN/FDN have developed a
problem showing up in my fidopoll.log (Zero Reader and Caphood) Carlos
is not having any issues though. Anyway here is the recent log..

That's strange Skuz... I'm still getting new messages, so I didn't know anything was wrong.

Jan 16 15:48:56 Sent: NUL VER Mystic/1.12A31 binkp/1.0
Jan 16 15:48:56 Sent: ADR 1:275/91@fidonet
Jan 16 15:48:56 Authorization State: 2 HH:0 NH:1
Jan 16 15:49:26 Session timeout
Jan 16 15:49:26 Authorization failed

Haven't touched any settings on my end in months. What does this error seem
to indicate?

--- Mystic BBS v1.12 A31 (Raspberry Pi)
* Origin: Alcoholiday / Est. 1995 / alco.bbs.io (21:1/113)

On 1/18/2017 11:05 AM, Zero Reader wrote:

That's strange Skuz... I'm still getting new messages, so I didn't know anything was wrong.
Haven't touched any settings on my end in months. What does this error seem to indicate?

I have not changed anything here either, so I guess nothing is wrong... It might just be a timing issue when I poll yours and it see a busy flag or something to that effect. Know worries, unless the flow stops.

--- Mystic BBS/NNTP v1.12 A31 (Windows)
* Origin: flupH | fluph.darktech.org (21:1/105)

On 01/18/17, Skuz pondered and said...

On 1/18/2017 11:05 AM, Zero Reader wrote:

That's strange Skuz... I'm still getting new messages, so I didn't know anything was wrong.
Haven't touched any settings on my end in months. What does this error s to indicate?

I have not changed anything here either, so I guess nothing is wrong...
It might just be a timing issue when I poll yours and it see a busy flag or something to that effect. Know worries, unless the flow stops.

Zero - check your system has not added Skuz to the badip.txt file... that
would explain you polling him ok but him not being able to poll you.

Best, Paul

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

19 Jan 17 13:19, you wrote to me:

Zero - check your system has not added Skuz to the badip.txt file...
that would explain you polling him ok but him not being able to poll
you.

Thanks for sharing your thoughts on this.. after I first noticed the issue in my logs, 1st I double checked Zero, Caphood and Carlos domain IP's for changes and they were all correct and up-to-date in my goodip.txt and my whitelist. None of them where in my badip.txt or my blacklist. FYI my event fidopoll runs once per hour, if someone forgets to poll me for their mail. I hold everyones FDN filebone in their boxes up to one month, if the files pile up they end-up just getting deleted (: ... Like most networks, there are alot of systems that run like clockwork and others that are not up to the task. I just hope James decides to return to coding Mystic again, so we can all pick-up where we left off.. The last time he took a break (vacation) it lasted about 6 or 7 years.
By my count, his last post was about 6 months ago. Whatever he decides to do, I

hope he his fun doing it and enjoys whatever life as in store for him. Thanks for sending out your Agents of SHIELD to find out about Al ...also ;)

--- GoldED+/W32-MSVC 1.1.5-b20160201
* Origin: flupH * fluph.darktech.org (21:1/105)

On 01/18/17, Skuz said the following...

I have not changed anything here either, so I guess nothing is wrong...
It might just be a timing issue when I poll yours and it see a busy flag or something to that effect. Know worries, unless the flow stops.

Avon mentioned that your IP may be blocked on my end for some reason. I'll
see if I can dig through the banned file and clear that up.

--- Mystic BBS v1.12 A31 (Raspberry Pi)
* Origin: Alcoholiday / Est. 1995 / alco.bbs.io (21:1/113)

On 01/19/17, Avon said the following...

Zero - check your system has not added Skuz to the badip.txt file... that would explain you polling him ok but him not being able to poll you.

Seems like that was it indeed. I removed his IP from the badip.txt. Hopefully that solves it.

--- Mystic BBS v1.12 A31 (Raspberry Pi)
* Origin: Alcoholiday / Est. 1995 / alco.bbs.io (21:1/113)

On 01/18/17, Skuz pondered and said...

clockwork and others that are not up to the task. I just hope James decides to return to coding Mystic again, so we can all pick-up where we left off.. The last time he took a break (vacation) it lasted about 6 or
7 years. By my count, his last post was about 6 months ago. Whatever he decides to do, I hope he his fun doing it and enjoys whatever life as in store for him. Thanks for sending out your Agents of SHIELD to find out about Al ...also ;)

Agreed... and you're most welcome Skuz :)

Thanks also to you for helping to keep the scene alive and well - you do a great job!

Best, Paul

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

On 01/19/17, Zero Reader pondered and said...

Seems like that was it indeed. I removed his IP from the badip.txt. Hopefully that solves it.

Good, I've seen this before :)

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

19 Jan 17 09:54, you wrote to Avon:

On 01/19/17, Avon said the following...

Zero - check your system has not added Skuz to the badip.txt
file... that would explain you polling him ok but him not being
able to poll you.

Seems like that was it indeed. I removed his IP from the badip.txt. Hopefully that solves it.

The problem is still happening from seeing my fidopoll.log for you and caphood.

I would suggest that you and hawk add my 74.194.189.150 to your goodip.txt
your whitelist. That would negate any future influences of my IP getting added to your badip.txt or blacklist ... I can tell my system to not poll yours, by just removing the session domain names for each network. But that would stop any crash mail form being sent directly (in real time) when it was created.

Something I've always wondered about Mystic -cfg is the Netmail options in the configure. In the Message base setting,. mine looks like this..
Message Settings
List Compression Yes Quote Color Sample
List Columns 2 Text Color Sample
Show Message Header Yes Tear Color Sample
Bases in Group List Yes Origin Color Sample
Max AutoSig Lines 4 Kludge Color Sample
Force NL Match No Netmail Crash Yes
Extended Reply ACS s255 Netmail Hold No
Attachment ACS s255 Netmail Killsent Yes
Msg Upload ACS s20 Netmail Direct Yes
Add [ANSI] Prefix Echo Only Create Semaphore Logout
Add Re: Prefix Yes
Default Origin flupH | fluph.darktech.org

My thinking here is the options are meant to -cfg what option to allow. While in the Echomail node setting for each link we have Normal,Crash,Hold and Direct. While other software (like ALLFIX) also as Crash/Direct option.

Myself, I have never seen Mystic ask a user sending Netmail If they what it sent out with a Crash flag or a Direct flag in the Netmail header. Maybe, I should revisit the whatsnew.txt and refreash my menory. Another thing about sending Netmail to other systems in the nodelist, that I've noticed. Even if mystic has added a Direct flag to a message. It will send it out routed as a Normal/Crash Netmail .. even through it marked with a Direct flag.

Maybe, mystic needs to add some type of ROUTE.MYS info file that would enhance The the already used Route Info ________________________________________ used.

My present fido Route Info data line looks like this, but it don't alway work as expected. 1:* 2:* 3:* 4:* !1:277/60 261/38 123/525 135/369 116/* 275/92 /94 /91.5 .6 .7 .8 .9 For example, I've seen direct netmail to 116/22 still get routed through 1:275/100 (my uplinks) hub. Anyway, these are things I've noticed since switching to a full native mystic system.

--- GoldED+/W32-MSVC 1.1.5-b20160201
* Origin: flupH * fluph.darktech.org (21:1/105)

On 01/19/17, Zero Reader pondered and said...

Seems like that was it indeed. I removed his IP from the badip.txt. Hopefully that solves it.

Just further to Skuz's follow-up... I'd ensure you close and restart MIS
after making changes to goodip.txt, badip.txt etc. I find without doing this sometimes they are not acted on by the server.

Best, Paul

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