Hi All,

I've downloaded and compiled JamNNTPd from:
https://github.com/ftnapps/jamnntpd

It was easy enough to compile on Ubuntu 22.04.3 LTS and configure. I setup a couple of bases as a test and I can see some (but not all) of the messages in Thunderbird. When I post a message GoldED will see that there's a new message but can't display it. Exiting GoldED it warns me that the message base is corrupted.

I've tried making a new test base (creating the JAM base files w/ GoldED) with the same behaviour. GoldED does create the missing *.jlr files so I didn't need to run the (missing) fidoconfig2jamnntpd.pl file referenced in ReadMe_hpt.txt.

Does anyone have any pointers as to what I may be doing wrong?


Jay

... My ex-wife still misses me. But their aim is starting to improve!
--- GoldED+/W64-MSVC 1.1.5-b20180707
* Origin: Northern Realms (21:3/110)

Hello Warpslide,

On Tue, 16 Jan 2024 02:16:22 -0500, you wrote:

I've downloaded and compiled JamNNTPd from: https://github.com/ftnapps/jamnntpd

It was easy enough to compile on Ubuntu 22.04.3 LTS and configure. I
setup a couple of bases as a test and I can see some (but not all) of
the messages in Thunderbird. When I post a message GoldED will see that there's a new message but can't display it. Exiting GoldED it warns me that the message base is corrupted.

I've tried making a new test base (creating the JAM base files w/
GoldED) with the same behaviour. GoldED does create the missing *.jlr files so I didn't need to run the (missing) fidoconfig2jamnntpd.pl file referenced in ReadMe_hpt.txt.

Does anyone have any pointers as to what I may be doing wrong?

First, and really nothing to do with the issues you're having, but give Smapinntpd a try instead. Smapinntpd uses the smapi library which includes newer and probably better JAM support (rather than the ancient jamlib that Jamnntpd uses).

With that said, Jamnntpd/Smapinntpd doesn't work very well with the latest Thunderbird. Not only does the issue you speak of happen almost 100% of the time, but the FROM field ends up using node numbers instead of actual names, also.

Take a look at Claws Mail, Sylpheed, or Pan as a newsreader. I'm using the Windows version of Claws Mail with Smapinntpd (hosted on Linux) and it works great.

Regards,
Nick

... "Take my advice, I don't use it anyway."
--- Claws Mail 4.2.0 (GTK 3.24.38; x86_64-w64-mingw32)
* Origin: _thePharcyde distribution system (Wisconsin) (21:1/200.0)

On Tuesday January 16 2024, Accession said the following...

First, and really nothing to do with the issues you're having, but
give Smapinntpd a try instead. Smapinntpd uses the smapi library which includes newer and probably better JAM support (rather than the
ancient jamlib that Jamnntpd uses).

I seem to have an issue compiling SmapiNNTPd. It says "This program needs SMAPI to run", when I run make linux I see:

make -f Makefile.linux
make[1]: Entering directory '/tmp/smapinntpd/src'
gcc -Wall -Wno-pointer-sign -DPLATFORM_LINUX -D__PROGPROT_H__ -c main.c -o main.o
In file included from main.c:1:
nntpserv.h:22:10: fatal error: smapi/msgapi.h: No such file or directory
22 | #include <smapi/msgapi.h>
| ^~~~~~~~~~~~~~~~
compilation terminated.
make[1]: *** [Makefile.linux:37: main.o] Error 1
make[1]: Leaving directory '/tmp/smapinntpd/src'
make: *** [Makefile:15: linux] Error 2

I've git clone'd https://github.com/huskyproject/smapi.git and moved the smapi/smapi directory to smapinntpd/src so smapi/msgapi.h does exist, I'm not sure why it's saying it doesn't.

Any pointers on getting it compiled?

With that said, Jamnntpd/Smapinntpd doesn't work very well with the
latest Thunderbird. Not only does the issue you speak of happen almost 100% of the time, but the FROM field ends up using node numbers
instead of actual names, also.

Take a look at Claws Mail, Sylpheed, or Pan as a newsreader. I'm using
the Windows version of Claws Mail with Smapinntpd (hosted on Linux)
and it works great.

Thanks for this. I'll check out Claws Mail.


Jay

... I want to be cremated as it is my last hope for a smoking hot body
--- GoldED+/W64-MSVC 1.1.5-b20180707
* Origin: Northern Realms (21:3/110)

Hello Warpslide,

On Wed, 17 Jan 2024 01:00:30 -0500, you wrote:

I seem to have an issue compiling SmapiNNTPd. It says "This program
needs SMAPI to run", when I run make linux I see:

