location of storeowner permissions changed?

dneuhaeuser

Was there a change in how storeowner permissions on mailboxes are displayed and set?

For shared mailboxes I had set "additional store owners" before on the "permissions" tab.

After I updated from gromox 3.8.9 to 3.10.51, I noticed that these permissions are not displayed on this tab anymore, but instead on the "folders" tab, the users now have the permissions "storeowner" and "freebusysimple".

So far all seems to work normal, but I'm wondering if this is intended and what is the background?

crpb

yikes...
@Steakie 👋

crpb

The Delegates also look a bit wonky

Now i'm wondering if there was something in there or not, the output with an empty line makes me wonder.

root@gromi:~# grommunio-admin user delegates info@example.tld list
User with delegate permission for 'info@example.tld':

root@gromi:~#

i don't get an empty line if i run the command for a mailbox where i'm sure there was nothing in it.

dneuhaeuser

crpb

The Delegates also look a bit wonky

I also see this on one mailbox...

Steakie

crpb delegates simply read a file on the user store directory. If an empty line is included (for whatever reason) this is the result

WalterH

I can reproduce this behavior on my system._

Steakie

Yes there was a change. We introduced an adaptation in the AAPI because of internal gromox permission bits, which honestly i still do not fully understand (and apparently neither does anyone else besides @jengelh ).
There have been multiple complaints about this bug over the last few days so we'll handle this as priority 1

WalterH

The same problem exists with "Additional store owners". They are no longer shown in the Admin UI.

Steakie

https://github.com/grommunio/admin-api/commit/d8557b380f5b3f449c2b89ae1b3de56564373482

this is the cause of the problem. I do not think that a simple revert is a good solution, since it will reintroduce previous bugs

We also changed
https://github.com/grommunio/admin-api/commit/bb64403184c7d2e5d03dfe2a6e0dc1fc8b2d2f17

Edit: I am honestly lost atp, we need to discuss this internally before breaking it even more

WalterH

Steakie
I see a lot of these messages in log: D-2352: /var/lib/gromox/user/dddddd/uuuuu has an ACE with unrecognized bits! folder=0x9 user=uuuu@dddddd.com perms=0x2000, unknown: 0x2000. Behavior unspecified.
btw. this is a supported edition. Ticket#815936

Steakie

WalterH When did we release supported? We changed this about 2 weeks ago

WalterH

Steakie Supported was released at 28.08.2026 gromox 3.10.51 and the hotfix 3.10.55 was released at 02.09.2026.

dneuhaeuser

Steakie
I am on supported v3.10.51 (released 31.08.2026).

WalterH

dneuhaeuser v3.10.51

There is a hotfix 3.10.55 for EWS.

dneuhaeuser

WalterH There is a hotfix 3.10.55 for EWS.

how do we get this?

it is not in the repo!?

grommunio:~ # zypper ref
Repository 'base' is up to date.
Repository 'grommunio' is up to date.
All repositories have been refreshed.
grommunio:~ # zypper se -s -t package gromox
Loading repository data...
Reading installed packages...

S  | Name                | Type    | Version                   | Arch   | Repository
---+---------------------+---------+---------------------------+--------+-----------
i+ | gromox              | package | 3.10.51.21ea4ab-lp160.7.1 | x86_64 | grommunio
v  | gromox              | package | 2.45-bp160.1.5            | x86_64 | base

WalterH

dneuhaeuser
Sorry my fault, incorrect line.
The correct time line: gromox-3.10.46 at 28.08.2026 and the hotfix gromox-3.10.51 at 31.08.2026.

WalterH

I hope grommunio resolves this issue quickly in both the Community and Supported editions. Untested changes in the Supported Edition are a significant concern.

jengelh

D-xxxx are informational messages showing only when the log_level is set to DEBUG (just developers, and potentially upon instruction). Nothing has yet changed in the way Gromox evaluates the ACEs.

WalterH

https://github.com/grommunio/admin-api/commit/7deb809ed6380b4b1319a63cff9f1ac4775c9c26
This fix will be tomorrow in the community edition.