BBS:      TELESC.NET.BR
Assunto:  JamNNTPd updates
De:       Stephen Walsh
Data:     Mon, 23 Feb 2026 16:16:24 +1100
-----------------------------------------------------------

Hello Tommi!

22 Feb 26 09:07, you wrote to me:

 CN>>>>  CN>> .... This is intended to be a tagline.
 CN>>>> BTW, an extra dot was inserted there. :-|
 SW>>
 TK>>> I also noticed that. PyGate in not yet to displace Jamnntpd as a
 TK>>> nntp reader. :)
 SW>>
 SW>> It's not even designed to do that, so you get to keep the broken
 SW>> bits!

 TK> But PyGate is designed to post messages to NNTP server. It should take
 TK> into consideration the special case of a dot as a first character.

 TK> It's not a big deal. We can keep the broken bits. ;)

 TK> You can also see rfc3977 if you wish.

### Version 1.5.12 (February 23, 2026)

#### Double Dot-Stuffing Fix (RFC 3977 Compliance)
Fixed a bug where lines starting with a dot in FidoNet messages had an extra dot
added when gated to NNTP, violating RFC 3977 s3.1.1.

Result: a FidoNet body line `. 1` became `... 1` on the wire. INN stripped one dot
per RFC 3977 and stored `.. 1`, so the user saw an extra leading dot on every
dot-prefixed line.

Fix: removed the dot-stuffing block from `build_nntp_article()`. Dot-stuffing is a
wire-level transport encoding and belongs only in `post()`. Article content must
contain literal dots; `post()` handles the protocol escaping.





Stephen


--- GoldED+/LNX 1.1.5-b20250409
 * Origin: Dragon's Lair ---:- dragon.vk3heg.net -:--- Prt: 6800 (3:633/280)

-----------------------------------------------------------
[Voltar]