Hello Michael!

05 Oct 20, Michael Pierce wrote to Kai Richter:

 MP> mystic A47 now has an export areas.bbs function.. but no import
 MP> function as of yet?

If you say so i would say yes. That's a state of mind problem of BBS concept.
The majority of BBS sysop think of "my" BBS, "my" users, "my" content.

The basic function of the areas.bbs file is to provide an interface to an
external mail editor. Control of mail transport (if any) is still part of the
BBS.

 KR>> Be careful with the migration. There should be only one point in
 KR>> control of the areas. When created export the fidoconf to
 KR>> areas.bbs and import that one to mystic.
 MP> yes.. thats the plan not sure how it will work.

This would degrade the BBS to a mail reading tool. If that isn't part of the
design you wouldn't have success.

 MP> would be wonderful if both hpt and mystic would develop an import
 MP> function

Hm, i haven't tried it for myself, but why not use the autoareacreate function
for that? You could query your uplinks areafix for your connected echos and
then send this list back as +ECHO list. The areafix of hpt will put and setup
the "new" linked echos into the autoareacreate location.

You will have to do some manual configuration, link definition with passwords
for example. I hope that there will be never an export function for the full
configuration because i think an export of passwords is a security risk in
general and have to be avoided.

Regards

Kai

--- GoldED+/LNX 1.1.4.7