--- GoldED+/BSD 1.1.5-b20170303-b20170303 + HPT 1.9.0 + Binkd 1.1a-115
* Origin: FIDONODO DE JAS | ¯\_(O,O)_/¯ (21:3/100.2)
s2r
--- GoldED+/BSD 1.1.5-b20170303-b20170303 + HPT 1.9.0 + Binkd 1.1a-115
* Origin: A FSX point in Buenos Aires (21:3/100.2)
From Retroswim@21:2/121 to All on Thu Sep 25 04:32:40 2025
I sent a message to the BBS support echo yesterday ~18:30 (UTC+10) that hasn't propagated out. I can see that it was accepted by the hub in my binkd logs though.
There is also one message visible in that echo on Agency that hasn't been received by either me or 2
So, yeah, testing 1 2 3 :D
--- Ezycom V2.15g1 01FD0295
* Origin: >> Pool's Open - The RetroSwim BBS (21:2/121)
From Al@21:4/106 to Retroswim on Thu Sep 25 03:30:26 2025
I sent a message to the BBS support echo yesterday ~18:30 (UTC+10) that hasn't propagated out. I can see that it was accepted by the hub in my binkd logs though.
There is also one message visible in that echo on Agency that hasn't been received by either me or 2
So, yeah, testing 1 2 3 :D
I'm reading you OK here, I hope you get my reply.
--- BBBS/Li6 v4.10 Toy-7
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)
From Zip@21:1/202 to Retroswim on Thu Sep 25 23:35:03 2025
Hello Retroswim!
On 24 Sep 2025, Retroswim said the following...
I sent a message to the BBS support echo yesterday ~18:30 (UTC+10) that hasn't propagated out. I can see that it was accepted by the hub in my binkd logs though.
There is also one message visible in that echo on Agency that hasn't been received by either me or 2
So, yeah, testing 1 2 3 :D
--- Ezycom V2.15g1 01FD0295
* Origin: >> Pool's Open - The RetroSwim BBS (21:2/121)
Got you here, although I'm a bit behind on reading through the echos... =)
Best regards
Zip
--- Mystic BBS v1.12 A49 2024/05/29 (Linux/64)
* Origin: Star Collision BBS, Uppsala, Sweden (21:1/202)
From hdt@21:3/137 to All on Wed Oct 15 21:53:08 2025
From deon@21:2/116 to Vorlon on Wed Oct 22 17:59:21 2025
Re: Test
By: Vorlon to deon on Wed Oct 22 2025 12:00 pm
Howdy,
Fail: No Origin or Tear line.
This is one of this mystic packet fails.
This one is operator error.
Golded: PID: GED+W64 1.1.5-b20250409
So it might be both then.
I seen these kinds of messages all the time - and my theory of an external mail tool looks like it is a part of the problem.
The question is, is the external tool not set up properly and mystic is blindly sending out the mail, or is the external tool submitting something back that is tripping up mystic.
...δεσ∩
--- SBBSecho 3.29-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)
From Zip@21:1/202 to Sabre on Thu Oct 23 00:14:20 2025
Hello Sabre!
On 21 Oct 2025, Sabre said the following...
Hello everybody!
Quick test please.
Thanks,
Sabre
Got you here (but no tearline or origin line -- perhaps the message board type wasn't set to "Networked" or similar?).
Best regards
Zip
--- Mystic BBS v1.12 A49 2024/05/29 (Linux/64)
* Origin: Star Collision BBS, Uppsala, Sweden (21:1/202)
From Vorlon@21:1/195 to deon on Thu Oct 23 15:02:18 2025
Hello deon!
22 Oct 25 12:59, you wrote to me:
Fail: No Origin or Tear line.
This is one of this mystic packet fails.
This one is operator error.
Golded: PID: GED+W64 1.1.5-b20250409
I seen these kinds of messages all the time - and my theory of an
external mail tool looks like it is a part of the problem.
The question is, is the external tool not set up properly and mystic
is blindly sending out the mail, or is the external tool submitting something back that is tripping up mystic.
I have seen this same problem with another bbs software package, and golded. The issue was a misconfigured golded. (From memory)
From Accession@21:1/200 to deon on Wed Oct 22 23:02:16 2025
Hey deon!
On Wed, 22 Oct 2025 11:51:04 +1100, you wrote:
This is one of this mystic packet fails.
I dont know what the trigger is, version wise, or whether it is cause
going through a hub.
I think I thought they were caused by an external editor being used..?
They are easy to spot tho, no origin lines, and the seenby lines are
shown.
Most definitely. It's when you use Golded to access your Mystic or Synchronet (or maybe any others, too) message bases without actually defining the use of a tearline and origin line in Golded's config.
There is two "example" config files for Golded, 'simple.cfg' and 'advance.cfg'. It is most definitely defined in the 'advance.cfg' (I just looked), but it is not defined in 'simple.cfg'. If you see the guy around, tell him to put this in his golded.conf/cfg:
... Sarcasm: because beating people up is illegal.
--- GoldED+/LNX 1.1.5-b20250409
* Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (21:1/200)
From Accession@21:1/200 to deon on Wed Oct 22 23:08:36 2025
Hey deon!
On Wed, 22 Oct 2025 12:59:20 +1100, you wrote:
The question is, is the external tool not set up properly and mystic is blindly sending out the mail, or is the external tool submitting
something back that is tripping up mystic.
The former. If Golded doesn't add these, Mystic definitely should upon export, but I don't believe it does.
It's definitely not sending something back tripping up Mystic. James actually updated his JAM format to work with Golded, but maybe missed this because most people enable the tearline and origin line in Golded. *shrug*
Regards,
Nick
... Sarcasm: because beating people up is illegal.
--- GoldED+/LNX 1.1.5-b20250409
* Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (21:1/200)
From deon@21:2/116 to Accession on Thu Oct 23 16:30:53 2025
Re: Test
By: Accession to deon on Wed Oct 22 2025 06:08 pm
Howdy,
The former. If Golded doesn't add these, Mystic definitely should upon export, but I don't believe it does.
It's definitely not sending something back tripping up Mystic. James actually updated his JAM format to work with Golded, but maybe missed this because most people enable the tearline and origin line in Golded. *shrug*
OK, if that is the cause, then great.
ie: PID=Golded, no origin line.
(I think tearline is optional anyway, cant remember, need to check.)
I dont think its an issue with Synchronet, since SBBSecho adds that stuff anyway I think (not noticed anyway with anything other than Mystic so far).
I'll look to put in some validation in to clrhgouz to detect mail packets like this and inform the sender.
I think at moment the packet is rejected completely (I need to double check my code), so my downlinks wont get it, and any mail beyond the offending message in the same packet. (Then I sometimes see a bunch of "I didnt get that message" messages soon after :)
...δεσ∩
--- SBBSecho 3.29-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)
From Accession@21:1/200 to deon on Thu Oct 23 01:23:58 2025
Hey deon!
On Thu, 23 Oct 2025 11:30:52 +1100, you wrote:
OK, if that is the cause, then great.
Well, so long as the offender is willing to change his config. ;)
ie: PID=Golded, no origin line.
(I think tearline is optional anyway, cant remember, need to check.)
Yeah, it is optional.
I dont think its an issue with Synchronet, since SBBSecho adds that
stuff anyway I think (not noticed anyway with anything other than Mystic
so far).
sbbsecho forces it's own tear/origin lines. You can't disable it. So in that case, Golded needs to NOT send it's own tear/origin lines.
I'll look to put in some validation in to clrhgouz to detect mail
packets like this and inform the sender.
Don't think you could really go wrong with that, as most other software doesn't do anything remotely close. It either passes it on, or rejects it (most probably just pass it on).
I think at moment the packet is rejected completely (I need to double
check my code), so my downlinks wont get it, and any mail beyond the offending message in the same packet. (Then I sometimes see a bunch of
"I didnt get that message" messages soon after :)
Ouch. Yeah that's not good! In that case, maybe you're better off just passing on the messages, then. But by all means, if your software informs the sender of an error it'll already be doing better than most other softwares that don't say anything.
Regards,
Nick
... Sarcasm: because beating people up is illegal.
--- GoldED+/LNX 1.1.5-b20250409
* Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (21:1/200)
From manu@21:3/215 to All on Thu Oct 23 17:07:16 2025
Test
... A black cat crossing your path signifies that the animal is going somewhere
--- Mystic BBS v1.12 A48 (Windows/64)
* Origin: The Next Byte BBS (21:3/215)
From Sabre@21:1/206 to Zip on Thu Oct 23 12:59:28 2025
Hello Zip!
04 Jun 71 12:42, you wrote to me:
Hello Sabre!
On 21 Oct 2025, Sabre said the following...
Hello everybody!
Quick test please.
Thanks,
Sabre
Got you here (but no tearline or origin line -- perhaps the message
board type wasn't set to "Networked" or similar?).
Best regards
Zip
Ok, does this look better?
Thanks,
Sabre
--- SBBSecho 3.29-Linux
* Origin: Live Wire BBS [livewirebbs.com:1025] (21:1/206)
From Zip@21:1/202 to Sabre on Thu Oct 23 22:57:12 2025
Hello Sabre!
On 23 Oct 2025, Sabre said the following...
Ok, does this look better?
Yep! Looks fine:
--- SBBSecho 3.29-Linux
* Origin: Live Wire BBS [livewirebbs.com:1025] (21:1/206)
Best regards
Zip
--- Mystic BBS v1.12 A49 2024/05/29 (Linux/64)
* Origin: Star Collision BBS, Uppsala, Sweden (21:1/202)
From Zip@21:1/202 to manu on Thu Oct 23 22:58:55 2025
Hello manu!
On 23 Oct 2025, manu said the following...
Test
... A black cat crossing your path signifies that the animal is going somewhere
--- Mystic BBS v1.12 A48 (Windows/64)
* Origin: The Next Byte BBS (21:3/215)
Got you here!
Best regards
Zip
--- Mystic BBS v1.12 A49 2024/05/29 (Linux/64)
* Origin: Star Collision BBS, Uppsala, Sweden (21:1/202)
From manu@21:3/215 to Zip on Fri Oct 24 13:42:39 2025
Thanks
Manu
... A book misplaced is a book lost
--- Mystic BBS v1.12 A48 (Raspberry Pi/32)
* Origin: The Next Byte BBS (21:3/215)
From j0hnny a1pha@21:4/158.2 to All on Fri Oct 31 00:24:04 2025
From Zip@21:1/202 to Tanausu M. on Fri Nov 7 00:00:13 2025
Hello Tanausu!
On 06 Nov 2025, Tanausu M. said the following...
Hello, test message, greetings to all
--- SBBSecho 3.23-FreeBSD
* Origin: (21:3/219)
Hi there, and welcome!
Got you here!
Best regards
Zip
--- Mystic BBS v1.12 A49 2024/05/29 (Linux/64)
* Origin: Star Collision BBS, Uppsala, Sweden (21:1/202)
From Mindsurfer@21:3/119 to FSXNET.FSX_TST on Fri Nov 7 05:35:00 2025
Hey,
just found out that OpenXP (the good old Crosspoint). beside being a Fido Point Software, can do NNTP(s) as well. Not really a Fan of openXP's
Keyboard Shortcuts, but lets see if it sends out this message via NNTPS through my BBS.
From Al@21:4/106 to Mindsurfer on Thu Nov 6 23:15:32 2025
just found out that OpenXP (the good old Crosspoint). beside being a Fido Point Software, can do NNTP(s) as well. Not really a Fan of openXP's
Keyboard Shortcuts, but lets see if it sends out this message via NNTPS through my BBS.
--- BBBS/Li6 v4.10 Toy-7
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)
From Zip@21:1/202 to Mindsurfer on Sat Nov 8 00:34:56 2025
Hello Mindsurfer!
On 06 Nov 2025, Mindsurfer said the following...
Hey,
just found out that OpenXP (the good old Crosspoint). beside being a
Fido Point Software, can do NNTP(s) as well. Not really a Fan of openXP's Keyboard Shortcuts, but lets see if it sends out this message via NNTPS through my BBS.
--- BBBS/Li6 v4.10 Toy-7
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)
From Accession@21:1/200 to shindakun on Thu Nov 27 00:23:36 2025
Hey shindakun!
On Wed, 26 Nov 2025 09:27:44 +0000, you wrote:
@TZUTC: 0000
@MSGID: 21:1/999 d29297a7
@PID: gettossed 0.1
@TID: clrghouz 5c93c706
@DBID: 856005
This is a test!
--- gettossed/angstridden
* Origin: Angstridden BBS (21:3/222)
@PATH: 3/222 100 1/100 200
PATH matches the origin line, but the MSGID doesn't. Is this a possible bug?
Regards,
Nick
... Sarcasm: because beating people up is illegal.
--- GoldED+/LNX 1.1.5-b20250409
* Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (21:1/200)
From Lonewolf@21:3/223 to All on Thu Nov 27 02:41:26 2025
From shindakun@21:3/222 to Accession on Thu Nov 27 02:24:43 2025
Good catch Nick! Yeah I'm neckbearding and writing my own systems lol.
Looks like I'm missing settings the timezone and the msgid is just
wrong.
Lots more test messages to come lol!
Steve
--- gettossed/angstridden
* Origin: Angstridden BBS (21:3/222)
From CrackerTron@21:3/216 to All on Fri Nov 28 00:18:49 2025
... TCOB1: binkd only binkd.rima.ie
--- FMail-lnx 2.3.1.0
* Origin: TCOB1 A Mail Only System (21:1/229)
From Brian Scott@21:3/221 to All on Tue Dec 16 08:27:10 2025
Test
...I got a new shadow. My last shadow wasn't doing what I was doing.
--- SBBSecho 3.32-Linux
* Origin: -=The Ham Shack BBS=- Siloam Springs, Ar. (21:3/221)
From TheCivvie@21:1/229 to Brian Scott on Tue Dec 16 15:09:58 2025
...I got a new shadow. My last shadow wasn't doing what I was doing.
--- SBBSecho 3.32-Linux
* Origin: -=The Ham Shack BBS=- Siloam Springs, Ar. (21:3/221)
Got ya here
TheCivvie
... TCOB1: binkd only binkd.rima.ie
--- FMail-lnx 2.3.1.0
* Origin: TCOB1 A Mail Only System (21:1/229)
From Mindsurfer@21:3/119 to Brian Scott on Tue Dec 16 16:27:28 2025
Re: Test
By: Brian Scott to All on Tue Dec 16 2025 08:27:10
Test
...I got a new shadow. My last shadow wasn't doing what I was doing.
--- SBBSecho 3.32-Linux
* Origin: -=The Ham Shack BBS=- Siloam Springs, Ar. (21:3/221)
From Zip@21:1/202 to Brian Scott on Tue Dec 16 21:31:32 2025
Hello Brian!
On 16 Dec 2025, Brian Scott said the following...
Test
...I got a new shadow. My last shadow wasn't doing what I was doing.
--- SBBSecho 3.32-Linux
* Origin: -=The Ham Shack BBS=- Siloam Springs, Ar. (21:3/221)
Got you here! =)
Best regards
Zip
--- Mystic BBS v1.12 A49 2024/05/29 (Linux/64)
* Origin: Star Collision BBS, Uppsala, Sweden (21:1/202)
From Roon@21:4/148 to Brian Scott on Fri Dec 19 10:43:30 2025
From s2r@21:3/100.2 to Khronos on Mon Jan 26 21:50:12 2026
Hello Khronos!
25 Jan 26 13:24, you wrote to all:
@TZUTC: -0500
@MSGID: 92.fsxnet_fsx_tst@21:2/153 2ddb9626
@PID: Synchronet 3.21b-Linux master/6a514d1a1 Jan 24 2026 GCC 11.5.0
@TID: clrghouz 075829d8
@CHRS: ASCII 1
@NOTE: FSEditor.js v1.105
Sending a test.
Have not seen any messages from this net in a day or two.