REPLY: 2:335/364.1 5e0c7cd8
MSGID: 2:5015/46 5e0e5cd7
CHRS: CP866 2
TZUTC: 0300
TID: hpt/lnx 1.9.0-cur 17-02-17
Hello, Fabio!

Wednesday January 01 2020 12:04, from Fabio Bizzi -> Nil Alexandrov:

 FB> Smapinntp coredumps randomly on my system (devuan ascii x64).

If you can reproduce the crash, then submit a bug report.
I've seen a coredump inside the smapi library itself when opening a corrupted
JAM database file (after jamnntpd 64bit mess).

 FB> But the big issue also with 32 bit binaries on a 64 bit system is that
 FB> the answering in an echo conference doesnt put the right name in the
 FB> To: field.

Does your NNTP client provide the 'X-Comment-To:' header?

Just tested with NewsTapLite for iOS and SmapiNNTPd.
NewsTapLite passes the X-Comment-To:' and SmapiNNTPd puts it to the 'To:' FTN
field.

 FB> With some version of jamnntpd the answer is always To:ALL with others
 FB> the field is left empty. :(

Reply (which is called a follow-up in NNTP/Usenet world) will put the right
'To:' when I post from the latest Thunderbird, cannot verify now, probably it
passes the X-Comment-To as well.

Do you expect that jamnntpd/smapinntpd would go ahead and find out the name
from the original message to which the reply is being posted?

Best Regards, Nil
--- GoldED+/LNX 1.1.5
 * Origin: -=NIL BBS=- (2:5015/46)
SEEN-BY: 1/123 15/0 19/36 34/999 57/0 90/1 106/201 116/18 123/140
SEEN-BY: 128/2 153/250 757 7715 154/10 203/0 220/70 221/0 222/2 227/114
SEEN-BY: 229/426 452 1014 230/150 152 240/5832 249/206 317 250/1 261/38
SEEN-BY: 261/100 1466 266/512 267/155 800 275/100 280/464 5003 5555
SEEN-BY: 282/1031 1056 291/1 111 310/31 317/3 320/119 219 322/757
SEEN-BY: 340/400 342/13 200 633/280 640/1321 712/848 770/0 1 100 340
SEEN-BY: 772/0 1 210 500 801/189 2320/105 3634/12 5020/1042
PATH: 5015/46 5020/1042 261/38 712/848 770/1 310/31 280/464 229/426