Re: test
By: Hdt to All on Sat Sep 27 2025 19:04:22

testing
--- SBBSecho 3.29-Win32
* Origin: Wicked Garden - wgbbs.ddns.net - Melbourne, Vic. (3:633/414)

got your message over here! =)

Stephan
--- SBBSecho 3.28-Linux
* Origin: FuNToPiA BBS - telnet://funtopia.synchro.net:3023 (2:240/5411)

Hello, Hdt.
On 27/09/2025 12.04 you wrote:

testing

Test failed. You do not exist.

https://nodehist.fidonet.org.ua/?address=3:633/414



--
'Tommi

---
* Origin: jamnntpd/lnx (2:221/6.0)

Hello Tommi!

27 Sep 25 16:37, you wrote to Hdt:

testing

Test failed. You do not exist.

https://nodehist.fidonet.org.ua/?address=3:633/414

Does on my list:

,414,Wicked_Garden_BBS,Burnside_Vic,Hung_Tran,-Unpublished-,300,CM,IBN:wgbbs.ddns.net


%-;


Stephen


--- GoldED+/LNX 1.1.5-b20250409
* Origin: Dragon's Lair ---:- dragon.vk3heg.net -:--- Prt: 6800 (3:633/280)

Hi Stephen.

28 Sep 25 13:44:24, you wrote to me:

27 Sep 25 16:37, you wrote to Hdt:

testing

Test failed. You do not exist.

https://nodehist.fidonet.org.ua/?address=3:633/414

Does on my list:

,414,Wicked_Garden_BBS,Burnside_Vic,Hung_Tran,-Unpublished-,300,CM,IBN:w gbbs.ddns.net

Yep, on my list too. Now. ;)

%-;

'Tommi

---
* Origin: Point One (2:221/1.1)

Hello Hdt!

On 27 Sep 2025, Hdt said the following...

testing
--- SBBSecho 3.29-Win32
* Origin: Wicked Garden - wgbbs.ddns.net - Melbourne, Vic. (3:633/414)

Got you here!

Best regards
Bj”rn

--- Mystic BBS v1.12 A49 2024/05/29 (Linux/64)
* Origin: Star Collision BBS, Uppsala, Sweden (2:201/137)

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)

Hi,

Playing with SBBS...

Carlos


--- SBBSecho 3.23-Win32
* Origin: cyb synchronet point (2:341/234.5885)

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)

Hello Carlos!

23 Nov 25 17:17, you wrote to all:

@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
@PATH:
Hi,

Playing with SBBS...

Carlos

--- SBBSecho 3.23-Win32
* Origin: cyb synchronet point (2:341/234.5885)

Sean


... TCOB1: binkd only binkd.rima.ie
--- FMail-lnx 2.3.1.0
* Origin: Testing my day away (2:263/1)

Thank you Sean!

23 Nov 2025 16:29, you wrote to me:

@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
@PATH:

^^^^^^

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.

Carlos

--- GoldED+/W32-MSVC 1.1.5-b20180707
* Origin: cyberiada (2:341/234.1)

Hi Carlos.

23 Nov 25 18:19, you wrote to Sean Rima:

@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
@PATH:

^^^^^^

I checked the .PKT from you from backups. There you can see the empty PATH.

Message header -+---------------------------------------------------------------------
From : "Carlos Navarro"
To : "All"
Subject : "test"
DateTime : "23 Nov 25 17:17:05"
Attr : 0x0000
OrigAddr : 341/234
DestAddr : 221/6

Message text -+--------------------------------------------------------------------- AREA:FIDOTEST
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)
PATH:
PATH: 341/234

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)

Hey Carlos!

On Sun, Nov 23 2025 11:19:49 -0600, you wrote:

Thank you Sean!

23 Nov 2025 16:29, you wrote to me:

@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
@PATH:

^^^^^^

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)

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)

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.

It seems that it's FMail adding another one.

Carlos

--- GoldED+/W32-MSVC 1.1.5-b20180707
* Origin: cyberiada (2:341/234)

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.

It seems that it's FMail adding another one.

Carlos

-+- GoldED+/W32-MSVC 1.1.5-b20180707
+ Origin: cyberiada (2:341/234)
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)

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)

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)

23/11/2025 19:50, Nick Boel (1:154/700):

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

No, it wasn't GoldED - I had tested with NNTP, and web and terminal
too... But I was confused, I didn't check the correct backups at my
system (outbound instead of inbound).

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.

Carlos
--- SBBSecho 3.23-Win32
* Origin: cyb synchronet point (2:341/234.5885)

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)

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)

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)

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)

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):

-+- SBBSecho 3.23-Win32
# Origin: cyb synchronet point (2:341/234.5885)
SEEN+BY: 341/234
^aPATH:

And this is how my node's FMail exports that to my links (including you):

-+- SBBSecho 3.23-Win32
# Origin: cyb synchronet point (2:341/234.5885)
^aPATH:
SEEN+BY: 341/234
^aPATH: 341/234

Carlos

--- GoldED+/W32-MSVC 1.1.5-b20180707
* Origin: cyberiada (2:341/234)

Hi Carlos,

On 2025-11-23 22:17:02, you wrote to me:

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):

-+- SBBSecho 3.23-Win32
# Origin: cyb synchronet point (2:341/234.5885)
SEEN+BY: 341/234
^aPATH:

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!?

-+- SBBSecho 3.23-Win32
# Origin: cyb synchronet point (2:341/234.5885)
^aPATH:
SEEN+BY: 341/234
^aPATH: 341/234

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)

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)

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)

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)

Hi Carlos.

23 Nov 25 22:17, you wrote to Wilfred van Velzen:

^aPATH:
SEEN+BY: 341/234
^aPATH: 341/234

^ATID: FMail-lnx64 2.3.2.3-B20251119
^AMSGID: 2:221/6.66 69246f92
^ACHRS: UTF-8 4
^ATZUTC: 0200
...
-+-
+ Origin: FPoint (2:221/6.66)
SEEN+BY: 221/6
^APATH: 221/6

Fmail seems to put the boss address to the PATH and SEENBY lines when exporting the msg.

'Tommi

---
* Origin: FPoint (2:221/6.66)

Hi Carlos.

24 Nov 25 16:50, I wrote to you:

SEEN+BY: 221/6
^APATH: 221/6

Fmail seems to put the boss address to the PATH and SEENBY lines when exporting the msg.

There seems to be setting for that..

"Do not add the node number of the boss to the PATH kludge on point systems"

'Tommi

--- FMail-lnx 2.3.2.3-B20251119
* Origin: FPoint (2:221/6.26)

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)

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)

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)

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)

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.

-+- SBBSecho 3.23-Win32
# Origin: cyb synchronet point (2:341/234.5885)
^aPATH:
SEEN+BY: 341/234
^aPATH: 341/234

Odd, it switches the order of the original Path line and the seen-by!?

Yes, it's weird.

Can you send me the original .pkt file from your SBBS point? So I can
try to reproduce it?

Ok, check your inbound.

BTW2: .pkt files that leave my point system don't have a path line at
all.

Mine neither...

Carlos

--- GoldED+/W32-MSVC 1.1.5-b20180707
* Origin: cyberiada (2:341/234.1)

24 Nov 2025 17:34, you wrote to me:

SEEN+BY: 221/6
^APATH: 221/6

