MSGID: 2:221/0.0 65c5c08c
REPLY: 1:154/10 65c54aa8
PID: JamNNTPd/Linux32/IPv6 ubi386 20240208
NOTE: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:115.0) Gecko/20100101
Thunderbird/115.7.0.
CHRS: UTF-8 4
TZUTC: 0200
TID: hpt/lnx 1.9 2024-02-05
On 08.02.2024 23:42, Nicholas Boel wrote:

>   CN> I think I managed to fix the issues that Smapi/JamNNTPd have with lines
>   CN> starting with a dot.
>
> I had asked about that at one point, when I discovered I only need to
> put two dots at the beginning of a tearline and Smapinntpd will add a
> third. Is that not an NNTP standard? I thought I read about that somewhere...

It is part of the nntp standard during the nntp transfer, but it is NOT needed
to remove/add the dots in fido msgbase. :)

https://www.w3.org/Protocols/rfc977/rfc977.html

=== Cut ===

   If the text contained a period as the first character of the text
   line in the original, that first period is doubled.  Therefore, the
   client must examine the first character of each line received, and
   for those beginning with a period, determine either that this is the
   end of the text or whether to collapse the doubled period to a single
   one.

=== Cut ===

'Tommi

---
 * Origin: jamnntpd/lnx (2:221/0.0)
SEEN-BY: 15/0 90/1 103/705 105/81 106/201 124/5016 128/260 135/225
SEEN-BY: 153/757 7715 154/10 30 203/0 218/700 221/1 6 242 360 226/30
SEEN-BY: 227/114 229/110 112 113 206 307 317 426 428 470 664 700 240/1120
SEEN-BY: 240/5832 266/512 280/464 5003 5555 282/1038 291/111 292/8125
SEEN-BY: 301/1 310/31 320/219 322/757 341/66 234 342/200 396/45 423/81
SEEN-BY: 423/120 460/58 256 1124 467/888 633/280 712/848 770/1 5020/400
SEEN-BY: 5054/30
PATH: 221/1 280/464 460/58 229/426