make -f Makefile.linux
make[1]: Entering directory '/tmp/smapinntpd/src'
gcc -Wall -Wno-pointer-sign -DPLATFORM_LINUX -D__PROGPROT_H__ -c main.c
-o main.o
In file included from main.c:1:
nntpserv.h:22:10: fatal error: smapi/msgapi.h: No such file or directory
22 | #include <smapi/msgapi.h>
| ^~~~~~~~~~~~~~~~
compilation terminated.
make[1]: *** [Makefile.linux:37: main.o] Error 1
make[1]: Leaving directory '/tmp/smapinntpd/src'
make: *** [Makefile:15: linux] Error 2

I've git clone'd https://github.com/huskyproject/smapi.git and moved the smapi/smapi directory to smapinntpd/src so smapi/msgapi.h does exist,
I'm not sure why it's saying it doesn't.

Any pointers on getting it compiled?

I had the same issue. It seems you have to compile smapi with 'DYNLIBS=1 LIBDIR=/usr/local/lib' on the make and make install line so that it can share libraries. Just putting the code in a subfolder of smapinntpd (where it seems like it should be) never worked for me, either.

I had tried editing nntpserv.h, msgapi.h and a couple others to point directly to the files they were looking for, which probably isn't proper practice, but I figured I would probably never pull Smapinntpd from github again unless I wanted to start over with the original code, and have updated it for IPv6 support and UTF-8 hackery on my own version here, so I just made sure I could get it to compile, then reverted all of the original files. ;)

Also, if smapi still doesn't want to compile after it finds the libraries, it may depend on other things in the husky project, like huskylib or huskybse. I already have all of this installed as I use it here, but it may be more of a pain for someone who doesn't already use it.

Otherwise, if all of this is just for fun and tinkering, Jamnntpd will probably still do what you want it to, and won't require all of the extra work.

With that said, Jamnntpd/Smapinntpd doesn't work very well with the
latest Thunderbird. Not only does the issue you speak of happen
almost 100% of the time, but the FROM field ends up using node
numbers instead of actual names, also.

Take a look at Claws Mail, Sylpheed, or Pan as a newsreader. I'm
using the Windows version of Claws Mail with Smapinntpd (hosted on
Linux) and it works great.

Thanks for this. I'll check out Claws Mail.

If you don't care for the way it works/looks, Pan would be a great option also, since you're using Ubuntu. I don't have that option, since I'm using my main Windows machine to connect to smapinntpd (hosted on Linux). The Windows version of Pan is outdated and unsupported, and has quite a few bugs I wasn't able to get around.

Regards,
Nick

... "Take my advice, I don't use it anyway."
--- Claws Mail 4.2.0 (GTK 3.24.38; x86_64-w64-mingw32)
* Origin: _thePharcyde distribution system (Wisconsin) (21:1/200.0)

16/01/2024 14:02, Accession wrote:

With that said, Jamnntpd/Smapinntpd doesn't work very well with the latest Thunderbird. Not only does the issue you speak of happen almost 100% of the time, but the FROM field ends up using node numbers instead of actual names, also.

Does your SmapiNNTPd use <z:n/f.p> or <p@f.n.z> addresses in the From field?

Carlos
--- SBBSecho 3.20-Linux
* Origin: Zruspa's BBS - bbs.zruspas.org (21:1/192)

Hello Carlos,

On Wed, 17 Jan 2024 20:35:08 +0100, you wrote:

Does your SmapiNNTPd use <z:n/f.p> or <p@f.n.z> addresses in the From field?

My From field in Claws Mail for this message shows: Carlos Navarro -> Accession, and here are the control lines:

From: "Carlos Navarro -> Accession" <21:1/192>
Subject: Re: JamNNTPd Corrupting Message Bases
Date: Wed, 17 Jan 2024 20:35:08 +0100
Newsgroups: FSX_BBS
X-SMAPI-From: Carlos Navarro <0:0/0.0>
X-SMAPI-To: Accession <0:0/0.0>
X-SMAPI-DateWritten: 17 Jan 24 14:35:08
X-SMAPI-DateArrived: 17 Jan 24 07:40:34
X-SMAPI-Control: @TZUTC: 0100
X-SMAPI-Control: @MSGID: 271.fsx_bbs@2:341/200 2a0d0e9a
X-SMAPI-Control: @REPLY: 21:1/200.0 65a67e52
X-SMAPI-Control: @PID: Synchronet 3.20a-Linux master/483355a47 Jan 7 2024 GCC 12.2.0
X-SMAPI-Control: @TID: SBBSecho 3.20-Linux master/483355a47 Jan 7 2024 GCC 12.2.0
X-SMAPI-Control: @BBSID: ZRUSPAS
X-SMAPI-Control: @CHRS: UTF-8 4

