MSGID: 1:154/10 66135716
REPLY: 2:341/234.1 66125a27
PID: SmapiNNTPd/Linux 2.3.4
CHRS: UTF-8 4
TZUTC: -0500
TID: hpt/lnx 1.9 2024-02-05
On Sun, 7 Apr 2024 15:32:20 +0200, you wrote:

 CN> 31 Mar 2024 16:20, you wrote to me:

 CN>>>   Can you please quote-reply this message with slrn?

 CN>>> --- GoldED+/W32-MSVC 1.1.5-b20180707
 CN>>>   * Origin: cyberiada (2:341/234.1)

 NB>> Not sure how Smapinntpd will process it, but here quoting this I see
 NB>> the extra space before the origin line as well. Otherwise, here is
 NB>> quote-reply you are looking for. Everything above was quoted as-is,
 NB>> with no manual intervention by me. So if there's anything unusual it
 NB>> is either slrn (which I've seen no issues with yet - they have all
 NB>> been TB related), or Smapinntpd itself.

 CN> Thank you Nick. So it's not only TB... slrn also adds (or keeps) the
 CN> extra space in quotes.

Not sure what it's doing, exactly. I don't see the extra space in Golded or
tin, but I do see it in slrn and TB. Must be specific to only some newsreaders.

 CN> I don't know if the way they do is correct. If it is, then
 CN> Smapi/JamNNTPd should remove those stuffed spaces from the quotes when
 CN> posting to the messagebase. Either way, I'm working on a fix.

Testing it here as well. Thanks for the updates!

Regards,
Nick

... Take my advice, I don't use it anyway.
--- Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:115.0) Gecko/20100101 Thunderb
 * Origin: _thePharcyde distribution system (Wisconsin) (1:154/10)
SEEN-BY: 15/0 90/1 103/705 105/81 106/201 120/616 123/10 124/5016
SEEN-BY: 128/260 135/220 225 153/757 7715 154/10 30 40 50 700 203/0
SEEN-BY: 218/700 220/90 221/0 6 226/30 227/114 229/110 112 113 206
SEEN-BY: 229/307 317 426 428 470 664 700 240/1120 5832 266/512 280/464
SEEN-BY: 280/5003 5555 282/1038 291/111 292/8125 301/1 310/31 320/219
SEEN-BY: 322/757 341/66 234 342/200 396/45 423/120 460/58 256 1124
SEEN-BY: 467/888 633/280 712/848 770/1 2320/105 3634/12 5020/400 5054/30
PATH: 154/10 280/464 460/58 229/426