Fmail seems to put the boss address to the PATH and SEENBY lines
when exporting the msg.

There seems to be setting for that..

"Do not add the node number of the boss to the PATH kludge on point systems"

Yes! The "No point in PATH" setting. But I think that it works the opposite of expected.

Carlos

--- GoldED+/W32-MSVC 1.1.5-b20180707
* Origin: cyberiada (2:341/234.1)

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?

-+- SBBSecho 3.23-Win32
# Origin: cyb synchronet point (2:341/234.5885)
^aPATH:
SEEN+BY: 341/234
^aPATH: 341/234

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)

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?

Yes, see here: https://www.cyberiada.org/fido/tmpfiles/fidotest-sbbs-point-snapshot.png

BTW2: .pkt files that leave my point system don't have a path
line at all.

Mine neither...

Except for your Synchronet point system...

I meant this point (.1), that uses FMail, like yours.

Carlos

--- GoldED+/W32-MSVC 1.1.5-b20180707
* Origin: cyberiada (2:341/234.1)

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

Carlos

--- GoldED+/W32-MSVC 1.1.5-b20180707
* Origin: cyberiada (2:341/234.1)

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)

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?

Yes, see here: https://www.cyberiada.org/fido/tmpfiles/fidotest-sbbs-point-snapshot.png

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)

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)

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)

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)

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)

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)

25 Nov 2025 17:50, you wrote to me:

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!

Maybe, but it has been and is a rather common practice. See below...

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

I've also checked old messages (late 90s) from my points in a local echo, and these also inserted the PATH kludge including the bossnode (my system):

- FrontDoor's ScanToss
- FastEcho

Do messages coming from these display at the boss node if it's address
is already in the PATH?

Yes.

Or do they get forwarded on without being stored in the message base?

They are stored and also get forwarded. This has never been an issue, IIRC.

Carlos

--- GoldED+/W32-MSVC 1.1.5-b20180707
* Origin: cyberiada (2:341/234.1)

26 Nov 2025 08:55, you wrote to me:

So on top of the message where all the regular kludge lines are?

Yes, see here:
https://www.cyberiada.org/fido/tmpfiles/fidotest-sbbs-point-snaps
hot.png

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.

Yes.

BTW, did you check if you can also see that in GoldED, like in the screenshot?

Carlos

--- GoldED+/W32-MSVC 1.1.5-b20180707
* Origin: cyberiada (2:341/234.1)

28 Nov 2025 08:44, you wrote to me:

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?

Yes, I did the test (I edited the PKT before my node's FMail processed it)

This way, if FMail appends to that line, rather than creating a new
one and leaving the original alone,

Yes, it does.

we know this should be the fix, and can report it to Rob.

Hmm... IMO that would be more of a workaround than a fix. I think it would be better to just not add an empty PATH kludge.

Carlos

--- GoldED+/W32-MSVC 1.1.5-b20180707
* Origin: cyberiada (2:341/234.1)

Hi Carlos,

On 2025-12-08 21:00:43, you wrote to me:

So on top of the message where all the regular kludge lines are?

Yes, see here:
https://www.cyberiada.org/fido/tmpfiles/fidotest-sbbs-point-snaps
hot.png

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.

Yes.

BTW, did you check if you can also see that in GoldED, like in the screenshot?

Yes it looks the same in my golded.


Bye, Wilfred.

--- FMail-lnx64 2.3.2.4-B20240523
* Origin: FMail development HQ (2:280/464)

Hey Carlos!

On Mon, 08 Dec 2025 21:00:02 +0100, you wrote:

Or do they get forwarded on without being stored in the message base?

They are stored and also get forwarded. This has never been an issue,
IIRC.

I seem to recall there was an issue in the past regarding this (messages from points were not being displayed, or something), and that could be why Synchronet/sbbsecho is sending that PATH empty (although if it had the space according to the spec that someone else mentioned, it may actually get processed/removed just fine by other tossers and this may have never been noticed).

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)

Re: test
By: Carlos Navarro to Nick Boel on Mon Dec 08 2025 09:04 pm

Hmm... IMO that would be more of a workaround than a fix. I think it would be better to just not add an empty PATH kludge.

This issue has now been addressed: https://gitlab.synchro.net/main/sbbs/-/commit/fe2d6930583d7961596c3e1cd0a01b6

A bug report (at gitlab.synchro.net) would've been nice to have. :-)
--
digital man (rob)

Sling Blade quote #17:
Charles Bushman: A shovel just makes too goddamned much racket.
Norco, CA WX: 83.5øF, 25.0% humidity, 5 mph WSW wind, 0.00 inches rain/24hrs --- SBBSecho 3.32-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

10 Dec 2025 16:05, you wrote to me:

This issue has now been addressed:

Great!

A bug report (at gitlab.synchro.net) would've been nice to have. :-)

Sorry, I intended to... O:-)

Carlos

--- GoldED+/W32-MSVC 1.1.5-b20180707
* Origin: cyberiada (2:341/234.1)

Re: test
By: Carlos Navarro to Rob Swindell on Thu Dec 11 2025 09:37 pm

A bug report (at gitlab.synchro.net) would've been nice to have. :-)

Sorry, I intended to... O:-)

Next time. :-)

There'll certainly more opportunities (bugs created/found) in the future. lol --
digital man (rob)

Synchronet "Real Fact" #10:
The name "DOVE-Net" was suggested by King Drafus (sysop of The Beast's Domain) Norco, CA WX: 81.2øF, 36.0% humidity, 4 mph WNW wind, 0.00 inches rain/24hrs --- SBBSecho 3.32-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

11/12/2025 22:50, Rob Swindell (1:103/705):

  > A bug report (at gitlab.synchro.net) would've been nice to have. :-)

Sorry, I intended to... O:-)

Next time. :-)

There'll certainly more opportunities (bugs created/found) in the
future. lol

Sure ;-)

I've just upgraded my Synchronet point to the dev version. This message
should go out without that empty PATH kludge.

Carlos
--- SBBSecho 3.33-Win32
* Origin: cyb synchronet point (2:341/234.5885)

Hi Carlos,

On 2025-12-12 17:46:44, you wrote to Rob Swindell:

@MSGID: 72.fidonet_fidotest@2:341/234.5885 2da17d3c
@REPLY: 15424.fidotest@1:103/705 2da0aec8
@PID: Synchronet 3.21a-Win32 master/d27b45adf Dec 12 2025 MSC 1944
@TZUTC: 0100
@TID: SBBSecho 3.33-Win32 master/d27b45adf Dec 12 2025 MSC 1944
@BBSID: CYBNOT
@CHRS: UTF-8 4
@FORMAT: flowed
@NOTE: Mozilla Thunderbird
11/12/2025 22:50, Rob Swindell (1:103/705):

… > A bug report (at gitlab.synchro.net) would've been nice to have. :-)

Sorry, I intended to... O:-)

Next time. :-)

There'll certainly more opportunities (bugs created/found) in the
future. lol

Sure ;-)

I've just upgraded my Synchronet point to the dev version. This message should go out without that empty PATH kludge.

Confirmed! ;-)

Carlos
--- SBBSecho 3.33-Win32
* Origin: cyb synchronet point (2:341/234.5885)
SEEN-BY: 103/705 124/5016 153/757 154/10 30 203/0 221/0 6 240/1120 5832 SEEN-BY: 263/1 280/464 5003 5006 5555 292/854 8125 301/1 310/31 341/66 SEEN-BY: 341/234 396/45 423/120 460/58 633/280 712/848 770/1 5020/400 @PATH: 341/234 280/464

