Hi everyone,

Please make sure your systems are cofigured correctly when it comes to Micronet. I am having all sorts of weird mail come in which I'm just deleting.

Thanks,
Sean

--- Mystic BBS v1.12 A48 (Linux/64)
* Origin: Classic BBS (618:250/1)

Hey Sean!

On Thu, Jul 24 2025 19:04:58 -0500, you wrote:

Hi everyone,

Please make sure your systems are cofigured correctly when it comes
to Micronet. I am having all sorts of weird mail come in which I'm
just deleting.

Thanks,
Sean

--- Mystic BBS v1.12 A48 (Linux/64)
* Origin: Classic BBS (618:250/1)

I can't believe this is even possible with Mystic. Someone was able to send a Micronet message to FSXnet with the original MSGID and origin line?

HPT should have caught that as an invalid message. How it got past two HPT tossers is kinda mind boggling.

Regards,
Nick

... Sarcasm: because beating people up is illegal.
--- SBBSecho 3.29-Linux
* Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (21:1/700)

Re: Re: Syste misconfiguration
By: Accession to Sean Dennis on Fri Jul 25 2025 05:15 pm

Howdy,

* Origin: Classic BBS (618:250/1)

I can't believe this is even possible with Mystic. Someone was able to send a Micronet message to FSXnet with the original MSGID and origin line?

HPT should have caught that as an invalid message. How it got past two HPT tossers is kinda mind boggling.

Actually, I've noticed HPT does it a lot, so I dont think it validates that?

I normally hear about it because clrghouz does reject invalid zones (for a domain), and netmails the sender (often another hub) of the invalid message.

For the most part it works well - the sender (if it isnt the hub) gets notified and it gets fixed. The bad part is other nodes on other hubs get the message anyway and reply to it - then I get a bunch of "I didnt get that message" messages to me from my nodes... :(


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

I can't believe this is even possible with Mystic. Someone was able to send Micronet message to FSXnet with the original MSGID and origin line?

HPT should have caught that as an invalid message. How it got past two HPT tossers is kinda mind boggling.

Another key to my point how FTN is screwed in mystic.

... Every girl's crazy 'bout a sharp dressed man.

--- Renegade v1.35/DOS
* Origin: The Titantic BBS Telnet - ttb.rgbbs.info (21:1/144)

Hey deon!

On Fri, Jul 25 2025 17:56:25 -0500, you wrote:

Actually, I've noticed HPT does it a lot, so I dont think it
validates that?

That's possible. I guess I just don't see something like this happen often enough. This specific message just stood out a bit more since it was clearly from Micronet, and I don't believe Sean is even a member of FSXnet. So how it got here was puzzling, to say the least.

I normally hear about it because clrghouz does reject invalid zones
(for a domain), and netmails the sender (often another hub) of the
invalid message.

Clrghaus may be one of the only tossers that rejects messages like that. I think the original idea was to allow anything that isn't a duplicate message to go through, so that ...

The bad part is other nodes on other hubs get the message anyway and
reply to it - then I get a bunch of "I didnt get that message"
messages to me from my nodes... :(

.. none of this ever happens. Then you also get the anti-censorship people that flail their arms around about free speech and all that (which can be understood in a non-crazy person kinda way, I guess), etc.

However, then you're more subject to people dumping a bunch of old messages back into a network if one's dupe detection isn't setup right. Here, I believe messages older than 14 days are rejected, and dupe detection goes back 365 days. So, if the messages that are dumped are older than a year it can still happen, or if the MSGID or message body was altered/changed in any way (sometimes RESCANS alter message body text, even though they shouldn't).

While there were standards in place all these years, a lot of developers interpreted those standards in their own way. So, it seems every tosser acts a bit different in different scenarios. So nothing is perfect. /shrug/

Regards,
Nick

... Sarcasm: because beating people up is illegal.
--- SBBSecho 3.29-Linux
* Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (21:1/700)

Hey Exodus!

On Fri, Jul 25 2025 15:19:42 -0500, you wrote:

HPT should have caught that as an invalid message. How it got past two HPT
tossers is kinda mind boggling.

Another key to my point how FTN is screwed in mystic.

I blame most faults of Mystic's FTN on people not understanding how to set it up correctly. I've used it pretty extensively and have never had any issues. Maybe it would be nice if Mystic had more self checking to the point where if someone set it up incorrectly (node numbers didn't match between echoareas and system address, etc) it would let them know, or just not work at all.

Either way, it's still a million times better than Irex. :D

Regards,
Nick

... Sarcasm: because beating people up is illegal.
--- SBBSecho 3.29-Linux
* Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (21:1/700)

Please make sure your systems are cofigured correctly when it comes
to Micronet. I am having all sorts of weird mail come in which I'm
just deleting.

Thanks,
Sean

--- Mystic BBS v1.12 A48 (Linux/64)
* Origin: Classic BBS (618:250/1)

I can't believe this is even possible with Mystic. Someone was able to send a Micronet message to FSXnet with the original MSGID and origin line?

HPT should have caught that as an invalid message. How it got past two HPT tossers is kinda mind boggling.

My recollection on Mystic is rusty at best, but I didn't even know you
could crosslink echoes... like point them to the same msg base... in the
config program. This message was originally posted by Sean from his own BBS
in MIN_ADMIN. Classic BBS must have echoed it back out into this echo
somehow. I don't think Sean is even on FSXnet.

What is even better is that they used *my* Micronet node number to do it,
too. ;) Looks like I need to have a talk with someone.


* SLMR 2.1a * May The Force be with you...
--- SBBSecho 3.28-Linux
* Origin: capitolcityonline.net * Telnet/SSH:2022/HTTP (21:1/175)

Hey Dumas!

On Sat, Jul 26 2025 11:10:19 -0500, you wrote:

My recollection on Mystic is rusty at best, but I didn't even know
you could crosslink echoes... like point them to the same msg base...
in the config program. This message was originally posted by Sean
from his own BBS in MIN_ADMIN. Classic BBS must have echoed it back
out into this echo somehow. I don't think Sean is even on FSXnet.

I'd imagine if you used the same echotag for both areas, it could be possible with just about anything. But, there's quite a difference between FSX_BBS and MIN_ADMIN, so there has to be something else at play here.

What is even better is that they used *my* Micronet node number to do it, too. ;) Looks like I need to have a talk with someone.

