Subj : Re: Echomail not importing
To   : metalhead
From : Avon
Date : Sat Jan 02 2021 03:31 pm

On 01 Jan 2021 at 05:27p, metalhead pondered and said...
 
 me>   Importing 01192625.PKT (1:275/100 to 1:275/99)
 me>   Skip unsecure echomail in FIDO-REQ

There's your issue. 

Your packets are landing in your unsecure echomail in folder when they arrive
at Mystic

 me> "/home/admin/web/compfuck.xyz/public_html/mystic/echomail/in/unsecure/0000

Mystic will toss in packets from systems it knows, so those files it's
tossing should be in

/home/admin/web/compfuck.xyz/public_html/mystic/echomail/in

Best to fix things by ensuring the packets land in the correct inbound folder
from your mailer.. if they are landing there as a result of a BinkP
transaction then there's an issue in the session between both systems running
BinkP in that passwords are not matching up so Mystic accepts the packets but
dumps them in the unsecure folder as it treats the incoming system as
'unknown'

There's also this work around which you could enable in your ini file, I
generally don't do it for unknown systems regarding echomail

        ; Toss packets from unsecure directory in addition to inbound?
        
    unsecure_dir = true


Note: Mystic will alway toss netmail from systems known and unknown.

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

.