MSGID: 2:221/1.1 663717fd
TZUTC: 0300
TID: TZZ
CHRS: UTF-8 4
PID: nntpPoint 2.5.0.69
RFC-MIME-Version: 1.0
RFC-Content-Language: en-US
REPLY: 1:154/10 663685a6
RFC-References: <66367192@p0.f1.n221.z2.ftn> <663685a6@p0.f10.n154.z1.ftn>
RFC-From: Tommi Koivula 
RFC-In-Reply-To: <663685a6@p0.f10.n154.z1.ftn>
RFC-Content-Type: text/plain; charset=UTF-8; format=flowed
RFC-Content-Transfer-Encoding: 7bit
On 04.05.2024 13:59, Nicholas Boel wrote:

>>> Is that specific to Thunderbird and/or Sylpheed? I believe slrn
>>> and tin it doesn't use or display "RFC". It just sends
>>> "User-Agent:", "Content-Type:", and
>>> "Content-Transfer-Encoding:".
> 
> TK> The "RFC-" part of the kludge was added by me.
> 
> I get that. But, did you get that from some technical document that
> that should be in use?

Nope.. Just my own thing, something what soupgate does..

> Or is this something you've just done yourself because FMail adds a
> RFC-X-NO-ARCHIVE kludge?

Nothing to do with FMail. Actually I cannot find anything like that in 
fmail docs or in the code. Maybe it is the GoldED of Wilfred that is 
adding that kludge. ;)

> From Wikipedia:
> 
> "The proper field to prevent a message from being archived is:
> X-No-Archive: Yes (abbreviated as "XNAY")."
> 
> So I imagine what FMail is doing, isn't actually preventing messages
> from being archived.

In the fidonet, probably not.

'Tommi

--- Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:115.0) Gecko/20100101
Thunderbird/115.10.1
 * Origin: nntp point at (2:221/1.1)
SEEN-BY: 15/0 90/1 103/705 105/81 106/201 124/5016 128/260 135/220
SEEN-BY: 135/225 153/757 7715 154/10 30 203/0 218/700 840 221/0 1
SEEN-BY: 221/6 226/30 227/114 229/110 112 113 206 317 426 428 470
SEEN-BY: 229/664 700 240/1120 5832 266/512 280/464 5003 5555 282/1038
SEEN-BY: 291/111 292/8125 301/1 310/31 320/219 322/757 335/364 341/66
SEEN-BY: 341/200 234 342/200 396/45 423/120 460/58 256 1124 467/888
SEEN-BY: 633/280 712/848 770/1 902/26 5020/400 1042 5054/30
PATH: 221/6 341/66 280/464 460/58 229/426