MSGID: 2:5015/46 5e0bad3d
CHRS: CP866 2
TZUTC: 0300
TID: hpt/lnx 1.9.0-cur 17-02-17
Hi Folks,

Here's my recent experience w/ jamnntpd.
Cloned from https://github.com/ftnapps/smapinntpd and built for Ubuntu 14.04.6.

First issue showed up was the message-id format for STAT/ARTICLE/HEAD/BODY,
RFC-3977 says

> A message-id MUST begin with "<", end with ">"  should be wrapped
> with square braces.

Jamnntpd (and smapinntpd) won't understand the message-id w/ square braces but
will be happy w/o. It breaks some NNTP readers which use message-id rather
than message number.

Second issue was w/ posting an article - it will break the JAM database!
* Jamnntpd will not be able to read back posted message (the message counter
remains the same).
* GoldED+/LNX 1.1.5 will show a new completely empty message w/o headers and
body
* Husky HPT 1.9 will core dump while dealing w/ that JAM file (which is
actually bad).

I've also tried smapinntpd from https://github.com/ftnapps/smapinntpd and 
posting to JAM worked for me.

Regards,
Nil
--- GoldED+/LNX 1.1.5
 * Origin: -=NIL BBS=- (2:5015/46)
SEEN-BY: 1/120 123 14/6 15/0 18/0 19/36 34/999 90/1 106/201 116/18
SEEN-BY: 123/0 25 50 140 150 755 128/2 135/300 153/7715 154/10 203/0
SEEN-BY: 221/0 1 6 242 360 222/2 227/114 229/426 452 1014 230/150
SEEN-BY: 230/152 240/1120 5832 249/206 317 250/1 261/38 100 1466 266/512
SEEN-BY: 267/155 275/100 280/464 5003 5555 282/1031 1056 291/1 111
SEEN-BY: 300/4 310/31 317/3 320/119 219 322/757 340/400 342/13 200
SEEN-BY: 423/81 640/305 1138 1321 1384 712/848 801/189 2320/105 3634/0
SEEN-BY: 3634/12 15 27 50 119 5020/1042
PATH: 5015/46 5020/1042 261/38 3634/12 640/1384 221/1 280/464 229/426