Bye, Wilfred.

--- FMail-lnx64 2.3.2.4-B20240523
* Origin: FMail development HQ (2:280/464)

Hi Carlos.

12 Dec 25 17:46, you wrote to Rob Swindell:

@TZUTC: 0100
@MSGID: 72.fidonet_fidotest@2:341/234.5885 2da17d3c
@REPLY: 15424.fidotest@1:103/705 2da0aec8
@PID: Synchronet 3.21a-Win32 master/d27b45adf Dec 12 2025 MSC 1944
@TID: SBBSecho 3.33-Win32 master/d27b45adf Dec 12 2025 MSC 1944
@BBSID: CYBNOT
@CHRS: UTF-8 4
@FORMAT: flowed
@NOTE: Mozilla Thunderbird
11/12/2025 22:50, Rob Swindell (1:103/705):

  > A bug report (at gitlab.synchro.net) would've been nice to

have. :-)

Sorry, I intended to... O:-)

Next time. :-)

There'll certainly more opportunities (bugs created/found) in the
future. lol

Sure ;-)

I've just upgraded my Synchronet point to the dev version. This
message should go out without that empty PATH kludge.

Yep!

Carlos
--- SBBSecho 3.33-Win32
* Origin: cyb synchronet point (2:341/234.5885)
SEEN-BY: 221/6 280/464 341/66 234
@PATH: 341/234

'Tommi

---
* Origin: nntps://news.fidonet.fi (2:221/360)

12 Dec 2025 17:52, you wrote to me:

I've just upgraded my Synchronet point to the dev version. This
message should go out without that empty PATH kludge.

Confirmed! ;-)

Thanks. Same here in my FMail-based node.

Carlos

--- GoldED+/W32-MSVC 1.1.5-b20180707
* Origin: cyberiada (2:341/234)

12 Dec 2025 18:55, you wrote to me:

I've just upgraded my Synchronet point to the dev version. This
message should go out without that empty PATH kludge.

Yep!

But your tosser removed it anyway, didn't it?

You'd have to check the PKT my node sent to you... (No need to, I've already done)

Carlos

--- GoldED+/W32-MSVC 1.1.5-b20180707
* Origin: cyberiada (2:341/234)

Hi Carlos.

I've just upgraded my Synchronet point to the dev version. This
message should go out without that empty PATH kludge.

Yep!

But your tosser removed it anyway, didn't it?

You'd have to check the PKT my node sent to you... (No need to, I've already done)

I sure did before reporting. :)

'Tommi

---
* Origin: FPoint (2:221/6.66)

Re: Re: test
By: Wilfred van Velzen to Carlos Navarro on Fri Dec 12 2025 05:52 pm

I've just upgraded my Synchronet point to the dev version. This message should go out without that empty PATH kludge.

Confirmed! ;-)

Thank you!
--
digital man (rob)

Synchronet/BBS Terminology Definition #18:
CRC = Cyclic Redunancy Check
Norco, CA WX: 73.6øF, 49.0% humidity, 3 mph WNW wind, 0.00 inches rain/24hrs --- SBBSecho 3.32-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

12 Dec 2025 19:24, you wrote to me:

I sure did before reporting. :)

But of course! :-)

Carlos

--- GoldED+/W32-MSVC 1.1.5-b20180707
* Origin: cyberiada (2:341/234)

test

... Remind me again how lucky I am to work here

--- BinktermPHP v1.8.5
* Origin: Claude's BBS - https://claudes.lovelybits.org (1:153/150)

02 Mar 26 10:41:07 Matthew Asham (1:153/150) wrote:

==== begin of the message ====
@CHRS: UTF-8 4
@TZUTC: -0800
@MSGID: 1:153/150 EC5BF23F
@MAILER: BinktermPHP 1.8.5 Linux
test

... Remind me again how lucky I am to work here

-+- BinktermPHP v1.8.5
+ Origin: Claude's BBS - https://claudes.lovelybits.org (1:153/150)
SEEN+BY: 19/10 134/100 101 153/135 143 148 149 150 151 153 757 7083 154/10 SEEN+BY: 201/0 218/840 221/1 6 360 240/1120 280/464 5003 5555 292/854 301/1 SEEN+BY: 320/119 219 335/364 341/66 234 342/11 423/81 460/58 3634/12 5020/1042 @PATH: 153/150 757 221/6 1
==== end of the message ====

---
* Origin: RBB Test Robot @ FIDOTEST (2:221/360)

On 02 Mar 26 10:41:07 Matthew Asham (1:153/150) wrote:

==== start of message ====
@CHRS: UTF-8 4
@TZUTC: -0800
@MSGID: 1:153/150 EC5BF23F
@MAILER: BinktermPHP 1.8.5 Linux
test

... Remind me again how lucky I am to work here

-+- BinktermPHP v1.8.5
+ Origin: Claude's BBS - https://claudes.lovelybits.org (1:153/150)
SEEN+BY: 19/10 105/81 106/201 128/187 129/14 134/100 153/135 143 148
SEEN+BY: 153/149 150 151 153 757 7083 7715 154/10 110 218/700 840
SEEN+BY: 221/1 6 360 226/30 227/114 229/110 112 134 200 206 300 307
SEEN+BY: 229/317 400 426 428 452 470 664 700 705 266/512 280/464 5555
SEEN+BY: 291/111 292/854 301/1 320/219 322/757 335/364 341/66 234
SEEN+BY: 342/11 200 396/45 460/58 256 1124 5858 633/280 712/848 902/26
SEEN+BY: 3634/12 4600/140 5020/1042 5054/30 5075/35
@PATH: 153/150 757 221/6 460/58 229/426
==== end of message ====

--- mirror.pl
* Origin: Eastern Canada (1:229/0)

Hello Matthew,

02 Mar 26 10:41, you wrote to All:

@CHRS: UTF-8 4
@TZUTC: -0800
@MSGID: 1:153/150 EC5BF23F
@MAILER: BinktermPHP 1.8.5 Linux
test

... Remind me again how lucky I am to work here

--- BinktermPHP v1.8.5
* Origin: Claude's BBS - https://claudes.lovelybits.org (1:153/150) SEEN-BY: 19/10 30/0 134/100 101 153/135 143 148 149 150 151 153 757
7083
SEEN-BY: 154/10 201/0 218/840 221/1 6 360 240/502 1120 1634 8002 8005
8010
SEEN-BY: 240/8050 280/464 5003 5555 292/854 301/1 313/41 320/119 219 335/364
SEEN-BY: 341/66 234 342/11 371/0 52 382/200 423/81 460/58 492/0
530/204
SEEN-BY: 550/278 3634/12 5020/1042
@PATH: 153/150 757 221/6 1 240/1120 371/0

ByEbYe
--
Daniel

telnet://bbs.roonsbbs.hu:1212 <<=-

... Uptime: 11d 11h 39m 29s
--- GoldED/2 1.1.4.7+EMX
* Origin: Roon's BBS - Budapest, HUNGARY (2:371/52)

testing internet rex and pxw config change.

... It wasn't my fault your wife wandered into my house!
--- Wildcat! v10.0.500.1 (Oct 16 2025), Editor Mod v1.7
* Origin: Over The Brink * Grand Island, NY USA *| brinkbbs.org (1:261/20)

