All,

I'm trying to have Allfix create new fileecho's in EleBBS. This works when an area is automatically created using the mask which is defined in the filegroups. But when I manually enter a new fileecho in asetup then this doesn't seem to create anything in EleBBS. I would assume that it's supposed to
create it in elebbs too?


Groetjes,
Tom

--- GoldED+/W32-MINGW 1.1.5-b20130111
* Origin: BrainDeath BBS (2:292/8125)

On Thu, 14 Nov 2013, Tom De Puysseleyr wrote to All:

I'm trying to have Allfix create new fileecho's in EleBBS. This
works when an area is automatically created using the mask which
is defined in the filegroups. But when I manually enter a new
fileecho in asetup then this doesn't seem to create anything in
EleBBS. I would assume that it's supposed to create it in elebbs
too?

no... if you create them in allfix manually, then it would seem to be that you would also manually create them in the bbs software... the same thing comes for
updating one's FREQ directories list for mailers or FREQ processors to use so they know what directories to look in for FREQs...

)\/(ark

--- FMail/Win32 1.60
* Origin: (1:3634/12.71)

mark,

14 Nov 13 12:31, you wrote to me:

I'm trying to have Allfix create new fileecho's in EleBBS. This
works when an area is automatically created using the mask which
is defined in the filegroups. But when I manually enter a new
fileecho in asetup then this doesn't seem to create anything in
EleBBS. I would assume that it's supposed to create it in elebbs
too?

no... if you create them in allfix manually, then it would seem to be
that you would also manually create them in the bbs software... the
same thing comes for updating one's FREQ directories list for mailers
or FREQ processors to use so they know what directories to look in for FREQs...

And is that on purpose? I mean, I don't know about the freq things, but the functions for creating the areas in the bbs software already exist in the source, so why not run them when an area is manually created (could be a setting somewhere)? Same thing for using the import fuction to import a filebone.na file...



Groetjes,
Tom

--- GoldED+/W32-MINGW 1.1.5-b20130111
* Origin: BrainDeath BBS (2:292/8125)

On Fri, 15 Nov 2013, Tom De Puysseleyr wrote to mark lewis:

I'm trying to have Allfix create new fileecho's in EleBBS. This
works when an area is automatically created using the mask which
is defined in the filegroups. But when I manually enter a new
fileecho in asetup then this doesn't seem to create anything in
EleBBS. I would assume that it's supposed to create it in elebbs
too?

no... if you create them in allfix manually, then it would seem to be
that you would also manually create them in the bbs software... the
same thing comes for updating one's FREQ directories list for mailers
or FREQ processors to use so they know what directories to look in for FREQs...

And is that on purpose?

yes as far as i know... it has always been that way...

I mean, I don't know about the freq things,

FREQs are file requests... inbound FREQs have to be processed by some software that knows where to look for the file(s) being requested so one must maintain a
list of directories that others are allowed to FREQ from... there is also a list of "magic names" where one can FREQ one specific name and get the latest file for that name...

eg: nodelist -> nodelist.z12

where nodelist.z12 is changed in the list every time a new nodelist.z?? file is
received...

but the functions for creating the areas in the bbs software
already exist in the source, so why not run them when an area is manually created (could be a setting somewhere)?

because you may be setting up an area that you do not want on the BBS...

Same thing for using the import fuction to import a filebone.na
file...

yeah, i don't know who started that but the importation of the *.NA files was only to import the ares's description into the configs... using the *.NA files to create all of one's file and message areas is not really a good idea for various reasons... but it has been done and others are copying it :/

)\/(ark

--- FMail/Win32 1.60
* Origin: (1:3634/12.71)

mark,

15 Nov 13 09:06, you wrote to me:

but the functions for creating the areas in the bbs software
already exist in the source, so why not run them when an area is
manually created (could be a setting somewhere)?

because you may be setting up an area that you do not want on the
BBS...

That's why providing a setting or an option to choose if you want to export them would be a good idea :-)

yeah, i don't know who started that but the importation of the *.NA
files was only to import the ares's description into the configs...
using the *.NA files to create all of one's file and message areas is
not really a good idea for various reasons... but it has been done and others are copying it :/

My use would be like this: I just started a week or so with setting up my system again after a 10 year break. I signed up to receive files in a couple of
areas, and to get a small filebase to start with, I downloaded a bunch of files
for those area's from someone else's system. Some areas are created in Allfix automatically because files already came in from my uplink, but other areas are
probably a lot more quiet. To create those area's, I wanted to take a part of some .NA file and import in Allfix... and therefor it would be very practical if it created them in Elebbs as well. And it would be pretty easy to implement such a feature because all the code is already there...



Groetjes,
Tom

--- GoldED+/W32-MINGW 1.1.5-b20130111
* Origin: BrainDeath BBS (2:292/8125)