So it looks like it's using <z:n/f.p>, but it looks like it drops it from the actual From column displayed in the newsreader. It seems to carry over the original poster's node number, I believe based off the origin line.. and with the REPLY kludge in tact, and fills out the From field in the header with the node number that was taken out of the newsreader's From column.

This is not the case when using the latest Thunderbird versions, though. For some reason it doesn't use our actual names, but instead you would see something like "1/192 -> 1/200" or something similar in the From column, which leads me to believe there has been something changed in Thunderbird that Jamnntpd/Smapinntpd has not been (nor probably will be) updated to handle.

Regards,
Nick

... "Take my advice, I don't use it anyway."
--- Claws Mail 4.2.0 (GTK 3.24.38; x86_64-w64-mingw32)
* Origin: _thePharcyde distribution system (Wisconsin) (21:1/200.0)

CN> Does your SmapiNNTPd use <z:n/f.p> or <p@f.n.z> addresses in the From
CN> field?

My From field in Claws Mail for this message shows: Carlos Navarro -> Accession, and here are the control lines:

From: "Carlos Navarro -> Accession" <21:1/192>

[...]

So it looks like it's using <z:n/f.p>, but it looks like it drops it from the actual From column displayed in the newsreader. It seems to carry over the original poster's node number, I believe based off the origin line.. and with the REPLY kludge in tact, and fills out the From field in the header with the node number that was taken out of the newsreader's From column.

This is not the case when using the latest Thunderbird versions, though. For some reason it doesn't use our actual names, but instead you would see something like "1/192 -> 1/200" or something similar in the From column, which leads me to believe there has been something changed in Thunderbird that Jamnntpd/Smapinntpd has not been (nor probably will be) updated to handle.

This issue was fixed it JamNNTPd version 1.2 with a patch by Peter Krefting:

https://github.com/ftnapps/jamnntpd/commit/0f66465b4f93cd436b6da19ecad7b05c9133620d

From History.txt:
====================
Changes in version 1.2

- Make From addresses into valid RFC 5322 addresses.

- JamNNTPd traditionally has used Fidonet-style addresses in the From
header. This breaks RFC 5322 and causes some e-mail software (Alpine,
Opera) not to display the sender address properly.

This patch changes the From header to use a valid RFC 5322 syntax,
albeit not a valid Internet e-mail address.

====================

Unfortunately it seems that this patch was not applied to SmapiNNTPd, at
least to the one on the ftnapps repo.

Carlos
--- SBBSecho 3.20-Linux
* Origin: Zruspa's BBS - bbs.zruspas.org (21:1/192)

On Wednesday January 17 2024, Accession said the following...

I had the same issue. It seems you have to compile smapi with
'DYNLIBS=1 LIBDIR=/usr/local/lib' on the make and make install line so that it can share libraries. Just putting the code in a subfolder of smapinntpd (where it seems like it should be) never worked for me,
either.

Hmm, I tried setting DYNLIBS=1 and LIBDIR=${PREFIX}/lib in huskymak.cfg but then hpt complained it couldn't find linked libraries and wouldn't run at all.

Otherwise, if all of this is just for fun and tinkering, Jamnntpd will probably still do what you want it to, and won't require all of the
extra work.

I installed Claws mail for Windows and tried Jamnntpd again with a newly created test base and it still corrupts the base. This is mostly for fun/tinkering and seeing if I could use this from my phone, but Jamnntpd doesn't seem to support MODE READER so it's kind of all for naught anyway.


Jay

... I used to play piano by ear but now I use my hands
--- GoldED+/W64-MSVC 1.1.5-b20180707
* Origin: Northern Realms (21:3/110)

Hello Carlos,

On Wed, 17 Jan 2024 23:09:08 +0100, you wrote:

This issue was fixed it JamNNTPd version 1.2 with a patch by Peter Krefting:

https://github.com/ftnapps/jamnntpd/commit/0f66465b4f93cd436b6da19ecad7b05c9133620d

From History.txt:
====================
Changes in version 1.2

- Make From addresses into valid RFC 5322 addresses.

- JamNNTPd traditionally has used Fidonet-style addresses in the From
header. This breaks RFC 5322 and causes some e-mail software (Alpine,
Opera) not to display the sender address properly.

This patch changes the From header to use a valid RFC 5322 syntax,
albeit not a valid Internet e-mail address.

====================

By all means you can go ahead and give it a try. But in my installations of both versions of Jamnntpd (1.0 by Johan Billings, and the updated 1.3), neither of them worked properly with Thunderbird. So maybe that patch was a fix for something that happened previously (only Opera and Alpine are mentioned in the commit), and then Thunderbird kept going on their own path into the future which could have broken something again. *shrug*

