I have noticed over the last few months my Mystic board will get random bad packets and lockup mutil when trying to toss. I have looked at the packets
and it's not single area, it happens in random areas. The only solution is
to delete that packet. It's kinf of weird to me, I don't have any issues
with the packets on this IREX unit. Anyone else experience this or have a solution?

Thanks,

-Scuz


--- Oblivion/2 v2.40beta2
* Origin: Hexedbbs.com:23999 (21:1/244)

Hello All.

2 questions. How can you tell why a packet went bad? How can I re-toss a bad packet?

Thanks,
RickV

=== GoldED+/W64-MSVC 1.1.5-b20240306
# Origin: The File Cabinet BBS [filecabi.casacam.net:1025] (21:1/206)
--- SBBSecho 3.24-Win32
* Origin: The File Cabinet BBS [filecabi.casacam.net:1025] (21:1/206)

RickV wrote to All <=-

Hello All.

2 questions. How can you tell why a packet went bad? How can I re-toss
a bad packet?

As is usual with Synchronet, the answers are likely on the Wiki, as I
believe has been suggested to you quite a few times already...

I searched "bad packet" on the Wiki, and found this:

https://wiki.synchro.net/ref:fidonet_glossary?s[]=bad&s[]=packet

Looks pretty straightforward, eh?

You'd likely get more/quicker answers by asking in the appropriate echo
areas on DoveNet, since it's pretty much SBBS-specific.



... Gone crazy, be back later, please leave message.
=== MultiMail/Linux v0.52
--- SBBSecho 3.23-Linux
* Origin: Palantir * palantirbbs.ddns.net * Pensacola, FL * (21:2/138)

Hey RickV!

On Sun, 30 Mar 2025 10:05:22 -0500, you wrote:

2 questions. How can you tell why a packet went bad? How can I re-toss a bad packet?

--- SBBSecho 3.24-Win32

Usually, the #1 place that will inform you about a bad packet would be your tosser's logs.

At the moment, you seem to currently be using Synchronet, while asking this question in a Mystic support area. Which tosser are you actually asking the question about? Most tossers don't handle bad packets/bundles the exact same.

To learn more about how these things that you're using work, and also where bad packets are explained for each tosser respectively..

For Synchronet:
https://wiki.synchro.net/util:sbbsecho

For Mystic:
https://wiki.mysticbbs.com/doku.php?id=mutil_import_echomail

Regards,
Nick

... Sarcasm: because beating people up is illegal.
--- GoldED+/LNX 1.1.5-b20240604
* Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (21:1/200)

Hello Gamgee.

11 Jul 70 10:26, you wrote to me:

RickV wrote to All <=-

Hello All.

2 questions. How can you tell why a packet went bad? How can I
re-toss a bad packet?

As is usual with Synchronet, the answers are likely on the Wiki, as I believe has been suggested to you quite a few times already...

I searched "bad packet" on the Wiki, and found this:

https://wiki.synchro.net/ref:fidonet_glossary?s[]=bad&s[]=packet

Looks pretty straightforward, eh?

You'd likely get more/quicker answers by asking in the appropriate
echo areas on DoveNet, since it's pretty much SBBS-specific.

... Gone crazy, be back later, please leave message.
=== MultiMail/Linux v0.52

I posted the question in a Mystic support echo because that's where the bad packets are. On my Mystic system, my SBBS system is fine. You should make sure YOU know what your talking about.

RickV

=== GoldED+/W64-MSVC 1.1.5-b20240306
# Origin: The File Cabinet BBS [filecabi.casacam.net:1025] (21:1/206)
--- SBBSecho 3.24-Win32
* Origin: The File Cabinet BBS [filecabi.casacam.net:1025] (21:1/206)

RickV wrote to Gamgee <=-

2 questions. How can you tell why a packet went bad? How can I
re-toss a bad packet?

I searched "bad packet" on the Wiki, and found this:

https://wiki.synchro.net/ref:fidonet_glossary?s[]=bad&s[]=packet

You'd likely get more/quicker answers by asking in the appropriate
echo areas on DoveNet, since it's pretty much SBBS-specific.

I posted the question in a Mystic support echo because that's where the bad packets are. On my Mystic system, my SBBS system is fine. You
should make sure YOU know what your talking about.

--- SBBSecho 3.24-Win32
* Origin: The File Cabinet BBS [filecabi.casacam.net:1025] (21:1/206)

Yep, OK... but sure looks like you're posting from SBBS... ^^^



... If what you don't know can't hurt you, she's practically invulnerable.
=== MultiMail/Linux v0.52
--- SBBSecho 3.23-Linux
* Origin: Palantir * palantirbbs.ddns.net * Pensacola, FL * (21:2/138)

Re: Re: Bad packets
By: Gamgee to RickV on Sun Mar 30 2025 12:37:36