03 Mar 26 15:20:20 Robert Wolfe (1:261/20) wrote:

==== begin of the message ====
@TID: PX/Win v7.0 PX28-1176M
@MSGID: 1:261/20 7e04d7a8
@TZUTC: -0500
testing internet rex and pxw config change.

... It wasn't my fault your wife wandered into my house!
-+- Wildcat! v10.0.500.1 (Oct 16 2025), Editor Mod v1.7
+ Origin: Over The Brink * Grand Island, NY USA *| brinkbbs.org (1:261/20) SEEN+BY: 1/19 100 16/0 19/36 37 123/130 134/101 142/104 799 201/0 203/0 221/0 SEEN+BY: 221/1 6 229/426 240/1120 5832 261/20 280/464 5003 5555 292/854 301/1 SEEN+BY: 320/119 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/360)

On 03 Mar 26 15:20:20 Robert Wolfe (1:261/20) wrote:

==== start of message ====
@TID: PX/Win v7.0 PX28-1176M
@MSGID: 1:261/20 7e04d7a8
@TZUTC: -0500
testing internet rex and pxw config change.

... It wasn't my fault your wife wandered into my house!
-+- Wildcat! v10.0.500.1 (Oct 16 2025), Editor Mod v1.7
+ Origin: Over The Brink * Grand Island, NY USA *| brinkbbs.org (1:261/20) SEEN+BY: 1/19 100 16/0 19/36 37 105/81 106/201 123/130 128/187 129/14
SEEN+BY: 142/104 799 153/7715 154/110 203/0 218/700 221/0 226/30 227/114 SEEN+BY: 229/110 112 134 200 206 300 307 317 400 426 428 452 470 664
SEEN+BY: 229/700 705 240/5832 261/20 266/512 291/111 292/854 320/119
SEEN+BY: 320/219 319 2119 322/757 762 325/304 342/19 200 396/45 460/58
SEEN+BY: 633/280 712/848 902/26 5075/35
@PATH: 261/20 320/219 229/426
==== end of message ====

--- mirror.pl
* Origin: Eastern Canada (1:229/0)

testing beta version of px/wins

... If she can't take the heat, get her out of the oven!
--- Wildcat! v10.0.500.1 (Oct 16 2025), Editor Mod v1.7
* Origin: Over The Brink * Grand Island, NY USA *| brinkbbs.org (1:261/20)

05 Mar 26 10:15:58 Robert Wolfe (1:261/20) wrote:

==== begin of the message ====
@TID: PX/Win v7.0 PX28-1176M
@MSGID: 1:261/20 13a4d09d
@TZUTC: -0500
testing beta version of px/wins

... If she can't take the heat, get her out of the oven!
-+- Wildcat! v10.0.500.1 (Oct 16 2025), Editor Mod v1.7
+ Origin: Over The Brink * Grand Island, NY USA *| brinkbbs.org (1:261/20) SEEN+BY: 1/19 100 16/0 19/36 37 123/130 134/101 142/104 799 201/0 203/0 221/0 SEEN+BY: 221/1 6 229/426 240/1120 5832 261/20 280/464 5003 5555 292/854 301/1 SEEN+BY: 320/119 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/360)

On 05 Mar 26 10:15:58 Robert Wolfe (1:261/20) wrote:

==== start of message ====
@TID: PX/Win v7.0 PX28-1176M
@MSGID: 1:261/20 13a4d09d
@TZUTC: -0500
testing beta version of px/wins

... If she can't take the heat, get her out of the oven!
-+- Wildcat! v10.0.500.1 (Oct 16 2025), Editor Mod v1.7
+ Origin: Over The Brink * Grand Island, NY USA *| brinkbbs.org (1:261/20) SEEN+BY: 1/19 100 16/0 19/36 37 105/81 106/201 123/130 128/187 129/14
SEEN+BY: 142/104 799 153/7715 154/110 203/0 218/700 221/0 226/30 227/114 SEEN+BY: 229/110 112 134 200 206 300 307 317 400 426 428 452 470 664
SEEN+BY: 229/700 705 240/5832 261/20 266/512 291/111 292/854 320/119
SEEN+BY: 320/219 319 2119 322/757 762 325/304 342/19 200 396/45 460/58
SEEN+BY: 633/280 712/848 902/26 5075/35
@PATH: 261/20 320/219 229/426
==== end of message ====

--- mirror.pl
* Origin: Eastern Canada (1:229/0)

On 05 Mar 2026, Robert Wolfe said the following...

testing beta version of px/wins

There is a newer version of PX out there??

IB Joe, Pronouns (FJB/LGB)
AKA Joe Schweier
SysOp of 4A 6F 65 73 42 42 53
-=JoesBBS.com=-

... I wish life had a scroll-back buffer.

--- Mystic BBS v1.12 A49 2023/04/30 (Windows/64)
* Origin: JoesBBS.Com, Telnet:23 SSH:22 HTTP:80 (1:342/201)

testing

... The man who dies with the most toys is dead..
--- Wildcat! v10.0.500.1 (Oct 16 2025), Editor Mod v1.7
* Origin: Over The Brink * Grand Island, NY USA *| brinkbbs.org (1:261/20)

06 Mar 26 14:01:46 Robert Wolfe (1:261/20) wrote:

==== begin of the message ====
@TID: PX/Win v7.0 PX28-1176M
@MSGID: 1:261/20 41cc8b4d
@TZUTC: -0500
testing

... The man who dies with the most toys is dead..
-+- Wildcat! v10.0.500.1 (Oct 16 2025), Editor Mod v1.7
+ Origin: Over The Brink * Grand Island, NY USA *| brinkbbs.org (1:261/20) SEEN+BY: 1/19 100 16/0 19/36 37 123/130 134/101 142/104 799 201/0 203/0 221/0 SEEN+BY: 221/1 6 229/426 240/1120 5832 261/20 280/464 5003 5555 292/854 301/1 SEEN+BY: 320/119 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/360)

On 06 Mar 26 14:01:46 Robert Wolfe (1:261/20) wrote:

==== start of message ====
@TID: PX/Win v7.0 PX28-1176M
@MSGID: 1:261/20 41cc8b4d
@TZUTC: -0500
testing

... The man who dies with the most toys is dead..
-+- Wildcat! v10.0.500.1 (Oct 16 2025), Editor Mod v1.7
+ Origin: Over The Brink * Grand Island, NY USA *| brinkbbs.org (1:261/20) SEEN+BY: 1/19 100 16/0 19/36 37 105/81 106/201 123/130 128/187 129/14
SEEN+BY: 142/104 799 153/7715 154/110 203/0 218/700 221/0 226/30 227/114 SEEN+BY: 229/110 112 134 200 206 300 307 317 400 426 428 452 470 664
SEEN+BY: 229/700 705 240/5832 261/20 266/512 291/111 292/854 320/119
SEEN+BY: 320/219 319 2119 322/757 762 325/304 342/19 200 396/45 460/58
SEEN+BY: 633/280 712/848 902/26 5075/35
@PATH: 261/20 320/219 229/426
==== end of message ====

--- mirror.pl
* Origin: Eastern Canada (1:229/0)

Hello Robert,

03 Mar 26 15:20, you wrote to All:

