Okay once again, here's my main.ini and mailin.ini:

maint.ini
https://bit.ly/2nvJhKd

mailin.ini
https://bit.ly/2o0YhA5

Those shouldn't expire for another couple of days.

The problem I'm experiencing is that some files were hatched out a couple of days ago, causing the autocreation of file bases on my system. I have it set
to autocreate file bases in /home/mystic/files/fsx/ when they come from the Solaris' Tholian Hub at 21:/2/100

Anything NOT coming from my designated hub is hatched out in:the directory /home/mystic/files/

But these file areas were created in /home/mystic/files/ anyway. Which is NOT what I expected.

So I've got a couple of questions.

1.) What Am I doing wrong in my mailin.ini file, if anything?

2.) What is the *proper* way to move them from /home/mystic/files/ to /home/mystic/files/fsx/ ?The last time I did this, I merely moved them to the subdir fsx/ and then changed the paths in the File Base Editor - that seemed
to work fine, except I had problems with the nodelist as per my earlier post.

The File Areas created from this most recent hatching were:

FSX_MUTL
FSX_ARTS
FSX_TEXT

I can't remember if the infopack ws already created or not, but it's in the correct location of /home/mystic/files/fsx/FSX_INFO/

I wanted to make sure that all of this is working as expected, or at least
that I understand completely how it is going to behave, before I start with Fidonet message and file bases (Which by the way, I wish to have them be autocreated at /home/mystic/files/fido/).

Once I'm confident that everything is 'just so', I'll open the floodgates so
to speak ;)

Thanks, in advance, for any assistance rendered :)

Kindest regards,

Bradley

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: Vger.Cloud - NOMAD Internetwork (21:2/104)

On 30 Sep 2019 at 11:01p, tallship pondered and said...

Okay once again, here's my main.ini and mailin.ini:

Just off to sleep but will try to reply to yours and Zips messages tomorrow night. I did note the log size for mutil.log is different between both ini files so you may want to set both the same.

I'd also look at the forward statement in mailin.ini so as to pick up
directing alias netmails to your real name.

Will chat more tomorrow.

--- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

On 01 Oct 2019, Avon said the following...

On 30 Sep 2019 at 11:01p, tallship pondered and said...

Okay once again, here's my maint.ini and mailin.ini:

Just off to sleep but will try to reply to yours and Zips messages tomorrow night. I did note the log size for mutil.log is different
between both ini files so you may want to set both the same.

I'd also look at the forward statement in mailin.ini so as to pick up directing alias netmails to your real name.

Okay I've taken care of those two items, setting the log configs the same and
I set "sysop" to forward to Bradley Thornton. Maybe I should set another forwarder to forward "tallship" to Bradley Thornton as well? Is that standard etiquette?

Another weird thing, is that Entries in my File Base aren't being listed as new: https://bit.ly/2n8uXaY

Awaiting your input on those other issues :)

Kindest regards,

Bradley

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: Vger.Cloud - NOMAD Internetwork (21:2/104)

On 02 Oct 2019 at 06:25p, tallship pondered and said...

Okay I've taken care of those two items, setting the log configs the
same and I set "sysop" to forward to Bradley Thornton. Maybe I should
set another forwarder to forward "tallship" to Bradley Thornton as well? Is that standard etiquette?

It's a good idea to try to capture possible aka's and other aliases that
could be in the 'To:' field of any netmail intended for you. At least that's
my thinking around the topic :) That way stuff intended for you arrives in a way you can see and read it.

Here's mine... it's a bit overkill but you get the idea :)

forward = sysop;Paul Hayton
forward = system operator;Paul Hayton
forward = postmaster;Paul Hayton
forward = admin;Paul Hayton
forward = administrator;Paul Hayton
forward = Paul;Paul Hayton
forward = Paul H;Paul Hayton
forward = P Hayton;Paul Hayton
forward = Paul Haydon;Paul Hayton
forward = Avon;Paul Hayton

Note I added one with a typo, that was because I had some sent to me that way but because the name was incorrect I could see one new message in the netmail area but not read it as it was not addressed to my actual name.

Another weird thing, is that Entries in my File Base aren't being listed as new: https://bit.ly/2n8uXaY

I wonder if that because you might have already view the file via other
means, or run a different scan for new files process to then set the 'new'
flag to off. If you want to you can always set a new file scan date using the FP menu command that would reset the pointers to a date of your choosing.
You might want to check the bases are set to be included in a new file scan too.

Display File ³
Template ³ ansiflst
Def. Scan ³ Yes

Best, Paul

--- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

On 30 Sep 2019 at 11:01p, tallship pondered and said...

