TID: FMail-lnx64 2.1.0.18-B20170815
TZUTC: 0200
CHRS: UTF-8 4
MSGID: 2:221/6.600 63b047c0
REPLY: 2:280/464 63b03533
Hi Wilfred.

31 Dec 22 14:08, you wrote to me:

 WV> Hi Tommi,

 WV> On 2022-12-31 11:15:06, I wrote to you:

 TK>>>> It seems that FMAIL is removing the kludge. I'm not joking. The
 TK>>>> kludge is there in JAM base before 'fmail scan'.

 TK>>> FMail also changes the order of kludges when scanning.

 TK>>> ===
 TK>>> MSGID: 2:221/6.600 63b001e0
 TK>>> PID: SmapiNNTPd/Linux/IPv6 1.3 20221231
 TK>>> CHRS: CP437 2
 TK>>> TZUTC: 0200
 TK>>> ===
 TK>>> TID: FMail-lnx64 2.1.0.18-B20
 TK>>> CHRS: CP437 2
 TK>>> PID: SmapiNNTPd/Linux/IPv6 1.3 20221231
 TK>>> MSGID: 2:221/6.600 63b001e0
 TK>>> ===

 WvV>> I'd like to investigate your jam messagebase files for a test area, from
 WvV>> before and after the scan.

 WV> I investigated the before and after jam message base you sent me. Except
for
 WV> the Snt flag, FMail doesn't seem to touch the message. When I look at the
 WV> messages with GoldED they are identical including the order of the
kludges...

So it touches only the outgoing message, there is a setting in FConfig not to
alter the local sent message. Have to check it next year. :)

'Tommi

--- FMail-lnx64 2.1.0.18-B20170815
 * Origin: -----> (2:221/6.600)
SEEN-BY: 1/123 15/0 90/1 103/705 105/81 106/201 120/340 123/131 124/5016
SEEN-BY: 129/305 153/757 7715 154/10 203/0 218/700 221/1 6 360 226/30
SEEN-BY: 229/110 111 112 113 114 206 307 317 424 426 428 470 550 664
SEEN-BY: 229/700 240/1120 5832 266/512 280/464 5003 5555 282/1038
SEEN-BY: 292/854 8125 301/1 310/31 317/3 320/219 322/757 335/364 341/66
SEEN-BY: 341/234 342/200 396/45 423/81 120 460/58 633/267 280 281
SEEN-BY: 633/412 416 418 509 712/848 770/1 4500/1
PATH: 221/6 1 280/464 633/280 229/426