Let me know if you guys see anything else I can try. Thanks so much!
Do you have anything in mystic/echomail/bad?
If so, maybe move those files back into mystic/echomail/in after setting loglevel=3 and importing again to give us a hint in the logs.
Importing 01192625.PKT (1:275/100 to 1:275/99)
Skip unsecure echomail in FIDO-REQ
"/home/admin/web/compfuck.xyz/public_html/mystic/echomail/in/unsecure/0000
Best to fix things by ensuring the packets land in the correct inbound folderfrom 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 runningBinkP in that passwords are not matching up so Mystic accepts the packets butdumps them in the unsecure folder as it treats the incoming system as'unknown'
I believe he mentioned in a previous message that he's not using a Bink password with his uplink. Would adding one fix this?
Your packets are landing in your unsecure echomail in folder when they arrive at Mystic
"/home/admin/web/compfuck.xyz/public_html/mystic/echomail/in/unsecure
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
; Toss packets from unsecure directory in addition to inbound?
unsecure_dir = true
Sysop: | digital man |
---|---|
Location: | Riverside County, California |
Users: | 1,033 |
Nodes: | 15 (0 / 15) |
Uptime: | 122:38:17 |
Calls: | 529 |
Calls today: | 23 |
Files: | 95,154 |
D/L today: |
4,405 files (585M bytes) |
Messages: | 298,857 |
Posted today: | 12 |