I recently switched from a temporary node to an assigned. I didn't edit my mailin.ini file prior to polling the new hub and several message areas now
show in each message group.

Is there a fix for this?

Thanks much

Mike Dippel

--- Mystic BBS v1.12 A46 2020/08/26 (Windows/64)
* Origin: Mystic Hobbies BBS (21:1/999)

On 21 Dec 2021 at 11:19p, Mike Dippel pondered and said...

I recently switched from a temporary node to an assigned. I didn't edit my mailin.ini file prior to polling the new hub and several message
areas now show in each message group.

Is there a fix for this?

Not quite sure what you mean by this, so you are seeing say messages posted in FSX_GEN showing up under two message groups or is it message bases?

--- Mystic BBS v1.12 A47 2021/11/06 (Linux/64)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

Any new conferences automatically added themselves to EVERY message group. To solve this, I deleted the new ones, edited my mailin.ini to reflect the
change of HUB IP and now anything new goes to the proper conference group.

It seems that every time I have a problem and post it, I immediately find the solution on my own, so all is well now!

Mike Dippel

--- Mystic BBS v1.12 A46 2020/08/26 (Windows/64)
* Origin: Mystic Hobbies BBS (21:1/999)

Any new conferences automatically added themselves to EVERY message
group. To solve this, I deleted the new ones, edited my mailin.ini to reflect the change of HUB IP and now anything new goes to the proper conference group.

Do you mean any new message bases add themselves to every message conference? Are you setting access to reflect which conference its in?

Like on 2o,

conference 1 = Local Messages
conference 2 = fsxNet

So in my local message bases the acs is:
s10g1
s20g1
etc.

fsxNet is:
s20g2
s20g2
etc.

Sorry if this isn't what you mean, but a lot of sysops jank this up and their bases show up in every conference. You must get the GROUP access... group=conference.

Sidenote; for file areas you use 'z', like:
s20z1

or

s20z2



|07p|15AULIE|1142|07o
|08.........

--- Mystic BBS v1.12 A47 2021/10/25 (Raspberry Pi/32)
* Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (21:2/150)

I fixed it by deleting the few new ones that were improperly assigned,
knowing that eventually they would auto create the area again once new
messages came in. I also edited my mailin.ini to reflect the change of the
new HUB that was assigned to me.

All appears to be working now.

Mike Dippel

--- Mystic BBS v1.12 A46 2020/08/26 (Windows/64)
* Origin: Mystic Hobbies BBS (21:1/999)

On 22 Dec 2021, Mike Dippel said the following...

I fixed it by deleting the few new ones that were improperly assigned, knowing that eventually they would auto create the area again once new messages came in. I also edited my mailin.ini to reflect the change of the new HUB that was assigned to me.

It actually wasn't corrupt, when new message bases come in they create the base in ALL groups. You then just go in and edit the access section and assign them to a group. (ex: s20g10, for access 20 Group 10), when they come in they will be most likely just s255.. Next time you see that, go into each echo and check the access section.. :)

Al

... Confucius say: "Man who runs behind car gets exhausted"

--- Mystic BBS v1.12 A47 2021/11/18 (Windows/32)
* Origin: The Wrong Number Family Of BBS' - Wrong Number ][ (21:4/131)

On 22 Dec 2021 at 08:51a, Mike Dippel pondered and said...

Any new conferences automatically added themselves to EVERY message
group. To solve this, I deleted the new ones, edited my mailin.ini to reflect the change of HUB IP and now anything new goes to the proper conference group.

It seems that every time I have a problem and post it, I immediately
find the solution on my own, so all is well now!

Yep as others have mentioned it's not a case of having to delete the bases, rather change the ACS settings and all will be well using the g ACS codes :)

--- Mystic BBS v1.12 A47 2021/11/06 (Linux/64)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

On 22 Dec 2021, Mike Dippel said the following...
On 22 Dec 2021, Mike Dippel said the following...

I fixed it by deleting the few new ones that were improperly

assigned,

knowing that eventually they would auto create the area again

once new

It actually wasn't corrupt, when new message bases come in they create
the base in ALL groups. You then just go in and edit the access
section and assign them to a group. (ex: s20g10, for access 20 Group

I have a similier ongoing issue here but with the filebases. Although I
have "auto-make" setup, areas are never auto-made. I have to manually
make them. I can also never get the system to toss files down to my
point. It just won't work, and I've never been able to figure out what's
wrong.



Mickey - Mick Manning
Test Driving the new Talisman Model 35
-------------------------


--- Talisman v0.35-dev (Windows/x64)
* Origin: Trent Hills Retribution - centralontarioremote.com:2300 / ssh:2222 (21:1/156.1)

On 24 Dec 2021, Mickey said the following...

I have a similier ongoing issue here but with the filebases. Although I have "auto-make" setup, areas are never auto-made. I have to manually
make them. I can also never get the system to toss files down to my
point. It just won't work, and I've never been able to figure out what's wrong.

It's actually the same thing, except instead of using s20g15 you would use s20z15 or whatever the group is. When bases or file areas come in the just auto create the base and set the access levels to whatever you have in mutil.ini.. As for tossing to a point system, I haven't set my points up to take files yet. Guess I should test that and setup the filebases... Something else to do.. LOL

... What hair color do they put on the driver's licenses of bald men?

--- Mystic BBS v1.12 A47 2021/11/18 (Windows/32)
* Origin: The Wrong Number Family Of BBS' - Wrong Number ][ (21:4/131)