@TZUTC: -0700
@MSGID: 35.fido-tgsuppor@1:153/757.2 24d480ee
@PID: Synchronet 3.19a-Linux master/46c91758e Apr 8 2021 GCC 10.2.0
@TID: SBBSecho 3.14-Linux master/46c91758e Apr 8 2021 GCC 10.2.0
@BBSID: TRMB
@CHRS: ASCII 1
@PATH 153/757 770/1 280/464 229/101 426
.. of spaceship tg_support.
--- SBBSecho 3.14-Linux
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757.2)
@MSGID: 35.fido-tgsuppor@1:153/757.2 24d480ee
@PID: Synchronet 3.19a-Linux master/46c91758e Apr 8 2021 GCC 10.2.0 @TZUTC: -0700
@TID: SBBSecho 3.14-Linux master/46c91758e Apr 8 2021 GCC 10.2.0
@BBSID: TRMB
@CHRS: ASCII 1
.. of spaceship tg_support.
--- SBBSecho 3.14-Linux
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757.2)
SEEN-BY: 153/105 135 250 757 802 203/0 220/70 221/0 6 226/17 229/101 SEEN-BY: 261/38 267/800 280/464 301/1 340/1000 396/45 423/120 712/848 SEEN-BY: 770/1 100 340 772/220 230
@PATH: 153/757 770/1 280/464
.. of spaceship tg_support.
Why?
My automated message sent out on the 1st is visible on Agency but not
on Al's system.
There seems to have been a break somewhere in the link for this echo,
but it looks like it's cleared up now.
@PATH: 229/664 426 301/1 280/464 770/1
My automated message sent out on the 1st is visible on Agency but not
on Al's system.
Well, that's discouraging.
My automated message sent out on the 1st is visible on Agency but not
on Al's system.
Well, that's discouraging.
MSGID: 1:229/664@fidonet 87eb9b94--- Telegard v3.09.g2-sp4/mL
TZUTC: -0400
CHRS: ASCII 1
TID: FastEcho 1.46.1 7731285
Echo Tag: TG_SUPPORT
Moderator: Jay Harris, 1:229/664
Access: Anyone
Topic: TG_SUPPORT is the support echo for Telegard BBS Software
---
* Origin: Northern Realms | 289-424-5180 | bbs.nrbbs.net (1:229/664)
PATH: 229/664 426
@PATH 153/757 770/1 280/464 229/101 426 Hello Jay,
Without being accusational/assigning blame, etc: I'm wondering if 229/101 was perhaps having issues the same time SciNet was "down"?
I send mail in the TG_SUPPORT area to 1:261/38, 2:221/6 and recently 3:770/1 as well as a handful of other nodes.
You might consider something like that. It can be helpful when one
point fails as they will from time to time.
You might consider something like that. It can be helpful when one
point fails as they will from time to time.
I'm assumung that's where dupe checking comes in?
@PATH 153/757 770/1 280/464 229/101 426 Hello Jay,
P.S: Here's the path your message took to me.
Without zone numbers, it's hard to be certain:
You -> Paul/Avon -> Wilfred -> Frank/Netsurge -> Nick/atreyu
Without being accusational/assigning blame, etc: I'm wondering if
229/101 was perhaps having issues the same time SciNet was "down"?
@PATH 153/757 770/1 280/464 229/101 426 Hello Jay,
Without zone numbers, it's hard to be certain:
No it isn't, because there are no double net numbers anymore in the fidonet nodelist.
You -> Paul/Avon Frank/Netsurge -> Nick/atreyu
You got it right! ;)
That's likely. But with enough (fidoweb style) links, mail would just route around Frank's system...
...there are no double net numbers anymore in the fidonet
nodelist.
...there are no double net numbers anymore in the fidonet
nodelist.
The last time I looked about 2 years ago, there were two systems
sharing the same net number.
Hi August,
On 2021-04-10 09:20:41, you wrote to me:
...there are no double net numbers anymore in the fidonet
nodelist.
The last time I looked about 2 years ago, there were two systems
sharing the same net number.
I very much doubt that. I think it's more than a decade ago, there were double net numbers in the fidonet nodelist.
...there are no double net numbers anymore in the fidonet
nodelist.
The last time I looked about 2 years ago, there were two systems
sharing the same net number.
I very much doubt that. I think it's more than a decade ago, there were
double net numbers in the fidonet nodelist.
310 is used in both Z1 and Z2.
310 is used in both Z1 and Z2.
Your right, I forgot about that one. It crept back into the nodelist
in 2017. The Host (and RC) for that net is incompetent anyway. He
never cared to respond to inquiries that were made if he could fix
the situation at that time, as far as I remember.
Your right, I forgot about that one. It crept back into the nodelist
in 2017. The Host (and RC) for that net is incompetent anyway. He
never cared to respond to inquiries that were made if he could fix
the situation at that time, as far as I remember.
Who would have thought that Fido would have a net war! LOL
Sysop: | Coz |
---|---|
Location: | Anoka, MN |
Users: | 2 |
Nodes: | 4 (0 / 4) |
Uptime: | 157:42:44 |
Calls: | 162 |
Files: | 5,334 |
Messages: | 221,571 |