Subj : Re: Problem with tossing packets
To   : Sparky
From : Avon
Date : Thu Feb 04 2021 17:06:46

On 23 Jan 2021 at 06:08a, Sparky pondered and said...
 
 Sp> ! Jan 22 18:43:27    Moving c:\mystic\temputil\0b60a401.pkt to
 Sp> \0b60a401.pkt + Jan 22 18:43:27    Importing 0b60a40c.pkt (1:154/10 to
 Sp> 1:120/457) ! Jan 22 18:43:27    Invalid PKT password
 Sp> ! Jan 22 18:43:27    Moving c:\mystic\temputil\0b60a40c.pkt to
 Sp> \0b60a40c.pkt + Jan 22 18:43:27    Importing 0b60a51e.pkt (1:154/10 to
 Sp> 1:120/457) ! Jan 22 18:43:27    Invalid PKT password
 Sp> Should I have my HUB just remove packet passwords? 
 Sp> Jeff

 Sp> --- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)

Couple of things.

There's a bug in this version of Mystic that caught me out.
If the packet is deemed BAD it should move it to a bad packet folder.
If you don't have that in your ini file then it is shifting them to your root
directory! So look for them there and move them to where you want them to be.
I'd suggest back into your inbound dir...

But before you do, yes, it's easiest to set your packet password as per the
system that is sending those packets to you. Then Mystic will toss them in.

As for that ini switch here's what I added for my setup


[ImportEchoMail]

    ; If you want bad packets that cannot be imported moved to a directory
    ; then uncomment and set this value to an existing directory.

    bad_packet = C:\bbs\mystic\echomail\in\bad

--- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
 * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

.