g00r00, I may have found some info that can help you.

I added an echo as before and when I immediately pulled I got the following when listing the newsgroups from mis2.log

09:43:00 NNTP 1-S: Computer.Security.&.Hacking 0 0 y
+ 09:43:00 NNTP 1-S: Counter-Terrorism 0 0 y
+ 09:43:00 NNTP 1-S: Covert.Communication 0 0 y
+ 09:43:00 NNTP 1-S: Cryptography.&.Steganography 0 0 y
+ 09:43:00 NNTP 1-S: Darknets,.Network.Underground 0 0 y
+ 09:43:00 NNTP 1-S: Disease,.Pandemics.&.Disasters 0 0 y
+ 09:43:00 NNTP 1-S: End.Times.&.The.Last.Days 0 0 y
+ 09:43:00 NNTP 1-S: Truth,.Polygraphs,.Serums 0 0 y
+ 09:43:00 NNTP 1-S: Financial.Crisis.&.Meltdown 0 0 y
+ 09:43:00 NNTP 1-S: General.Conspiracies 0 0 y
+ 09:43:00 NNTP 1-S: General.Forensics 0 0 y
+ 09:43:00 NNTP 1-S: Intelligence.&.Espionage 0 0 y
+ 09:43:00 NNTP 1-S: Intelligence.&.The.Law 0 0 y
+ 09:43:00 NNTP 1-S: Interrogation.&.Torture 0 0 y
+ 09:43:00 NNTP 1-S: Languages.&.Public.Speaking 0 0 y
+ 09:43:00 NNTP 1-S: Middle.East.Studies 0 0 y
+ 09:43:00 NNTP 1-S: Mind.Control.&.Programming 0 0 y
+ 09:43:00 NNTP 1-S: New.World.Order 0 0 y
+ 09:43:00 NNTP 1-S: Paranormal.Studies 0 0 y
+ 09:43:00 NNTP 1-S: Predictive.Studies 0 0 y
+ 09:43:00 NNTP 1-S: Propaganda.&.Disinformation 0 0 y
+ 09:43:00 NNTP 1-S: Politics.&.People 0 0 y
+ 09:43:00 NNTP 1-S: Safe.Houses.&.Sanctuarie 0 0 y
+ 09:43:00 NNTP 1-S: Secret.Societies 0 0 y
+ 09:43:00 NNTP 1-S: Silencers.of.Information 0 0 y
+ 09:43:00 NNTP 1-S: Spooks.&.Their.Weapons 0 0 y
+ 09:43:00 NNTP 1-S: TSCM.Bug.Detection 0 0 y
+ 09:43:00 NNTP 1-S: Violent.Extremist.Religions 0 0 y
+ 09:43:00 NNTP 1-S: Whistle.Blowers 0 0 y
+ 09:43:00 NNTP 1-S: .
+ 09:43:00 NNTP 1-S: 205 Goodbye
+ 09:43:00 NNTP 1-Connection closed
+ 09:43:46 NNTP > Connect on slot 1/1
+ 09:43:46 NNTP 1-Address 75.20.174.252
+ 09:43:46 NNTP 1-HostName 75-20-174-252.lightspeed.ftwotx.sbcglobal.net
+ 09:43:46 NNTP 1-S: 200 Mystic BBS NNTP server ready
+ 09:43:46 NNTP 1-C: AUTHINFO
+ 09:43:46 NNTP 1--C: AUTHINFO user nugax
+ 09:43:46 NNTP 1-S: 381 Password required
+ 09:43:46 NNTP 1-C: AUTHINFO
+ 09:43:46 NNTP 1-C: AUTHINFO PASS ***
+ 09:43:46 NNTP 1-S: 281 Authentication accepted
+ 09:43:46 NNTP 1-Logged in as nugax
+ 09:43:46 NNTP 1-C: GROUP Data: filegate_hubs_coords
+ 09:43:46 NNTP 1-S: 211 0 0 0 filegate_hubs_coords
+ 09:43:46 NNTP 1-Group set to Filegate Hubs and Coordinators
+ 09:43:46 NNTP 1-C: XOVER Data: 0-0
+ 09:43:46 NNTP 1-S: 420 No article(s) selected
+ 09:44:01 NNTP 1-S: 205 Goodbye
+ 09:44:01 NNTP 1-Connection closed
cadams@byte-bbs:~/mystic/logs$


You can see each one does not have any messages listed. It errored as before. Notice the 0 0 y. One stands for number of messages I believe.


After reboot, I got the following showing messages and completely different info in the mis2 NNTP log:

