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

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)