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 63b035e9
REPLY: 2:221/6.600 63b0350c
Hi Tommi,

On 2022-12-31 15:11:44, you wrote to me:

 WVV>>  WVV>>  TK> TZUTC seems to disappear from the messages written in
 WVV>>  WVV>>  TK> SmapiNNTPd. Not Golded.
 WVV>>  WVV>>
 WVV>>  WVV>> So it seems, so there must be something different to what
 WVV>>  WVV>> SmapiNNTPd does in a jam messagebase compared to Golded.
 WVV>>
 WVV>>  TK> And the same SmapiNNTPd with HPT has no such a problem.
 WVV>>
 WVV>> Isn't SmapiNNTPd part of the HPT suite?

 TK> No, but it uses the same smapi library.

 WVV>>
 WVV>>  TK> Let's see how JamNNTPd behaves with FMail.
 WVV>>
 WVV>> That would be interesting!

 TK> No problems with Jamnntpd.

 TK> But I made some research with GoldED's JAM hexdumps. There are two ways to
 TK> store the TZUTC in JAM.

 TK> 02004 [  4]: "0200"              smapinntpd & gecho
 TK> 02000 [ 11]: "TZUTC: 0200"       jamnntpd & golded

 TK> Maybe there is the reason why FMail strips the TZUTC when exporting?

That rings a bell. But I have to investigate...


Bye, Wilfred.

--- FMail-lnx64 2.1.0.19-B20221229
 * Origin: FMail development HQ (2:280/464)
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/0 226/30 229/110
SEEN-BY: 229/111 112 113 114 206 307 317 424 426 428 470 550 664 700
SEEN-BY: 240/1120 5832 266/512 280/464 5003 5555 282/1038 292/854
SEEN-BY: 292/8125 301/1 310/31 317/3 320/219 322/757 341/66 234 342/200
SEEN-BY: 396/45 423/120 460/58 633/267 280 281 412 416 418 509 712/848
SEEN-BY: 770/1
PATH: 280/464 633/280 229/426