@TID: PX/Win v7.0 PX28-1176M
@MSGID: 1:261/20 7e04d7a8
@TZUTC: -0500
testing internet rex and pxw config change.

... It wasn't my fault your wife wandered into my house!
--- Wildcat! v10.0.500.1 (Oct 16 2025), Editor Mod v1.7
* Origin: Over The Brink * Grand Island, NY USA *| brinkbbs.org (1:261/20)
SEEN-BY: 1/19 100 16/0 19/36 37 30/0 123/130 134/101 142/104 799 201/0 203/0
SEEN-BY: 221/0 1 6 229/426 240/502 1120 1634 5832 8002 8005 8010 8050 261/20
SEEN-BY: 280/464 5003 5555 292/854 301/1 313/41 320/119 219 319 2119 322/762
SEEN-BY: 325/304 335/364 342/19 371/0 52 382/200 423/81 492/0 530/204 550/278
@PATH: 261/20 320/219 221/1 240/1120 371/0

ByEbYe
--
Daniel

telnet://bbs.roonsbbs.hu:1212 <<=-

... Uptime: 16d 8h 33m 56s
--- GoldED/2 1.1.4.7+EMX
* Origin: Roon's BBS - Budapest, HUNGARY (2:371/52)

Hello Robert,

05 Mar 26 10:15, you wrote to All:

@TID: PX/Win v7.0 PX28-1176M
@MSGID: 1:261/20 13a4d09d
@TZUTC: -0500
testing beta version of px/wins

... If she can't take the heat, get her out of the oven!
--- Wildcat! v10.0.500.1 (Oct 16 2025), Editor Mod v1.7
* Origin: Over The Brink * Grand Island, NY USA *| brinkbbs.org (1:261/20)
SEEN-BY: 1/19 100 16/0 19/36 37 30/0 123/130 134/101 142/104 799 201/0 203/0
SEEN-BY: 221/0 1 6 229/426 240/502 1120 1634 5832 8002 8005 8010 8050 261/20
SEEN-BY: 280/464 5003 5555 292/854 301/1 313/41 320/119 219 319 2119 322/762
SEEN-BY: 325/304 335/364 342/19 371/0 52 382/200 423/81 492/0 530/204 550/278
@PATH: 261/20 320/219 221/1 240/1120 371/0

ByEbYe
--
Daniel

telnet://bbs.roonsbbs.hu:1212 <<=-

... Uptime: 16d 8h 33m 56s
--- GoldED/2 1.1.4.7+EMX
* Origin: Roon's BBS - Budapest, HUNGARY (2:371/52)

Hello Robert,

06 Mar 26 14:01, you wrote to All:

@TID: PX/Win v7.0 PX28-1176M
@MSGID: 1:261/20 41cc8b4d
@TZUTC: -0500
testing

... The man who dies with the most toys is dead..
--- Wildcat! v10.0.500.1 (Oct 16 2025), Editor Mod v1.7
* Origin: Over The Brink * Grand Island, NY USA *| brinkbbs.org (1:261/20)
SEEN-BY: 1/19 100 16/0 19/36 37 30/0 123/130 134/101 142/104 799 201/0 203/0
SEEN-BY: 221/0 1 6 229/426 240/502 1120 1634 5832 8002 8005 8010 8050 261/20
SEEN-BY: 280/464 5003 5555 292/854 301/1 313/41 320/119 219 319 2119 322/762
SEEN-BY: 325/304 335/364 342/19 371/0 52 382/200 423/81 492/0 530/204 550/278
@PATH: 261/20 320/219 221/1 240/1120 371/0

ByEbYe
--
Daniel

telnet://bbs.roonsbbs.hu:1212 <<=-

... Uptime: 16d 8h 33m 56s
--- GoldED/2 1.1.4.7+EMX
* Origin: Roon's BBS - Budapest, HUNGARY (2:371/52)

testing


--- MagickaBBS v0.15alpha (Linux/x86_64)
* Origin: Capitol City Hub (1:2320/105)

Matthew,

test

It made it to Arkansas.

Daryl

... An error? Impossible! My telnet connection is error correcting.
=== MultiMail/Win v0.52
--- SBBSecho 3.32-Win32
* Origin: The Thunderbolt BBS - Little Rock, Arkansas (1:19/33)

testing posting via thunderbird and nntp
--- Platinum Xpress/Win/WINServer v10.0
* Origin: Over The Brink * Grand Island, NY USA *| brinkbbs.org (1:261/20)

13 Mar 26 13:21:32 Robert Wolfe (1:261/20) wrote:

==== begin of the message ====
@TID: PX/Win v10.0 PX28-1176M
@MSGID: 1:261/20 859f55c2
@TZUTC: -0400
testing posting via thunderbird and nntp
-+- Platinum Xpress/Win/WINServer v10.0
+ Origin: Over The Brink * Grand Island, NY USA *| brinkbbs.org (1:261/20) SEEN+BY: 1/19 100 16/0 19/36 37 123/130 134/101 142/104 799 201/0 203/0 221/0 SEEN+BY: 221/1 6 229/426 240/1120 5832 261/20 280/464 5003 5555 292/854 301/1 SEEN+BY: 320/119 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/360)

On 13 Mar 26 13:21:32 Robert Wolfe (1:261/20) wrote:

==== start of message ====
@TID: PX/Win v10.0 PX28-1176M
@MSGID: 1:261/20 859f55c2
@TZUTC: -0400
testing posting via thunderbird and nntp
-+- Platinum Xpress/Win/WINServer v10.0
+ Origin: Over The Brink * Grand Island, NY USA *| brinkbbs.org (1:261/20) SEEN+BY: 1/19 100 16/0 19/36 37 105/81 106/201 123/130 128/187 129/14
SEEN+BY: 142/104 799 153/7715 154/110 203/0 218/700 221/0 226/30 227/114 SEEN+BY: 229/110 112 134 200 206 300 307 317 400 426 428 452 470 664
SEEN+BY: 229/700 705 240/5832 261/20 266/512 291/111 292/854 320/119
SEEN+BY: 320/219 319 2119 322/757 762 325/304 342/19 200 396/45 460/58
SEEN+BY: 633/280 712/848 902/26 5075/35
@PATH: 261/20 320/219 229/426
==== end of message ====

--- mirror.pl
* Origin: Eastern Canada (1:229/0)

Hello Robert,

13 Mar 26 13:21, you wrote to All:

@TID: PX/Win v10.0 PX28-1176M
@MSGID: 1:261/20 859f55c2
@TZUTC: -0400
testing posting via thunderbird and nntp
--- Platinum Xpress/Win/WINServer v10.0
* Origin: Over The Brink * Grand Island, NY USA *| brinkbbs.org (1:261/20)
SEEN-BY: 1/19 100 16/0 19/36 37 30/0 123/130 134/101 142/104 799 201/0 203/0
SEEN-BY: 221/0 1 6 229/426 240/502 1120 1634 5832 8002 8005 8010 8050 261/20
SEEN-BY: 280/464 5003 5555 292/854 301/1 313/41 320/119 219 319 2119 322/762
SEEN-BY: 325/304 335/364 342/19 371/0 52 382/200 423/81 492/0 530/204 550/278
@PATH: 261/20 320/219 221/1 240/1120 371/0

ByEbYe
--
Daniel

telnet://bbs.roonsbbs.hu:1212 <<=-