That's specifically why I went with Smapinntpd, and because the JAM libraries are newer, better and more up to date than the old jamlib that Jamnntpd uses.

Unfortunately it seems that this patch was not applied to SmapiNNTPd, at least to the one on the ftnapps repo.

The ftnapps repo is probably never going to be updated/maintained again. I believe "Jame" or RJ Clay (the main guy) has passed on, and I'm unsure anyone else that was able to commit to that repo are around to do anything about it these days.

I can definitely try to take a look and add this patch (or at least try to modify it - since most, if not all variables and other wording has changed between Jamnntpd and Smapinntpd) to my custom version of Smapinntpd. It seems to ONLY be Thunderbird that acts wierd. Everything else I've tried (both GUI and console, like slrn) have worked fine. Granted, I haven't tried Opera or Alpine, because ... I have no interest in them. ;)

Regards,
Nick

... "Take my advice, I don't use it anyway."
--- Claws Mail 4.2.0 (GTK 3.24.38; x86_64-w64-mingw32)
* Origin: _thePharcyde distribution system (Wisconsin) (21:1/200.0)

Hello Warpslide,

On Wed, 17 Jan 2024 16:38:00 -0500, you wrote:

On Wednesday January 17 2024, Accession said the following...

I had the same issue. It seems you have to compile smapi with
'DYNLIBS=1 LIBDIR=/usr/local/lib' on the make and make install line
so that it can share libraries. Just putting the code in a
subfolder of smapinntpd (where it seems like it should be) never
worked for me, either.

Hmm, I tried setting DYNLIBS=1 and LIBDIR=${PREFIX}/lib in huskymak.cfg
but then hpt complained it couldn't find linked libraries and wouldn't
run at all.

Did you recompile hpt (as well as everything else) to use the dynamic libraries? I believe once you change those two settings in huskymak.cfg you can just run "Build.sh" again to recompile everything. I was under the assumption that you only cloned the smapi portion of the husky project and had nothing else. If you're using the whole project, you probably have to rebuild it all. Sorry.

Otherwise, if all of this is just for fun and tinkering, Jamnntpd
will probably still do what you want it to, and won't require all
of the extra work.

I installed Claws mail for Windows and tried Jamnntpd again with a newly created test base and it still corrupts the base. This is mostly for fun/tinkering and seeing if I could use this from my phone, but Jamnntpd doesn't seem to support MODE READER so it's kind of all for naught anyway.

Which version of Jamnntpd are you trying this with? 1.3?
Did you remember to create the 4th jam base file that Jamnntpd doesn't do?

To be honest, and no offense to the guy (and RIP), but once RJ took it over from Johan it seems like he broke more than he fixed. I had luck in the past with Johan's original version (v1.0), but I moved away from that quite some time ago.

Regards,
Nick

... "Take my advice, I don't use it anyway."
--- Claws Mail 4.2.0 (GTK 3.24.38; x86_64-w64-mingw32)
* Origin: _thePharcyde distribution system (Wisconsin) (21:1/200.0)

On 1/17/2024 1:35 PM, 211/192 wrote:

Does your SmapiNNTPd use <z:n/f.p> or <p@f.n.z> addresses in the From field?

This message I'm replying to, and as you can see above "211/192 wrote", my From: field is showing 211/192.

Was this what was addressed in the v1.2 patch?

Honestly, I haven't seen Thunderbird work with Jamnntpd in that regard for years.
--- Mozilla Thunderbird
* Origin: _thePharcyde distribution system (Wisconsin) (21:1/200.0)

Hello Warpslide,

On Wed, 17 Jan 2024 16:38:00 -0500, you wrote:

I installed Claws mail for Windows and tried Jamnntpd again with a newly created test base and it still corrupts the base. This is mostly for fun/tinkering and seeing if I could use this from my phone, but Jamnntpd doesn't seem to support MODE READER so it's kind of all for naught anyway.

I just remembered something. The issues we were having with Jamnntpd corrupting message bases was because we were compiling it on 64bit Linux. So it could be a 64bit issue altogether. That's why a couple of us ended up going with Smapinntpd instead, since that works on 64bit.

I'm guessing if you were to compile it on 32bit, Jamnntpd would work better. ;)

With that said, if you want to continue messing around with Smapinntpd, I can help you more with that.

Regards,
Nick

... "Take my advice, I don't use it anyway."
--- Claws Mail 4.2.0 (GTK 3.24.38; x86_64-w64-mingw32)
* Origin: _thePharcyde distribution system (Wisconsin) (21:1/200.0)

17/01/2024 19:07, Accession wrote:

