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
SEEN-BY: 106/127 120/457 123/10 134/100 153/105 135 757 802 154/10 30 40 50 SEEN-BY: 154/700 203/0 220/80 90 221/6 226/18 227/201 280/464 301/1 3634/12 SEEN-BY: 116/116 123/25 150 755 135/300 153/7715 261/38 3634/15 27 50 119 SEEN-BY: 123/115 170 257 180 40 299/6 123/190 35 126 200 3634/0 18/0 123/0 SEEN-BY: 1/120

* 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
SEEN-BY: 103/705 106/127 124/5016 134/100 153/105 135 757 802 154/10 SEEN-BY: 203/0 221/1 6 360 229/101 240/5832 280/464 5003 288/100 292/854 SEEN-BY: 292/8125 301/1 310/31 335/364 396/45 423/81 120 770/1 2452/250 SEEN-BY: 4500/1
@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)

Hello Wilfred,

2) The Sysop should be re
SEEN-BY: 103/705 106/127 124/5016 134/100 153/105 135 757 802
154/10
SEEN-BY: 203/0 221/1 6 360 229/101 240/5832 280/464 5003 288/100
292/854
SEEN-BY: 292/8125 301/1 310/31 335/364 396/45 423/81 120 770/1
2452/250
SEEN-BY: 4500/1
@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)

Hi Alan,

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

2) The Sysop should be re
SEEN-BY: 103/705 106/127 124/5016 134/100 153/105 135 757 802
154/10
SEEN-BY: 203/0 221/1 6 360 229/101 240/5832 280/464 5003 288/100
292/854
SEEN-BY: 292/8125 301/1 310/31 335/364 396/45 423/81 120 770/1
2452/250
SEEN-BY: 4500/1
@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)

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)

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..

SEEN-BY: 123/456

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)

Re: ILink Application
By: Alan Ianson to Wilfred van Velzen on Sat Jun 26 2021 04:00:12

Hello. I was a member on Ilink and I would like to join agains. Can someone please semd the information to plt[at]sbbs.dynu.net please?

Thanks
--- SBBSecho 3.14-Linux
* Origin: sbbs.dynu.net 2025 (1:275/201.100)

Hello Phil,

Hello. I was a member on Ilink and I would like to join agains. Can someone please semd the information to plt[at]sbbs.dynu.net please?

I found this application for ilink a few messges back.


==== Begin: "ilink.txt" ====
= OTHERNETS (1:153/757) =======================================================
Msg : 1222 of 1239
From : Michael Luko 1:266/512 26 Aug 21 03:35:00
To : All
Subj : ILink Application ===============================================================================
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 reasonably active in maintaining
his/her board and willing to keep the ILink conference
list current when requested by the ILink Conference
Administrator.

3) The BBS must be capable of transferring mail using a
network-compatible method such as QWK or FTN.


BBS software you are using [ ]

At present, the following BBS software is acceptable: PCBoard,
WildCat!, Remote Access, or Synchronet. Other BBS software will be
considered; on approval by the Admin Team. Test conference(s) can be
used for review. Once messages prove to be flowing properly you will
be given access to all ILink conferences.

How long has your system been in operation at its
current location? [ ]

Software is licensed to (name) [ ]

Primary Sysop Name [ ]
Address [ ]
City [ ] State/Province/Country [ ]
Postal Code [ ]
Daytime phone number (incl. country and area code) [ ]
Evening phone number (incl. country and area code) [ ]
What is your email address? [ ]

Your BBS Name [ ]
Main data number (incl. country and area code)[ ]
Is your BBS telnettable? YES [Telnet:// ] NO [ ]

Do you have a HomePage YES [http:// ] NO [ ]

Description of your BBS (maximum 55 characters):
[ ]

How do you plan on transferring mail packets:
QWK: Via Dialup [ ], Telnet [ ], FTP [ ], HTTP [ ]
FTN: Via Dialup [ ], FTP [ ], Email [ ], Binkp [ ]

Thank you! Please email your application to:

Barry.Martin@techware2k.com

Application form last Reviewed/Revised on: 09-07-18 by Michael Luko
==== End: "ilink.txt" ====

I would fill that out and email it to Barry Martin at the address listed above or possibly netmail Michael Luko at 1:266/512.

Ttyl :-),
Al

--- GoldED+/LNX 1.1.5-b20180707
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)

Michael\

Yes
--- SBBSecho 3.14-Linux
* Origin: sbbs.dynu.net 2025 (1:275/201.100)