Subj : Re: Importing echomail problem
To   : Mega Man
From : Avon
Date : Sat Feb 20 2021 15:12:03

On 19 Feb 2021 at 07:32p, Mega Man pondered and said...
 
 MM>  Av> Can you post the level 3 logs?
 MM> 
 MM> Attached is my log file

OK thanks, there's a few things here to dig into.

 MM> - Feb 19 15:13:58  EXEC ExportEchoMail
 MM> - Feb 19 15:13:58  EXEC ImportEchoMail
 MM> - Feb 19 15:13:58  EXEC FileToss
 MM> + Feb 19 15:13:58  Process: Toss FDN/TIC Files
 MM> + Feb 19 15:13:58  Results: Bad dir does not exist
 MM> d:\mystic\files\badfile\ in 0.02s

Firstly I'd separate out running export echomail from the other two
functions, you really want to call exporting as a standalone ini just to keep
things separated out..

Next you should create a badfile dir on your HDD... if you see above in your
ini file you currently point to a path in D drive that should be created.
Mystic will use this to shift files it has an issue with when processing them
as you run the import echomail / file toss.

It's a useful folder to have as it shows stuff up and allows you to fix
things, move the files back to the inbound dir and then run the process of
importing files/messages again :)

 MM> ! Feb 19 15:13:58    Import from d:\mystic\echomail\in\
 MM> ! Feb 19 15:13:58    Unknown inbound file FILE_ID.DIZ
 MM> ! Feb 19 15:13:58    Unknown inbound file ep210209.htm
 MM> ! Feb 19 15:13:58    Unknown inbound file ep210209.jpg
 MM> ! Feb 19 15:13:58    Unknown inbound file ep210209.txt
 MM> ! Feb 19 15:13:58    Unknown inbound file ep210209.zip
 MM> ! Feb 19 15:13:58    Unknown inbound file 1bxhc78v.tic

There are a mix of orphan files and ones that should import when running the  
toss FDN/TIC stanza... usually what you can expect to see is a pair of files,
the file to import and it's accompanying .TIC file... that if you look in
that text TIC file you will see the accompanying actual file mentioned, some
stuff about where the BBS should import it to etc.

Now in the list above the first four items, won't ever import, I'd just
delete them.

The other two should import, perhaps not because the bad files dir is
stopping things from running correctly.

 MM> ! Feb 19 15:13:58    Cannot find arctype for 22d19a24.we0; skipping
 MM> ! Feb 19 15:13:58    Cannot find arctype for 22d4db08.we0; skipping
 MM> ! Feb 19 15:13:58    Cannot find arctype for 22d80941.we0; skipping
 MM> ! Feb 19 15:13:58    Cannot find arctype for 28302d1b.su0; skipping
 MM> ! Feb 19 15:13:58    Cannot find arctype for 28388e47.su0; skipping
 MM> ! Feb 19 15:13:58    Cannot find arctype for 2846c71b.su0; skipping
 MM> ! Feb 19 15:13:58    Cannot find arctype for 292d5916.mo0; skipping
 MM> ! Feb 19 15:13:58    Cannot find arctype for 294ad70a.mo0; skipping

These are (usually) zipped up message packets, if you copy one to another
directory and try to unzip it you should find a message *.PKT file in it that
the BBS would import into a message area on your system.

The fact it's having issues could be a few things.

You don't have unzip on your system, unzip is not in a location Mystic can
find to use, you're settings in the archiver section for zip are incorrect,
or the compressed packets sent to you are corrupt and can't be opened by any
means... hence it's worth checking manually to see if you can crack them open.

What zip/unzip are you using? Hopefully infozip.

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

.