CN> Does your SmapiNNTPd use <z:n/f.p> or <p@f.n.z> addresses in the From
CN> field?

This message I'm replying to, and as you can see above "211/192 wrote", my From: field is showing 211/192.

Was this what was addressed in the v1.2 patch?

I think so. I just checked another sysop's JamNNTPd 1.0 server and it
has exactly that same issue with the latest Thunderbird.

Honestly, I haven't seen Thunderbird work with Jamnntpd in that regard for years.

Works fine with mine. It's JamNNTPd 1.3 (with a couple small patches), compiled for Win32.

Carlos
--- SBBSecho 3.20-Linux
* Origin: Zruspa's BBS - bbs.zruspas.org (21:1/192)

Hello Carlos,

On Thu, 18 Jan 2024 03:45:48 +0100, you wrote:

This message I'm replying to, and as you can see above "211/192
wrote", my From: field is showing 211/192.

Was this what was addressed in the v1.2 patch?

I think so. I just checked another sysop's JamNNTPd 1.0 server and it
has exactly that same issue with the latest Thunderbird.

Works fine with mine. It's JamNNTPd 1.3 (with a couple small patches), compiled for Win32.

When you started doing those small patches in the JAMNNTPD echo earlier, I looked back at some old netmails between myself and another sysop when we were also trying to set these up. Now I remember us discussion the fact that Jamnntpd works compiled on 32bit, but is buggy as all get out on 64bit (it compiles, but then you have problems). So I'm guessing that's where Warpslide is having his issues.

Smapinntpd works fine on 64bit Linux. So we have a couple options.. If you (or someone) is able to make Jamnntpd 1.3 work better on 64bit, or continue with Smapinntpd and try to modify it with something similar to the Jamnntpd 1.2 patch so that the From field is fixed.

With Smapinntpd, I already have a "CHRS: UTF-8 4" kludge fix (which is kind of like the one you posted today), I've also added IPv6 support, and I just today added your fix for MODE READER, although I'm unsure Smapinntpd actually needed it since I haven't seen that error in the logs since I started using it.

Regards,
Nick

... "Take my advice, I don't use it anyway."
--- Claws Mail 4.2.0 (GTK 3.24.38; x86_64-w64-mingw32)
* Origin: _thePharcyde distribution system (Wisconsin) (21:1/200.0)

On Wed, 17 Jan 2024 13:35:24 -0600
"Accession -> Warpslide" <0@200.1.21> wrote:

I just remembered something. The issues we were having with Jamnntpd corrupting message bases was because we were compiling it on 64bit
Linux. So it could be a 64bit issue altogether. That's why a couple
of us ended up going with Smapinntpd instead, since that works on
64bit.

I'm guessing if you were to compile it on 32bit, Jamnntpd would work
better. ;)

With that said, if you want to continue messing around with
Smapinntpd, I can help you more with that.

Ok, I spun up a Ubuntu 16 32bit VM, compiled JamNNTPd there and
copied the binaries over and it seems to be working much better.

How would one add these READER & IPv6 patches?


Jay

---
* Origin: Northern Realms (21:3/110)

Hello Warpslide,

On Wed, 17 Jan 2024 23:24:10 -0500, you wrote:

I'm guessing if you were to compile it on 32bit, Jamnntpd would work
better. ;)

With that said, if you want to continue messing around with
Smapinntpd, I can help you more with that.

Ok, I spun up a Ubuntu 16 32bit VM, compiled JamNNTPd there and
copied the binaries over and it seems to be working much better.

X-SMAPI-Control: @PID: JamNNTPd/Linux 1

Looks like you're using Johan's version now? Now that you have it working, you may want to use 1.3 instead.

And copied what binaries over to where? Or did you mean config files? Cuz you definitely shouldn't be copying binaries from one architecture to another. ;)

How would one add these READER & IPv6 patches?

The MODE READER patch/hack was posted to the JAMNNTPD echo on Fidonet earlier today. As for the IPv6 stuff, here's the diffs I used to patch mine. You'll notice this is from an even more modified version that I'm currently trying to get my hands on, but the guy has been unreachable for awhile.

That said, you can go to the lines mentioned, and then scroll a little bit for the exact lines you need to remove. They won't be on the exact lines mentioned and some lines calling for removal may not even be in the original code at all (like lines containing cfg_hostname and cfg_ipaddr, for example), since these diffs are from a more modified version. Only remove (-) and add (+) the lines specified, or it won't work. And some lines definitely wrapped below when I pasted it.

=== [ CUT ] ========================================================
diff -urN ganjanntpd-1.9/main.c ganjanntpd-1.9-ipv6/main.c
--- ganjanntpd-1.9/main.c 2017-02-27 23:41:23.000000000 +0300
+++ ganjanntpd-1.9-ipv6/main.c 2017-03-13 12:59:42.872717283 +0300
@@ -223,16 +223,6 @@

