TID: FMail-lnx64 2.1.0.18-B20170815
TZUTC: 0200
CHRS: CP437 2
EID: Sylpheed 3.7.0 (GTK+ 2.24.30; i686-pc-mingw32).
PID: JamNNTPd/Cygwin32 1.3 20221231
REPLY: 2:280/464 63b02dca
MSGID: 2:221/6.600 63b0350c
Wilfred van Velzen wrote:

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?

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!

No problems with Jamnntpd.

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

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

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

'Tommi

---
 * Origin: rbb.fidonet.fi - Lake Ylo - Finland (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