... Uptime: 22d 9h 1m 49s
--- GoldED/2 1.1.4.7+EMX
* Origin: Roon's BBS - Budapest, HUNGARY (2:371/52)

On 13 Mar 2026, Robert Wolfe said the following...

testing posting via thunderbird and nntp

did it work??

IB Joe, Pronouns (FJB/LGB)
AKA Joe Schweier
SysOp of 4A 6F 65 73 42 42 53
-=JoesBBS.com=-

... They say there's always one weirdo on the bus, but I couldn't find them!

--- Mystic BBS v1.12 A49 2023/04/30 (Windows/64)
* Origin: JoesBBS.Com, Telnet:23 SSH:22 HTTP:80 (1:342/201)

Hey Robert!

On Fri, 13 Mar 2026 13:21:32 -0400, you wrote:

testing posting via thunderbird and nntp
--- Platinum Xpress/Win/WINServer v10.0
* Origin: Over The Brink * Grand Island, NY USA *| brinkbbs.org
(1:261/20)

If this is a test regarding all of the headers that used to be posted in your NNTP messages, then the test passed!

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)

If this is a test regarding all of the headers that used to be posted in you
NNTP messages, then the test passed!

unfortunately, no it wasn't.

... I gave up on my wife, and married my computer.
--- Wildcat! v10.0.500.1 (Oct 16 2025), Editor Mod v1.7
* Origin: Over The Brink * Grand Island, NY USA *| brinkbbs.org (1:261/20)

Hey Robert!

On Sun, 15 Mar 2026 07:36:32 -0400, you wrote:

unfortunately, no it wasn't.

Then, I suppose I didn't understand what you were trying to do.

You said something in the lines of "testing Thunderbird and NNTP". Your message didn't include all of those headers. Maybe that only happens when you reply to another message? I don't know.

Regards,
Nick

... Sarcasm: because beating people up is illegal.
--- GoldED+/LNX 1.1.5-b20260304
* Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (1:154/10)

On Mar 16, 2026 08:28am, Nick Boel wrote to
Robert Wolfe:

Hey Robert!

On Sun, 15 Mar 2026 07:36:32 -0400, you

wrote:

unfortunately, no it wasn't.

Then, I suppose I didn't understand what

you were trying to do.

You said something in the lines of

"testing Thunderbird and NNTP". Your

message didn't include all of those

headers. Maybe that only happens

when you reply to another message? I

don't know.

Regards,
Nick

... Sarcasm: because beating people up

is illegal.

--- GoldED+/LNX 1.1.5-b20260304
* Origin: _thePharcyde

telnet://bbs.pharcyde.org (Wisconsin)
(1:154/10)

Thank you, because I kept getting messages
from people saying they saw nntp headers in
the body of messages I post via newsreader.
Apparently some tossers filter that out in
import better than others
--- Platinum Xpress/Win/WINServer v10.0
* Origin: Over The Brink * Grand Island, NY USA *| brinkbbs.org (1:261/20)

Thank you, because I kept getting messages
from people saying they saw nntp headers in
the body of messages I post via newsreader.
Apparently some tossers filter that out in
import better than others

FWIW, apparently both sbbsecho (synchronet) and hpt are filtering
them out.

Mike

--- MagickaBBS v0.15alpha (Linux/x86_64)
* Origin: Capitol City Hub (1:2320/105)

Hey Robert!

On Mon, 16 Mar 2026 09:39:24 -0400, you wrote:

Thank you, because I kept getting messages
from people saying they saw nntp headers in
the body of messages I post via newsreader.

I was one of them that saw those headers, and wrote to you about it.

Apparently some tossers filter that out in
import better than others

Are you sure you didn't adjust Thunderbird to NOT write headers to the message body?

Were you using the "Reply" button, rather than "Follow-Up"?

I doubt it was a "some tossers" issue, as your last couple of tests via Thunderbird haven't had the headers in the bodies.

Regards,
Nick

... Sarcasm: because beating people up is illegal.
--- GoldED+/LNX 1.1.5-b20260304
* Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (1:154/10)

Hey Mike!

On Mon, 16 Mar 2026 09:04:56 -0500, you wrote:

FWIW, apparently both sbbsecho (synchronet) and hpt are filtering
them out.

Not sure about that, or I probably wouldn't have seen them in the first place (I use both of what you mention above here, and hpt hasn't been updated since 2024; nor did I change any settings).

Granted, maybe it only includes those headers in the message body when he replies (followup) to a message via NNTP, rather than just posting a new one.

Regards,
Nick

... Sarcasm: because beating people up is illegal.
--- GoldED+/LNX 1.1.5-b20260304
* Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (1:154/10)

On 3/16/2026 10:57 AM, Nick Boel wrote:

Hey Mike!

On Mon, 16 Mar 2026 09:04:56 -0500, you wrote:

> FWIW, apparently both sbbsecho (synchronet) and hpt are filtering
> them out.

Not sure about that, or I probably wouldn't have seen them in the first place (I use both of what you mention above here, and hpt hasn't been updated since 2024; nor did I change any settings).

Granted, maybe it only includes those headers in the message body when he replies (followup) to a message via NNTP, rather than just posting a new one.

Regards,
Nick

.. Sarcasm: because beating people up is illegal.
--- GoldED+/LNX 1.1.5-b20260304
* Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (1:154/10)

Let's try this one. I have ent santronicsa message regarding this.
They are pretty receptive to feedback After all, they are adding binkp
to their front end mailer product after all these years.
--- Platinum Xpress/Win/WINServer v10.0
* Origin: Over The Brink * Grand Island, NY USA *| brinkbbs.org (1:261/20)

On 3/16/2026 10:52 AM, Nick Boel wrote:

Hey Robert!

On Mon, 16 Mar 2026 09:39:24 -0400, you wrote:

> Thank you, because I kept getting messages
> from people saying they saw nntp headers in
> the body of messages I post via newsreader.

I was one of them that saw those headers, and wrote to you about it.

> Apparently some tossers filter that out in
> import better than others

Are you sure you didn't adjust Thunderbird to NOT write headers to the message
body?

Were you using the "Reply" button, rather than "Follow-Up"?

I doubt it was a "some tossers" issue, as your last couple of tests via Thunderbird haven't had the headers in the bodies.

tbh, i don't know how to do that. as long as the mailer part works,
thats all im concerned about.
--- Platinum Xpress/Win/WINServer v10.0
* Origin: Over The Brink * Grand Island, NY USA *| brinkbbs.org (1:261/20)

16 Mar 26 12:13:42 Robert Wolfe (1:261/20) wrote:

==== begin of the message ====
@TID: PX/Win v10.0 PX28-1176M
@MSGID: 1:261/20 6f2a39ff
@TZUTC: -0400
On 3/16/2026 10:52 AM, Nick Boel wrote:

Hey Robert!

On Mon, 16 Mar 2026 09:39:24 -0400, you wrote:

> Thank you, because I kept getting messages
> from people saying they saw nntp headers in
> the body of messages I post via newsreader.

I was one of them that saw those headers, and wrote to you about it.

> Apparently some tossers filter that out in
> import better than others

Are you sure you didn't adjust Thunderbird to NOT write headers to the message
body?

Were you using the "Reply" button, rather than "Follow-Up"?

I doubt it was a "some tossers" issue, as your last couple of tests via Thunderbird haven't had the headers in the bodies.

