A Mystic-system writing netmail to a point-system royally messes-up that message and makes it effectively unroutable ...

INTL 2:292/854.1 2:292/140

An accidental point on a INTL isn't quite "royally messing up", Ward! :)

Its a bug that was fixed and released immediately once it was reported to me.

Seems to be routing okay despite this issue with just about everything we're currently using, so /shrug?

--- Mystic BBS v1.12 A40 2018/12/23 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (1:129/215)

Hi g00r00,

INTL 2:292/854.1 2:292/140

An accidental point on a INTL isn't quite "royally messing up", Ward! :)

I beg to differ ... an INTL 2:292/854.1 is unroutable by every definition in the book. The only reason why I got it is because I am the de-facto outbound for that particular downlink. Had the message been intended for someone beyond my system it never would have gottten anywhere.

Let's not discuss FTS/routing-101 here.

Its a bug that was fixed and released immediately once it was reported to me.

With thanks BTW for the speedy response. Was tested in the meantime and works just fine.

Seems to be routing okay despite this issue with just about everything
we're currently using, so /shrug?

Again, I beg to differ, it did not route just OK. But now it does.

Merry Xmas or whatever is important to you on this day in the year.

\%/@rd

--- D'Bridge 3.99 SR40
* Origin: The best gold is at the bottom of barrels of crap (2:292/854)

An accidental point on a INTL isn't quite "royally messing up", Ward! :

I beg to differ ... an INTL 2:292/854.1 is unroutable by every

Yes, its clearly been so much of a major issue that royally messed everything up! So much so that no one noticed it for 6 years!

Let's not discuss FTS/routing-101 here.

We're not. We're discussing you being over dramatic by trying to turn a mole hill into a mountain. :)

Its simply enough to report it and get it fixed without all the unnecessary dramatics.

--- Mystic BBS v1.12 A40 2018/12/23 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (1:129/215)

On 2018 Dec 24 11:19:14, you wrote to Ward Dossche:

Seems to be routing okay despite this issue with just about everything we're currently using, so /shrug?

i think he meant that other systems have problems with it... mystic may handle it just fine but others may choke...

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
... Steve Hawkins' new cosmological cookbook: "A brief history of thyme."
---
* Origin: (1:3634/12.73)

On 12/24/18, g00r00 said the following...

We're not. We're discussing you being over dramatic by trying to turn a mole hill into a mountain. :)

Its simply enough to report it and get it fixed without all the unnecessary dramatics.

DAMNIT!! NO dramatics? How DARE you! The only reason I was following this thread is I was hoping to see a lightsaber, phaser, or SOMEthing pulled out
by ONE of you. I'm going to go back to my rockad crawl under it, THANKS
g00r00!


BTW,
:'|

--- Mystic BBS v1.12 A39 2018/04/21 (Linux/64)
* Origin: theamiga.frontierbbs.net:2023 (Ohio) (1:226/16)

Re: Re: Kludge-mess
By: Charles Stephenson to g00r00 on Thu Dec 27 2018 01:13 pm

DAMNIT!! NO dramatics? How DARE you! The only reason I was following this thread is I was hoping to see a lightsaber, phaser, or SOMEthing pulled out by ONE of you. I'm going to go back to my rockad crawl under it,

Maybe I should learn to proofread my messages, wtf is a rockad??
Regards,
KrUpTiOn
--- SBBSecho 3.04-Linux
* Origin: The New Frontier 2: thenewfrontier2.hopto.org (OH) (1:226/17)

Hello Charles!

27 Dec 18 13:55, you wrote to KrUpTiOn:

DAMNIT!! NO dramatics? How DARE you! The only reason I was
following this thread is I was hoping to see a lightsaber,
phaser, or SOMEthing pulled out by ONE of you. I'm going to go
back to my rockad crawl under it,

Maybe I should learn to proofread my messages, wtf is a rockad??

Rock and perhaps?

Andrew

--- GoldED+/LNX 1.1.5-b20180707
* Origin: Phoenix BBS * phoenix.bnbbbs.net (1:320/219)