1. Forum
  2. FidoNet
  3. TUB

  • 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 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.4øF, 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 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 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.8øF, 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)