Just a sample of the Echomail archive
[ << oldest | < older | list | newer > | newest >> ]
|  Message 2156  |
|  Tommi Koivula to Nil Alexandrov  |
|  Field TO in reply message  |
|  03 Jan 20 09:42:14  |
 MSGID: 2:221/0 5e0ef052 REPLY: 2:5015/46 5e0ed551 PID: SmapiNNTPd/Linux-Pi/IPv6 1.3 20191227 EID: Mozilla/5.0 (Windows NT 5.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0 CHRS: IBMPC 2 TZUTC: 0200 TID: hpt/lnx 1.9.0-cur 2019-12-05 On 03.01.2020 8:21, Nil Alexandrov - Fabio Bizzi : NA> I have looked into the implementation details of what goes into NA> Fidonet 'To' field when you follow-up on (reply to) a message in NA> jamnntpd/smapinntpd. NA> When you view an article, the 'To' field from the JAM message will NA> show up as an optional 'X-Comment-To:' header. NA> When you post an article as a result of a follow-up, your client may NA> provide an optional field 'References: ' with the message-id of the NA> original message you replied to (and sometimes the whole chain). NA> I have tested with Thunderbird for Mac and NewsTapLite for iOS and NA> both passed the correct 'References: ' header. Jamnntpd/smapinntpd NA> will look up that message-id from the 'Reference: ' header in the JAM NA> database and will extract the 'From' field of that message. That NA> 'From' name will become a 'To' field of the newly posted message. NA> That 'From' name will also be used as initials when smart quoting NA> feature is enabled. :D :D 'Tommi --- * Origin: smapinntp://rpi.rbb.bbs.fi (2:221/0) SEEN-BY: 1/123 90/1 154/10 203/0 221/1 6 242 360 227/114 229/426 452 SEEN-BY: 229/1014 240/1120 5832 249/206 317 280/464 5003 5555 310/31 SEEN-BY: 317/3 322/757 342/200 423/81 PATH: 221/1 280/464 229/426 |
[ << oldest | < older | list | newer > | newest >> ]