REPLY: 2:221/1.0 68d25876
MSGID: 2:5015/46 68d2a4db
CHRS: CP866 2
TZUTC: 0300
TID: hpt/lnx 1.9 
Hello, Tommi!

Tuesday September 23 2025 11:21, from Tommi Koivula -> Nil Alexandrov:

 NA>> X-SMAPI-To: Nil A <2:5001/100.1>
 TK> I have 'fixed' this in the past, removed the ftn address part. :) I

The bug in the code is that it takes From field from the Origin line but later
it will override with the From field from the JAM/Squish database which is not
set right usually.

> # Get address from the Origin line instead of the  OADDRESS  field
> # of  the JAM message header. This option makes SmapiNNTPd slower, but
> # may be useful if your  tosser  does  not  set  the  OADDRESS field.
> readorigin

Also, I like the idea of the readorigin option in the config file.
Unfortunately, it is not fully implemented.

 TK> think these X-SMAPI-* fields are only for information.. ?

Correct, for those who are interested in original FTN headers. I am thinking
of writing a mobile app using the AI help (cause I have no experience in GUI,
mobile, etc) that can work over the NNTP protocol and understand different
NNTP<->FTN gateway software that exists today, so that the *normal* FTN
headers are displayed instead of RFC representation.

Best Regards, Nil
--- GoldED+/LNX 1.1.5-b20240306
 * Origin: ChatGPT can make mistakes. Check important info. (2:5015/46)
SEEN-BY: 1/19 16/0 19/10 37 50/109 105/81 106/201 123/130 128/187
SEEN-BY: 129/14 142/104 153/757 7715 154/10 110 203/0 218/700 840
SEEN-BY: 221/1 6 242 360 226/30 227/114 229/110 206 317 426 428 470
SEEN-BY: 229/664 700 705 240/1120 5832 266/512 280/464 5003 291/111
SEEN-BY: 301/1 320/119 219 319 2119 322/757 762 335/364 341/66 234
SEEN-BY: 342/200 396/45 423/81 460/58 633/280 712/848 902/26 5015/46
SEEN-BY: 5015/255 5020/846 1042 4441 5030/49 5054/8 5058/104 5061/133
SEEN-BY: 5075/128 5083/1 444 6035/66
PATH: 5015/46 5020/1042 221/6 1 320/219 229/426