cfg_logfile=argv[++c];
}
- else if(stricmp(arg,"-ip")==0 || stricmp(arg,"-ipaddress")==0)
- {
- if(c+1 == argc)
- {
- printf("Missing argument for %s%s\n",argv[c],src);
- return(FALSE);
- }
-
- cfg_ipaddr=argv[++c];
- }
else if(stricmp(arg,"-config")==0)
{
if(filename)
@@ -359,7 +349,6 @@
fprintf(fp,"users \"%s\"\n",cfg_usersfile);
fprintf(fp,"xlat \"%s\"\n",cfg_xlatfile);
fprintf(fp,"hostname \"%s\"\n",cfg_hostname);
- fprintf(fp,"ipaddress \"%s\"\n",cfg_ipaddr);
fprintf(fp,"logfile \"%s\"\n",cfg_logfile);
fprintf(fp,"%snoecholog\n",cfg_noecholog ? "" : "#");
fprintf(fp,"%sdebug\n",cfg_debug ? "" : "#");
@@ -401,7 +390,7 @@
{
SOCKET sock;
int error,res;
- struct soc

On Wednesday January 17 2024, Accession said the following...

Ok, I spun up a Ubuntu 16 32bit VM, compiled JamNNTPd there and
copied the binaries over and it seems to be working much better.

X-SMAPI-Control: @PID: JamNNTPd/Linux 1

Looks like you're using Johan's version now? Now that you have it
working, you may want to use 1.3 instead.

I've just been using this one:
https://github.com/ftnapps/jamnntpd

The page references v1.3 but when I git clone it, I guess I'm getting v1?

Is there another place to get 1.3?

And copied what binaries over to where? Or did you mean config files?
Cuz you definitely shouldn't be copying binaries from one architecture
to another. ;)

I compiled on Ubuntu 16 32bit and copied the binaries over to Ubuntu 22 64bit. Crude but effective. :)

The MODE READER patch/hack was posted to the JAMNNTPD echo on Fidonet earlier today. As for the IPv6 stuff, here's the diffs I used to patch mine. You'll notice this is from an even more modified version that
I'm currently trying to get my hands on, but the guy has been
unreachable for awhile.

Cool, I'll check that out this evening.

That said, you can go to the lines mentioned, and then scroll a little
bit for the exact lines you need to remove. They won't be on the exact lines mentioned and some lines calling for removal may not even be in
the original code at all (like lines containing cfg_hostname and cfg_ipaddr, for example), since these diffs are from a more modified version. Only remove (-) and add (+) the lines specified, or it won't work. And some lines definitely wrapped below when I pasted it.

I've never manually patched something before, this sounds more like a weekend thing! ;)

Right now I'm just putting the IPv4 addy in the clients which seems to work well enough.

And make sure sysctl net.ipv6.bindv6only=0 is set for ipv4 to work as well.

Good luck!

Thanks so much for your help with this, much appreciated!


Jay

... I want to be cremated as it is my last hope for a smoking hot body
--- GoldED+/W64-MSVC 1.1.5-b20180707
* Origin: Northern Realms (21:3/110)

On Wednesday January 17 2024, Accession said the following...

The MODE READER patch/hack was posted to the JAMNNTPD echo on Fidonet earlier today. As for the IPv6 stuff, here's the diffs I used to patch mine. You'll notice this is from an even more modified version that
I'm currently trying to get my hands on, but the guy has been
unreachable for awhile.

200 Welcome to JamNNTPd/Linux 1.3 (posting may or may not be allowed,
try your luck)

< AUTHINFO USER warpslide

381 Received login name, now send password

< AUTHINFO PASS ...
Logged in as warpslide

281 Authentication accepted

< MODE READER

200 Server ready - posting allowed

< LIST ACTIVE

215 List of newsgroups follows
FSX_TST 1004 1 y
FSX_BBS 839 1 y
.

< LIST NEWSGROUPS

215 List of newsgroups follows
FSX_TST
FSX_BBS
.

Thanks again, you're awesome!


Jay

... I want to be cremated as it is my last hope for a smoking hot body
--- GoldED+/W64-MSVC 1.1.5-b20180707
* Origin: Northern Realms (21:3/110)

Hello Warpslide,

On Thu, 18 Jan 2024 01:28:58 -0500, you wrote:

I've just been using this one:
https://github.com/ftnapps/jamnntpd

The page references v1.3 but when I git clone it, I guess I'm getting v1?

Is there another place to get 1.3?

