• FOLLOW-UP ON: Problem with legacy tosser (Squish) and Sync's MSGID

    From Marc Lewis@1:396/45 to Fred Riccio on Wed Dec 2 19:03:43 2020
    Hello Fred.

    <<Following up a message from Marc Lewis to Fred Riccio about RE: Problem with legacy tosser (Squish) and Sync's MSGID >>


    Squish *can* use MSGID to do dupe checking, but it doesn't have to.
    Check the DupeCheck keyword in Squish.Cfg, does it say MSGID,
    HEADER, or both? You could try using only HEADER to see what
    happens.

    Okay, I've changed the DupeCheck line to read HEADER.

    I've asked one of the Nodes that feeds off me to send a NetMail to
    me to see what happens.

    Unfortunately, Fred, that had no effect whatsoever. It may be time for me to just hang it up. I can't afford the time to completely redesign the system to accomodate the Synchronet way of doing things... And they're so predominant now-a-days that almost 2/3 of the nodes feeding off me run Synchronet. Mr. Swindell says it's Squish's fault and I strongly disagree with him, but there's not much I can do about it. It's apparent in his opinion that he's right and Squish is wrong, despite the lenght of time its been around doing its job without problem.

    Best regards,
    Marc

    --- timEd/2 1.10.y2k+
    * Origin: Sursum Corda! BBS-Huntsville,AL-bbs.sursum-corda.com (1:396/45)
  • From Rob Swindell to Marc Lewis on Wed Dec 2 18:18:26 2020
    Re: FOLLOW-UP ON: Problem with legacy tosser (Squish) and Sync's MSGID
    By: Marc Lewis to Fred Riccio on Wed Dec 02 2020 07:03 pm

    Unfortunately, Fred, that had no effect whatsoever. It may be time for me to just hang it up. I can't afford the time to completely redesign the system to accomodate the Synchronet way of doing things...

    Who asked you to redesign anything? If you reall wnat to "hang it up" and are just looking for an excuse, I guess you found one. But you enjoy solving problems, you found one of those too.

    And they're so
    predominant now-a-days that almost 2/3 of the nodes feeding off me run Synchronet. Mr. Swindell says it's Squish's fault and I strongly disagree with him, but there's not much I can do about it. It's apparent in his opinion that he's right and Squish is wrong, despite the lenght of time its been around doing its job without problem.

    It doesn't sound like you've read the relevant FTN specs or my write-up about this the FTN-MSGID topic, but just so you're aware: Synchronet was not the first software to generate FTN MSGIDs which don't conform to what you (and apparently Squish) think should be the norm. Here are some examples:
    X-FTN-MSGID <vg3zhjtkbo8.fsf@coffee.modeemi.fi> 33bc160d
    X-FTN-MSGID <x4pkFV$7VHA.3076@hal.ad.rbb.homeip.net> 6f22dbc9
    X-FTN-MSGID <y2aimij78p9.fsf@offog.org> 86afd87b
    X-FTN-MSGID <NG00.k4jpsi$sl0$2@dont-email.me> 0001327e
    X-FTN-MSGID <FIEFKANCPGAHBHEGCJNMAEAFINAA.shurato@shurato.net> 20c0db2e X-FTN-MSGID <alpine.BSF.2.21.9999.2004012225290.24008@cerebro.liukuma.net> 2ceda87e
    X-FTN-MSGID <alpine.DEB.2.20.1711181828200.926@onramp.os2bbs.org> 1a31d5a1 X-FTN-MSGID <b0bjtv$sao$595@host.elcom.ru> 1f885ab1
    X-FTN-MSGID <20060904114516.19f25d93d7f80a223b6e85f47e965fd7.90b642a290.wbe@email.secureserver.net> 5daee08b

    I could dig up tons of other examples, none of which were generated by Synchronet or SBBSecho.
    --
    digital man

    This Is Spinal Tap quote #39:
    Airport Security Officer: Do you have any artificial plates or limbs?
    Norco, CA WX: 67.1°F, 14.0% humidity, 6 mph SW wind, 0.00 inches rain/24hrs