Subj : Re: Problem with tossing packets
To   : Avon
From : Sparky
Date : Thu Feb 04 2021 15:37:21

 Av> On 23 Jan 2021 at 06:08a, Sparky pondered and said...
 Av>  
 Av>  Sp> ! Jan 22 18:43:27    Moving c:\mystic\temputil\0b60a401.pkt to
 Av>  Sp> \0b60a401.pkt + Jan 22 18:43:27    Importing 0b60a40c.pkt (1:154/10 t
 Av>  Sp> 1:120/457) ! Jan 22 18:43:27    Invalid PKT password
 Av>  Sp> ! Jan 22 18:43:27    Moving c:\mystic\temputil\0b60a40c.pkt to
 Av>  Sp> \0b60a40c.pkt + Jan 22 18:43:27    Importing 0b60a51e.pkt (1:154/10 t
 Av>  Sp> 1:120/457) ! Jan 22 18:43:27    Invalid PKT password
 Av>  Sp> Should I have my HUB just remove packet passwords? 
 Av>  Sp> Jeff
 Av> 
 Av>  Sp> --- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
 Av> 
 Av> Couple of things.
 Av> 
 Av> There's a bug in this version of Mystic that caught me out.
 Av> If the packet is deemed BAD it should move it to a bad packet folder.
 Av> If you don't have that in your ini file then it is shifting them to your
 Av> root directory! So look for them there and move them to where you want
 Av> them to be. I'd suggest back into your inbound dir...
 Av> 
 Av> But before you do, yes, it's easiest to set your packet password as per
 Av> the system that is sending those packets to you. Then Mystic will toss
 Av> them in.

Hi Avon, The problem turned out to be I thought the HUB I was calling was
using a packet password, they were not. Deleted the packet password tossed
the packets back in the "inbound" directory and everything tossed nicely.
Jeff

--- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
 * Origin: Communicatin Connection 21:100/192 (21:1/192)

.