• Re: test

    From Tommi Koivula@2:221/6.600 to Wilfred van Velzen on Sat Dec 31 11:05:32 2022
    * Forwarded from FIDOTEST by Tommi Koivula (2:221/6.600).
    * Originally by: Tommi Koivula (2:221/6.600), 31 Dec 22 11:00.
    * Originally to: Wilfred van Velzen.

    On 31.12.2022 0:14, Wilfred van Velzen wrote:

    There is no TZUTC: kludge...

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

    A test message before scanning in Golded:

    ===
    Subj : 123

    @MSGID: 2:221/6.600 63aff95c
    @PID: SmapiNNTPd/Linux/IPv6 1.3 20221231
    @CHRS: UTF-8 4
    @TZUTC: 0200
    123
    ===

    A test message after scanning in Golded:

    ===
    Subj : 123

    @MSGID: 2:221/6.600 63aff95c
    @PID: SmapiNNTPd/Linux/IPv6 1.3 20221231
    @TID: FMail-lnx64 2.1.0.18-B20170815
    @CHRS: UTF-8 4
    123
    ===

    'Tommi

    --- FMail-lnx64 2.1.0.18-B20170815
    * Origin: -----> (2:221/6.600)
  • From Tommi Koivula@2:221/6.600 to Tommi Koivula on Sat Dec 31 11:46:06 2022
    Tommi Koivula wrote:

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

    FMail also changes the order of kludges when scanning.

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

    'Tommi

    --- FMail-lnx64 2.1.0.18-B20170815
    * Origin: nntps://news.fidonet.fi (2:221/6.600)
  • From Wilfred van Velzen@2:280/464 to Tommi Koivula on Sat Dec 31 10:51:16 2022
    Hi Tommi,

    On 2022-12-31 11:05:32, you wrote to me:

    @MSGID: 2:221/6.600 63affb9c
    @TID: FMail-lnx64 2.1.0.18-B20170815
    @TZUTC: 0200
    @CHRS: UTF-8 4

    This one has the kludge! So it's only happening in FIDOTEST?
    But this one has no PID:, should it?

    * Forwarded from FIDOTEST by Tommi Koivula (2:221/6.600).
    * Originally by: Tommi Koivula (2:221/6.600), 31 Dec 22 11:00.
    * Originally to: Wilfred van Velzen.

    On 31.12.2022 0:14, Wilfred van Velzen wrote:

    There is no TZUTC: kludge...

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

    A test message before scanning in Golded:

    ===
    Subj : 123

    @MSGID: 2:221/6.600 63aff95c
    @PID: SmapiNNTPd/Linux/IPv6 1.3 20221231
    @CHRS: UTF-8 4
    @TZUTC: 0200
    123
    ===

    A test message after scanning in Golded:

    ===
    Subj : 123

    @MSGID: 2:221/6.600 63aff95c
    @PID: SmapiNNTPd/Linux/IPv6 1.3 20221231
    @TID: FMail-lnx64 2.1.0.18-B20170815
    @CHRS: UTF-8 4
    123
    ===

    That is highly surprising! Are you sure nothing else touches it?
    It never happens on my own system, so I can't debug what doesn't reproduce. But can you send me the piece of FMail log where this
    happens?

    Did you compile FMail yourself? Or did you use one of the precompiled ones?

    Can you experiment with the 'Tearline' option. There is a setting that doesn't add the TID kludge.

    Bye, Wilfred.

    --- FMail-lnx64 2.1.0.19-B20221229
    * Origin: FMail development HQ (2:280/464)
  • From Wilfred van Velzen@2:280/464 to Tommi Koivula on Sat Dec 31 11:15:06 2022
    Hi Tommi,

    On 2022-12-31 11:46:06, you wrote to you:

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

    FMail also changes the order of kludges when scanning.

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

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

    Bye, Wilfred.

    --- FMail-lnx64 2.1.0.19-B20221229
    * Origin: FMail development HQ (2:280/464)
  • From Tommi Koivula@2:221/6.600 to Wilfred van Velzen on Sat Dec 31 12:35:38 2022
    Hi Wilfred.

    @MSGID: 2:221/6.600 63affb9c
    @TID: FMail-lnx64 2.1.0.18-B20170815
    @TZUTC: 0200
    @CHRS: UTF-8 4

    This one has the kludge! So it's only happening in FIDOTEST?
    But this one has no PID:, should it?

    No, written in Golded. Tearline, no PID.

    That is highly surprising! Are you sure nothing else touches it?

    I'm sure. Only SmapiNNTPd, Golded and FMail.

    TZUTC seems to disappear from the messages written in SmapiNNTPd. Not Golded.

    It never happens on my own system, so I can't debug what doesn't reproduce. But can you send me the piece of FMail log where this
    happens?

    I send you the log.

    Did you compile FMail yourself? Or did you use one of the precompiled ones?

    The precompiled from your site.

    Can you experiment with the 'Tearline' option. There is a setting that doesn't add the TID kludge.

    Sure.

    'Tommi

    --- FMail-lnx64 2.1.0.18-B20170815
    * Origin: -----> (2:221/6.600)
  • From Tommi Koivula@2:221/6.600 to Wilfred van Velzen on Sat Dec 31 12:51:16 2022
    Wilfred van Velzen wrote:

    Can you experiment with the 'Tearline' option. There is a setting
    that doesn't add the TID kludge.

    No TID, but no TZUTC either. :(

    I added a TEST kludge to smapinntpd. :)

    'Tommi

    --- FMail-lnx64 2.1.0.18-B20170815
    * Origin: --- (2:221/6.600)
  • From Tommi Koivula@2:221/6.600 to Wilfred van Velzen on Sat Dec 31 13:06:38 2022
    Wilfred van Velzen wrote:

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

    Investigate your inbound. :)

    'Tommi

    ---
    * Origin: --- (2:221/6.600)
  • From Wilfred van Velzen@2:280/464 to Tommi Koivula on Sat Dec 31 12:23:19 2022
    Hi Tommi,

    On 2022-12-31 12:35:38, you wrote to me:

    This one has the kludge! So it's only happening in FIDOTEST?
    But this one has no PID:, should it?

    No, written in Golded. Tearline, no PID.

    That is highly surprising! Are you sure nothing else touches it?

    I'm sure. Only SmapiNNTPd, Golded and FMail.

    TZUTC seems to disappear from the messages written in SmapiNNTPd. Not Golded.

    So it seems, so there must be something different to what SmapiNNTPd does in a jam messagebase compared to Golded.

    It never happens on my own system, so I can't debug what doesn't
    reproduce. But can you send me the piece of FMail log where this
    happens?

    I send you the log.

    Got it thanks.

    Did you compile FMail yourself? Or did you use one of the precompiled
    ones?

    The precompiled from your site.

    I don't think it would make a difference, but I like to have all the information. ;)

    Can you experiment with the 'Tearline' option. There is a setting
    that doesn't add the TID kludge.

    Sure.

    ...

    Bye, Wilfred.

    --- FMail-lnx64 2.1.0.19-B20221229
    * Origin: FMail development HQ (2:280/464)
  • From Wilfred van Velzen@2:280/464 to Tommi Koivula on Sat Dec 31 12:26:52 2022
    Hi Tommi,

    On 2022-12-31 12:51:16, you wrote to me:

    @MSGID: 2:221/6.600 63b0141e
    @REPLY: 2:280/464 63b00619
    @PID: SmapiNNTPd/Linux/IPv6 1.3 20221231
    @TEST: HELLO WORLD!
    @CHRS: CP437 2
    @EID: Sylpheed 3.7.0 (GTK+ 2.24.30; i686-pc-mingw32).
    Wilfred van Velzen wrote:

    Can you experiment with the 'Tearline' option. There is a setting
    that doesn't add the TID kludge.

    No TID, but no TZUTC either. :(

    So it's not connected to adding or not adding the TID kludge...

    I added a TEST kludge to smapinntpd. :)

    'Tommi

    --- FMail-lnx64 2.1.0.18-B20170815
    * Origin: --- (2:221/6.600)
    SEEN-BY: 103/705 124/5016 153/757 154/10 203/0 221/1 6 360 240/1120 5832 SEEN-BY: 280/464 5003 5555 292/854 8125 301/1 310/31 335/364 341/66 SEEN-BY: 341/234 396/45 423/81 120 633/280 712/848 770/1 4500/1
    @PATH: 221/6 1 280/464

    Bye, Wilfred.

    --- FMail-lnx64 2.1.0.19-B20221229
    * Origin: FMail development HQ (2:280/464)
  • From Wilfred van Velzen@2:280/464 to Tommi Koivula on Sat Dec 31 12:27:46 2022
    Hi Tommi,

    On 2022-12-31 13:06:38, you wrote to me:

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

    Investigate your inbound. :)

    Got it, found it in my insecure-inbound. ;-)

    Bye, Wilfred.

    --- FMail-lnx64 2.1.0.19-B20221229
    * Origin: FMail development HQ (2:280/464)
  • From Tommi Koivula@2:221/6 to Wilfred van Velzen on Sat Dec 31 14:02:30 2022
    Wilfred van Velzen wrote:

    TZUTC seems to disappear from the messages written in
    SmapiNNTPd. Not Golded.

    So it seems, so there must be something different to what
    SmapiNNTPd does in a jam messagebase compared to Golded.

    And the same SmapiNNTPd with HPT has no such a problem.

    Let's see how JamNNTPd behaves with FMail.

    'Tommi

    ---
    * Origin: nntp://news.fidonet.fi (2:221/6.0)
  • From Wilfred van Velzen@2:280/464 to Tommi Koivula on Sat Dec 31 13:28:43 2022
    Hi Tommi,

    On 2022-12-31 14:02:30, you wrote to me:

    TZUTC seems to disappear from the messages written in
    SmapiNNTPd. Not Golded.

    So it seems, so there must be something different to what
    SmapiNNTPd does in a jam messagebase compared to Golded.

    And the same SmapiNNTPd with HPT has no such a problem.

    Isn't SmapiNNTPd part of the HPT suite?

    Let's see how JamNNTPd behaves with FMail.

    That would be interesting!


    Bye, Wilfred.

    --- FMail-lnx64 2.1.0.19-B20221229
    * Origin: FMail development HQ (2:280/464)
  • From Wilfred van Velzen@2:280/464 to Tommi Koivula on Sat Dec 31 14:02:59 2022
    Hi Tommi,

    On 2022-12-31 14:02:30, you wrote to me:

    @MSGID: 2:221/6.0 63b024d6
    @REPLY: 2:280/464 63b01c1e
    @PID: SmapiNNTPd/Linux/IPv6 1.3 20221231
    @EID: Sylpheed 3.7.0 (GTK+ 2.24.30; i686-pc-mingw32).
    @CHRS: CP437 2
    @TZUTC: 0200
    @TEST: HELLO WORLD!
    @TID: hpt/lnx 1.9 2022-07-03

    Btw: This one has the TZUTC: kludge!


    Bye, Wilfred.

    --- FMail-lnx64 2.1.0.19-B20221229
    * Origin: FMail development HQ (2:280/464)
  • From Wilfred van Velzen@2:280/464 to Tommi Koivula on Sat Dec 31 14:08:54 2022
    Hi Tommi,

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

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

    FMail also changes the order of kludges when scanning.

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

    I'd like to investigate your jam messagebase files for a test area, from 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)
  • From Tommi Koivula@2:221/6.600 to Wilfred van Velzen on Sat Dec 31 15:11:44 2022
    Wilfred van Velzen wrote:

    TZUTC seems to disappear from the messages written in
    SmapiNNTPd. Not Golded.

    So it seems, so there must be something different to what
    SmapiNNTPd does in a jam messagebase compared to Golded.

    And the same SmapiNNTPd with HPT has no such a problem.

    Isn't SmapiNNTPd part of the HPT suite?

    No, but it uses the same smapi library.


    Let's see how JamNNTPd behaves with FMail.

    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)
  • From Wilfred van Velzen@2:280/464 to Tommi Koivula on Sat Dec 31 14:14:40 2022
    Hi Tommi,

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

    TZUTC seems to disappear from the messages written in
    SmapiNNTPd. Not Golded.

    So it seems, so there must be something different to what
    SmapiNNTPd does in a jam messagebase compared to Golded.

    And the same SmapiNNTPd with HPT has no such a problem.

    Isn't SmapiNNTPd part of the HPT suite?

    No, but it uses the same smapi library.


    Let's see how JamNNTPd behaves with FMail.

    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?

    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)
  • From Tommi Koivula@2:221/6.600 to Wilfred van Velzen on Sat Dec 31 16:28:17 2022
    Hi Wilfred.

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

    Hi Tommi,

    On 2022-12-31 14:02:30, you wrote to me:

    @MSGID: 2:221/6.0 63b024d6
    @REPLY: 2:280/464 63b01c1e
    @PID: SmapiNNTPd/Linux/IPv6 1.3 20221231
    @EID: Sylpheed 3.7.0 (GTK+ 2.24.30; i686-pc-mingw32).
    @CHRS: CP437 2
    @TZUTC: 0200
    @TEST: HELLO WORLD!
    @TID: hpt/lnx 1.9 2022-07-03

    Btw: This one has the TZUTC: kludge!

    Yes. See the TID.

    'Tommi

    --- FMail-lnx64 2.1.0.18-B20170815
    * Origin: -----> (2:221/6.600)
  • From Tommi Koivula@2:221/6.600 to Wilfred van Velzen on Sat Dec 31 16:29:50 2022
    Hi Wilfred.

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

    Hi Tommi,

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

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

    FMail also changes the order of kludges when scanning.

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

    I'd like to investigate your jam messagebase files for a test area, from
    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...

    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)
  • From Wilfred van Velzen@2:280/464 to Tommi Koivula on Sat Dec 31 15:30:38 2022
    Hi Tommi,

    On 2022-12-31 14:14:40, I wrote to you:

    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?

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

    Found it! That special jam subfield 2004 is ignored by FMail. Apparently it is hardly ever used by software. Because it was in FMail like this from the start, a few decades ago. Golded knows how to handle it when encountered, but doesn't use it when creating new messages in the jambase...

    It should be an easy fix, but it will have to wait until next year. ;-)

    Bye, Wilfred.

    --- FMail-lnx64 2.1.0.19-B20221229
    * Origin: FMail development HQ (2:280/464)
  • From Tommi Koivula@2:221/6.600 to Wilfred van Velzen on Mon Jan 2 19:44:28 2023
    On 31.12.2022 16:30, Wilfred van Velzen wrote:


    Found it! That special jam subfield 2004 is ignored by FMail. Apparently it is hardly ever used by software. Because it was in FMail like this from the start, a few decades ago. Golded knows how to handle it when encountered,
    but doesn't use it when creating new messages in the jambase...

    It should be an easy fix, but it will have to wait until next year. ;-)


    Fixed this year. :)

    'Tommi

    --- FMail-lnx64 2.1.0.20-B20230102
    * Origin: nntps://news.fidonet.fi (2:221/6.600)
  • From Tommi Koivula@2:221/6.600 to Wilfred van Velzen on Mon Jan 2 19:50:14 2023
    Hi Wilfred.

    02 Jan 23 19:44, I wrote to you:

    Fixed this year. :)

    I turned "Update text after Scan" to "Yes"

    Before scanning:
    00002 [ 13]: "Tommi Koivula"
    00003 [ 18]: "Wilfred van Velzen"
    00006 [ 4]: "test"
    00004 [ 20]: "2:221/6.600 63b317f4"
    00005 [ 18]: "2:280/464 63b048bd"
    00007 [ 34]: "SmapiNNTPd/Linux/IPv6 1.3 20230101"
    02000 [ 91]: "EID: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:102.0) Geck" 02000 [ 13]: "CHRS: UTF-8 4"
    02004 [ 4]: "0200"
    02000 [ 10]: "BBSID: MXO"

    After scanning:
    00002 [ 13]: "Tommi Koivula"
    00003 [ 18]: "Wilfred van Velzen"
    00004 [ 20]: "2:221/6.600 63b317f4"
    00005 [ 18]: "2:280/464 63b048bd"
    00006 [ 4]: "test"
    00007 [ 34]: "SmapiNNTPd/Linux/IPv6 1.3 20230101"
    02000 [ 35]: "TID: FMail-lnx64 2.1.0.20-B20230102"
    02000 [ 10]: "BBSID: MXO"
    02000 [ 11]: "TZUTC: 0200"
    02000 [ 13]: "CHRS: UTF-8 4"
    02000 [ 91]: "EID: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:102.0) Geck"

    So FMail now 'converts' 2004 to 2000.

    'Tommi

    --- FMail-lnx64 2.1.0.20-B20230102
    * Origin: -----> (2:221/6.600)
  • From Wilfred van Velzen@2:280/464 to Tommi Koivula on Mon Jan 2 19:22:18 2023
    Hi Tommi,

    On 2023-01-02 19:44:28, you wrote to me:

    @MSGID: 2:221/6.600 63b317f4
    @REPLY: 2:280/464 63b048bd
    @PID: SmapiNNTPd/Linux/IPv6 1.3 20230101
    @TID: FMail-lnx64 2.1.0.20-B20230102
    @BBSID: MXO
    @TZUTC: 0200
    @CHRS: UTF-8 4
    @EID: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.6.1.

    It should be an easy fix, but it will have to wait until next year. ;-)

    Fixed this year. :)

    Thanks for testing! ;)

    --- FMail-lnx64 2.1.0.20-B20230102

    Bye, Wilfred.

    --- FMail-lnx64 2.1.0.20-B20230102
    * Origin: FMail development HQ (2:280/464)
  • From Wilfred van Velzen@2:280/464 to Tommi Koivula on Mon Jan 2 19:24:13 2023
    Hi Tommi,

    On 2023-01-02 19:50:14, you wrote to me:

    I turned "Update text after Scan" to "Yes"

    Before scanning:
    02004 [ 4]: "0200"

    After scanning:
    02000 [ 11]: "TZUTC: 0200"

    So FMail now 'converts' 2004 to 2000.

    Not intentional, but I can see how that can happen, when it's written back to the jam message base.

    Anyway both are correct.

    Bye, Wilfred.

    --- FMail-lnx64 2.1.0.20-B20230102
    * Origin: FMail development HQ (2:280/464)
  • From Tommi Koivula@2:221/360 to Wilfred van Velzen on Mon Jan 2 20:51:10 2023

    Monday January 02 2023 19:24, Wilfred van Velzen wrote to Tommi Koivula:

    Before scanning:
    02004 [ 4]: "0200"

    After scanning:
    02000 [ 11]: "TZUTC: 0200"

    So FMail now 'converts' 2004 to 2000.

    Not intentional, but I can see how that can happen, when it's written back to
    the jam message base.

    That's opposite what happens with GoldED and HPT. ;) GoldED enters 2000 and HPT converts it to 2004.

    02000 [ 11]: "TZUTC: 0200" GOLDED BEFORE HPT SCAN
    02004 [ 4]: "0200" GOLDED AFTER HPT SCAN

    I also checked my tossers what they do when tossing to JAM. Gecho, Fastecho and HPT all put 2004 into JAM.

    'Tommi

    --- GEcho/2 1.20/Pro
    * Origin: * RBB * Lake Ylo * Finland * (2:221/360)
  • From Wilfred van Velzen@2:280/464 to Tommi Koivula on Mon Jan 2 20:55:01 2023
    Hi Tommi,

    On 2023-01-02 20:51:10, you wrote to me:

    Before scanning:
    02004 [ 4]: "0200"

    After scanning:
    02000 [ 11]: "TZUTC: 0200"

    So FMail now 'converts' 2004 to 2000.

    Not intentional, but I can see how that can happen, when it's written
    back to the jam message base.

    That's opposite what happens with GoldED and HPT. ;) GoldED enters 2000 and
    HPT converts it to 2004.

    02000 [ 11]: "TZUTC: 0200" GOLDED BEFORE HPT SCAN
    02004 [ 4]: "0200" GOLDED AFTER HPT SCAN

    I also checked my tossers what they do when tossing to JAM. Gecho, Fastecho
    and HPT all put 2004 into JAM.

    It would be easy to change, but I'm reluctant to change what worked for decades. And both are correct, so it doesn't matter...

    Bye, Wilfred.

    --- FMail-lnx64 2.1.0.20-B20230102
    * Origin: FMail development HQ (2:280/464)
  • From Tommi Koivula@2:221/1 to Wilfred van Velzen on Mon Jan 2 22:34:04 2023
    On 2.1.2023 21:55, Wilfred van Velzen wrote:

    That's opposite what happens with GoldED and HPT. ;) GoldED enters 2000 and
    HPT converts it to 2004.

    02000 [ 11]: "TZUTC: 0200" GOLDED BEFORE HPT SCAN
    02004 [ 4]: "0200" GOLDED AFTER HPT SCAN

    I also checked my tossers what they do when tossing to JAM. Gecho, Fastecho
    and HPT all put 2004 into JAM.

    It would be easy to change, but I'm reluctant to change what worked
    for decades. And both are correct, so it doesn't matter...

    I agree. It is not important how it is stored in JAM, it is important how it goes in and out. ;)

    'Tommi

    --- Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:5.0) Aura/20220608 Interlink/52.9.8194
    * Origin: nntp://rbb.fidonet.fi - Lake Ylo - Finland (2:221/1.0)