Hi Nil.

06 Dec 22 15:43:40, you wrote to me:

 PH>>> I'm starting to see this error in my logs
 PH>>> A Dec:04:2022:21:23:21  JAM ERROR: wrongly sized subfield
 PH>>> occured! is the base corrupt? How best to resolve?

 NA> The JAM base is definitely corrupted here, but the question is how
 NA> you'vee ended up like this then?

Good question indeed. I cannot remember how and when and which system I saw that happening. :(

 NA> Are you guys running some software not compatible with 64bit?
 NA> I remember seeing this with the original jamlib which was a part of
 NA> jamnntpd for example, that only worked on 32-bit machines or you have
 NA> to compile it with -m32 flag.

JamNNTPd compiled 64bit is broken for sure. I can tell that JamNNTPd works fine in 32bit systems here like OS/2, Raspbian/32bit and Cygwin32. The latest compiled and installed in 64bit windows.

I run SmapiNNTPd/64bit in Debian10/64bit with Golded/64bit and Husky/64bit. All compiled in that system, works fine.

 TK>>  You could try to delete those empty messages
 TK>> with GoldED and then run "sqpack NETMAIL".

 NA> That sounds like a workaround in absence of the database fix utility.

The only problem running SQPACK is that it always renumbers the message base. Not acceptable with nntp clients. :(

'Tommi

---