On 08/09/17, Avon said the following...

Don't I know it :) Yep, it can often be something really simple ... when you finally figure it out! :)

Yea, then you spend the next couple hours kicking yourself in the ass for not catching it sooner :D

--- Mystic BBS v1.12 A34 (Windows/32)
* Origin: internal dimension + idbbs.dlinkddns.com + port 59 (21:1/178)

On 08/09/17, Jeff Smith said the following...

Sure thing. I recall here once that the software was calling the
archiver with switches that the archiver that was installed didn't fully support. Had to check each step in the process to find the point of dis-function.

yea.. like using switches for LHA that do not work on LHASA or JLHA-Utils .. it's so hard to find the original archivers

--- Mystic BBS v1.12 A34 (Windows/32)
* Origin: internal dimension + idbbs.dlinkddns.com + port 59 (21:1/178)

Here is a direct copy from the log file for some incoming files:

! Aug 08 02:58:31 Import from /home/dan/mystic/echomail/in/
! Aug 08 02:58:31 Unknown inbound file 0qptjg2g.tic
! Aug 08 02:58:31 Unknown inbound file FNEWSY32.ZIP

As far as I can tell, this is NOT the TIC processor logs.

--- Mystic BBS v1.12 A35 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

Yup, that was the issue. I changed that line, and ran mailin, and it tossed those files real quick. :)

I still can't believe I missed that line...

I would think that an error message of 'Path not found', or 'Change t path, Dummy' would help a bit more... ;)

I'm not sure exactly what the issue is but it does print a message if the directories do not exist.

--- Mystic BBS v1.12 A35 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

On 08/25/17, g00r00 pondered and said...

I would think that an error message of 'Path not found', or 'Cha path, Dummy' would help a bit more... ;)

I'm not sure exactly what the issue is but it does print a message if the directories do not exist.

It related to Dan missing a change to a path statement in the filetoss
stanza. He had moved from windows to linux and missed changing the syntax of
a path .. from memory it was dir_prefix

The error logging shared at the time made me comment that some further detail in the logging may have helped... but I can't (quickly) find the posts now
and I figured I'd just post this quick reply.

Saturday here and I am about to do a solid day outside in the garden with my wife! Wish me luck :)

Best, paul

--- Mystic BBS v1.12 A34 (Windows/32)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)

On 08/26/17, Avon said the following...

On 08/25/17, g00r00 pondered and said...

I would think that an error message of 'Path not found', or path, Dummy' would help a bit more... ;)

I'm not sure exactly what the issue is but it does print a message if directories do not exist.

It related to Dan missing a change to a path statement in the filetoss stanza. He had moved from windows to linux and missed changing the
syntax of a path .. from memory it was dir_prefix

The error logging shared at the time made me comment that some further detail in the logging may have helped... but I can't (quickly) find the posts now and I figured I'd just post this quick reply.

Saturday here and I am about to do a solid day outside in the garden
with my wife! Wish me luck :)

good times!!

--- Mystic BBS v1.12 A34 (Linux/32)
* Origin: Clutch BBS * telnet://clutch.darktech.org (21:1/199)

On 08/25/17, g00r00 said the following...

! Aug 08 02:58:31 Import from /home/dan/mystic/echomail/in/
! Aug 08 02:58:31 Unknown inbound file 0qptjg2g.tic
! Aug 08 02:58:31 Unknown inbound file FNEWSY32.ZIP

As far as I can tell, this is NOT the TIC processor logs.

That's what shows in the MUTIL.LOG file when you have the bad_dir in the .INI file set to a DOS path when running Linux... :/

It's working now... ;)


---

Black Panther
aka Dan Richter
Sysop - Castle Rock BBS
telnet://castlerockbbs.com
The sparrows are flying again...

--- Mystic BBS v1.12 A35 (Linux/64)
* Origin: Castle Rock BBS - castlerockbbs.com (21:1/186)

On 08/08/17, Black Panther said the following...

I did find out what I did though. In the MAILIN.INI file, there is a dir_prefix in the FileToss stanza. I forgot to change the path on that one... For some reason, Linux couldn't find c:\bbs\mystic\files\. It has

Old thread but I had several months of files, changing this just tossed the majority of them. Thanks!

-=>Richard Miles<=-
-=>Captain Obvious<=-
-=>bbs.shadowscope.com<=-

--- Mystic BBS v1.12 A38 2018/01/01 (Windows/32)
* Origin: Shadowscope BBS | bbs.shadowscope.com | Temple, GA (21:1/157)

On 01/26/18, Captain Obvious said the following...

I did find out what I did though. In the MAILIN.INI file, there is a dir_prefix in the FileToss stanza. I forgot to change the path on tha one... For some reason, Linux couldn't find c:\bbs\mystic\files\. It

Old thread but I had several months of files, changing this just tossed the majority of them. Thanks!

I'm not sure why, but that line in the .INI file is very easy to miss... I'm glad you were able to get it working.

What was the issue with the ones that didn't toss?


---

Black Panther
a.k.a. Dan Richter
Sysop - Castle Rock BBS (RCS)
The sparrows are flying again....

--- Mystic BBS v1.12 A38 2018/01/01 (Linux/64)
* Origin: Castle Rock BBS - bbs.castlerockbbs.com (21:1/186)

On 01/26/18, Black Panther said the following...

I'm not sure why, but that line in the .INI file is very easy to miss... I'm glad you were able to get it working.

Thing is, it was working with my settings until sometime last fall.

Quite a few of the ones that should have been good were tossed into the bad area. I'll have to take a look at some point and see why.

-=>Richard Miles<=-
-=>Captain Obvious<=-
-=>bbs.shadowscope.com<=-

--- Mystic BBS v1.12 A38 2018/01/01 (Windows/32)
* Origin: Shadowscope BBS | bbs.shadowscope.com | Temple, GA (21:1/157)