From Eastside75@1:123/4040 to All on Saturday, August 09, 2025 16:30:25
Having some issues with fido out of the blue sending test.
--- SBBSecho 3.23-Win32
* Origin: Thunder-Line BBS - thunder.synchro.net (1:123/4040)
From RBB Test Robot@2:221/360 to Eastside75 on Sunday, August 10, 2025 01:43:38
09 Aug 25 16:30:25 Eastside75 (1:123/4040) wrote:
==== begin of the message ====
@TZUTC: -0500
@MSGID: 12.fidonet_fidotest@1:123/4040 2cfcf3fd
@PID: Synchronet 3.20d-Win32 master/500ef7050 Mar 03 2025 MSC 1942
@TID: SBBSecho 3.23-Win32 master/500ef7050 Mar 03 2025 MSC 1942
@COLS: 80
@BBSID: THUNDER
@CHRS: ASCII 1
@NOTE: SlyEdit 1.89e (2025-02-09) (ICE style)
Having some issues with fido out of the blue sending test.
-+- SBBSecho 3.23-Win32
+ Origin: Thunder-Line BBS - thunder.synchro.net (1:123/4040)
SEEN+BY: 1/120 18/0 19/10 104/119 114/10 116/116 120/616 123/0 25 180 755 3001 SEEN+BY: 123/3002 4040 129/215 135/115 153/757 7715 154/10 30 50 700 218/840 SEEN+BY: 220/6 20 30 90 221/1 6 360 222/2 226/18 44 50 1701 250/1 275/1000 SEEN+BY: 280/464 301/1 335/364 341/66 234 460/58 712/1321 2320/105 3634/0 12 SEEN+BY: 3634/24 27 56 57 58 60 119 5020/1042
@PATH: 123/4040 3634/12 154/10 221/6
==== end of the message ====
---
* Origin: RBB Test Robot @ FIDOTEST (2:221/360)
From Matthew Asham@1:153/149.42 to All on Sunday, September 07, 2025 12:46:57
Noticed a response I sent on Saturday didn't make its way out - hopefully not shadow banned by the gods of upstream!
--- BinktermPHP v1.4.5
* Origin: myPoint System (1:153/149.42)
From RBB Test Robot@2:221/360 to Matthew Asham on Sunday, September 07, 2025 23:03:04
07 Sep 25 12:46:57 Matthew Asham (1:153/149.42) wrote:
==== begin of the message ====
@TZUTC: -0700
@MSGID: 1:153/149.42 1E389012
Noticed a response I sent on Saturday didn't make its way out - hopefully not shadow banned by the gods of upstream!
---
* Origin: RBB Test Robot @ FIDOTEST (2:221/360)
From awehttam@2:460/256 to RBB Test Robot on Monday, September 08, 2025 00:19:29
07 Sep 25 12:46:57 Matthew Asham (1:153/149.42) wrote:
==== begin of the message ====
@TZUTC: -0700
@MSGID: 1:153/149.42 1E389012
Noticed a response I sent on Saturday didn't make its way out - hopefully not shadow banned by the gods of upstream!
-+- BinktermPHP v1.4.5
+ Origin: myPoint System (1:153/149.42)
SEEN+BY: 19/10 134/100 153/135 143 148 149 151 153 757 7083 154/10 218/840
SEEN+BY: 221/1 6 360 280/464 301/1 335/364 341/66 234 460/58 3634/12 5020/1042
@PATH: 153/149 757 221/6
==== end of the message ====
Thanks. Weird
--- tg BBS v0.7.1
* Origin: Fido by Telegram BBS from Stas Mishchenkov (2:460/256)
From Nick Andre@1:229/426 to Matthew Asham on Monday, September 08, 2025 13:08:57
On 07 Sep 25 12:46:57, Matthew Asham said the following to All:
Noticed a response I sent on Saturday didn't make its way out - hopefully n shadow banned by the gods of upstream!
What does that mean, "shadow banned"
Nick
--- Renegade vY2Ka2
* Origin: Joey, do you like movies about gladiators? (1:229/426)
From Matthew Asham@1:153/149.42 to Nick Andre on Monday, September 08, 2025 12:42:43
Noticed a response I sent on Saturday didn't make its way out - hopefully shadow banned by the gods of upstream!
What does that mean, "shadow banned"
It means silently discarded. Like if someone sets up a filter to silently discard posts from a certain sender.
When I noticed a response hadn't made its way out I had to quip about it.
Matthew
--- BinktermPHP v1.4.5
* Origin: myPoint System (1:153/149.42)
From August Abolins@1:153/149.42 to Matthew Asham on Monday, September 08, 2025 13:36:48
--- Original Message ---
From: Matthew Asham
Date: 2025-09-08 12:42:43.323958
Subject: Re: test
What does that mean, "shadow banned"
It means silently discarded. Like if someone sets up a filter to silently discard posts from a certain sender.
I suppose in fidonet parlance that would be a twit filter?
--- BinktermPHP v1.4.5
* Origin: myPoint System (1:153/149.42)
From awehttam@2:460/256 to August Abolins on Tuesday, September 09, 2025 00:07:07
From: Matthew Asham
Date: 2025-09-08 12:42:43.323958
Subject: Re: test
What does that mean, "shadow banned"
It means silently discarded. Like if someone sets up a filter to silently discard posts from a certain sender.
I suppose in fidonet parlance that would be a twit filter?
Exactly ?
--- tg BBS v0.7.1
* Origin: Fido by Telegram BBS from Stas Mishchenkov (2:460/256)
From Daryl Stout@1:19/33 to Matthew Asham on Monday, September 08, 2025 10:06:02
Matthew,
Noticed a response I sent on Saturday didn't make its way out -
hopefully not shadow banned by the gods of upstream!
The networks were hungry, and needed some nourishment. <G>
Daryl
... ALERT!! Moderator is in the echo!! Look innocent!!
=== MultiMail/Win v0.52
--- SBBSecho 3.23-Win32
* Origin: The Thunderbolt BBS -- Little Rock, Arkansas (1:19/33)
From Hdt@3:633/414 to All on Saturday, September 27, 2025 19:04:22
--- Mystic BBS v1.12 A49 2024/05/29 (Linux/64)
* Origin: Star Collision BBS, Uppsala, Sweden (2:201/137)
From Daryl Stout@1:19/33 to Hdt on Saturday, September 27, 2025 12:15:55
testing
It made it to Arkansas.
Daryl
... I'm not speeding...I'm late for lunch.
=== MultiMail/Win v0.52
--- SBBSecho 3.29-Win32
* Origin: The Thunderbolt BBS - Little Rock, Arkansas (1:19/33)
From RBB Test Robot@2:221/360 to Carlos Navarro on Sunday, November 23, 2025 18:27:36
23 Nov 25 17:17:05 Carlos Navarro (2:341/234.5885) wrote:
==== begin of the message ====
@MSGID: 2:341/234.5885 692333cc
@PID: GED+W64 1.1.5-b20250409
@TID: SBBSecho 3.23-Win32 master/500ef7050 Mar 03 2025 MSC 1942
@BBSID: CYBNOT
@TZUTC: 0100
@CHRS: CP850 2
Hi,
Playing with SBBS...
Carlos
-+- SBBSecho 3.23-Win32
+ Origin: cyb synchronet point (2:341/234.5885)
SEEN+BY: 19/10 153/757 154/10 218/840 221/1 6 360 280/464 301/1 335/364 341/66 SEEN+BY: 341/234 460/58 5020/1042
@PATH: 341/234 221/6
==== end of the message ====
---
* Origin: RBB Test Robot @ FIDOTEST (2:221/360)
From Sean Rima@2:263/1 to Carlos Navarro on Sunday, November 23, 2025 16:29:53
This is what I wanted to check. Messages exported from my SBBS point have two PATH kludge lines, one of them empty (and inserted before the SEEN+BYs). :-m
Tommi's robot did not display it, so I guess some tosser removed it.
This is what I wanted to check. Messages exported from my SBBS point
have two PATH kludge lines, one of them empty (and inserted before the SEEN+BYs). :-m
Tommi's robot did not display it, so I guess some tosser removed it.
It is not in the msgbase here, so I think my hpt removed it.
'Tommi
---
* Origin: nntps://news.fidonet.fi (2:221/360)
From Nick Boel@1:154/700 to Carlos Navarro on Sunday, November 23, 2025 12:50:17
This is what I wanted to check. Messages exported from my SBBS point
have two PATH kludge lines, one of them empty (and inserted before
the SEEN+BYs). :-m
Tommi's robot did not display it, so I guess some tosser removed it.
Here is a reply via Synchronet's NNTP service. Maybe someone can let me know if there is two PATH kludge lines here, too.
If not, it could be specific to Golded accessing the Synchronet message bases (full support is nowhere near, and Golded uses very old SMB libraries, if I'm not mistaken).
Regards,
Nick
... Sarcasm: because beating people up is illegal.
--- SBBSecho 3.32-Linux
* Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (1:154/700)
From Nick Boel@1:154/700 to Tommi Koivula on Sunday, November 23, 2025 12:55:12
Hello Tommi,
On Sun Nov 23 2025 08:15 pm UTC+2:00, you wrote:
It is not in the msgbase here, so I think my hpt removed it.
If you could, please check my last message and this one. This one is directly from the BBS itself.
Regards,
Nick
... "Take my advice, I don't use it anyway."
--- SBBSecho 3.32-Linux
* Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (1:154/700)
From Carlos Navarro@2:341/234 to All on Sunday, November 23, 2025 20:10:36
23 Nov 2025 18:19, I wrote to Sean Rima:
This is what I wanted to check. Messages exported from my SBBS point
have two PATH kludge lines, one of them empty (and inserted before the SEEN+BYs). :-m
I correct myself. My SBBS point does not export 2 PATH lines - only one (and empty one)
Sorry.
From RBB Test Robot@2:221/360 to Carlos Navarro on Sunday, November 23, 2025 21:11:28
23 Nov 25 20:10:36 Carlos Navarro (2:341/234) wrote:
==== begin of the message ====
@TID: FMail-W32 2.3.2.3-B20240423
@TZUTC: 0100
@CHRS: UTF-8 4
@MSGID: 2:341/234 69235c39
@REPLY: 2:341/234.1 69234239
23 Nov 2025 18:19, I wrote to Sean Rima:
This is what I wanted to check. Messages exported from my SBBS point
have two PATH kludge lines, one of them empty (and inserted before the SEEN+BYs). :-m
I correct myself. My SBBS point does not export 2 PATH lines - only one (and empty one)
Sorry.
---
* Origin: RBB Test Robot @ FIDOTEST (2:221/360)
From Tommi Koivula@2:221/1.1 to Nick Boel on Sunday, November 23, 2025 21:13:10
Hi Nick.
23 Nov 25 12:55:12, you wrote to me:
It is not in the msgbase here, so I think my hpt removed it.
If you could, please check my last message and this one. This one is directly from the BBS itself.
I checked, no double PATH's from you.
Maybe it is SBBS as a point?
'Tommi
---
* Origin: Point One (2:221/1.1)
From Tommi Koivula@2:221/1.1 to Carlos Navarro on Sunday, November 23, 2025 21:14:57
Hi Carlos.
23 Nov 25 20:10:36, you wrote to All:
I correct myself. My SBBS point does not export 2 PATH lines - only one (and empty one)
But it should not do that.
'Tommi
---
* Origin: Point One (2:221/1.1)
From Wilfred van Velzen@2:280/464 to Carlos Navarro on Sunday, November 23, 2025 21:31:29
Hi Carlos,
On 2025-11-23 20:10:36, you wrote to All:
It seems that it's FMail adding another one.
Doubt full. Never seen that happen...
Bye, Wilfred.
--- FMail-lnx64 2.3.2.4-B20240523
* Origin: FMail development HQ (2:280/464)
From Wilfred van Velzen@2:280/464 to Carlos Navarro on Sunday, November 23, 2025 21:35:58
Hi Carlos,
On 2025-11-23 20:27:44, you wrote to Nick Boel:
So it seems that SBBS with point address sends PKTs with empty PATH kludge. FMail (the tosser at my bossnode) doesn't like it and adds
another PATH line.
Is it really a kludge line? Starting with a Ctrl-A (0x01) character?
Bye, Wilfred.
--- FMail-lnx64 2.3.2.4-B20240523
* Origin: FMail development HQ (2:280/464)
From Nick Boel@1:154/10 to Carlos Navarro on Sunday, November 23, 2025 15:09:00
Hey Carlos!
On Sun, 23 Nov 2025 20:10:36 +0100, you wrote:
I correct myself. My SBBS point does not export 2 PATH lines - only
one (and empty one) Sorry.
It seems that it's FMail adding another one.
So, if the message originates from a point, and goes to a boss node, the PATH should be empty until the boss node adds it's node to it, correct?
Regards,
Nick
... Sarcasm: because beating people up is illegal.
--- GoldED+/LNX 1.1.5-b20250409
* Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (1:154/10)
From Nick Boel@1:154/10 to Carlos Navarro on Sunday, November 23, 2025 15:13:46
Hey Carlos!
On Sun, 23 Nov 2025 20:27:44 +0100, you wrote:
So it seems that SBBS with point address sends PKTs with empty PATH
kludge. FMail (the tosser at my bossnode) doesn't like it and adds
another PATH line.
As a point, should it send no PATH kludge at all then?
Regards,
Nick
... Sarcasm: because beating people up is illegal.
--- GoldED+/LNX 1.1.5-b20250409
* Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (1:154/10)
From Carlos Navarro@2:341/234 to Wilfred van Velzen on Sunday, November 23, 2025 22:17:02
23 Nov 2025 21:35, you wrote to me:
So it seems that SBBS with point address sends PKTs with empty
PATH kludge. FMail (the tosser at my bossnode) doesn't like it
and adds another PATH line.
Is it really a kludge line? Starting with a Ctrl-A (0x01) character?
Yes. This is how my node receives the PKTs from the SBBS point (I'm changing 0x01 to ^a, etc):
And this is how my node's FMail exports that to my links (including you):
I found it, and I can confirm your findings. I can also see it's still present in .pkt files that left my system to my other links. But it isn't present in my messagebase!?
Odd, it switches the order of the original Path line and the seen-by!?
Can you send me the original .pkt file from your SBBS point? So I can try to reproduce it?
BTW: I don't know if there is something to improve, it might just be a matter of GIGO. ;-)
BTW2: .pkt files that leave my point system don't have a path line at all.
Bye, Wilfred.
--- FMail-lnx64 2.3.2.4-B20240523
* Origin: FMail development HQ (2:280/464)
From Nick Boel@1:154/10 to Wilfred van Velzen on Monday, November 24, 2025 07:23:40
Hey Wilfred!
On Mon, 24 Nov 2025 12:08:24 +0100, you wrote:
I found it, and I can confirm your findings. I can also see it's still present in .pkt files that left my system to my other links. But it
isn't present in my messagebase!?
Difference between stored and forwarded, maybe?
BTW: I don't know if there is something to improve, it might just be a matter of GIGO. ;-)
BTW2: .pkt files that leave my point system don't have a path line at
all.
That is what I was wondering..
1) Should a system setup as a point be sending an empty PATH kludge?
2) Should a system setup as a boss node be appending it's address to an existing PATH kludge (even if it is empty), rather than creating a new one?
Regards,
Nick
... Sarcasm: because beating people up is illegal.
--- GoldED+/LNX 1.1.5-b20250409
* Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (1:154/10)
From Wilfred van Velzen@2:280/464 to Nick Boel on Monday, November 24, 2025 14:39:54
Hi Nick,
On 2025-11-24 07:23:40, you wrote to me:
I found it, and I can confirm your findings. I can also see it's still
present in .pkt files that left my system to my other links. But it
isn't present in my messagebase!?
Difference between stored and forwarded, maybe?
Of course, but I was just wondering why that happens.
BTW: I don't know if there is something to improve, it might just be a
matter of GIGO. ;-)
BTW2: .pkt files that leave my point system don't have a path line at
all.
That is what I was wondering..
1) Should a system setup as a point be sending an empty PATH kludge?
No, an empty path doesnt' add anything compared to no path at all, it just takes up space.
2) Should a system setup as a boss node be appending it's address to
an existing PATH kludge (even if it is empty),
Or delete the empty one and create a new one. But the end result would be the same. ;-)
rather than creating a new one?
Leaving the empty one in and create a new one, is the worse thing to do I suppose.
Bye, Wilfred.
--- FMail-lnx64 2.3.2.4-B20240523
* Origin: FMail development HQ (2:280/464)
From Nick Boel@1:154/10 to Wilfred van Velzen on Monday, November 24, 2025 08:06:40
Hey Wilfred!
On Mon, 24 Nov 2025 14:39:54 +0100, you wrote:
Difference between stored and forwarded, maybe?
Of course, but I was just wondering why that happens.
Since this is only Synchronet (point) -> FMail (boss), it might be nice to see how other tossers setup as a boss handle the situation before creating a ticket anywhere.
BTW: I don't know if there is something to improve, it might just be
a matter of GIGO. ;-)
The beauty of kludge lines. ;)
1) Should a system setup as a point be sending an empty PATH
kludge?
No, an empty path doesnt' add anything compared to no path at all, it
just takes up space.
Although, one could argue the originating system creates the PATH kludge, and all others after would append it. At one time I think there was an issue where the originating system (as a point) would put it's 3D address in the PATH, which would screw with the boss node being seen as a dupe or an already processed message.
2) Should a system setup as a boss node be appending it's address
to an existing PATH kludge (even if it is empty),
Or delete the empty one and create a new one. But the end result would
be the same. ;-)
Sure, but should that be done with the boss node?
rather than creating a new one?
Leaving the empty one in and create a new one, is the worse thing to do
I suppose.
If there wasn't one to begin with, this wouldn't be an issue. I just don't know if there is /supposed/ to be an empty one created by the point (originating system), or not (per standards or whatever). If not, it should be a Synchronet/sbbsecho issue, not something FMail needs to work around. Especially if the issue has never been seen before this.
Regards,
Nick
... Sarcasm: because beating people up is illegal.
--- GoldED+/LNX 1.1.5-b20250409
* Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (1:154/10)
From Tommi Koivula@2:221/6.66 to Carlos Navarro on Monday, November 24, 2025 16:50:28
From Mike Powell@1:2320/107 to Carlos Navarro on Monday, November 24, 2025 08:32:22
Re: test
By: Carlos Navarro to All on Sun Nov 23 2025 17:17:05
Playing with SBBS...
Received in Kentucky, USA!
Mike
--- SBBSecho 3.28-Linux
* Origin: Capitol City Test System (1:2320/107)
From Mike Powell@1:2320/107 to Carlos Navarro on Monday, November 24, 2025 08:34:35
Re: test
By: Carlos Navarro to Sean Rima on Sun Nov 23 2025 18:19:49
@PATH:
^^^^^^
This is what I wanted to check. Messages exported from my SBBS point have tw
Sounds like a bug that maybe should be reported to Digital Man.
Tommi's robot did not display it, so I guess some tosser removed it.
Some tossers are good at cleaning stuff up. ;)
Mike
--- SBBSecho 3.28-Linux
* Origin: Capitol City Test System (1:2320/107)
From Wilfred van Velzen@2:280/464 to Nick Boel on Monday, November 24, 2025 18:15:54
Hi Nick,
On 2025-11-24 08:06:40, you wrote to me:
Difference between stored and forwarded, maybe?
Of course, but I was just wondering why that happens.
Since this is only Synchronet (point) -> FMail (boss), it might be nice to see
how other tossers setup as a boss handle the situation before creating a ticket anywhere.
And nothing seems to be breaking anyway. It's just a bit annoying to see the empty path line. ;-)
BTW: I don't know if there is something to improve, it might just be
a matter of GIGO. ;-)
The beauty of kludge lines. ;)
1) Should a system setup as a point be sending an empty PATH
kludge?
No, an empty path doesnt' add anything compared to no path at all, it
just takes up space.
Although, one could argue the originating system creates the PATH kludge, and
all others after would append it. At one time I think there was an issue where
the originating system (as a point) would put it's 3D address in the PATH, which would screw with the boss node being seen as a dupe or an already processed message.
Well, a 3D address in a path line is not according to the standard and as such a real bug...
2) Should a system setup as a boss node be appending it's address
to an existing PATH kludge (even if it is empty),
Or delete the empty one and create a new one. But the end result would
be the same. ;-)
Sure, but should that be done with the boss node?
Where else? (Given the point system creates the empty path line, which it shouldn't)
rather than creating a new one?
Leaving the empty one in and create a new one, is the worse thing to do
I suppose.
If there wasn't one to begin with, this wouldn't be an issue. I just don't know if there is /supposed/ to be an empty one created by the point (originating system), or not (per standards or whatever).
Of course not.
If not, it should be a Synchronet/sbbsecho issue, not something FMail needs to work around. Especially if the issue has never been seen
before this.
No software should create an empty path line. But it doesn't seem to break anything if it does, so I'm not going to change FMail to handle this exception more gracefully...
Bye, Wilfred.
--- FMail-lnx64 2.3.2.4-B20240523
* Origin: FMail development HQ (2:280/464)
From Nick Boel@1:154/10 to Wilfred van Velzen on Monday, November 24, 2025 13:07:34
Hey Wilfred!
On Mon, 24 Nov 2025 18:15:54 +0100, you wrote:
Well, a 3D address in a path line is not according to the standard and
as such a real bug...
Typo. 2 is right next to 3. ;)
Regards,
Nick
... Sarcasm: because beating people up is illegal.
--- GoldED+/LNX 1.1.5-b20250409
* Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (1:154/10)
From Carlos Navarro@2:341/234.1 to Wilfred van Velzen on Monday, November 24, 2025 20:54:58
24 Nov 2025 12:08, you wrote to me:
I found it, and I can confirm your findings. I can also see it's still present in .pkt files that left my system to my other links. But it
isn't present in my messagebase!?
I can see the empty PATH kludge with GoldED, but just before the message text, instead of after the SEENBY lines.
From Wilfred van Velzen@2:280/464 to Carlos Navarro on Monday, November 24, 2025 21:24:03
Hi Carlos,
On 2025-11-24 20:54:58, you wrote to me:
I found it, and I can confirm your findings. I can also see it's
still present in .pkt files that left my system to my other links.
But it isn't present in my messagebase!?
I can see the empty PATH kludge with GoldED, but just before the message text,
instead of after the SEENBY lines.
So on top of the message where all the regular kludge lines are?
Odd, it switches the order of the original Path line and the seen-by!?
Yes, it's weird.
After reading the "PATH" section in fsc-0074.001, the proposed successor of fts-0004.001, which has much better definitions of everything, I got a theory about this.
fsc-0074.001 states:
- Shall begin with the seven character literal:
^APATH:<space>
The empty PATH line in your messages doesn't have the space before the new line, so FMail probably doesn't regard this as a PATH line, but as a regular line. And puts it at the end of the message text, before the newly generated seen-by's and path lines.
Can you send me the original .pkt file from your SBBS point? So I can
try to reproduce it?
Ok, check your inbound.
Got it, thanks.
BTW2: .pkt files that leave my point system don't have a path line at
all.
Mine neither...
Except for your Synchronet point system...
Bye, Wilfred.
--- FMail-lnx64 2.3.2.4-B20240523
* Origin: FMail development HQ (2:280/464)
From Carlos Navarro@2:341/234.1 to Wilfred van Velzen on Tuesday, November 25, 2025 21:34:02
24 Nov 2025 21:24, you wrote to me:
I can see the empty PATH kludge with GoldED, but just before the
message text, instead of after the SEENBY lines.
So on top of the message where all the regular kludge lines are?
From Carlos Navarro@2:341/234.1 to Nick Boel on Tuesday, November 25, 2025 21:42:35
23 Nov 2025 15:13, you wrote to me:
So it seems that SBBS with point address sends PKTs with empty PATH
kludge. FMail (the tosser at my bossnode) doesn't like it and adds
another PATH line.
As a point, should it send no PATH kludge at all then?
Not sure what is correct. Some tossers and point packages do, while others don't.
I've checked .PKT's from several points I'm using or have tested.
These don't insert a PATH kludge:
- Winpoint
- OpenXP
- Crashmail II
- FMail (default, but can be enabled)
These insert a PATH kludge (including the bossnode's 2D address):
- HotdogEd
- Aftershock
- D'Bridge
From Nick Boel@1:154/10 to Carlos Navarro on Tuesday, November 25, 2025 17:50:20
Hey Carlos!
On Tue, 25 Nov 2025 21:42:34 +0100, you wrote:
As a point, should it send no PATH kludge at all then?
Not sure what is correct. Some tossers and point packages do, while
others don't.
I would imagine an empty PATH kludge would be better than inserting the bossnode's 2D address *before* it gets to the bossnode!
Someone did notice that the correct way to write the PATH (without addresses) is "^APATH:<space>" and Synchronet seems to be writing "^APATH:", so maybe that is the only issue?
I've checked .PKT's from several points I'm using or have tested.
Well done on the testing! You're absolutely killing it lately. ;)
These don't insert a PATH kludge:
- Winpoint
- OpenXP
- Crashmail II
- FMail (default, but can be enabled)
These insert a PATH kludge (including the bossnode's 2D address):
- HotdogEd
- Aftershock
- D'Bridge
Do messages coming from these display at the boss node if it's address is already in the PATH? Or do they get forwarded on without being stored in the message base?
Regards,
Nick
... Sarcasm: because beating people up is illegal.
--- GoldED+/LNX 1.1.5-b20250409
* Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (1:154/10)
From Wilfred van Velzen@2:280/464 to Carlos Navarro on Wednesday, November 26, 2025 08:55:37
Hi Carlos,
On 2025-11-25 21:34:02, you wrote to me:
I can see the empty PATH kludge with GoldED, but just before the
message text, instead of after the SEENBY lines.
So on top of the message where all the regular kludge lines are?
It kind of makes sense, because the "^APATH:" line without the <space> after the ':' is just a kludge line. So I can see the logic in placing it on top with the other kludge lines.
Bye, Wilfred.
--- FMail-lnx64 2.3.2.4-B20240523
* Origin: FMail development HQ (2:280/464)
From Nick Boel@1:154/10 to Carlos Navarro on Friday, November 28, 2025 08:44:46
Hey Carlos!
On Tue, 25 Nov 2025 21:42:34 +0100, you wrote:
Not sure what is correct. Some tossers and point packages do, while
others don't.
Is there a way you could edit the raw message that Synchronet creates, and add a space to the PATH kludge before it gets sent off to FMail?
This way, if FMail appends to that line, rather than creating a new one and leaving the original alone, we know this should be the fix, and can report it to Rob.
Regards,
Nick
... Sarcasm: because beating people up is illegal.
--- GoldED+/LNX 1.1.5-b20250409
* Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (1:154/10)
From Wilfred van Velzen@2:280/464 to Nick Boel on Friday, November 28, 2025 16:38:01
Hi Nick,
On 2025-11-28 08:44:46, you wrote to Carlos Navarro:
This way, if FMail appends to that line, rather than creating a new
one and leaving the original alone, we know this should be the fix,
and can report it to Rob.
The simplest fix is to not create empty PATH lines at all (with or without space)! ;-)
Bye, Wilfred.
--- FMail-lnx64 2.3.2.4-B20240523
* Origin: FMail development HQ (2:280/464)
From Nick Boel@1:154/10 to Wilfred van Velzen on Friday, November 28, 2025 10:15:04
Hey Wilfred!
On Fri, 28 Nov 2025 16:38:00 +0100, you wrote:
The simplest fix is to not create empty PATH lines at all (with or
without space)! ;-)
Is /not/ creating a PATH kludge covered anywhere in the holy grail of documented standards and/or proposals?
So far, all that has been pointed out is a document that shows the proper format of the PATH kludge.
Regards,
Nick
... Sarcasm: because beating people up is illegal.
--- GoldED+/LNX 1.1.5-b20250409
* Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (1:154/10)
From Wilfred van Velzen@2:280/464 to Nick Boel on Friday, November 28, 2025 17:42:37
Hi Nick,
On 2025-11-28 10:15:04, you wrote to me:
The simplest fix is to not create empty PATH lines at all (with or
without space)! ;-)
Is /not/ creating a PATH kludge covered anywhere in the holy grail of documented standards and/or proposals?
So far, all that has been pointed out is a document that shows the proper format of the PATH kludge.
fts-0004.001 says it's not required.
fsc-0074.001 says:
- Shall contain a list of net/node numbers.
- Shall identify at least one net/node number. "Blank"
path lines shall not be transmitted.
So that is pretty clear to me! ;-)
Bye, Wilfred.
--- FMail-lnx64 2.3.2.4-B20240523
* Origin: FMail development HQ (2:280/464)
From Stephen Hurd@1:103/1 to Nick Boel on Friday, November 28, 2025 22:38:00
Re: test
By: Nick Boel to Wilfred van Velzen on Fri Nov 28 2025 10:15 am
Is /not/ creating a PATH kludge covered anywhere in the holy grail of documented standards and/or proposals?
There's FSC-0067 which proposes a 5D (in a neat new format) SPTH ("Sticky PaTH") and strips the PATH lines.
--- SBBSecho 3.31-FreeBSD
* Origin: BBSDev.net - The BBS Developers Network (1:103/1)
From Ivan Zelenyi@2:50/86.1 to All on Saturday, August 08, 2026 18:24:58
test
--
With best regards,
Ivan Zelenyi
--- Hotdoged/2.13.5/Android
* Origin: HUAWEI EVE-LX9N (2:50/86.1)
From RBB Test Robot@2:221/360 to Ivan Zelenyi on Sunday, August 09, 2026 00:53:04
08 Aug 26 18:24:58 Ivan Zelenyi (2:50/86.1) wrote:
==== begin of the message ====
@MSGID: 2:50/86.1 2702ed40
@PID: Hotdoged/2.13.5/Android
@TID: jNode/Android
@CHRS: CP866 2
test
--- AfterShock/Android 1.7.5
* Origin: my android phone (1:261/20.716)
From Robert Wolfe@1:261/20 to All on Sunday, July 26, 2026 20:43:08
testing new aup update pf pxw
... Women who wear mini-skirts sure are cheeky folk.
--- Wildcat! v10.0.500.1 (Jun 28 2026), Editor Mod v1.7
* Origin: Over the Brink : Grand Island, NY - brinkbbs.org (1:261/20)
From Robert Wolfe@1:261/20.2 to all on Tuesday, August 04, 2026 17:54:32
testing
--- Over the Brink ANetBBS
* Origin: Over the Brink ANetBBS - Powered by RockyLinux (1:261/20.2)
From Robert Wolfe@1:261/20.2 to Ivan Zelenyi on Monday, August 10, 2026 14:34:10
reply.
--- Ivan Zelenyi wrote:
test
--
With best regards,
Ivan Zelenyi
--- Over the Brink ANetBBS
* Origin: Over the Brink ANetBBS - Powered by RockyLinux (1:261/20.2)
From robert wolfe@1:261/20.716 to All on Thursday, August 13, 2026 14:57:50
Testing
--- AfterShock/Android 1.8.0
* Origin: my android phone (1:261/20.716)
From Robert Wolfe@1:261/20 to All on Wednesday, August 19, 2026 09:44:36
testing. new build came down the pipeline this morning.
... Platinum Xpress & Wildcat!..... Nice!!!!
--- Platinum Xpress/Win/WINServer v10.0gr18.1
* Origin: Over the Brink : Grand Island, NY - brinkbbs.org (1:261/20)
From RBB Test Robot@2:221/1 to Robert Wolfe on Friday, August 21, 2026 22:17:28
26 Jul 26 20:43:08 Robert Wolfe (1:261/20) wrote:
==== begin of the message ====
@TID: PX/Win v10.0gr17 PX28-1176M
@MSGID: 1:261/20 0d2b43b1
@TZUTC: -0400
testing new aup update pf pxw
... Women who wear mini-skirts sure are cheeky folk.
-+- Wildcat! v10.0.500.1 (Jun 28 2026), Editor Mod v1.7
+ Origin: Over the Brink : Grand Island, NY - brinkbbs.org (1:261/20)
SEEN+BY: 1/19 100 16/0 19/36 37 134/101 142/104 799 201/0 203/0 221/0 1 6 250 SEEN+BY: 229/426 240/1120 5832 261/20 280/464 5003 5555 292/854 301/1 320/119 SEEN+BY: 320/219 319 2119 322/762 325/304 342/19 423/81
@PATH: 261/20 320/219 221/1
==== end of the message ====
---
* Origin: RBB Test Robot @ FIDOTEST (2:221/1.0)
From Mirror Robot@1:229/0 to Robert Wolfe on Friday, August 21, 2026 15:35:02
On 19 Aug 26 09:44:36 Robert Wolfe (1:261/20) wrote:
==== start of message ====
@TID: PX/Win v10.0gr18.1 PX28-1176M
@MSGID: 1:261/20 5DE2BF88
@TZUTC: -0400
testing. new build came down the pipeline this morning.
---
* Origin: RBB Test Robot @ FIDOTEST (2:221/360)
From RBB Test Robot@2:221/360 to Martin Kazmaier on Friday, July 24, 2026 20:36:30
23 Nov 24 02:01:00 Martin Kazmaier (1:340/1101) wrote:
==== begin of the message ====
@RESCANNED 2:221/1
@MSGID: 1:340/1101 01010447
@REPLY: 2:221/360 67418950
@PID: THE READER V4.50 [freeware]
@NOTE: IceEdit 2.35 K96741
@TID: FastEcho 1.46.1 43288
22 Nov 24 20:33:00 Martin Kazmaier (1:340/1101) wrote:
==== begin of the message ====
@MSGID: 1:340/1101 0121115e
@PID: THE READER V4.50 [freeware]
@NOTE: IceEdit 2.35 K96741
@TID: FastEcho 1.46.1 43288
I'm not seeing responses to my test messsges, but I am receiving netmail.
---
* Origin: RBB Test Robot @ FIDOTEST (2:221/1.0)
From Robert Wolfe@1:261/20 to All on Saturday, August 22, 2026 08:05:10
testing
... Women prefer the simple things in life...MEN!
--- Wildcat! v10.0.500.2 (Jun 28 2026), Editor Mod v1.7
* Origin: Over the Brink : Grand Island, NY - brinkbbs.org (1:261/20)
From RBB Test Robot@2:221/1 to Robert Wolfe on Saturday, August 22, 2026 15:12:22
22 Aug 26 08:05:10 Robert Wolfe (1:261/20) wrote:
==== begin of the message ====
@TID: PX/Win v10.0gr18.1 PX28-1176M
@MSGID: 1:261/20 a5818d92
@TZUTC: -0400
testing
... Women prefer the simple things in life...MEN!
-+- Wildcat! v10.0.500.2 (Jun 28 2026), Editor Mod v1.7
+ Origin: Over the Brink : Grand Island, NY - brinkbbs.org (1:261/20)
SEEN+BY: 1/19 100 16/0 19/36 37 134/101 142/104 799 201/0 203/0 221/0 1 6 250 SEEN+BY: 229/426 240/1120 5832 261/20 280/464 5003 5555 292/854 301/1 320/119 SEEN+BY: 320/219 319 2119 322/762 325/304 342/19 423/81
@PATH: 261/20 320/219 221/1
==== end of the message ====
---
* Origin: RBB Test Robot @ FIDOTEST (2:221/1.0)
From Mirror Robot@1:229/0 to Robert Wolfe on Saturday, August 22, 2026 08:00:08
On 22 Aug 26 07:31:36 Robert Wolfe (1:261/20) wrote:
