• Re: Problem with legacy t

    From Dumas Walker@1:2320/105 to MARC LEWIS on Wed Dec 2 17:34:00 2020
    I've asked one of the Nodes that feeds off me to send a NetMail to me to see wh
    t happens.

    Based on some of the other messages here, I would ask that node what they
    are using as the PacketType setting for your node in their sbbsecho.ini
    file. Maybe they need to change that to something else?

    Mike


    * SLMR 2.1a * ...a host of holy horrors to direct our aimless dance...
    --- SBBSecho 3.11-Linux
    * Origin: capitolcityonline.net * Telnet/SSH:2022/HTTP (1:2320/105)
  • From Marc Lewis@1:396/45 to Dumas Walker on Wed Dec 2 18:47:37 2020
    Hello Dumas (or Mike).

    <On 02Dec2020 17:34 Dumas Walker (1:2320/105) wrote a message to MARC LEWIS regarding RE: Problem with legacy t >

    @TZUTC: -0500
    @MSGID: 53.tub@1:2320/105 242d5066
    @REPLY: 1:396/45.0 fc6a8011
    @PID: Synchronet 3.18a-Linux May 24 2020 GCC 7.5.0
    @TID: SBBSecho 3.11-Linux r3.173 May 24 2020 GCC 7.5.0
    @CHRS: ASCII 1
    I've asked one of the Nodes that feeds off me to send a NetMail to me
    to see what happens.

    Based on some of the other messages here, I would ask that node
    what they are using as the PacketType setting for your node in
    their sbbsecho.ini file. Maybe they need to change that to
    something else?

    It seems that everyone is using the 2+ type packet. As you can see from the quoted message kludge lines above, the @MSGID line, which includes the extraneous characts worked fine since this this EchoMail unlike NetMail where it plays hell with Squish. There's bound to be something that can be addressed with regards to that; I *seriously* doubt that Squish is at fault.

    Best regards,
    Marc

    --- timEd/2 1.10.y2k+
    * Origin: Sursum Corda! BBS-Huntsville,AL-bbs.sursum-corda.com (1:396/45)
  • 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@1:103/705 to Marc Lewis on Wed Dec 2 17:59:38 2020
    Re: RE: Problem with legacy t
    By: Marc Lewis to Dumas Walker on Wed Dec 02 2020 06:47 pm

    I *seriously* doubt that Squish is at fault.

    Based on what information?
    --
    digital man

    Synchronet/BBS Terminology Definition #26:
    DTE = Data Terminal Equipment
    Norco, CA WX: 67.4F, 14.0% humidity, 3 mph SSW wind, 0.00 inches rain/24hrs --- SBBSecho 3.11-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Rob Swindell@1:103/705 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.secureser ver.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.1F, 14.0% humidity, 6 mph SW wind, 0.00 inches rain/24hrs
    --- SBBSecho 3.11-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Oli@2:280/464.47 to Marc Lewis on Thu Dec 3 11:18:56 2020
    02 Dec 20 18:47, you wrote to Dumas Walker:

    Based on some of the other messages here, I would ask that node
    what they are using as the PacketType setting for your node in
    their sbbsecho.ini file. Maybe they need to change that to
    something else?

    It seems that everyone is using the 2+ type packet. As you can see
    from the quoted message kludge lines above, the @MSGID line, which includes the extraneous characts worked fine since this this EchoMail unlike NetMail where it plays hell with Squish. There's bound to be something that can be addressed with regards to that; I *seriously*
    doubt that Squish is at fault.

    I don't believe it has anything to do with the MSGID. If Squish had a problem with this kind of MSGID lines, it would be clearly Squish's fault. But I think it's unlikely, because this problem would be already known for a long time (and most likely fixed). MSGID are just IDs for dupe checking and message linking, not for figuring out the zone number or address.

    or fixing the problem we have to know the real cause of the problem. Have you inspected the raw packets before tossing?

    * Origin: kakistocracy (2:280/464.47)
  • From Fred Riccio@1:132/174 to Oli on Thu Dec 3 08:33:11 2020
    Hello Oli!

    03 Dec 20 11:18, Oli wrote to Marc Lewis:

    For fixing the problem we have to know the real cause of the problem.
    Have you inspected the raw packets before tossing?

    Yes. My Packet Inspector program didn't note any problems. The zone IS in the packet header where it is supposed to be.

    I also ran the packet through GMD...


    ----- gmd.txt begins -----

    GMD - Grunged Message Detect Utility, version 3.10 for PC/MS-DOS.
    Written by David Troendle (1:396/5)
    Documented and distributed by John Souvestre (1:396/1)

    + 08:30:28 4R108DBK.PKT (ID=FF, 2,533b) from 1:103/705 to 1:132/174
    - 08:30:28 #1, From: Rob Swindell Area: Net Mail
    * 08:30:28 1 Packet (2,533b), 1 msg (0 bad), Time: 0:00
    ----- gmd.txt ends -----


    IMHO, the REAL cause is the design of the "packed message" header in the packet. It does not have a place to put zone or point, forcing the tosser to get it somewhere else. Using the packet header is incorrect, since NetMail is often routed, and the packet header indicates the system who sent the message to me and not the original author.

    --- Msged/NT 6.0.1
    * Origin: Somewhere in New Hampshire's White Mountains (1:132/174)
  • From Dumas Walker@1:2320/105 to ROB SWINDELL on Thu Dec 3 15:42:00 2020
    As I already told you, Synchronet (actually, SBBSecho) only recently started ev
    n adding MSGIDs to FTN NetMail messages. "that line" didn't even exist in Synch
    onet-generated FTN NetMail messages before June of this year.

    Do other tossers add MSGIDs to netmail messages?


    * SLMR 2.1a * She cried away her life since she fell off the cradle!!
    --- SBBSecho 3.11-Linux
    * Origin: capitolcityonline.net * Telnet/SSH:2022/HTTP (1:2320/105)
  • From Rob Swindell@1:103/705 to Dumas Walker on Thu Dec 3 17:35:11 2020
    Re: RE: Problem with legacy t
    By: Dumas Walker to ROB SWINDELL on Thu Dec 03 2020 03:42 pm

    As I already told you, Synchronet (actually, SBBSecho) only recently started ev
    n adding MSGIDs to FTN NetMail messages. "that line" didn't even exist in Synch
    onet-generated FTN NetMail messages before June of this year.

    Do other tossers add MSGIDs to netmail messages?

    Apparently they do. It wasn't *my* idea. :-) http://cvs.synchro.net/commitlog.ssjs#42030
    --
    digital man

    Synchronet "Real Fact" #23:
    The third ever Synchronet BBS was The Beast's Domain (sysop: King Drafus). Norco, CA WX: 63.9F, 10.0% humidity, 6 mph ESE wind, 0.00 inches rain/24hrs --- SBBSecho 3.11-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Wilfred van Velzen@2:280/464 to Dumas Walker on Fri Dec 4 09:55:51 2020
    Hi Dumas,

    On 2020-12-03 15:42:00, you wrote to ROB SWINDELL:

    Do other tossers add MSGIDs to netmail messages?

    It's usually the message editors that do that, the tossers shouldn't add this, unless they are the ones generating some auto created message.

    Bye, Wilfred.

    --- FMail-lnx64 2.1.0.18-B20170815
    * Origin: FMail development HQ (2:280/464)
  • From Rob Swindell@1:103/705 to Wilfred van Velzen on Fri Dec 4 11:02:40 2020
    Re: RE: Problem with legacy t
    By: Wilfred van Velzen to Dumas Walker on Fri Dec 04 2020 09:55 am

    Hi Dumas,

    On 2020-12-03 15:42:00, you wrote to ROB SWINDELL:

    Do other tossers add MSGIDs to netmail messages?

    It's usually the message editors that do that, the tossers shouldn't add this, unless they are the ones generating some auto created message.

    Or the BBS software. As is with Synchronet, the message editors are just simple text editors and don't really know anything about FidoNet "control paragraphs" (kludge lines). So Synchronet adds the FTN message-ID when the message is saved by the user, regardless of what editor was used to write the text.

    I realize offline editors, like GoldEd, work differently.
    --
    digital man

    Synchronet "Real Fact" #113:
    Weedpuller "Assassin" http://youtu.be/opw9RPUOcv8
    Norco, CA WX: 69.8F, 12.0% humidity, 0 mph SW wind, 0.00 inches rain/24hrs
    --- SBBSecho 3.11-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Wilfred van Velzen@2:280/464 to Rob Swindell on Fri Dec 4 20:47:50 2020
    Hi Rob,

    On 2020-12-04 11:02:40, you wrote to me:

    Do other tossers add MSGIDs to netmail messages?

    It's usually the message editors that do that, the tossers shouldn't add
    this, unless they are the ones generating some auto created message.

    Or the BBS software. As is with Synchronet, the message editors are just simple text editors and don't really know anything about FidoNet "control paragraphs" (kludge lines). So Synchronet adds the FTN message-ID when
    the
    message is saved by the user, regardless of what editor was used to write the text.

    You could consider that "the editor"... ;)


    Bye, Wilfred.

    --- FMail-lnx64 2.1.0.18-B20170815
    * Origin: FMail development HQ (2:280/464)