I would imagine you're using the right one. I took a look at nntpserv.h and it shows:

#define SERVER_NAME "JamNNTPd/" PLATFORM_NAME
#define SERVER_VERSION "1.3"
#define SERVER_PIDVERSION "1"

So that's why it's showing you using Jamnntpd/Linux 1 instead of 1.3. In most other versions those two numbers are the same. Not a big deal, though.

I compiled on Ubuntu 16 32bit and copied the binaries over to Ubuntu 22 64bit. Crude but effective. :)

Ah, as long as it worked, I guess you're all good!

I actually tried enabling multilib on my 64bit Archlinux, and installed 32bit libraries. Then added "-m32" to Makefile.linux in the source directory as well as the jamlib directory.. and after a successful compile of Jamnntpd 1.3, it was a *little* better, but it was still broken. :(

I think I'm just going to stick with Smapinntpd and see if I can get the From field working properly in Thunderbird, some day.. maybe. lol

I've never manually patched something before, this sounds more like a weekend thing! ;)

It's not too difficult. Just pay attention to detail, back up the original, and make sure you don't make any typos. ;)

Thanks so much for your help with this, much appreciated!

No problem. Glad you got it working!

Regards,
Nick

... "Take my advice, I don't use it anyway."
--- Claws Mail 4.2.0 (GTK 3.24.38; x86_64-w64-mingw32)
* Origin: _thePharcyde distribution system (Wisconsin) (21:1/200.0)

Hello Warpslide,

On Thu, 18 Jan 2024 02:05:36 -0500, you wrote:

< MODE READER

200 Server ready - posting allowed

Looks like you got it!

Thanks again, you're awesome!

Credit goes to Carlos for that one. ;)

Regards,
Nick

... "Take my advice, I don't use it anyway."
--- Claws Mail 4.2.0 (GTK 3.24.38; x86_64-w64-mingw32)
* Origin: _thePharcyde distribution system (Wisconsin) (21:1/200.0)

Wed, 17 Jan 2024 11:09:50 -0600 "Accession" (21:1/200) wrote:

The ftnapps repo is probably never going to be updated/maintained
again. I believe "Jame" or RJ Clay (the main guy) has passed on,

Yes, :-( I had read about it somewhere else...

and I'm unsure anyone else that was able to commit to that repo are
around to do anything about it these days.

I don't know either. Jame is the only public member of
github.com/ftnapps

But I suppose that anyone could fork it or start another repo...

I can definitely try to take a look and add this patch (or at least
try to modify it - since most, if not all variables and other wording
has changed between Jamnntpd and Smapinntpd) to my custom version of Smapinntpd.

I see there are lots of differences. Good luck! ;-)

Carlos
--- SBBSecho 3.20-Linux
* Origin: Zruspa's BBS - bbs.zruspas.org (21:1/192)

Wed, 17 Jan 2024 15:16:42 -0600 "Accession" (21:1/200) wrote:

With Smapinntpd, I already have a "CHRS: UTF-8 4" kludge fix (which
is kind of like the one you posted today), I've also added IPv6
support, and I just today added your fix for MODE READER, although
I'm unsure Smapinntpd actually needed it since I haven't seen that
error in the logs since I started using it.

I had to fix the MODE READER issue so that I could access my JamNNTPd
server with PhoNews, an Android app.

Carlos
--- SBBSecho 3.20-Linux
* Origin: Zruspa's BBS - bbs.zruspas.org (21:1/192)

On Wed, 17 Jan 2024 17:32:32 -0600
"Accession -> Warpslide" <0@200.1.21> wrote:

As for the IPv6 stuff, here's the diffs I used to patch mine.

And make sure sysctl net.ipv6.bindv6only=0 is set for ipv4 to work as
well.

It looks like I didn't muck it up too badly...

