Can't find the message but someone suggested making Mystic NNTP more like Jammnntp.

I'm not sure what even more the NNTP server would need or what jams does that mystic doesn't already do.

The main reason people use NNTP is to stay connected to echomail while on
their phones.

I'd like to see mystic Linux build NNTP server work without crashing each
time you add a new echo area. I've tried every client iOS offers and every
one of them crash mystics NNTP server each time. Even the new build.

If you work on NNTP I'd say fix the errors you have. I don't even see any reason for more options to NNTP. It works fine as is. Except for the crashing bug.


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

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

I'd like to see mystic Linux build NNTP server work without crashing each time you add a new echo area. I've tried every client iOS offers and
every one of them crash mystics NNTP server each time. Even the new
build.

The crashing seems specific to your setup. It doesn't crash using the identical clients and OS for me, and there is also no one else reporting a similar issue. Its difficult to fix something like that but we'll get it.

The error in both the GROUP and XOVER commands are errors that say it cannot open or create the message base files needed.

I just added in some new logging in every single place it tries to physically open a message base, so that it will print if it doesn't have access. I also changed the way the "GROUP" command works to not even list the group if it cannot open it. Same with the XOVER command.

Until its reproducible all I can do is continue to add in logging here and there and make minor changes until we figure out a solution. :(

I'll upload new A37 build right now that will contain these changes.

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

Roger. Thanks man. I'm not in a hurry, I was mostly just saying I don't see
any reason to add options to NNTP. It works fine as is (minus my particular errors).

It works great once you add the areas. It just errors on adding then pulling the messages

On 05:47 06/12 , g00r00 wrote:

I'd like to see mystic Linux build NNTP server work without crashing each time you add a new echo area. I've tried every client iOS offers and every one of them crash mystics NNTP server each time. Even the new build.

The crashing seems specific to your setup. It doesn't crash using the >identical clients and OS for me, and there is also no one else reporting a >similar issue. Its difficult to fix something like that but we'll get it.

The error in both the GROUP and XOVER commands are errors that say it cannot >open or create the message base files needed.

I just added in some new logging in every single place it tries to physically >open a message base, so that it will print if it doesn't have access. I also >changed the way the "GROUP" command works to not even list the group if it >cannot open it. Same with the XOVER command.

Until its reproducible all I can do is continue to add in logging here and >there and make minor changes until we figure out a solution. :(

I'll upload new A37 build right now that will contain these changes.

--- Mystic BBS v1.12 A37 2017/12/05 (Windows/32)
* 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/12/03 (Linux/64)
* Origin: -=The ByteXchange BBS : bbs.thebytexchange.com=- (21:1/107)

The crashing seems specific to your setup. It doesn't crash using the identical clients and OS for me, and there is also no one else reporting
a similar issue. Its difficult to fix something like that but we'll get it.

I have reported it. The crash happens when my NNTP Client login. It was
logging every minute and the MIS server would crash after about 15 minutes. I changed the code to login only when a message needed to be posted and it does not crash anymore.

National Incident Alerts
telnet:\\niabbs.com
www.nationalincidentalerts.com

--- Mystic BBS v1.12 A35 (Windows/32)
* Origin: NIA BBS (21:2/108)

Roger. Thanks man. I'm not in a hurry, I was mostly just saying I don't see any reason to add options to NNTP. It works fine as is (minus my particular errors).

It works great once you add the areas. It just errors on adding then pulling the messages

Next time you get a chance to test with the latest prealpha please show me
the log and we can go from there.

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

Sure I'll try to do it tonight

On 11:48 06/12 , g00r00 wrote:

Roger. Thanks man. I'm not in a hurry, I was mostly just saying I don't see any reason to add options to NNTP. It works fine as is (minus my particular errors).

It works great once you add the areas. It just errors on adding then pulling the messages

Next time you get a chance to test with the latest prealpha please show me >the log and we can go from there.

--- Mystic BBS v1.12 A37 2017/12/05 (Windows/32)
* 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/12/03 (Linux/64)
* Origin: -=The ByteXchange BBS : bbs.thebytexchange.com=- (21:1/107)

I have reported it. The crash happens when my NNTP Client login. It was logging every minute and the MIS server would crash after about 15 minutes. I changed the code to login only when a message needed to be posted and it does not crash anymore.

What you reported is not the same thing as his problem, and the problem you're reporting is from an older NNTP server, not the newer builds.

If you are having a problem I would recommend upgrading to A37 and submitting
a log of the session where it crashes (if its still a problem) so that it can be addressed.

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

If you are having a problem I would recommend upgrading to A37 and submitting a log of the session where it crashes (if its still a
problem) so that it can be addressed.

No not a problem for me any longer since I changed my code. Just thought you should know so you don't bring any bugs forward to the new alpha.

National Incident Alerts
telnet:\\niabbs.com
www.nationalincidentalerts.com

--- Mystic BBS v1.12 A35 (Windows/32)
* Origin: NIA BBS (21:2/108)

If you are having a problem I would recommend upgrading to A37 and submitting a log of the session where it crashes (if its still a problem) so that it can be addressed.

No not a problem for me any longer since I changed my code. Just thought you should know so you don't bring any bugs forward to the new alpha.

Thanks. There isn't much I can do unless we test it again the current iteration of the server though, so I have no way of knowing if there is an issue or not!

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