https://gitlab.synchro.net/main/sbbs/-/commit/0546fa33fab7404a70287910
Modified Files:
exec/load/newsutil.js
Log Message:
Do the FTN CHRS kludge to MIME charset translation for CP866->koi8-r

for Al (TRMB) and his Russian users, requested via DOVE-Net.

Do an FTN "ASCII 1" -> "US-ASCII" translation of the CHRS->charset too.

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

https://gitlab.synchro.net/main/sbbs/-/commit/bebed0b413b07ffb20caa05e
Modified Files:
exec/load/newsutil.js
Log Message:
Import and export the message "editor" as the NNTP "user-agent" header field

The message editor is exported/imported to/from FTN as the "NOTE" kludge.

For Accession, per irc.synchro.net

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

https://gitlab.synchro.net/main/sbbs/-/commit/e904206bf5cb23c9e5dede2d
Modified Files:
exec/load/newsutil.js
Log Message:
Fix the regex in the parsing of the "References" header field

We only want one Message-ID (we'll use the last, since that appears to be the message being replied to based on SLRN behavior). This fixes reply linkage
when posing from newsreaders that put multiple message-IDs in the
references header field. This is required for SBBSecho to do its magic
creation of the FTN REPLY kludge during export.

This is the fix that Accession was looking for, I think.

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

https://gitlab.synchro.net/main/sbbs/-/commit/bdf72516a77aeda5257e5b53
Modified Files:
exec/load/newsutil.js
Log Message:
In-Reply-To is not a valid NNTP article header field

... so this was just redundant noise. Altough "References" is a valid header field *both* for email and nntp articles, "In-Reply-To" is for email only.
per RFC 5536

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

https://gitlab.synchro.net/main/sbbs/-/commit/9bf86ab10c206945417c45d9
Modified Files:
exec/load/newsutil.js
Log Message:
Store original "references" header field as an RFC822HEADER in SMB

If an original references header field was supplied with the message, include *that* in the header (since it should contain all the IDs of the replied-to message thread) rather than just the message's reply_id (a single message
ID) when sending via NNTP. This maintains more NNTP post integrity when
sending back out via NNTP.

Not sure why we were storing received "references" in the hdr.references returned by parse_news_header(), we don't seem to be using it anywere. Maybe copied from 822header.js or mailproc_util.js? Seems like cruft, so remove it.

Also, don't ever send an "In-Reply-To" heder field via NNTP (it's not valid /used for NNTP articles, per RFC 5536).

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net