The problem I'm experiencing is that some files were hatched out a
couple of days ago, causing the autocreation of file bases on my system.
I have it set to autocreate file bases in /home/mystic/files/fsx/ when they come from the Solaris' Tholian Hub at 21:/2/100

Anything NOT coming from my designated hub is hatched out in:the
directory /home/mystic/files/

But these file areas were created in /home/mystic/files/ anyway. Which
is NOT what I expected.

So I've got a couple of questions.

1.) What Am I doing wrong in my mailin.ini file, if anything?

I can't see anything glaring.

21:2/100_bad_dir = /home/mystic/files/badfile/fsx/
21:2/100_dir_prefix = /home/mystic/files/fsx/
21:2/100_allow_replace = true
21:2/100_acs_list = s10z1
21:2/100_acs_ftp = s255z1
21:2/100_acs_download = s20z1
21:2/100_acs_upload = s30z1
21:2/100_acs_hatch = s255z1
21:2/100_acs_sysop = s255z1

..presuming both directories above are there and have correct permissions?

I note the main bad dir definition earlier in your file is the same as for 21:2/100 .. which is fine but just noticed that

bad_dir=/home/mystic/files/badfile/fsx

The following line

dir_prefix = /home/mystic/files/

I'm wondering if a prefix is important or not? I don't think so.. the problem is I have not auto created a lot of bases over time as mostly I have created them manually before the files landed in my BBS.

I'll do some tests to see if I can repro the issue.

I can't remember if the infopack ws already created or not, but it's in the correct location of /home/mystic/files/fsx/FSX_INFO/

Unless your MUTIL logs are around to check you or you can remember if you manually created the base.. you won't know I guess.. but if MUTIL created the base then above changes are even weirder.

2.) What is the *proper* way to move them from /home/mystic/files/ to /home/mystic/files/fsx/ ?The last time I did this, I merely moved them
to the subdir fsx/ and then changed the paths in the File Base Editor - that seemed to work fine, except I had problems with the nodelist as per my earlier post.

That's what I would do. Create the new directory within Mystic by stating the new file path in the file base editor then move the files from the old dir
into the newly created one.. don't touch the data file name.

--- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

On 30 Sep 2019 at 11:01p, tallship pondered and said...

The problem I'm experiencing is that some files were hatched out a
couple of days ago, causing the autocreation of file bases on my system.
I have it set to autocreate file bases in /home/mystic/files/fsx/ when they come from the Solaris' Tholian Hub at 21:/2/100

Anything NOT coming from my designated hub is hatched out in:the
directory /home/mystic/files/

But these file areas were created in /home/mystic/files/ anyway. Which
is NOT what I expected.

I did some tests with 21:1/100 and Agency at 21:1/101

Created a test file area called PTEST at 21:1/100 and added a file
(xqtr-gopher mod) then hatched it to Agency.

MUTIL logged the inbound file and TIC and reported this.

