Hello There,

Previously when I didn't have message groups specified in the message
area setup as snngn for the various access settings. I wasn't surprised
that the reader didn't display the areas in the proper groups when being displayed.

But with the last two pre-alpha releases. Even though the message areas
are seperated into groups. In the mail reader all message areas are displayed in all groups. Currently I have local areas set to group #1 with Fsxnet set
to group #2 and Fido set to group #3.The access sttings for a local area
would be:

List ACS | s50g1
Read ACS | s50g1
Post ACS | s50g1
Sysop ACS | s255g1

Fsxnet Areas would be:

List ACS | s50g2
Read ACS | s50g2
Post ACS | s50g2
Sysop ACS | s255g2

Fido Areas would be:
List ACS | s50g3
Read ACS | s50g3
Post ACS | s50g3
Sysop ACS | s255g3

Was something changed that changed the displayed grouping of the message
areas?


Jeff

--- Mystic BBS v1.12 A36 2017/11/09 (Linux/64)
* Origin: The OuijaBoard II (21:1/128.1)

On 11/10/17, JeffS pondered and said...

Previously when I didn't have message groups specified in the message
area setup as snngn for the various access settings. I wasn't surprised that the reader didn't display the areas in the proper groups when being displayed.

Which reader Jeff? Area Index Reader?

Check what you have set in ansimidx.ini in your text directory.

Perhaps you want something like this example?

[snip]

[Options]
; If set to true, area list will use groups to categorize bases
; If set to false, area list will use network address to categorize bases

group_list = true

; When generating by groups, a group can be excluded from the list by
; listing the number here separated by commas (ex exclude_groups=1,7)

;exclude_groups=1

; Sort bases by network and use division separators between network groups

show_divs = true

; Move message bases with new messages at the top of each category list

new_at_top = true

; If there are bases with new messages, automatically move the lightbar to
; highlight them on startup and after reading messages

snap_new = false

; If this is set to true, Mystic will override the users setting to start
; reading messages at the message list/index and go straight to the
message
; reader regardless of their setting.

no_index = false

[snip]

Best, Paul

--- Mystic BBS v1.12 A36 2017/11/09 (Windows/32)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)

Hello Avon,

On 11/10/17, JeffS pondered and said...

Previously when I didn't have message groups specified in the message
area setup as snngn for the various access settings. I wasn't surprised
that the reader didn't display the areas in the proper groups when being
displayed.

Which reader Jeff? Area Index Reader?

I am using the mailreader script. The script executes fine but displays all available message areas in all three message area groups even though each set of message areas is assigned to a different message group.

Check what you have set in ansimidx.ini in your text directory.
Perhaps you want something like this example?
[snip]
[Options]

I will take a look and let ya know. I hadn't made any changes regarding message
areas or message area groups between the release updates.

Jeff

--- BBBS/Li6 v4.10 Toy-3
* Origin: FsxNet: The Ouija Board - bbs.ouijabrd.net (21:1/128)

Was something changed that changed the displayed grouping of the message areas?

Hmm... No, nothing has changed in that area in years. Its working fine here for me, what does your groups configuration look like? Could it be a unix access issue?

--- Mystic BBS v1.12 A36 2017/11/10 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

On 11/11/17, g00r00 said the following...

Was something changed that changed the displayed grouping of the mess areas?

Hmm... No, nothing has changed in that area in years. Its working fine here for me, what does your groups configuration look like? Could it be

The message area setup relating to access and groups is:

Local Areas:
List ACS s50g1
Read ACS s50g1
Post ACS s50g1
Sysop ACS s255g1

Fidonet Areas:
List ACS s50g2
Read ACS s50g2
Post ACS s50g2
Sysop ACS s255g2

Fsxnet Areas:
List ACS s50g3
Read ACS s50g3
Post ACS s50g3
Sysop ACS s255g3

This might be a moot point though. Earlier this evening I
updated to the 11/9 release of A36 and after recompiling
all the scripts and loading the mailreader script the group
arangement looks to be working. During the last two updates
I went through exactly the same process.

Shutdown Mystic (MIS2)
Make backup copy of Mystic
Update all Mystic executables
Recompile all scripts
Reload mystic (MIS2)

Jeff

--- Mystic BBS v1.12 A36 2017/11/09 (Linux/64)
* Origin: The Ouijaboard II (21:1/128.1)

What is the date in the Mystic tagline for?



-Nugax

--- Mystic BBS v1.12 A35 (Linux/64)
* Origin: -=The ByteXchange BBS : bbs.thebytexchange.com=- (21:1/107)

Hello Nugax,

On 11/13/17, Nugax said the following...

What is the date in the Mystic tagline for?

-Nugax

--- Mystic BBS v1.12 A35 (Linux/64)
* Origin: -=The ByteXchange BBS : bbs.thebytexchange.com=- (21:1/107)

It's the release date of that particular Pre-Release Alpha.

Jeff

--- Mystic BBS v1.12 A36 2017/11/09 (Linux/64)
* Origin: The Ouijaboard II (21:1/128.1)