Testing hpt


--- MagickaBBS v0.15alpha (Linux/x86_64)
* Origin: Project Scorpio (21:1175/0.6)

Re: Testing hpt
By: Blue White to All on Fri Feb 27 2026 01:16 pm

Testing hpt

|08ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿
|15 Ü|07 Ü |08Ü |11codefenix |08³
|15 Û|07ÛÛÛ|08Û |09ConstructiveChaos BBS |08³
|15 Þ|07ÜÛÜ|08Ý |01conchaos.synchro.net |08³ |08ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ
|07
--- SBBSecho 3.37-Win32
* Origin: -=[conchaos.synchro.net | ConstructiveChaos BBS]=- (21:4/141)

Hello Blue White!

On 27 Feb 2026, Blue White said the following...

Testing hpt


--- MagickaBBS v0.15alpha (Linux/x86_64)
* Origin: Project Scorpio (21:1175/0.6)

Seems to be working fine!

Best regards
Zip

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

Re: Testing hpt
By: Blue White to All on Fri Feb 27 2026 01:16 pm

Testing hpt

Seems to have got out!
--- SBBSecho 3.37-Linux
* Origin: Yak Station - Some yakkin' happenin'... (21:3/233)

Hello Zip!

27 Feb 26 21:42, you wrote to Blue White:

@TID: Mystic BBS 1.12 A49
@MSGID: 21:1/202 10cfcba8
@REPLY: 21:1175/0.6 69a1df9a
@TZUTC: 0100
Hello Blue White!

On 27 Feb 2026, Blue White said the following...

Testing hpt


--- MagickaBBS v0.15alpha (Linux/x86_64)
* Origin: Project Scorpio (21:1175/0.6)

Seems to be working fine!

You call that working fine? Look at the address in the origin line....


Vorlon


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

Hello Blue,

27 Feb 26 13:16, you wrote to All:

@TZUTC: -0500
@CHRS: CP437 2
@MSGID: 21:1175/0.6 69a1df9a
Testing hpt

--- MagickaBBS v0.15alpha (Linux/x86_64)
* Origin: Project Scorpio (21:1175/0.6)

are you sure this is a good AKA ? :)

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 160 161 162 163 164 166 168 169 171 172 173 174 175
177 178
SEEN-BY: 1/181 182 183 186 187 188 189 190 191 193 194 195 197 198 199
200 201
SEEN-BY: 1/202 203 204 205 206 207 208 210 211 212 213 214 215 216 217
218 219
SEEN-BY: 1/220 222 223 224 225 226 227 228 229 230 231 232 234 235 236
237 238
SEEN-BY: 1/239 240 241 242 244 245 246 247 248 249 616 995 999 2/100
1202
SEEN-BY: 3/100 4/100 101 102 103 104 105 106 107 108 110 111 112 113
114 115
SEEN-BY: 4/117 122 124 125 131 134 136 141 142 144 145 147 148 151 153
156 157
SEEN-BY: 4/158 162 167 170 174 176 177 181 183 187 1340 5/100
@PATH: 1/175 100 4/100

ByEbYe
--
Daniel

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

... Uptime: 9d 9h 42m 25s
--- GoldED/2 1.1.4.7+EMX
* Origin: Roon's BBS - Budapest, HUNGARY (21:4/148)

Ok, let's just go with "working".

You call that working fine? Look at the address in the origin line....

Vorlon

--- EXCELSIOR! 1.23; XMAIL! 1.92
* Origin: silentnode.ddns.net:6400 (21:3/206)

Hello Vorlon!

On 28 Feb 2026, Vorlon said the following...

* Origin: Project Scorpio (21:1175/0.6)

Seems to be working fine!

You call that working fine? Look at the address in the origin line....

Hmm, yes, that seems a tad off... :-O

Best regards
Zip

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

--- MagickaBBS v0.15alpha (Linux/x86_64)
* Origin: Project Scorpio (21:1175/0.6)

Seems to be working fine!

Hmmm, that net/node number is borked. Let's see if this one looks
better. ;)


--- MagickaBBS v0.15alpha (Linux/x86_64)
* Origin: Project Scorpio (21:1/175.6)

You call that working fine? Look at the address in the origin
line....

Hopefully fixed now. Had a config typo. No '/' and two ':' = a
broken origin. ;)


--- MagickaBBS v0.15alpha (Linux/x86_64)
* Origin: Project Scorpio (21:1/175.6)

Hello Blue White!

On 28 Feb 2026, Blue White said the following...

Hmmm, that net/node number is borked. Let's see if this one looks
better. ;)

* Origin: Project Scorpio (21:1/175.6)

Yep! Looks fine, I think! =)

Best regards
Zip

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

Re: RE: Testing hpt
By: Blue White to Vorlon on Sat Feb 28 2026 10:12 am

Howdy,

Hopefully fixed now. Had a config typo. No '/' and two ':' = a
broken origin. ;)
* Origin: Project Scorpio (21:1/175.6)

So your origin line looks OK now.

This got me thinking, your first message wouldnt have made it to Hub 3, Avon probably got a netmail from clrghouz telling him that the message was rejected (since his system would have sent it to the hub).

Perhaps instead of silence from the hub (to the author), and the uplink getting seemingly annoying messages about messages with bad AKAs, that instead it posts a message (in FSX_TST at least, or the offending echo) so you get to know its a bad message?

And just so my intentions are clear, the goal is to help systems with a bad configuration, that may otherwise go unnoticed and/or result in silence (especially if its a netmail, which a reply would never make it back). This would then alert the offender of the (bad?) configuration - enabling them to fix it and not wonder why there might be dead air?

As an upside, since I normally quote the offending message, then the downstream nodes would see it too :)


...ëîåï
--- SBBSecho 3.29-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)

Hmmm, that net/node number is borked. Let's see if this one looks
better. ;)

--- MagickaBBS v0.15alpha (Linux/x86_64)
* Origin: Project Scorpio (21:1/175.6)

looks better!

... Old musicians never die. They just decompose!

--- Mystic BBS v1.12 A49 2023/01/27 (Raspberry Pi/32)
* Origin: The Dark Side (21:3/234)

q
/d0

Perhaps instead of silence from the hub (to the author), and the
uplink getting seemingly annoying messages about messages with bad
AKAs, that instead it posts a message (in FSX_TST at least, or the offending echo) so you get to know its a bad message?

And just so my intentions are clear, the goal is to help systems
with a bad configuration, that may otherwise go unnoticed and/or
result in silence (especially if its a netmail, which a reply would
never make it back). This would then alert the offender of the
(bad?) configuration - enabling them to fix it and not wonder why
there might be dead air?

I think that sounds like a very good idea. The offender would know
they have an issue a lot sooner, and the hub wouldn't have to be
bothered by something trivial like a broken net/node number in an
origin line that isn't theirs. ;)

Thanks, deon!


/d 0
/ 1
/d 1

--- MagickaBBS v0.15alpha (Linux/x86_64)
* Origin: Project Scorpio (21:1/175.6)