tbh, i don't know how to do that. as long as the mailer part works,
thats all im concerned about.
-+- Platinum Xpress/Win/WINServer v10.0
+ Origin: Over The Brink * Grand Island, NY USA *| brinkbbs.org (1:261/20) SEEN+BY: 1/19 100 16/0 19/36 37 123/130 134/101 142/104 799 201/0 203/0 221/0 SEEN+BY: 221/1 6 229/426 240/1120 5832 261/20 280/464 5003 5555 292/854 301/1 SEEN+BY: 320/119 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/360)

Hey Robert!

On Mon, 16 Mar 2026 12:11:16 -0400, you wrote:

On 3/16/2026 10:57 AM, Nick Boel wrote:

Hey Mike!

On Mon, 16 Mar 2026 09:04:56 -0500, you wrote:

> FWIW, apparently both sbbsecho (synchronet) and hpt are filtering
> them out.

Not sure about that, or I probably wouldn't have seen them in the
first place (I use both of what you mention above here, and hpt hasn't
been updated since
2024; nor did I change any settings).

Granted, maybe it only includes those headers in the message body when
he replies (followup) to a message via NNTP, rather than just posting
a new one.

Regards,
Nick

.. Sarcasm: because beating people up is illegal.
--- GoldED+/LNX 1.1.5-b20260304
* Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin)
(1:154/10)

Let's try this one. I have ent santronicsa message regarding this.
They are pretty receptive to feedback After all, they are adding binkp
to their front end mailer product after all these years.
--- Platinum Xpress/Win/WINServer v10.0
* Origin: Over The Brink * Grand Island, NY USA *| brinkbbs.org
(1:261/20)

This is how your message was received here (without one quote level, of course). Looks much better as far as quoting is concerned.

Was this done with Thunderbird? Or your BBS message editor?

Regards,
Nick

... Sarcasm: because beating people up is illegal.
--- GoldED+/LNX 1.1.5-b20260304
* Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (1:154/10)

This is how your message was received here (without one quote level, of course). Looks much better as far as quoting is concerned.

Was this done with Thunderbird? Or your BBS message editor?

this reply was done with my bbs' editor. the previous one was with thunderbird.

... Any sufficiently advanced technology looks like magic.
--- Wildcat! v10.0.500.1 (Oct 16 2025), Editor Mod v1.7
* Origin: Over The Brink * Grand Island, NY USA *| brinkbbs.org (1:261/20)

Granted, maybe it only includes those headers in the message body when he replies (followup) to a message via NNTP, rather than just posting a new one.

That could be!

Mike


--- GTMail 1.26
* Origin: moe's * 1+5028758938 3-9600 * moetiki.ddns.net:27 (1:2320/195.0)

This is how your message was received here (without one quote level, of course). Looks much better as far as quoting is concerned.

Was this done with Thunderbird? Or your BBS message editor?

This message was wriiten while logged into my bbs. Wildcat! always
uses "->" when quoting.

... Life is short, eat dessert first.
--- Wildcat! v10.0.500.1 (Oct 16 2025), Editor Mod v1.7
* Origin: Over The Brink * Grand Island, NY USA *| brinkbbs.org (1:261/20)

Re: test
By: Robert Wolfe to Nick Boel on Tue Mar 17 2026 10:29 am

This is how your message was
received here (without one quote
level, of course). Looks much
better as far as quoting is
concerned.

Was this done with Thunderbird? O
your BBS message editor?

This message was wriiten while logge
into my bbs. Wildcat! always
uses "->" when quoting.

... Life is short, eat dessert first

could be worse. I'm on a C64 Ultimate
and when my message word wraps, it
just slaps my words together, and
editing messages seems buggy for me.

If I try and move the cursor while
editing, lines appear and dissapear
seemingly at random, making it
impossible to actually edit anything.


--Just Post, World Is A Fuck!--

This Quality Shit-Post Brought
To You Via Commodore 64 Ultimate
--- SBBSecho 3.37-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

On Mar 17, 2026 08:20am, Mike Powell wrote to
Nick Boel:

Granted, maybe it only includes those

headers in the message body when he

replies (followup) to a message via NNTP,

rather than just posting a new

one.

That could be!

Mike

The good news is that I brought this to
Santronics' attention and they are going to
put the issue in a parallel bug fix for
px/wins and the wcqwk.exe qwk echomail
processor.
--- Platinum Xpress/Win/WINServer v10.0
* Origin: Over The Brink * Grand Island, NY USA *| brinkbbs.org (1:261/20)

Hi Robert,

On 2026-03-17 15:27:42, you wrote to Mike Powell:

Granted, maybe it only includes those

headers in the message body when he

replies (followup) to a message via NNTP,

rather than just posting a new

one.

That could be!

Mike

The good news is that I brought this to
Santronics' attention and they are going to
put the issue in a parallel bug fix for
px/wins and the wcqwk.exe qwk echomail
processor.

Can they also fix the "-> " quoting style? ;-)


Bye, Wilfred.

--- FMail-lnx64 2.3.2.6-B20251227
* Origin: FMail development HQ (2:280/464)

Can they also fix the "-> " quoting style? ;-)

why. its been that way since wildcat 2.xx

... You will be the victim of a bizarre joke.
--- Wildcat! v10.0.500.1 (Oct 16 2025), Editor Mod v1.7
* Origin: Over The Brink * Grand Island, NY USA *| brinkbbs.org (1:261/20)

Granted, maybe it only includes those headers in the message body when he replies (followup) to a message via NNTP, rather than just posting a new o

That could be!

I brought this up with hector and he is going to see if he can work a
fix for this into the .2 alpha cycle :)

... Some days you're the windshield, some days the bug.
--- Wildcat! v10.0.500.1 (Oct 16 2025), Editor Mod v1.7
* Origin: Over The Brink * Grand Island, NY USA *| brinkbbs.org (1:261/20)

The good news is that I brought this to
Santronics' attention and they are going to
put the issue in a parallel bug fix for
px/wins and the wcqwk.exe qwk echomail
processor.

Can they also fix the "-> " quoting style? ;-)

I think I could fix that directly, if I wanted to. I just need to ask if
its in the editor WCC code anywhere.


... I'm not afraid of heights; I'm afraid of widths.
--- Wildcat! v10.0.500.1 (Oct 16 2025), Editor Mod v1.7
* Origin: Over The Brink * Grand Island, NY USA *| brinkbbs.org (1:261/20)

Hi Robert,

On 2026-03-17 18:51:28, you wrote to me:

Can they also fix the "-> " quoting style? ;-)

why. its been that way since wildcat 2.xx

Because it's always been done wrong, doesn't make it right! ;-)

It doesn't follow the accepted and documented standard: http://ftsc.org/docs/fsc-0032.001

So other editors don't recognise this as a quoted line, so subsequent quotes become a mess as shown above...


Bye, Wilfred.

--- FMail-lnx64 2.3.2.6-B20251227
* Origin: FMail development HQ (2:280/464)

Hello Wilfred,

18 Mar 26 08:50, you wrote to Robert Wolfe:

Can they also fix the "-> " quoting style? ;-)

why. its been that way since wildcat 2.xx

Because it's always been done wrong, doesn't make it right! ;-)

It doesn't follow the accepted and documented standard: http://ftsc.org/docs/fsc-0032.001

So other editors don't recognise this as a quoted line, so subsequent quotes become a mess as shown above...

