1. Forum
  2. FidoNet
  3. OTHERNETS

  • ILink Application

    From Michael Luko@1:266/512 to All on Sat Jun 26 03:35:00 2021
    ILink Application

    Does your BBS meet the requirements below? YES [ ] NO [ ]

    1) The BBS must be available to callers for a reasonable
    period of time sufficient to allow exchange of echomail
    packages at least once each day, preferably seven days
    a week.

    2) The Sysop should be re
    * Origin: -Somewhere- (1:266/512)
  • From Wilfred van Velzen@2:280/464 to Michael Luko on Sat Jun 26 11:15:14 2021
    * Carbon copied to Michael Luko 1:266/512

    Hi Michael,

    On 2021-06-26 03:35:00, you wrote to All:

    @MSGID: 1:266/512@fidonet.org cfaf4622
    ILink Application

    Does your BBS meet the requirements below? YES [ ] NO [ ]

    1) The BBS must be available to callers for a reasonable
    period of time sufficient to allow exchange of echomail
    packages at least once each day, preferably seven days
    a week.

    2) The Sysop should be re
    @PATH: 153/757 221/6 1 280/464

    Yes we all should be "re" all the time!

    Missing origin line => broken message. :-(


    Bye, Wilfred.
    --- FMail-lnx64 2.1.0.18-B20170815
    * Origin: FMail development HQ (2:280/464)
  • From Alan Ianson@1:153/757 to Wilfred van Velzen on Sat Jun 26 02:40:02 2021
    Hello Wilfred,

    2) The Sysop should be re
    154/10
    292/854
    2452/250
    @PATH: 153/757 221/6 1 280/464

    That message as it sits in my msgbase has no path or seen by lines at all. It simply ends at "should be re" and has no tear or origin line.

    It has a msgid but no other kludges. I don't know what happened to it but it is broken.

    Ttyl :-),
    Al
    --- GoldED+/LNX 1.1.5-b20180707
    * Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)
  • From Wilfred van Velzen@2:280/464 to Alan Ianson on Sat Jun 26 11:49:33 2021
    Hi Alan,

    On 2021-06-26 02:40:02, you wrote to me:

    2) The Sysop should be re
    154/10
    292/854
    2452/250
    @PATH: 153/757 221/6 1 280/464

    That message as it sits in my msgbase has no path or seen by lines at all. It simply ends at "should be re" and has no tear or origin line.

    It has a msgid but no other kludges. I don't know what happened to it but it is broken.

    The previous message by Michael had this path line:

    PATH: 266/512 261/38 153/757 221/6 1 280/464

    So maybe it broke passing through 261/38. Janis had some problems this week...

    Bye, Wilfred.
    --- FMail-lnx64 2.1.0.18-B20170815
    * Origin: FMail development HQ (2:280/464)
  • From Alan Ianson@1:153/757 to Wilfred van Velzen on Sat Jun 26 03:00:12 2021
    Hello Wilfred,

    It has a msgid but no other kludges. I don't know what happened
    to it but it is broken.

    The previous message by Michael had this path line:

    PATH: 266/512 261/38 153/757 221/6 1 280/464

    Yes, both of those messages arrived here in the same .pkt.

    So maybe it broke passing through 261/38. Janis had some problems this week...

    I wish I had the input packet to look at but I don't, so I'm not sure what the cause is. I hope it didn't break here.

    Ttyl :-),
    Al
    --- GoldED+/LNX 1.1.5-b20180707
    * Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)
  • From Alan Ianson@1:153/757 to Wilfred van Velzen on Sat Jun 26 07:22:37 2021
    Hello Wilfred,

    PATH: 266/512 261/38 153/757 221/6 1 280/464

    So maybe it broke passing through 261/38. Janis had some problems this week...

    I went looking and I discovered a couple things..

    That message is intact at 261/38, it was also forwarded to 222/2 and it is intact there. What the cause is of my copy being short and missing path and seen by lines and tear and origin line I am not sure.

    There are two copies of that message at 261/38. A second short copy of that message arrived at 261/38 with a new origin line, "* Origin: -Somewhere- (1:266/512)". I think the message was changed at 301/1 and that's why it was tossed again.

    There were also two copies of my post to you. One of the copies that passed through 301/1 had quoted seen by lines removed. Those quoted lines looked like this..


    More questions than answers. It seems now that that short post happened here. I don't have the input .pkt to examine, so I am not sure how it compares to the original message.

    I am copying inbound files to a backup directory now but it is rather crude and doesn't take filename collisions into account. If need be I hope I can find the inbound packets in there to examine.

    Ttyl :-),
    Al
    --- GoldED+/LNX 1.1.5-b20180707
    * Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)
  • From Richard Dowson@1:105/44 to Michael Luko on Thu May 25 02:21:47 2023

    thanks a lot for information, was searching for it
    --- SBBSecho 3.14-Win32
    * Origin: The X-Bit BBS - x-bit.org - Forest Grove, Or (1:105/44)