Hello everybody!

Quick test please.

Thanks,
Sabre

I will take this opportunity to confirm you are good to go, while testing myself.

Cheers,
toz

... If all the world is a stage, where is the audience sitting?

--- Mystic BBS v1.12 A48 (Windows/32)
* Origin: .:[No Carrier BBS]:. Found within dn42! (bbs.dn42) (21:1/999)

Hello Sabre!

21 Oct 25 15:03, you wrote to all:

@TID: Mystic BBS 1.12 A48
@MSGID: 21:1/206@fsxnet.org 68f7e743
@PID: GED+W64 1.1.5-b20250409
@CHRS: CP437 2
@TZUTC: -0500
Hello everybody!

Quick test please.

Thanks,
Sabre

SEEN-BY: 1/100 101 102 103 105 106 107 108 109 110 111 112 113 114 116
117 118
SEEN-BY: 1/119 120 121 122 123 124 125 126 127 128 129 130 131 133 135
136 137
SEEN-BY: 1/138 139 140 141 142 143 144 145 146 147 148 149 150 152 153
155 156
SEEN-BY: 1/157 158 159 160 161 162 163 164 166 168 169 171 172 173 174
175 177
SEEN-BY: 1/178 181 182 183 186 187 188 189 190 191 193 194 195 196 197
198 199
SEEN-BY: 1/200 201 202 203 204 205 206 207 208 210 211 212 213 214 215
216 217
SEEN-BY: 1/218 219 220 222 223 224 225 226 227 228 229 230 231 232 234
235 236
SEEN-BY: 1/237 238 239 240 241 242 244 245 246 247 248 249 616 995 999 2/100
SEEN-BY: 2/1202 3/100 4/100 106 5/100
@PATH: 1/206 100 195

Fail: No Origin or Tear line.




Vorlon


--- GoldED+/LNX 1.1.5-b20250409
* Origin: Dragon's Lair ---:- dragon.vk3heg.net -:--- Prt: 6800 (21:1/195)

Re: Test
By: Vorlon to Sabre on Wed Oct 22 2025 09:46 am

Howdy,

Quick test please.

SEEN-BY: 1/100 101 102 103 105 106 107 108 109 110 111 112 113 114 116 117 118

Fail: No Origin or Tear line.

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.


...δεσ∩
--- SBBSecho 3.29-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)

Hello deon!

22 Oct 25 11:51, you wrote to me:

Quick test please.

SEEN-BY: 1/100 101 102 103 105 106 107 108 109 110 111 112 113
114 116 117 118

Fail: No Origin or Tear line.

This is one of this mystic packet fails.

This one is operator error.

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

Golded: PID: GED+W64 1.1.5-b20250409




Vorlon


--- GoldED+/LNX 1.1.5-b20250409
* Origin: Dragon's Lair ---:- dragon.vk3heg.net -:--- Prt: 6800 (21:1/195)

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)

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)

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:

ctrlinfonet none
ctrlinfolocal none
ctrlinfoecho tearline origin
tearline @longpid @version

Or maybe we'll get lucky and he'll read this.

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)

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)



Vorlon


--- GoldED+/LNX 1.1.5-b20250409
* Origin: Dragon's Lair ---:- dragon.vk3heg.net -:--- Prt: 6800 (21:1/195)

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)

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)

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)

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)

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)

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)

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)

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)

Testing... is this going out?


--- Retrograde 1.0.0/linux
* Origin: Retrograde BBS (21:4/158.2)

Hello j0hnny!

30 Oct 25 19:24, you wrote to all:

Testing... is this going out?

Yes it is!

--- Retrograde 1.0.0/linux
* Origin: Retrograde BBS (21:4/158.2)

s2r


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

Hello j0hnny!

On 30 Oct 2025, j0hnny a1pha said the following...

Testing... is this going out?

--- Retrograde 1.0.0/linux
* Origin: Retrograde BBS (21:4/158.2)

Yep! Got that one as well!

Best regards
Zip

--- Mystic BBS v1.12 A49 2024/05/29 (Linux/64)
* Origin: Star Collision BBS, Uppsala, Sweden (21:1/202)

j0hnny a1pha wrote to All <=-

Testing... is this going out?
--- Retrograde 1.0.0/linux
* Origin: Retrograde BBS (21:4/158.2)

Got it here!

... SURF NAKED: sharks hate to peel their food
___ MultiMail/Win v0.52

--- Mystic BBS/QWK v1.12 A48 (Windows/32)
* Origin: The Looney Bin BBS! - looneybinbbs.com (21:2/166)