My question is whether there is an option anywhere that effects
whether SEENBY lines and/or PATH lines are added/stripped, and if so where. I have had a complaint that packets are arriving upstream with
only a PATH of the system they have been sent to, and not including my systems in the path ie I sent from 4:920/69 to 4:920/1 to 2:301/1.
When the packet arrives at 2:301/1, the PATH is completely missing and
the SEENBY is " All the best John
SEEN+BY: 218/700 280/464 301/1 103/705
@P+TH: 103/705
My question is whether there is an option anywhere that effects
whether SEENBY lines and/or PATH lines are added/stripped, and if so
where. I have had a complaint that packets are arriving upstream with
only a PATH of the system they have been sent to, and not including my
systems in the path ie I sent from 4:920/69 to 4:920/1 to 2:301/1.
When the packet arrives at 2:301/1, the PATH is completely missing and
the SEENBY is " All the best John
SEEN+BY: 218/700 280/464 301/1 103/705
@P+TH: 103/705
4:920/1 is not in the PATH, and not in the SEEN+BY lines either.
The problem is real.
4:920/1 is not in the PATH, and not in the SEEN+BY lines either.
The problem is real.
This is normal for the synchronet specific areas. They are exchanged
using QWK with the other synchronet systems in their network. The QWK network is not FTN, and don't contain the PATH and SEENBY lines,
afaik...
This is normal for the synchronet specific areas. They are exchanged
using QWK with the other synchronet systems in their network. The QWK
network is not FTN, and don't contain the PATH and SEENBY lines,
afaik...
The problem occours with every mail leaving John's system. Since John is writing mails using different systems, it's quite difficult to diagnose from outside. However, since 4:4/0 is processing mails again, i've received
813 dupes from 4:920/1, all without path and all without seen by.
@PATH: 902/26 27 90/1 229/426 301/1 280/464
This is normal for the synchronet specific areas. They are exchanged using QWK with the other synchronet systems in their network. The QWK network is not FTN, and don't contain the PATH and SEENBY lines, afaik...
Dupes originating from 4:920/1 or other systems also?
Did they not contain any seen-by and path lines at all? Because in FN_SYSOP there were messages from Fernando Toledo today, that did
contain the full path:
@PATH: 902/26 27 90/1 229/426 301/1 280/464So it doesn't seem to be a general problem at 4:4/0. And if they went through 4:4/0 these dupes should at least contain the path from 90/1,
and some SEEN+BY's...
I agree, that would be the expected behaviour.Yup. Mea Culpa, Mea Maxima Culpa.
I think it's caused by 4:920/1's system, John Dovey.
@MSGID: 120.fidonet_syncsyso@4:920/1 2510d692
@REPLY: 2:280/464 60ab985c
@PID: Synchronet 3.18c-Linux master/113a9a5 Feb 17 2021 GCC 5.4.0
@TZUTC: -0500
@TID: SBBSecho 3.12-Linux master/113a9a5 Feb 17 2021 GCC 5.4.0
@BBSID: ELGATO
@CHRS: ASCII 1
@NOTE: SlyEdit 1.74 (2021-01-23) (DCT style)
Re: Re: Seenby/Path
By: Wilfred van Velzen to Matthias Hertzog on Mon May 24 2021 14:11:03
This is normal for the synchronet specific areas. They are exchanged
using QWK with the other synchronet systems in their network. The QWK
network is not FTN, and don't contain the PATH and SEENBY lines,
afaik...
True. Only when gated to FidoNet does it come into play. This message for example is posted on the same conference but the FidoNet version, so *should* have the correct path/seen-bys... ??? John
--- SBBSecho 3.12-Linux
* Origin: El Gato de Fuego - elgato.synchronetbbs.org (4:920/1)
SEEN-BY: 30/0 80/1 103/705 124/5016 154/10 203/0 218/700 221/0 1 6 229/101 SEEN-BY: 229/426 240/1120 5832 261/38 280/464 5003 288/100 292/8125 SEEN-BY: 301/0 1 101 113 341/66 396/45 423/120 712/848 770/1 920/1 2452/250
SEEN-BY: 5020/1042 5058/104
@PATH: 301/1 280/464
Dupes originating from 4:920/1 or other systems also?
All received by 4:920/1 here, original messages were from all kind of people from all over the world. The messages went from 4:4/0's system to 4:920/1's system and then got packed for 2:301/1, without seen by and without path.
Did they not contain any seen-by and path lines at all? Because in
FN_SYSOP there were messages from Fernando Toledo today, that did
contain the full path:
@PATH: 902/26 27 90/1 229/426 301/1 280/464
So it doesn't seem to be a general problem at 4:4/0. And if they went
through 4:4/0 these dupes should at least contain the path from 90/1,
and some SEEN+BY's...
I agree, that would be the expected behaviour.
I think it's caused by 4:920/1's system, John Dovey.
Eithe 301/1 strips the path line, or it doesn't contain any upon
arrival at 301/1...
So you received them from 4:920/1 directly? That wasn't clear to me.yes
Have you inspected the .pkt files directly? As received from 4:920/1?yes
confirm, they did not contain seen by and path lines.Did they not contain any seen-by and path lines at all?
Because
in FN_SYSOP there were messages from Fernando Toledo today, that
did contain the full path:
@PATH: 902/26 27 90/1 229/426 301/1 280/464
So it doesn't seem to be a general problem at 4:4/0. And if they
went through 4:4/0 these dupes should at least contain the path
from 90/1, and some SEEN+BY's...
I agree, that would be the expected behaviour.
I think it's caused by 4:920/1's system, John Dovey.
On http://wiki.synchro.net/config:sbbsecho.ini
I only see the 2 ZoneBlind(Threshold) settings that could be of influence...
On http://wiki.synchro.net/config:sbbsecho.ini
I only see the 2 ZoneBlind(Threshold) settings that could be of
influence...
I saw them too, but John says, his version of software does not
have these option. That's why he asked how to fix the problem.
No, I see the ZoneBlind options, just not any options to include or not the Seenbys and path.I only see the 2 ZoneBlind(Threshold) settings that could be of
influence...
I saw them too, but John says, his version of software does not
have these option. That's why he asked how to fix the problem.
I only see the 2 ZoneBlind(Threshold) settings that could be of
influence...
I saw them too, but John says, his version of software does not
have these option. That's why he asked how to fix the problem.
No, I see the ZoneBlind options, just not any options to include or
not the Seenbys and path.
I don't think there are any "direct" setting for this. Have you set the ZoneBlind options as suggested on the wiki?:That option has never been changed from "disabled".
"Assume that node numbers are not duplicated across zones (set to true with a Threshold of 4 for ?FidoWeb? operation)"
"Assume that node numbers are not duplicated across zones (set to
true with a Threshold of 4 for ?FidoWeb? operation)"
Ok, I've made that change and Matthias reports that it's now working as expected. Thank you for your assistance, much appreciated.
@PATH: 920/69 1 301/1 280/464
I don't think there are any "direct" setting for this. Have youThat option has never been changed from "disabled".
set the ZoneBlind options as suggested on the wiki?:
I have a question. In the docs on http://www.synchro.net/docs/sbbsecho.html it has screenshots of the SBBSEcho configuration program. It looks nothing like the one on my system
The problem occours with every mail leaving John's system. Since John is writing mails using different systems, it's quite difficult to diagnose from outside. However, since 4:4/0 is processing mails again, i've received 813 dupes from 4:920/1, all without path and all without seen by.
See https://wiki.synchro.net/util:sbbsecho for the current SBBSecho documentation.
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 371 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 174:34:56 |
| Calls: | 7,915 |
| Files: | 12,983 |
| Messages: | 5,797,649 |