Subj : JamNNTPd Corrupting Message Bases
To   : Carlos Navarro
From : Accession
Date : Wed Jan 17 2024 03:16 pm

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?

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

 CN> Works fine with mine. It's JamNNTPd 1.3 (with a couple small patches),
 CN> 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)

.