Yikes, makes it even more odd.

Regards,
Nick

... Sarcasm: because beating people up is illegal.
--- SBBSecho 3.29-Linux
* Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (21:1/700)

Re: Re: Syste misconfiguratio
By: Dumas Walker to ACCESSION on Sat Jul 26 2025 11:10 am

Howdy,

My recollection on Mystic is rusty at best, but I didn't even know you
could crosslink echoes... like point them to the same msg base... in the config program. This message was originally posted by Sean from his own BBS in MIN_ADMIN. Classic BBS must have echoed it back out into this echo somehow. I don't think Sean is even on FSXnet.

It might also be a bad packet?

I see fairly regularly from mystic systems - but I cant pinpoint why its occuring, but packets are corrupted because a subsequent messsage in the packet partially overwrites the previous message.

How I notice it, is I see or the SEEN-BY lines dumped as plain text in the message, often with the message truncated, and the "from" AKA shown as being the hub that sent the packet (at least for me in sync).


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

It might also be a bad packet?

I see fairly regularly from mystic systems - but I cant pinpoint why its occuring, but packets are corrupted because a subsequent messsage in the packe
partially overwrites the previous message.

How I notice it, is I see or the SEEN-BY lines dumped as plain text in the message, often with the message truncated, and the "from" AKA shown as being the hub that sent the packet (at least for me in sync).

I have seen those. In this case, I didn't notice the SEEN-BY lines in the
text but it could just be a different presentation of the same issue.


* SLMR 2.1a * The Word of the Day is "Legs." Spread the word.
--- SBBSecho 3.28-Linux
* Origin: capitolcityonline.net * Telnet/SSH:2022/HTTP (21:1/175)

Hi everyone,

My apologies that my BBS did this. I have been working with Mike from Micronet and after reserching the logs and verifying my configuration several times we are still not sure how this happened. My guess based on how the imports work is when Mystic was importing the networks somehow that message header got hosed up and/or corrupted and got redirected out to fsxNet as a post. This still blows my mind that this could even happen. I have had messages before and after in and out with no issues. I have turned logging up to debug incase it happens again in the future. Again, sorry for the weird post. Please let me know if you see this happen again.

Regards,
Mike Chilson (BitGuy)

BitGuy - Sysop - Classic BBS
classicbbs.net:9339 (telnet)
https://classicbbs.net (web)

--- Mystic BBS v1.12 A48 (Linux/64)
* Origin: Classic BBS (21:2/128)

Re: Re: Syste misconfiguratio
By: BitGuy to deon on Tue Jul 29 2025 11:41 am

Hey Mike,

My apologies that my BBS did this. I have been working with Mike from Micronet and after reserching the logs and verifying my configuration several times we are still not sure how this happened.

Its actually no big deal - and happens often (messages posted with the wrong origin line address, or posted to the wrong echo/network).

My tosser actually catches it, rejects it and sends the packet sender a netmail about it - but other tossers happily pass the message on.

We all fat finger something with this hobby...



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

Thanks deon. What was so strange about it is I verfied my configuration and nothing had changed in it for several months of moving messages in and out. If I had something misconfigured I would definately own up to it( I lost my ego many years ago). It was just really strange and we were unable to track anything specific down. Hopefully if it happens again in the future at least I have the logging turned up to debug so I can hopefully see what happened. :-)

Cheers,
Mike

BitGuy - Sysop - Classic BBS
classicbbs.net:9339 (telnet)
https://classicbbs.net (web)

--- Mystic BBS v1.12 A48 (Linux/64)
* Origin: Classic BBS (21:2/128)

origin line address, or posted to the wrong echo/network).

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Maybe with Mystic.

... The illuminati aren't out to get you. What was your name again?

--- Renegade v1.35/DOS
* Origin: The Titantic BBS Telnet - ttb.rgbbs.info (21:1/144)

Hey BitGuy!

On Tue, Jul 29 2025 17:59:06 -0500, you wrote:

Thanks deon. What was so strange about it is I verfied my
configuration and nothing had changed in it for several months of
moving messages in and out. If I had something misconfigured I would definately own up to it( I lost my ego many years ago). It was just
really strange and we were unable to track anything specific down. Hopefully if it happens again in the future at least I have the
logging turned up to debug so I can hopefully see what happened. :-)

As was mentioned already, it's not a big deal.

More than likely, you rebooted your machine or shut down/restarted Mystic while mutil was processing the packet, or something. As long as you're keeping an eye out for it, it probably won't happen again. ;)

Regards,
Nick

... Sarcasm: because beating people up is illegal.
--- SBBSecho 3.29-Linux
* Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (21:1/700)