• hpt squish __ftsc_date

    From Michael Dukelsky@2:5020/1042 to Oli on Tuesday, January 14, 2020 17:25:40
    Hello Oli,

    Tuesday January 14 2020, Oli wrote to Michael Dukelsky:

    a squish tosser should write the date string to the __ftsc_date field
    when importing mails and should use the __ftsc_date field (if it is
    not empty) on export. see the squish spec. smapi seems to support that field, but hpt doesn't use it.

    the JAM problem:
    it was mentioned in some other echoarea that hpt doesn't set the
    OADDRESS for echomail and that the origin address is missing on
    rescans. i also couldn't find a place in the sources where the
    OADDRESS is set.

    jammnntpd even has a workaround for missing OADDRESS fields.

    OK, thank you, I'll look at it when I have time.

    Michael

    ... node (at) f1042 (dot) ru
    --- GoldED+/LNX 1.1.5-b20170303
    * Origin: Moscow, Russia (2:5020/1042)
  • From Oli@2:280/464.47 to Michael Dukelsky on Tuesday, January 14, 2020 15:12:47
    And also PKTs from hpt itself? (which doesn't set the
    JAM OADDRESS and rewrites the message date for Squish
    messages.

    As far as I understand it from the documentation hpt
    always does import/export in one pass, is that correct?
    But What about echoareas that get rescanned? Around 50%
    of the mails (or a little bit less) will have a modified
    timestamp (DOS time format with 2 second granularity). To
    be clear, Squish message base format has a field for
    storing the original FTN time field, it is just not used
    by hpt (if I understand the C sources correctly).

    Could you please send me a bug report with full
    description of actions to reproduce the error with an
    example of the message base and pkt taking part in the
    actions. I am very busy at the moment but I'll try to
    investigate it when time permits.

    I'm not using hpt and I cannot provide example files, but the problem is simple:

    a squish tosser should write the date string to the __ftsc_date field when importing mails and should use the __ftsc_date field (if it is not empty) on export. see the squish spec. smapi seems to support that field, but hpt doesn't
    use it.

    the JAM problem:
    it was mentioned in some other echoarea that hpt doesn't set the OADDRESS for echomail and that the origin address is missing on rescans. i also couldn't find a place in the sources where the OADDRESS is set.

    jammnntpd even has a workaround for missing OADDRESS fields.

    please correct me if i'm wrong. if i had the time, i would do some testing with
    hpt.

    and thank you for your hpt support and bug fixing, michael.



    * Origin: kakistocracy (2:280/464.47)
  • From Tommi Koivula@2:221/1 to Oli on Tuesday, January 14, 2020 19:53:30
    14 Jan 20 15:12, Oli wrote to Michael Dukelsky:

    I'm not using hpt and I cannot provide example files, but the problem is simple:

    a squish tosser should write the date string to the __ftsc_date field when importing mails and should use the __ftsc_date field (if it is not empty)
    on
    export. see the squish spec. smapi seems to support that field, but hpt
    doesn't
    use it.

    Which field is that? Can I see it in GoldED hexdump pressing "i" ?

    These date's are found in your message in my squish base, tossed by hpt.

    === Cut ===
    DateTime : 14 Jan 20 15:12:47
    OrigAddr : 2:280/464.47
    DestAddr : 2:221/1.0
    See : 92, 0, 0, 0, 0, 0, 0, 0, 0
    Attr : 00020000h (00000000000000100000000000000000b)
    DateWritten : 2020-01-14 15:12:46 (7997502Eh)
    DateArrived : 2020-01-14 16:13:52 (81BA502Eh)
    UTC-Offset : 0
    === Cut ===

    'Tommi

    ---
    * Origin: 2001:470:1f15:cb0:f1d0:2:221:1 (2:221/1)
  • From Oli@2:280/464.47 to Tommi Koivula on Tuesday, January 14, 2020 21:24:09
    a squish tosser should write the date string to the
    __ftsc_date field when importing mails and should use the
    __ftsc_date field (if it is not empty) on export. see the
    squish spec. smapi seems to support that field, but hpt
    doesn't use it.

    Which field is that? Can I see it in GoldED hexdump
    pressing "i" ?

    Good question. I only discovered "i" recently by hitting the wrong key and don't know much about it ...

    These date's are found in your message in my squish base,
    tossed by hpt.

    ... but DateTime looks exactly like the value __ftsc_date should have. So I guess I was at least partly wrong. hpt does write __ftsc_date.

    === Cut ===
    DateTime : 14 Jan 20 15:12:47
    OrigAddr : 2:280/464.47
    DestAddr : 2:221/1.0
    See : 92, 0, 0, 0, 0, 0, 0, 0, 0
    Attr : 00020000h
    (00000000000000100000000000000000b)
    DateWritten : 2020-01-14 15:12:46 (7997502Eh)
    DateArrived : 2020-01-14 16:13:52 (81BA502Eh)
    UTC-Offset : 0
    === Cut ===



    * Origin: kakistocracy (2:280/464.47)