Yep, OK... but sure looks like you're posting from SBBS... ^^^

Well I was, but the question was in a Mystic echo about a Mystic packet problem.

RickV
--- SBBSecho 3.24-Win32
* Origin: The File Cabinet BBS [filecabi.casacam.net:1025] (21:1/206)

Rick V wrote to Gamgee <=-

Re: Re: Bad packets
By: Gamgee to RickV on Sun Mar 30 2025 12:37:36

Yep, OK... but sure looks like you're posting from SBBS... ^^^

Well I was, but the question was in a Mystic echo about a Mystic packet problem.

To be fair, you NEVER said a single word about it being a "Mystic"
packet problem.

In fact, just a few days ago, you were asking this EXACT same question
in the SBBS support forums on DoveNet, and specifically told Digitalman
"that helps" when he explained in good detail how to troubleshoot this
problem on SBBS. Let me know if you'd like me to quote some messages
from there.

So............. can you see why I was thinking you were asking about Synchronet?

As a general rule, asking good/detailed/complete questions about
something will get you good answers. Being vague and leaving out
helpful information ... will not.



... Internal Error: The system has been taken over by sheep at line 19960
=== MultiMail/Linux v0.52
--- SBBSecho 3.23-Linux
* Origin: Palantir * palantirbbs.ddns.net * Pensacola, FL * (21:2/138)

2 questions. How can you tell why a packet went bad? How can I re-toss a bad packet?

There are different packet types floating around the net.

The old standard Type 2. These are fine but they have no support for points unless you use a fakenet method. I don't think you'll see any of these today.

The most common is Type 2+ and Type 2e. These are the most common these days and they do support points.

There is also a Type 2.0 (and possibly others!) but these are not well supported. I think Synchronet will toss and produce all of these packet types if configured so but not all tossers can recognize them and will toss them bad.

--- BBBS/Li6 v4.10 Toy-7
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)

Hello Gamgee.

11 Jul 70 14:19, you wrote to Rick V:

Rick V wrote to Gamgee <=-

Re: Re: Bad packets
By: Gamgee to RickV on Sun Mar 30 2025 12:37:36

Yep, OK... but sure looks like you're posting from SBBS... ^^^

Well I was, but the question was in a Mystic echo about a Mystic
packet problem.

To be fair, you NEVER said a single word about it being a "Mystic"
packet problem.

In fact, just a few days ago, you were asking this EXACT same question
in the SBBS support forums on DoveNet, and specifically told
Digitalman "that helps" when he explained in good detail how to troubleshoot this problem on SBBS. Let me know if you'd like me to
quote some messages from there.

So............. can you see why I was thinking you were asking about Synchronet?

As a general rule, asking good/detailed/complete questions about
something will get you good answers. Being vague and leaving out
helpful information ... will not.

... Internal Error: The system has been taken over by sheep at line
19960
=== MultiMail/Linux v0.52

I guess we both made assumptions, I was in the Mystic echo and assumed that it would be viewed as a mystic question, and you saw it was a post FROM a SBBS system...

RickV

=== GoldED+/W64-MSVC 1.1.5-b20240306
# Origin: The File Cabinet BBS [filecabi.casacam.net:1025] (21:1/206)
--- SBBSecho 3.24-Win32
* Origin: The File Cabinet BBS [filecabi.casacam.net:1025] (21:1/206)

Hello Gamgee.

11 Jul 70 14:19, you wrote to Rick V:

Rick V wrote to Gamgee <=-

Re: Re: Bad packets
By: Gamgee to RickV on Sun Mar 30 2025 12:37:36

Yep, OK... but sure looks like you're posting from SBBS... ^^^

Well I was, but the question was in a Mystic echo about a Mystic
packet problem.

To be fair, you NEVER said a single word about it being a "Mystic"
packet problem.

In fact, just a few days ago, you were asking this EXACT same question
in the SBBS support forums on DoveNet, and specifically told
Digitalman "that helps" when he explained in good detail how to troubleshoot this problem on SBBS. Let me know if you'd like me to
quote some messages from there.

So............. can you see why I was thinking you were asking about Synchronet?

As a general rule, asking good/detailed/complete questions about
something will get you good answers. Being vague and leaving out
helpful information ... will not.

... Internal Error: The system has been taken over by sheep at line
19960
=== MultiMail/Linux v0.52

I guess we both made assumptions, I was in the Mystic echo and assumed that it would be viewed as a mystic question, and you saw it was a post FROM a SBBS system...

RickV

=== GoldED+/W64-MSVC 1.1.5-b20240306
# Origin: The File Cabinet BBS [filecabi.casacam.net:1025] (21:1/206)

--- Mystic BBS v1.12 A49 2024/05/29 (Windows/64)
* Origin: Altair IV BBS (21:1/206)