+ Oct 03 20:50:44 Process: Toss FDN/TIC Files
+ Oct 03 20:50:44 Waiting for BUSY nodes
+ Oct 03 20:50:44 Tossing xq-mbgopher.tic
- Oct 03 20:50:44 Unused Key (CREATED) Value (Created By Mystic BBS

[snip]

- Oct 03 20:50:44 Unused Key (PATH) Value (Path 21:1/100 Thu Oct 03 20:47:17 2019 UTC Mystic/1.12 A43)
- Oct 03 20:50:44 Unused Key (SEENBY) Value (Seenby 21:1/100)
- Oct 03 20:50:44 Unused Key (SEENBY) Value (Seenby 21:1/101)
- Oct 03 20:50:44 Unused Key (ORIGIN) Value (Origin 21:1/100)
+ Oct 03 20:50:44 File xq-mbgopher.zip Area PTEST From 21:1/100
+ Oct 03 20:50:44 Created area PTEST
- Oct 03 20:50:44 Replace "xq-mbgopher.zip"
+ Oct 03 20:50:44 Added to PTEST will it blend

Now my mailin.ini file has the following

; Agency HUB Z21 Uplink


21:1/100_bad_dir = c:\bbs\files\fsx\badfile\
21:1/100_dir_prefix = c:\bbs\files\fsx\fsx_
21:1/100_allow_replace = true
21:1/100_acs_list = s10z6
21:1/100_acs_ftp = s20z6
21:1/100_acs_download = s20z6
21:1/100_acs_upload = s255z6
21:1/100_acs_hatch = s255z6
21:1/100_acs_sysop = s255z5

and the default dir_prefix stated earlier looks like

dir_prefix = c:\bbs\files\fdn\fdn_

When I checked the file base created it reported the following

Base Name ³ PTEST will it blend
FTP Name ³ PTEST_will_it_blend
Echo Tag ³ PTEST
Net Address ³ 21:1/101 (fsxnet) Display File ³
Export To ³ 1 node(s) Template ³ ansiflst
List ACS ³ s10z6 Def. Scan ³ Yes
Upload ACS ³ s255z6 Free Files ³ No
Download ACS ³ s20z6 Slow Media ³ No
Hatch ACS ³ s255z3 Uploader ³ Yes
FTP ACS ³ s20z6 FileEcho Hub ³ No
Sysop ACS ³ s255z5 Anonymous FTP ³ No
List EACS ³
Data File ³ fdn_PTEST
File Path ³ c:\bbs\files\fdn\fdn_PTEST\

so you can see the stated settings for 21:1/100 were ignored and the default line used instead.

Clearly something is not working as it should be and I'm picking it's a bug that we'll need to report to the author g00r00 when he's next active again
and working on Mystic.

So in short it's nothing you did wrong :)

--- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

On 03 Oct 2019, Avon said the following...

21:1/100_bad_dir = c:\bbs\files\fsx\badfile\
21:1/100_dir_prefix = c:\bbs\files\fsx\fsx_
21:1/100_allow_replace = true

Okay that helps to answer another question I was wondering about, whether the dir_prefix needs to end with a slash (/) or not (backslash "\" on windows).

It appears that either way is acceptable, depending on if you want to create the dirs with or without a prefix, which is pretty kewl :)

and the default dir_prefix stated earlier looks like

dir_prefix = c:\bbs\files\fdn\fdn_

When I checked the file base created it reported the following
Net Address ³ 21:1/101 (fsxnet) Display File ³
Export To ³ 1 node(s) Template ³ ansiflst
List ACS ³ s10z6 Def. Scan ³ Yes
Upload ACS ³ s255z6 Free Files ³ No
Download ACS ³ s20z6 Slow Media ³ No
Hatch ACS ³ s255z3 Uploader ³ Yes
FTP ACS ³ s20z6 FileEcho Hub ³ No
Sysop ACS ³ s255z5 Anonymous FTP ³ No
Data File ³ fdn_PTEST
File Path ³ c:\bbs\files\fdn\fdn_PTEST\

so you can see the stated settings for 21:1/100 were ignored and the default line used instead.

Yes that's exactly what I'm experiencing. Good to know I'm not alone on this.

But your File Groups are a bit unusual from what I expected, and I remember a thread earlier in the week from.... maybe it was lemonline - someone anyway, who was noticing cross-posting response behavior that restriced responding in Echomail areas, with respect to groups.

I didn't pay too much attention but noted the thread for something to go back and look into later.

Clearly something is not working as it should be and I'm picking it's a bug that we'll need to report to the author g00r00 when he's next active again and working on Mystic.

So in short it's nothing you did wrong :)

That's really good news for me, because I thought it was me lol.

Anyway, yes it appears that it is something that needs a follow up when he's active again. Too bad he doesn't have a bug tracking system where it could be waiting when he does engage again, but those are often filled with superflous non-bugs that tend to waste the dev's time anyway, so maybe it's for the best.

This of course, is not a big deal at the moment, but could become a pita once
I start bringing in FidoNet FileBases. What I'll probably do is use FileFix
to order up about a half dozen at a time every few days so as not to be overhwelmed and monopolize my time doing other things ;)

Right now, the only connections that I "Can" receive are from 21:1/100 and 21:2/100 as anything else destined for my BINKD port is blocked by my
firewall.

Do you know if it will break mutil jobs if I comment out the default
dir_prefix line?

Something to contemplate anyway. In the meantime I'll just move those file bases as per your instructions and affect those changes in the File Base Editor.

Thanks Paul :)

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: Vger.Cloud - NOMAD Internetwork (21:2/104)

It's a good idea to try to capture possible aka's and other aliases that could be in the 'To:' field of any netmail intended for you. At least that's my thinking around the topic :) That way stuff intended for you arrives in a way you can see and read it.

This is really cool - I didn't realize you could do this. Where are these forward entries set in the mystic configuration files?

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: vswitchzero BBS (21:4/162)

Hello lemonlime!

On 03 Oct 2019, lemonlime said the following...

It's a good idea to try to capture possible aka's and other aliases t could be in the 'To:' field of any netmail intended for you. At least

This is really cool - I didn't realize you could do this. Where are these forward entries set in the mystic configuration files?

If those are the entries I think they are :) then they're in the [ImportEchoMail] stanza of mutil.ini.

Best regards
Zip

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: Star Collision BBS, Uppsala, Sweden (21:1/202)

If those are the entries I think they are :) then they're in the [ImportEchoMail] stanza of mutil.ini.

Best regards
Zip

They are indeed! Thanks Zip.

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: vswitchzero BBS (21:4/162)