g00r00,

I am not sure if you know about this, but I run 64 Bit Linux (Ubuntu server).

I use NNTP quite a bit. It works great.

Occasionally, the NNTP server will crash when you open a few messages and such. I never saw this when I had Windows.

Is this something you know about? It happens constantly and has happened on last build.

I have a reboot cron job for about every 2-4 hours for my BBS so I can re-start MIS -d when it crashes from NNTP.

if you get a chance would you take a look?

Thank you sir!



... 2 + 2 = 5 for extremely large values of 2.
___ MultiMail/Linux v0.50

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

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

Occasionally, the NNTP server will crash when you open a few messages
and such. I never saw this when I had Windows.

Have you tried using another NNTP server? Give JAMNNTPD a shot: If it
also crashes, then it could be a big hit.

I have used heavily Mystic's NNTP service under Windows, but recently I have been experimenting JAMNNTPD on my Fidonet echos for added functionality.

--- Mystic BBS v1.12 A33 (macOS/64)
* Origin: Chiron, experimental system - Brazil (21:1/146.1)

I have used heavily Mystic's NNTP service under Windows, but
recently I have been experimenting JAMNNTPD on my Fidonet echos for
added functionality.

What is the added functionality that you're looking for?

The NNTP server could certainly use a reworking its very old.

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

I like the NNTP server. I can't think of anything you should add. I just have
a few problems with the Linux version crashing occasionally. But, other than that, it works fine.

I am on my iPhone replying to this perfectly!

G00r00, you rock! Awesome job on Mystic!
Glad your back around!


On 17:38 24/05 , g00r00 wrote:

I have used heavily Mystic's NNTP service under Windows, but
recently I have been experimenting JAMNNTPD on my Fidonet echos for
added functionality.

What is the added functionality that you're looking for?

The NNTP server could certainly use a reworking its very old.

--- Mystic BBS v1.12 A34 (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 A33 (Linux/64)
* Origin: -=The ByteXchange BBS : bbs.thebytexchange.com=- (21:1/107)

On 05/24/17, g00r00 said the following...

What is the added functionality that you're looking for?

Mystic's embedded NNTP server is great: fast and reliable.

But it does have a "flaw", which is common to the NNTP protocol: Using
NNTP as a means to access the message base, you can send only messages to All.
With JAMNNTPD, when you "follow-up" a message using a news client, it automatically updates the TO: field accordingly.

Now that I have finished integrating the Jamnntpd server into my system, I'll include the fsxNET areas so that my NNTP users can access the network,
and you will see that all messages will go correctly to the recipient... It would be great if Mystic could incorporate that on its code.

--- Mystic BBS v1.12 A33 (Windows/64)
* Origin: Saturn's Orbit BBS - Rio de Janeiro, Brasil (21:1/146)

On 05/25/17, Nighthawk said the following...

On 05/24/17, g00r00 said the following...

What is the added functionality that you're looking for?

Mystic's embedded NNTP server is great: fast and reliable.

But it does have a "flaw", which is common to the NNTP protocol:
Using NNTP as a means to access the message base, you can send only messages to All. With JAMNNTPD, when you "follow-up" a message using a news client, it automatically updates the TO: field accordingly.

Why would you say that this is a flaw in the NNTP protocol? Nothing precludes you from setting a To: header in an article; or for that matter, setting an 'X-In-Reply-To:' header that BBS software could interpret as it sees fit.

--- Mystic BBS v1.12 A33 (Windows/32)
* Origin: ACiD Telnet HQ / blackflag.acid.org (21:1/112)

I guess this could be a nice feature, I never thought much about it because folks usually see the messages to someone anyhow.

The reply to all isn't really and issue for me, nor something I'm inclined to change NNTP servers for. Mystics works just fine for me and I use NNTP a lot!



On 05:13 25/05 , Nighthawk wrote:

On 05/24/17, g00r00 said the following...

What is the added functionality that you're looking for?

Mystic's embedded NNTP server is great: fast and reliable.

But it does have a "flaw", which is common to the NNTP protocol: Using
NNTP as a means to access the message base, you can send only messages to All.
With JAMNNTPD, when you "follow-up" a message using a news client, it
automatically updates the TO: field accordingly.

Now that I have finished integrating the Jamnntpd server into my system,
I'll include the fsxNET areas so that my NNTP users can access the network, >and you will see that all messages will go correctly to the recipient... It >would be great if Mystic could incorporate that on its code.

--- Mystic BBS v1.12 A33 (Windows/64)
* Origin: Saturn's Orbit BBS - Rio de Janeiro, Brasil (21:1/146)

--
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)

Now that I have finished integrating the Jamnntpd server into my system, I'll include the fsxNET areas so that my NNTP users can access
the network, and you will see that all messages will go correctly to the recipient... It would be great if Mystic could incorporate that on its code.

I've added that to the todo list but I'll have to research it a bit.

Thank you for the feedback!

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

Why would you say that this is a flaw in the NNTP protocol? Nothing precludes you from setting a To: header in an article; or for that
matter, setting an 'X-In-Reply-To:' header that BBS software could interpret as it sees fit.