19-Jan-24 17:13:07 JamNNTPd/Linux 1.3 is running on port 5000
19-Jan-24 17:13:07 Compiled Jan 19 2024 16:56:18
19-Jan-24 17:16:20 (2607:fea8:ab00:8b4::2) Connection established to 2607:fea8:ab00:8b4:7de8:d952:efad:1dfd
(2607:fea8:ab00:8b4::2) > 200 Welcome to JamNNTPd/Linux 1.3/IPv6
(posting may be allowed)
(2607:fea8:ab00:8b4::2) < AUTHINFO USER warpslide
(2607:fea8:ab00:8b4::2) > 381 Received login name, now send password (2607:fea8:ab00:8b4::2) < AUTHINFO PASS ...
19-Jan-24 17:16:20 (2607:fea8:ab00:8b4::2) Logged in as warpslide (2607:fea8:ab00:8b4::2) > 281 Authentication accepted
(2607:fea8:ab00:8b4::2) < MODE READER
(2607:fea8:ab00:8b4::2) > 200 Server ready - posting allowed (2607:fea8:ab00:8b4::2) < GROUP NETMAIL
(2607:fea8:ab00:8b4::2) > 211 17 1 17 NETMAIL Group selected (2607:fea8:ab00:8b4::2) < GROUP fsx_bbs
(2607:fea8:ab00:8b4::2) > 211 849 1 849 fsx_bbs Group selected (2607:fea8:ab00:8b4::2) < GROUP min_hub
(2607:fea8:ab00:8b4::2) > 211 88 1 88 min_hub Group selected (2607:fea8:ab00:8b4::2) < GROUP PERSONAL.MAIL
(2607:fea8:ab00:8b4::2) > 211 1 1 1 PERSONAL.MAIL Group selected (2607:fea8:ab00:8b4::2) < GROUP NNTPTEST
(2607:fea8:ab00:8b4::2) > 211 3 1 3 NNTPTEST Group selected (2607:fea8:ab00:8b4::2) < GROUP jamnntpd
(2607:fea8:ab00:8b4::2) > 211 42 1 42 jamnntpd Group selected
19-Jan-24 17:16:21 (2607:fea8:ab00:8b4::2) Connection closed

One thing I notice is now any IPv4 addresses are prefixed with ::ffff:
before the actual IP:

(::ffff:127.0.0.1:48724) < AUTHINFO USER warpslide
(::ffff:127.0.0.1:48724) > 381 Received login name, now send password (::ffff:127.0.0.1:48724) < AUTHINFO PASS ...
19-Jan-24 17:18:37 (::ffff:127.0.0.1:48724) Logged in as warpslide (::ffff:127.0.0.1:48724) > 281 Authentication accepted

But both still work, which is awesome.


Jay

---
* Origin: Northern Realms (21:3/110)

Hello Carlos,

On Sat, 20 Jan 2024 03:45:26 +0100, you wrote:

But I suppose that anyone could fork it or start another repo...

That's true. Ready to take it on? Jamlib needs 64bit compatibility. There's the first feature request. I had forgotten about that. That is why Jamnntpd hasn't worked for me for years. ;)

I can definitely try to take a look and add this patch (or at least
try to modify it - since most, if not all variables and other wording
has changed between Jamnntpd and Smapinntpd) to my custom version of
Smapinntpd.

I see there are lots of differences. Good luck! ;-)

I saw that too. So I tried a search and replace of the string Krefting added, and when I realized it was in like 5 or 6 different places in Smapinntpd already, figured it probably wouldn't work. Tried it anyways, compiled, and nothing changed. ;)

Regards,
Nick

... "Take my advice, I don't use it anyway."
--- Claws Mail 4.2.0 (GTK 3.24.38; x86_64-w64-mingw32)
* Origin: _thePharcyde distribution system (Wisconsin) (21:1/200.0)

Sorry for my previous replies being addressed to All. I tried using
Claws Mail but it seems it doesn't work well with Synchronet's NNTP
server (or I didn't set it up properly).

19/01/2024 23:41, Accession wrote:

CN> But I suppose that anyone could fork it or start another repo...

That's true. Ready to take it on? Jamlib needs 64bit compatibility. There's the first feature request. I had forgotten about that. That is why Jamnntpd hasn't worked for me for years. ;)

:-) Sorry, I'm no C programmer. I'm only doing small, easy patches for
now...

Carlos
--- SBBSecho 3.20-Linux
* Origin: Zruspa's BBS - bbs.zruspas.org (21:1/192)

Hello Carlos,

On Sat, 20 Jan 2024 17:08:42 +0100, you wrote:

Sorry for my previous replies being addressed to All. I tried using
Claws Mail but it seems it doesn't work well with Synchronet's NNTP
server (or I didn't set it up properly).

I think Synchronet's NNTP server does that by design? As well as most NNTP related things (it may even be a standard whereas Jam/Smapinntpd breaks that to add some kind of TO field. No worries, I was just trying to decipher which client(s) you were using at the time, since there's no PID or tearline.

That's true. Ready to take it on? Jamlib needs 64bit compatibility.

There's the first feature request. I had forgotten about that. That is
why Jamnntpd hasn't worked for me for years. ;)

:-) Sorry, I'm no C programmer. I'm only doing small, easy patches for now...

Same here, which makes fixing things much more difficult. ;)

Regards,
Nick

... "Take my advice, I don't use it anyway."
--- Claws Mail 4.2.0 (GTK 3.24.38; x86_64-w64-mingw32)
* Origin: _thePharcyde distribution system (Wisconsin) (21:1/200.0)