Just a sample of the Echomail archive
[ << oldest | < older | list | newer > | newest >> ]
|  Message 1975  |
|  Wilfred van Velzen to Tommi Koivula  |
|  Re: test  |
|  31 Dec 22 14:08:54  |
 TID: FMail-lnx64 2.1.0.19-B20221229 RFC-X-No-Archive: Yes TZUTC: 0100 CHRS: UTF-8 2 PID: GED+LNX 1.1.5-b20161221 MSGID: 2:280/464 63b03533 REPLY: 2:280/464 63b00bfa Hi Tommi, 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. I investigated the before and after jam message base you sent me. Except for the Snt flag, FMail doesn't seem to touch the message. When I look at the messages with GoldED they are identical including the order of the kludges... Bye, Wilfred. --- FMail-lnx64 2.1.0.19-B20221229 * Origin: FMail development HQ (2:280/464) SEEN-BY: 1/19 123 15/0 16/0 19/37 90/1 103/705 105/81 106/201 120/340 SEEN-BY: 123/130 131 124/5016 129/305 142/104 153/757 7715 154/10 SEEN-BY: 203/0 218/700 221/0 226/30 229/110 111 112 113 114 206 307 SEEN-BY: 229/317 424 426 428 470 550 664 700 240/1120 5411 5832 5853 SEEN-BY: 266/512 280/464 5003 5555 282/1038 292/854 8125 301/1 310/31 SEEN-BY: 317/3 320/119 219 319 2119 322/0 757 326/101 341/66 234 342/200 SEEN-BY: 396/45 423/120 460/58 633/280 712/848 770/1 2454/119 PATH: 280/464 240/5832 320/219 229/426 |
[ << oldest | < older | list | newer > | newest >> ]