09:46:37 NNTP 1-HostName 75-20-174-252.lightspeed.ftwotx.sbcglobal.net
+ 09:46:37 NNTP 1-S: 200 Mystic BBS NNTP server ready
+ 09:46:37 NNTP 1-C: AUTHINFO
+ 09:46:37 NNTP 1--C: AUTHINFO user nugax
+ 09:46:37 NNTP 1-S: 381 Password required
+ 09:46:37 NNTP 1-C: AUTHINFO
+ 09:46:37 NNTP 1-C: AUTHINFO PASS ***
+ 09:46:37 NNTP 1-S: 281 Authentication accepted
+ 09:46:37 NNTP 1-Logged in as nugax
+ 09:46:38 NNTP 1-C: GROUP Data: filegate_hubs_coords
+ 09:46:38 NNTP 1-S: 211 34 1 34 filegate_hubs_coords
+ 09:46:38 NNTP 1-Group set to Filegate Hubs and Coordinators
+ 09:46:38 NNTP 1-C: XOVER Data: 0-34
+ 09:46:38 NNTP 1-List messages (0-34 from Filegate Hubs and Coordinators
+ 09:46:38 NNTP 1-S: 224 Overview information follows
+ 09:46:38 NNTP 1-S: 205 Goodbye
+ 09:46:38 NNTP 1-Connection closed
cadams@byte-bbs:~/mystic/logs$


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

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

g00r00, I may have found some info that can help you.
You can see each one does not have any messages listed. It errored as before. Notice the 0 0 y. One stands for number of messages I believe.

Yep I saw this before although it was only one base in the log before.

This is the reason I was asking if the base had messages in it or if the accesses were off. Mystic is not properly reporting the high message number, which wasn't the case on my test here with the iPad.

Let me get a new build released so we're on the same page and we'll go from there.

--- Mystic BBS v1.12 A36 2017/11/25 (Windows/64)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

Thanks for your help g00r00! Mystic is the best.

On 07:43 25/11 , g00r00 wrote:

g00r00, I may have found some info that can help you.
You can see each one does not have any messages listed. It errored as before. Notice the 0 0 y. One stands for number of messages I believe.

Yep I saw this before although it was only one base in the log before.

This is the reason I was asking if the base had messages in it or if the >accesses were off. Mystic is not properly reporting the high message number, >which wasn't the case on my test here with the iPad.

Let me get a new build released so we're on the same page and we'll go from >there.

--- Mystic BBS v1.12 A36 2017/11/25 (Windows/64)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

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

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

I tried latest prealpha, same issue. Here is logfile. Base has 34 messages in it.

13:51:45 NNTP 1-S: 200 Mystic BBS NNTP server ready
+ 13:51:45 NNTP 1-C: AUTHINFO
+ 13:51:45 NNTP 1--C: AUTHINFO user nugax
+ 13:51:45 NNTP 1-S: 381 Password required
+ 13:51:45 NNTP 1-C: AUTHINFO
+ 13:51:45 NNTP 1-C: AUTHINFO PASS ***
+ 13:51:45 NNTP 1-S: 281 Authentication accepted
+ 13:51:45 NNTP 1-Logged in as nugax
+ 13:51:45 NNTP 1-C: GROUP Data: filegate_hubs_coords
+ 13:51:45 NNTP 1-S: 211 0 0 0 filegate_hubs_coords
+ 13:51:45 NNTP 1-Group set to Filegate Hubs and Coordinators
+ 13:51:45 NNTP 1-C: XOVER Data: 0-0
+ 13:51:45 NNTP 1-S: 420 No article(s) selected
+ 13:51:45 NNTP 1-DEBUG: fn=ifdc path=/var/opt/mystic/tempmis/
+ 13:51:52 NNTP 1-S: 205 Goodbye
+ 13:51:52 NNTP 1-Connection closed
+ 13:51:58 NNTP > Connect on slot 1/1
+ 13:51:58 NNTP 1-Address 172.56.7.225
+ 13:51:58 NNTP 1-HostName Unknown
+ 13:51:58 NNTP 1-S: 200 Mystic BBS NNTP server ready
+ 13:51:58 NNTP 1-C: AUTHINFO
+ 13:51:58 NNTP 1--C: AUTHINFO user nugax
+ 13:51:58 NNTP 1-S: 381 Authentication rejected
+ 13:51:58 NNTP 1-C: AUTHINFO
+ 13:51:58 NNTP 1-C: AUTHINFO PASS ***
+ 13:51:58 NNTP 1-S: 482 Bad Authentication sequence
+ 13:51:58 NNTP 1-S: 205 Goodbye
+ 13:51:58 NNTP 1-Connection closed
cadams@byte-bbs:~/mystic/logs$



On 07:43 25/11 , g00r00 wrote:

g00r00, I may have found some info that can help you.
You can see each one does not have any messages listed. It errored as before. Notice the 0 0 y. One stands for number of messages I believe.

Yep I saw this before although it was only one base in the log before.

This is the reason I was asking if the base had messages in it or if the >accesses were off. Mystic is not properly reporting the high message number, >which wasn't the case on my test here with the iPad.

Let me get a new build released so we're on the same page and we'll go from >there.

--- Mystic BBS v1.12 A36 2017/11/25 (Windows/64)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

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

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

I tried latest prealpha, same issue. Here is logfile. Base has 34
messages in it.

I may have found a permissions problem with MIS2 that I have cleaned up. I
am still not convinced that will fix your issue though.

I have been testing clients and it really seems that clients just do not query and obey the level of implementation the NNTP server has, and they start using commands in a way in which the particular RFC Mystic is built around does not support. Still, I don't think that has anything to do with your problem!

I am going to work on supporting later NNTP RFCs very soon, but that still may not fix the issue we're seeing here.

--- Mystic BBS v1.12 A36 2017/11/27 (Windows/64)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)