• bad VERT QWK packets??

    From mark lewis@1:3634/12.73 to digital man on Tue Aug 6 10:12:02 2019

    i'm trying to figure out why i have these .bad qwk packets from vert... i've never had any before and i just spotted these earlier when working on my files areas... plus someone had asked about these the other day on IRC (i think) so i was kinda watching out for them...

    -rw------- 1 sbbs sbbs 14587 Aug 4 23:31 VERT.qwk.5d47a330.bad
    -rw------- 1 sbbs sbbs 2186 Aug 5 13:31 VERT.qwk.5d486804.bad
    -rw------- 1 sbbs sbbs 4314 Aug 5 23:01 VERT.qwk.5d48ed7c.bad

    it looks like they're renamed to bad because there was an error (duplicate message found) during import...

    if the counts in the logs are to be believed, all the messages except the duplicate ones did get imported... how can we be sure? is there a way to export a list of messages in an area for the dates and times in question so we can check the Message-IDs and see what we really have in our message bases?

    for the above .bad files, the 1st and 2nd were renamed because each has a duplicate Message-ID... the 3rd one because of a duplicate message body hash...

    )\/(ark

    Once men turned their thinking over to machines in the hope that this would set them free. But that only permitted other men with machines to enslave them.
    ... Hot words make for a real cool friendship.
    ---
    * Origin: (1:3634/12.73)
  • From Digital Man@1:103/705 to mark lewis on Tue Aug 6 13:10:34 2019
    Re: bad VERT QWK packets??
    By: mark lewis to digital man on Tue Aug 06 2019 10:12 am


    i'm trying to figure out why i have these .bad qwk packets from vert...
    i've
    never had any before and i just spotted these earlier when working on my files areas... plus someone had asked about these the other day on IRC (i think) so i was kinda watching out for them...

    -rw------- 1 sbbs sbbs 14587 Aug 4 23:31 VERT.qwk.5d47a330.bad
    -rw------- 1 sbbs sbbs 2186 Aug 5 13:31 VERT.qwk.5d486804.bad
    -rw------- 1 sbbs sbbs 4314 Aug 5 23:01 VERT.qwk.5d48ed7c.bad

    it looks like they're renamed to bad because there was an error (duplicate message found) during import...

    if the counts in the logs are to be believed, all the messages except the duplicate ones did get imported... how can we be sure? is there a way to export a list of messages in an area for the dates and times in question so we can check the Message-IDs and see what we really have in our message bases?

    You could use "smbutil v" to view the headers of messages in a message base.

    for the above .bad files, the 1st and 2nd were renamed because each has a duplicate Message-ID... the 3rd one because of a duplicate message body hash...

    You can just safely delete them then.

    digital man

    Synchronet "Real Fact" #50:
    JAM and Squish were considered before developing Synchronet Message Base format.
    Norco, CA WX: 96.9øF, 24.0% humidity, 3 mph SE wind, 0.00 inches rain/24hrs
    --- SBBSecho 3.08-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Gamgee@1:103/705 to mark lewis on Tue Aug 6 20:02:00 2019
    Subject: Re: bad VERT QWK packets??
    @MSGID: <5D4A25A6.1601.dove-syncops@palantirbbs.ddns.net>
    @REPLY: <5D499A4C.45884.sync_sys@vert.synchro.net>
    @TZ: c168
    mark lewis wrote to digital man <=-

    i'm trying to figure out why i have these .bad qwk packets from
    vert... i've never had any before and i just spotted these
    earlier when working on my files areas... plus someone had asked
    about these the other day on IRC (i think) so i was kinda
    watching out for them...

    -rw------- 1 sbbs sbbs 14587 Aug 4 23:31 VERT.qwk.5d47a330.bad
    -rw------- 1 sbbs sbbs 2186 Aug 5 13:31 VERT.qwk.5d486804.bad
    -rw------- 1 sbbs sbbs 4314 Aug 5 23:01 VERT.qwk.5d48ed7c.bad

    it looks like they're renamed to bad because there was an error
    (duplicate message found) during import...

    if the counts in the logs are to be believed, all the messages
    except the duplicate ones did get imported... how can we be sure?
    is there a way to export a list of messages in an area for the
    dates and times in question so we can check the Message-IDs and
    see what we really have in our message bases?

    for the above .bad files, the 1st and 2nd were renamed because
    each has a duplicate Message-ID... the 3rd one because of a
    duplicate message body hash...

    I am seeing this *EXACT* same thing. I did a CVS update on Sunday
    8/4, and it's happened once/twice a day every day since then. Has
    never (ever) happened before...


    ... Windows 3.1 - From the people who brought you EDLIN.
    --- MultiMail/Linux v0.52
    þ Synchronet þ Palantir BBS * palantirbbs.ddns.net * Pensacola, FL
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)