yep, these quotations look shitty in golded as well as in most bbs sw..

ByEbYe
--
Daniel

telnet://bbs.roonsbbs.hu:1212 <<=-

... Uptime: 26d 22h 15m 50s
--- GoldED/2 1.1.4.7+EMX
* Origin: Roon's BBS - Budapest, HUNGARY (2:371/52)

On 17 Mar 26 20:25:16, Robert Wolfe said the following to Wilfred Van Velzen:

Can they also fix the "-> " quoting style? ;-)

I think I could fix that directly, if I wanted to. I just need to ask if its in the editor WCC code anywhere.

You don't have to do anything except show contempt for the Dutch twat.

Nick

--- Renegade vY2Ka2
* Origin: Joey, do you like movies about gladiators? (1:229/426)

I brought this up with hector and he is going to see if he can work a
fix for this into the .2 alpha cycle :)

Excellent news. Hope they are able to get it figured out and fixed for
you.

Mike


--- GTMail 1.26
* Origin: moe's * 1+5028758938 3-9600 * moetiki.ddns.net:27 (1:2320/195.0)

Can they also fix the "-> " quoting style? ;-)

why. its been that way since wildcat 2.xx

So other editors don't recognise this as a quoted line, so
subsequent quotes become a mess as shown above...

It is not coming across as a mess here?

Mike


--- MagickaBBS v0.15alpha (Linux/x86_64)
* Origin: Capitol City Hub (1:2320/105)

Because it's always been done wrong, doesn't make it right! ;-)

It doesn't follow the accepted and documented standard: http://ftsc.org/docs/fsc-0032.001

So other editors don't recognise this as a quoted line, so subsequent quotes
become a mess as shown above...

other standards have been updated, why can't this one. And as far as I
can tell you seem to be the only one PMSing about it. But to keep you
happy, I've reported this to Santronics. And it's off that PCBoard used
a similar quoting style and life went on.

... The above opinion is worth 2 cents.
--- Wildcat! v10.0.500.1 (Oct 16 2025), Editor Mod v1.7
* Origin: Over The Brink * Grand Island, NY USA *| brinkbbs.org (1:261/20)

On Mar 18, 2026 08:26am, Mike Powell wrote to
Robert Wolfe:

I brought this up with hector and he is

going to see if he can work a

fix for this into the .2 alpha cycle :)

Excellent news. Hope they are able to

get it figured out and fixed for

you.

Mike

--- GTMail 1.26
* Origin: moe's * 1+5028758938 3-9600 *

moetiki.ddns.net:27

(1:2320/195.0)

if they fix it, they fix it. Right now,
something that minor is the least of their
worries. Right now they are more focused on
getting their front end mailer updated with
binkp as their paying customers
(including me) have been needing for years --
proper binkp support in Platinum Xpress. you
know the saying "Money talks."
--- Platinum Xpress/Win/WINServer v10.0
* Origin: Over The Brink * Grand Island, NY USA *| brinkbbs.org (1:261/20)

Hi Mike,

On 2026-03-18 09:19:52, you wrote to me:

Can they also fix the "-> " quoting style? ;-)

why. its been that way since wildcat 2.xx

So other editors don't recognise this as a quoted line, so
subsequent quotes become a mess as shown above...

It is not coming across as a mess here?

It would become a real mess if the quoted line was longer and would flow over to the next line.

For instance:

abcde fghij klmnop qrstuv wxyz abcde fghij klmnop qrstuv wxyz abcde fghij klmnop qrstuv wxyz

Would become:

abcde fghij klmnop qrstuv wxyz abcde fghij klmnop qrstuv wxyz abcde

fghij klmnop qrstuv wxyz

And it would become more messy if it was quoted again:

abcde fghij klmnop qrstuv wxyz abcde fghij klmnop qrstuv wxyz abcde

fghij klmnop qrstuv wxyz

And again:

abcde fghij klmnop qrstuv wxyz abcde fghij klmnop qrstuv

wxyz abcde -> RW> fghij klmnop qrstuv wxyz

Etc... It's no longer clear who said what.



Bye, Wilfred.

--- FMail-lnx64 2.3.2.6-B20251227
* Origin: FMail development HQ (2:280/464)

Hi Robert,

On 2026-03-18 08:26:18, you wrote to me:

Because it's always been done wrong, doesn't make it right! ;-)

It doesn't follow the accepted and documented standard: http://ftsc.org/docs/fsc-0032.001

So other editors don't recognise this as a quoted line, so subsequent

quotes -> become a mess as shown above...

other standards have been updated, why can't this one.

It probably can, if you have good arguments, for the FTSC.

But to keep you happy, I've reported this to Santronics.

Thanks.


Bye, Wilfred.

--- FMail-lnx64 2.3.2.6-B20251227
* Origin: FMail development HQ (2:280/464)

On March 18 2026, Wilfred van Velzen wrote:

abcde fghij klmnop qrstuv wxyz abcde fghij klmnop qrstuv

wxyz abcde -> RW> fghij klmnop qrstuv wxyz

Etc... It's no longer clear who said what.

Hmmmm, yeah, that is not so nice. :(

Mike

--- BinktermPHP v1.8.7
* Origin: Claude's BBS - https://claudes.lovelybits.org (1:153/150)

Re: Re: test
By: Wilfred van Velzen to Robert Wolfe on Wed Mar 18 2026 08:50 am

Can they also fix the "-> " quoting style? ;-)

It doesn't follow the accepted and documented standard: http://ftsc.org/docs/fsc-0032.001

FSCs are not standards. <shrug>
--
digital man (rob)

Steven Wright quote #22:
What happens if you get scared half to death twice?
Norco, CA WX: 92.3øF, 24.0% humidity, 9 mph W wind, 0.00 inches rain/24hrs
--- SBBSecho 3.37-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Hello Robert!

18 Mar 26 08:26, you wrote to Wilfred Van Velzen:

So other editors don't recognise this as a quoted line, so

subsequent quotes -> become a mess as shown above...

other standards have been updated, why can't this one. And as far as
I can tell you seem to be the only one PMSing about it. But to keep
you happy, I've reported this to Santronics. And it's off that
PCBoard used a similar quoting style and life went on.

Some of your messages like this one come out looking fine, and go past what looks like a 40 character limit.
I'm going to quote your next message, and it will look like it was cut at that limit.




Stephen


--- GoldED+/LNX 1.1.5-b20250409
* Origin: Dragon's Lair ---:- dragon.vk3heg.net -:--- Prt: 6800 (3:633/280)

Hello Robert!

18 Mar 26 10:31, you wrote to Mike Powell:

--- GTMail 1.26
* Origin: moe's * 1+5028758938 3-9600 *

moetiki.ddns.net:27

(1:2320/195.0)

if they fix it, they fix it. Right now,
something that minor is the least of their
worries. Right now they are more focused on
getting their front end mailer updated with
binkp as their paying customers
(including me) have been needing for years --
proper binkp support in Platinum Xpress. you
know the saying "Money talks."

This is your next message. Notice how it's got no line flow and looks like it's stuck at 40 characters or did you press enter at
that mark. Either way it looks strange.



Stephen


--- GoldED+/LNX 1.1.5-b20250409
* Origin: Dragon's Lair ---:- dragon.vk3heg.net -:--- Prt: 6800 (3:633/280)