It seems as though he's trying to actually prefix his directory name, ie: fido_<dirname>, So Mystic seems to be telling him that ../mystic/files/fido_ doesn't exist. I've always understood the "Prefix

It removes the prefix part and checks to make sure the base directory is accessible. If it cannot access the base directory then it shows that error.

--- Mystic BBS v1.12 A46 2020/05/28 (Windows/64)
* Origin: Sector 7 | Mystic WHQ (1:129/215)

Hello g00r00,

On Thu Jun 11 2020 17:30:16, g00r00 wrote to Nicholas Boel:

It seems as though he's trying to actually prefix his directory
name, ie: fido_<dirname>, So Mystic seems to be telling him that
../mystic/files/fido_ doesn't exist. I've always understood the
"Prefix

It removes the prefix part and checks to make sure the base directory
is accessible. If it cannot access the base directory then it shows
that error.

Ah ok. Then disregard. ;)

Regards,
Nick

... "Take my advice, I don't use it anyway."
--- GoldED+/LNX 1.1.5-b20181215
* Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10)

Hello g00r00!

11 Jun 20 17:30, you wrote to Nicholas Boel:

It seems as though he's trying to actually prefix his directory
name, ie: fido_<dirname>, So Mystic seems to be telling him that
../mystic/files/fido_ doesn't exist. I've always understood the
"Prefix

It removes the prefix part and checks to make sure the base
directory is accessible. If it cannot access the base directory
then it shows that error.

And if that was the case I would totally understand the error and eliminate the cause of the error. But in this case /home/mystic/files
does indeed exist and is occupied by hundreds of sub-directories and thousands of files. All put there by Mystic for manually created file echos.

Jeff

quick question, if your files are litterly in /home/mystic/files, who owns the files/folders?? does the mystic folder and the files folder have the exact same permissions?? mutil might not be able to create the new folder if permissions are not right.

Michael

... Official Blue Wave Betazoid (oh, Deanna...?)
--- GoldED+/LNX 1.1.5-b20180707
* Origin: Mike's Mansion - Portland, OR - mansion.dynv6.net:2323 (1:340/201)

Hello Michael!

12 Jun 20 12:40, you wrote to me:

And if that was the case I would totally understand the error and
eliminate the cause of the error. But in this case
/home/mystic/files does indeed exist and is occupied by hundreds
of sub-directories and thousands of files. All put there by
Mystic for manually created file echos.

quick question, if your files are litterly in /home/mystic/files, who
owns the files/folders?? does the mystic folder and the files folder
have the exact same permissions?? mutil might not be able to create
the new folder if permissions are not right.

That was one of the first things that I checked. That entire directory structure /home/mystic/.... is owned by mystic and has read and write
access with create and delete rights. Mystic can toss files to the same
prefix directory /home/mystic/files/ when it tosses files for manually
created file echos. But for some reason doesn't seem to see
/home/mystic/files when using the auto-create option.

Jeff


--- Mystic v1.12 A46 (2020/06/10) GoldED+/LNX 1.1.5-b20170303
* Origin: The OuijaBoard BBS - bbs.ouijabrd.net (1:282/1031)

I use auto-create here and its working for me so thats as much as I know at the moment. I haven't had a chance to set up a test on the Linux
side.

I'm running Mystic v1.12 A45 (2020/02/18) on Windows 10 32bit. I can auto-create file areas but the auto-prefix option doesn't seem to work
for me.

It seems to ignore the (address)_dir_prefix= option and only use the dir_prefix= option.

Here's what I have in my mailin.ini:

bad_dir=c:\mystic\files\badfile
unsecure_dir = false
no_desc=No Description
uploader=NRBBS
check_crc = true
check_size = true
allow_unsecure = false
allow_replace = true
auto_create = true
1:229/426_bad_dir = c:\mystic\files\bad-fdn\
1:229/426_dir_prefix = c:\mystic\files\fdn_
1:229/426_allow_replace = true
1:229/426_acs_list = s10z2
1:229/426_acs_ftp = s255z2
1:229/426_acs_download = s20z2
1:229/426_acs_upload = s255z2
1:229/426_acs_hatch = s255z2
1:229/426_acs_sysop = s255z2
dir_prefix = c:\mystic\files\
dispfile =
template = ansiflst
acs_ftp = s255
acs_hatch = s255
free_files = 0
show_uploader = 1
new_scan = 1


I have several other lines in the .ini file such as:

21:3/100_dir_prefix = c:\mystic\files\fsx_
46:1/156_dir_prefix = c:\mystic\files\agora_
1337:3/100_dir_prefix = c:\mystic\files\tqw_
618:500/1_dir_prefix = c:\mystic\files\mcn_

It will create the new file base just fine, but it ignores the prefixed dir_prefix line and just uses "naked" dir_prefix option. All of the other settings seem to carry over. I tried removing the dir_prefix= option but
then the FileToss stanza just errors out.

Jay

--- Mystic BBS v1.12 A45 2020/02/18 (Windows/32)
* Origin: Northern Realms BBS | bbs.nrbbs.net | Binbrook, ON (1:229/664)

I have several other lines in the .ini file such as:

21:3/100_dir_prefix = c:\mystic\files\fsx_
46:1/156_dir_prefix = c:\mystic\files\agora_ 1337:3/100_dir_prefix = c:\mystic\files\tqw_
618:500/1_dir_prefix = c:\mystic\files\mcn_

This was not an option in A45. It was added in A46. If it doesn't work
after upgrading please let me know. There was someone else having a problem with this even in the A46 version so there is probably a bug somewhere that needs to be uncovered.

--- Mystic BBS v1.12 A46 2020/06/11 (Windows/64)
* Origin: Sector 7 | Mystic WHQ (1:129/215)

On 15 Jun 2020, g00r00 said the following...

This was not an option in A45. It was added in A46. If it doesn't work after upgrading please let me know. There was someone else having a problem with this even in the A46 version so there is probably a bug somewhere that needs to be uncovered.

Thank you sir, I'll give A46 a try today.

Jay

--- Mystic BBS v1.12 A45 2020/02/18 (Windows/32)
* Origin: Northern Realms BBS | bbs.nrbbs.net | Binbrook, ON (1:229/664)

quick question, if your files are litterly in /home/mystic/files,
who owns the files/folders?? does the mystic folder and the files
folder have the exact same permissions?? mutil might not be able
to create the new folder if permissions are not right.

That was one of the first things that I checked. That entire directory structure /home/mystic/.... is owned by mystic and has read and write access with create and delete rights. Mystic can toss files to the
same prefix directory /home/mystic/files/ when it tosses files for manually created file echos. But for some reason doesn't seem to
see /home/mystic/files when using the auto-create option.

it still sounds like a permissions issue?? maybe "auto-create" is using a different userid?? what if for a test, you chmod 777 files -R
see if being completely open for permission allows a file to be tossed.

the only other thing that comes to mind .. maybe auto-create is trying to create the file in a non-existent tmp location ?? like say instead of temp1 its /tmptic.xyz ??

Michael


... Bad Command:(A)bort (R)etry (T)ake RAM hostage
--- GoldED+/LNX 1.1.5-b20180707
* Origin: Mike's Mansion - Portland, OR - mansion.dynv6.net:2323 (1:340/201)