Yep, its really up to the client software to supply something like that, I guess. I need to research if there is some sort of standard for this to see what JamNNTP is doing for To fields.

If there is an established way to support To fields, I could certainly add it.

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

Yep, its really up to the client software to supply something like that,
I guess. I need to research if there is some sort of standard for this
to see what JamNNTP is doing for To fields.

The IOS client I use does NOT allow you to specify a "To" field.

So, that wouldnt matter to me.

I just write it to all.



-Nugax

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

On 05/25/17, tenser said the following...

Why would you say that this is a flaw in the NNTP protocol? Nothing precludes you from setting a To: header in an article; or for that
matter, setting an 'X-In-Reply-To:' header that BBS software could interpret as it sees fit.

That's exactly what JAMNNTPD does - what I meant was that Mystic's
embedded NNTP server does not have that functionality...

--- Mystic BBS v1.12 A33 (macOS/64)
* Origin: Chiron, experimental system - Brazil (21:1/146.1)

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

I guess this could be a nice feature, I never thought much about it because folks usually see the messages to someone anyhow.

The reply to all isn't really and issue for me, nor something I'm
inclined to change NNTP servers for. Mystics works just fine for me and
I use NNTP a lot!

Well, it helps tidying up the messages and makes sure that the recipient
is aware that the message is for him/her.

--- Mystic BBS v1.12 A33 (macOS/64)
* Origin: Chiron, experimental system - Brazil (21:1/146.1)

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

Yep, its really up to the client software to supply something like that,
I guess. I need to research if there is some sort of standard for this
to see what JamNNTP is doing for To fields.

If there is an established way to support To fields, I could certainly
add it.

JAMNNTPD has its code available at GitHub:

https://github.com/ftnapps/jamnntpd

I have the Windows binaries... Let me know if you would like to play
around with it.

--- Mystic BBS v1.12 A33 (macOS/64)
* Origin: Chiron, experimental system - Brazil (21:1/146.1)

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

The IOS client I use does NOT allow you to specify a "To" field.

So, that wouldnt matter to me.

What if I told you that JamNNTPD does fix the To: field for you,
regardless of the NNTP client you use?

I have a JamNNTPD client installed on my iPhone, and when I follow-up a message the TO: appears automatically after it's posted. The only "flaw" it
has is that it does not support handles very well, you can notice when I use the NNTP client when you see my real name on it (Flavio Bessa).

--- Mystic BBS v1.12 A33 (macOS/64)
* Origin: Chiron, experimental system - Brazil (21:1/146.1)

On 05/27/17, g00r00 said the following...

I've added that to the todo list but I'll have to research it a bit.

Thank you for the feedback!

Awesome! Happy to help!

--- Mystic BBS v1.12 A33 (macOS/64)
* Origin: Chiron, experimental system - Brazil (21:1/146.1)

Nor do most NNTP clients like this one

On 16:14 07/06 , Nighthawk wrote:

On 05/25/17, tenser said the following...

Why would you say that this is a flaw in the NNTP protocol? Nothing precludes you from setting a To: header in an article; or for that matter, setting an 'X-In-Reply-To:' header that BBS software could interpret as it sees fit.

That's exactly what JAMNNTPD does - what I meant was that Mystic's
embedded NNTP server does not have that functionality...

--- Mystic BBS v1.12 A33 (macOS/64)
* Origin: Chiron, experimental system - Brazil (21:1/146.1)

--
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)

That's a sweet option

On 16:20 07/06 , Nighthawk wrote:

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

The IOS client I use does NOT allow you to specify a "To" field.

So, that wouldnt matter to me.

What if I told you that JamNNTPD does fix the To: field for you,
regardless of the NNTP client you use?

I have a JamNNTPD client installed on my iPhone, and when I follow-up a
message the TO: appears automatically after it's posted. The only "flaw" it >has is that it does not support handles very well, you can notice when I use >the NNTP client when you see my real name on it (Flavio Bessa).

--- Mystic BBS v1.12 A33 (macOS/64)
* Origin: Chiron, experimental system - Brazil (21:1/146.1)

--
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/08/17, Nugax said the following...

That's a sweet option

Indeed, I have been trialing it into my system for a while with good results. A few users have been using clients for Windows, Android and Iphone and participating of a few message areas.

----
Regards from Nighthawk - AKA Flavio Bessa
Sysop of Saturn's Orbit BBS - Rio de Janeiro, Brazil
fcbessa@gmail.com - saturnsorbit.hopto.org

--- Mystic BBS v1.12 A34 (macOS/64)
* Origin: Chiron, orbiting Saturn - Chile (21:1/146.1)

I always use it

On 08:08 28/06 , Nighthawk wrote:

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

That's a sweet option

Indeed, I have been trialing it into my system for a while with good
results. A few users have been using clients for Windows, Android and Iphone >and participating of a few message areas.

----
Regards from Nighthawk - AKA Flavio Bessa
Sysop of Saturn's Orbit BBS - Rio de Janeiro, Brazil
fcbessa@gmail.com - saturnsorbit.hopto.org

--- Mystic BBS v1.12 A34 (macOS/64)
* Origin: Chiron, orbiting Saturn - Chile (21:1/146.1)

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

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