# grommunio: Replace Public Folders with a functional mailbox - step by step

Source: https://forgeone.solutions/en/tech/grommunio-public-folder-functional-mailbox-multiple-domains
Language: en
Published: 2026-09-16
Updated: 2026-11-17

Step-by-step guide with tested folder ACLs, grommunio Web automount, cross-domain permissions, Send-As, alias delivery and Thunderbird GUI evidence.

## Overview

This guide shows, step by step, how to replace a public-folder-style shared structure in grommunio with a functional mailbox. The lab covered two domains in one organization, granular MAPI folder permissions, root and parent folder visibility, automatic mounting in grommunio Web, Send-As, an SMTP alias, and Thunderbird GUI evidence.

The article documents only what was technically tested in the lab. Thunderbird was tested with real GUI screenshots in an isolated X11 environment. Outlook and automatic inbox rules are marked as open until they have been reproduced separately.

## Target setup

The test uses one organization with two domains. A classic public folder in domain A is not automatically a shared organization-wide workspace for users in domain B. For cross-domain shared folders inside one organization, the lab therefore used a normal functional mailbox.

```markdown
Example Group
├── example-a.test
└── example-b.test

shared-folders@example-a.test
├── Finance
├── Sales
├── Projects
│   ├── Project-A
│   └── Project-B
└── Shared
```

## Tested baseline

The guide is based on an isolated grommunio Appliance 2026.06.1. Only neutral test data was used. No production customer data was involved.

```markdown
Organization:        Example Group
Domains:             example-a.test, example-b.test
Users:               alice@example-a.test, bob@example-b.test
Functional mailbox:  shared-folders@example-a.test
SMTP alias:          finance@example-a.test
CLI version:         grommunio-admin 1.21.0+2
Tools:               grommunio-admin, gromox-mbop, jq, xxd, IMAP/SMTP test client, Thunderbird 156.0 for the current native-client acceptance run
```

## Replace the example values for your own PoC

All values below are neutral lab examples. For a customer PoC, replace them with your own test domains, users and functional mailbox. The command structure stays the same; the concrete names and the automatically discovered folder IDs will differ.

```markdown
| Example value | Replace in your own environment with |
| --- | --- |
| example-a.test | first test domain |
| example-b.test | second test domain in the same organization |
| alice@example-a.test | test user from domain A |
| bob@example-b.test | test user from domain B |
| shared-folders@example-a.test | central functional mailbox / shared mailbox |
| finance@example-a.test | optional alias for a functional mail target |
| 0x1d0000, 0x1e0000, 0x210000 | folder IDs discovered with folder find/list in your own environment |
```

## Prerequisites

You need administrative access to grommunio, shell access to the appliance, two domains in the same organization, at least two test users, and a separate functional mailbox. In production-like environments, run the procedure with neutral accounts first.

## Step 1: Verify organization, domains and users

First verify that both domains belong to the same organization and that the test users exist. The lab used Example Group, example-a.test and example-b.test.

```bash
grommunio-admin org list
grommunio-admin domain list
grommunio-admin user list
```

[![grommunio Admin showing the Example Group organization in the shared mailbox test](https://forgeone.solutions/media/grommunio-shared-mailbox-01-organizations.png)](https://forgeone.solutions/media/grommunio-shared-mailbox-01-organizations.png)

The organization must contain both test domains. Otherwise the cross-domain test inside one organization is not meaningful.

[![grommunio Admin showing the test domains example-a.test and example-b.test](https://forgeone.solutions/media/grommunio-shared-mailbox-02-domains.png)](https://forgeone.solutions/media/grommunio-shared-mailbox-02-domains.png)

The domain list shows example-a.test and example-b.test as active domains in the organization.

[![grommunio Admin showing Alice, Bob and the shared mailbox shared-folders@example-a.test](https://forgeone.solutions/media/grommunio-shared-mailbox-03-users.png)](https://forgeone.solutions/media/grommunio-shared-mailbox-03-users.png)

The user list shows Alice in example-a.test, Bob in example-b.test and the functional mailbox shared-folders@example-a.test. The SMTP alias finance@example-a.test belongs to the functional mailbox.

## Step 2: Create the functional mailbox

The functional mailbox is a normal grommunio user mailbox, not a special public-folder type. That gives it its own folder tree, aliases and separate Send-As permissions.

```bash
grommunio-admin user create shared-folders@example-a.test \
  --domain example-a.test \
  --lang en_US \
  --pop3-imap true \
  --smtp true \
  --privWeb true

grommunio-admin passwd --password '<internal-test-password>' \
  shared-folders@example-a.test

grommunio-admin user modify shared-folders@example-a.test \
  --alias finance@example-a.test

grommunio-admin user show shared-folders@example-a.test
```

In the lab, the mailbox existed afterwards, had its own mailbox in example-a.test and listed finance@example-a.test as an alias. The password is intentionally not published.

## Step 3: Create the folder tree

The folders were created with grommunio-admin exmdb in the store of the functional mailbox. The root ID in the lab was 0x9. Folder IDs can differ in other environments and should always be checked with folder list or folder find.

```bash
grommunio-admin exmdb shared-folders@example-a.test folder create Finance 0x9
grommunio-admin exmdb shared-folders@example-a.test folder create Sales 0x9
grommunio-admin exmdb shared-folders@example-a.test folder create Projects 0x9
grommunio-admin exmdb shared-folders@example-a.test folder create Shared 0x9

grommunio-admin exmdb shared-folders@example-a.test folder find Projects 0x9

# Lab example: Projects received ID 0x1f0000.
grommunio-admin exmdb shared-folders@example-a.test folder create Project-A 0x1f0000
grommunio-admin exmdb shared-folders@example-a.test folder create Project-B 0x1f0000

grommunio-admin exmdb shared-folders@example-a.test folder list -r
```

Expected result: Finance, Sales, Projects, Shared, and Project-A and Project-B below Projects appear in the recursive folder listing.

## Step 4: Set folder visibility and working permissions

foldervisible is the path permission through the hierarchy. It makes a folder visible in the tree, but it does not by itself grant read or write access to other folders. For nested target folders, the root and all parent folders must be visible.

```bash
# Make the root visible without granting content access on root.
grommunio-admin exmdb shared-folders@example-a.test folder grant \
  0x9 alice@example-a.test foldervisible

grommunio-admin exmdb shared-folders@example-a.test folder grant \
  0x9 bob@example-b.test foldervisible

# Alice may work in Finance.
grommunio-admin exmdb shared-folders@example-a.test folder grant \
  0x1d0000 alice@example-a.test \
  readany create editowned deleteowned editany deleteany createsubfolder folderowner foldercontact foldervisible

# Bob may work in Sales.
grommunio-admin exmdb shared-folders@example-a.test folder grant \
  0x1e0000 bob@example-b.test \
  readany create editowned deleteowned editany deleteany createsubfolder folderowner foldercontact foldervisible

# Bob may see the Projects parent folder.
grommunio-admin exmdb shared-folders@example-a.test folder grant \
  0x1f0000 bob@example-b.test foldervisible

# Bob may work in Project-A, but not Project-B.
grommunio-admin exmdb shared-folders@example-a.test folder grant \
  0x210000 bob@example-b.test \
  readany create editowned deleteowned editany deleteany foldervisible
```

No StoreOwner or blanket delegate rights were granted in the lab. The design deliberately keeps the permissions limited to folder ACLs.

## Step 5: Verify permissions

After setting permissions, the root, Finance, Sales, Projects, Project-A and Project-B were checked separately. The negative tests matter: users must see the expected folders, but folders without permission must remain inaccessible.

```bash
grommunio-admin exmdb shared-folders@example-a.test folder permissions 0x9
grommunio-admin exmdb shared-folders@example-a.test folder permissions 0x1d0000
grommunio-admin exmdb shared-folders@example-a.test folder permissions 0x1e0000
grommunio-admin exmdb shared-folders@example-a.test folder permissions 0x1f0000
grommunio-admin exmdb shared-folders@example-a.test folder permissions 0x210000
grommunio-admin exmdb shared-folders@example-a.test folder permissions 0x220000

grommunio-admin user storeowner shared-folders@example-a.test list
grommunio-admin user delegates shared-folders@example-a.test list
```

```markdown
Lab result:
Alice -> Finance: permission set, PASS
Alice -> Sales: no permission set, PASS
Bob -> Sales: permission set, PASS
Bob -> Finance: no permission set, PASS
Bob -> Projects: foldervisible only, PASS
Bob -> Project-A: permission set, PASS via CLI
Bob -> Project-B: no permission set, PASS
StoreOwner/Delegate: no blanket rights, PASS
```

## Step 6: Mount the shared store in grommunio Web

grommunio Web does not automatically show another mailbox in the left folder tree just because folder ACLs exist. For the web client, the functional mailbox was therefore written into each user’s web settings as a shared\_stores entry. In grommunio Web 5 this entry belongs under the grommunio namespace; older or migrated profiles may still contain zarafa entries.

USER\_A is the user who should see the store. USER\_B is the functional mailbox. The shared mailbox address is hex-encoded because grommunio Web stores the shared-store key in that form.

```bash
USER_A="alice@example-a.test"
USER_B="shared-folders@example-a.test"

ID=$(printf '%s' "$USER_B" | xxd -p -c 256)
SETTINGS=$(gromox-mbop -u "$USER_A" get-websettings)

UPDATED=$(printf '%s' "$SETTINGS" | jq --arg id "$ID" '
  .settings //= {}
  | .settings.grommunio //= {}
  | .settings.grommunio.v1 //= {}
  | .settings.grommunio.v1.contexts //= {}
  | .settings.grommunio.v1.contexts.hierarchy //= {}
  | .settings.grommunio.v1.contexts.hierarchy.shared_stores =
    (if (.settings.grommunio.v1.contexts.hierarchy.shared_stores | type) == "object"
     then .settings.grommunio.v1.contexts.hierarchy.shared_stores
     else {}
     end)
  | .settings.grommunio.v1.contexts.hierarchy.shared_stores[$id] = {
      "all": {
        "folder_type": "all",
        "show_subfolders": true
      }
    }
')

printf '%s' "$UPDATED" | gromox-mbop -u "$USER_A" set-websettings
```

The tested script variant preserves existing settings, initializes missing hierarchy objects and is idempotent. In the lab it was run twice for Alice and Bob without creating duplicates.

## Step 7: Test grommunio Web

After the websettings entry, the user must log out and back in. The check must verify not only that the functional mailbox is visible, but also that each user sees only the intended folders.

[![grommunio Web showing Alice with the mounted shared mailbox and Finance folder](https://forgeone.solutions/media/grommunio-shared-mailbox-04-alice-web-en.png)](https://forgeone.solutions/media/grommunio-shared-mailbox-04-alice-web-en.png)

Alice from example-a.test sees the mounted functional mailbox shared-folders@example-a.test and the permitted Finance folder. Sales is not granted to Alice.

[![grommunio Web showing Bob with the mounted shared mailbox and allowed folders](https://forgeone.solutions/media/grommunio-shared-mailbox-05-bob-web-en.png)](https://forgeone.solutions/media/grommunio-shared-mailbox-05-bob-web-en.png)

Bob from example-b.test sees the same shared mailbox, but with Bob-specific visibility for Sales and Projects. Finance remains hidden for Bob.

[![grommunio Web showing Bob with the shared mailbox folder tree in the cross-domain lab](https://forgeone.solutions/media/grommunio-shared-mailbox-06-bob-projects-check-en.png)](https://forgeone.solutions/media/grommunio-shared-mailbox-06-bob-projects-check-en.png)

The Project-A ACL is proven through the CLI. In the headless web run, expanding the nested Project-A branch was not counted as a visible web PASS because the tree expansion was not reproducible enough. This detail therefore remains explicitly limited.

## Step 8: Set Send-As separately from folder permissions

Folder ACLs and Send-As are separate controls. Alice can read or work in a folder without automatically being allowed to send as shared-folders@example-a.test. Send-As was therefore granted and tested separately via SMTP.

```bash
grommunio-admin user sendas shared-folders@example-a.test add alice@example-a.test
grommunio-admin user sendas shared-folders@example-a.test list
```

The mail-flow test from Alice with From: shared-folders@example-a.test to Bob succeeded. Send-As is therefore proven for the tested internal path.

## Step 9: Check the SMTP alias

The alias finance@example-a.test was assigned to the functional mailbox. Mail sent to that alias arrived in the shared mailbox in the lab. The alias itself is therefore verified.

```bash
grommunio-admin user modify shared-folders@example-a.test \
  --alias finance@example-a.test

grommunio-admin user show shared-folders@example-a.test
```

A server-side rule that automatically moves mail for finance@example-a.test into Finance was not counted as PASS in this run. Alias delivery is confirmed; the inbox rule configuration remains open.

## Step 10: Classify the current Thunderbird acceptance

The original screenshot sequence in this article came from an older Thunderbird lab. The published version now uses the current native-client acceptance evidence with Thunderbird 156.0 instead. This keeps the article visually current and separates grommunio Web/server evidence from native-client evidence.

[![Thunderbird with a grommunio IMAP account after upgrading to grommunio 2026.06.2](https://forgeone.solutions/media/06-thunderbird-156-current-inbox.png)](https://forgeone.solutions/media/06-thunderbird-156-current-inbox.png)

The current Thunderbird test proves the practical IMAP client path with a fresh profile, login and synchronized inbox. For functional mailboxes, keep the distinction clear: a separately configured IMAP account is not the same operating model as a delegated Exchange/MAPI shared mailbox. A successful IMAP acceptance must not be read as a full EWS/Outlook approval.

```markdown
Thunderbird 156.0 with a fresh profile: PASS
IMAP login and inbox synchronization: PASS
SMTP/IMAP baseline after the upgrade: PASS
Functional mailbox as a separate IMAP account: validate in production using the same pattern
Delegated EWS shared mailbox in Thunderbird: validate separately, do not infer it from IMAP
Outlook on Windows: separate client test required
```

For classic Outlook or EWS scenarios, keep a production-like validation path: open the account, add the additional mailbox, restart the client, verify the folder tree and permissions, test Send-As and document the result separately from IMAP.

## Public folder vs functional mailbox

The public-folder test showed separate public-folder stores per domain. example-a.test contained Example-A-Public, while example-b.test had its own empty public-folder store. Cross-domain ACLs can be set through the CLI, but that does not replace a full client-side proof for organization-wide public-folder usage.

```markdown
Public folder:
- domain-bound public-folder store
- client behavior must be checked per domain
- not automatically proven as an organization-wide shared workspace across domains

Functional mailbox:
- normal mailbox with its own folder tree
- cross-domain folder ACLs inside the same organization tested
- visible in grommunio Web through websettings automount
- Send-As and SMTP aliases controlled separately
```

## Troubleshooting

**Shared store does not appear in grommunio Web: **Check websettings, log the user out and back in, and verify that shared\_stores is an object.

```bash
gromox-mbop -u alice@example-a.test get-websettings | \
  jq '.settings.grommunio.v1.contexts.hierarchy.shared_stores'
```

**User cannot see subfolders: **Check root foldervisible, all parent folders and the target folder ACL. foldervisible on Projects does not grant content access to Project-A.

**User sees too much: **Check default rights, anonymous rights, group memberships, recursive grants and accidental StoreOwner or delegate rights.

**Send-As fails: **Check Send-As separately, select the sender address again in the client and restart the session after permission changes.

## Checklist for your own PoC

The server-side PoC is meaningful only when the permitted access paths work and the intentionally denied access paths have been checked as well. This checklist can be used directly as an acceptance record.

```markdown
- [ ] Both test domains belong to the same grommunio organization.
- [ ] A central functional mailbox was created.
- [ ] The required folder tree was created.
- [ ] User A belongs to domain A.
- [ ] User B belongs to domain B.
- [ ] Root and parent folders only have the required visibility.
- [ ] Target folders have the intended folder ACL.
- [ ] User A can open the permitted folder.
- [ ] User A cannot open a non-permitted folder.
- [ ] User B can open the permitted folder across domains.
- [ ] User B cannot open a non-permitted folder.
- [ ] The functional mailbox appears in grommunio Web.
- [ ] Existing web settings were not overwritten by the automount.
- [ ] Send-As was granted and tested separately, if required.
- [ ] Client paths that were not fully tested are marked separately.
```

## PASS/FAIL criteria for customer acceptance

PASS in this article means that the specific step was practically executed and the expected result was visible or proven through the CLI. FAIL means that the step was executed but the expected result did not appear, or a user saw more or less than intended. NOT TESTED means that the point was not fully verified in this run and must not be treated as passed.

```markdown
| Area | PASS when ... | FAIL when ... |
| --- | --- | --- |
| Organization and domains | both domains belong to the same organization | domains are missing or belong to different organizations |
| Folder tree | all target folders exist in the functional mailbox | folders are missing or created below the wrong parent |
| Folder ACL | permitted users can open their target folders | permitted users cannot access their target folders |
| Negative test | non-permitted folders stay hidden or unusable | users can see or open foreign folders |
| Folder visible | root and parent paths are visible without exposing content | parent paths are missing or too much content is visible |
| Automount | the shared store is visible in grommunio Web | the store does not appear after a fresh login |
| Websettings | existing settings are preserved | existing web settings are overwritten |
| Send-As | sending with the intended sender works | folder ACLs are incorrectly treated as Send-As replacement |
```

## Result check

The following result check separates confirmed lab results from open client tests. PASS means that the item was practically executed in this test environment.

```markdown
Area                                Check                                        Result
Shared mailbox                      Folder tree created                          PASS
ACL                                 Cross-domain user permission                 PASS
ACL                                 Root/parent foldervisible set                PASS
ACL                                 Non-permitted folders remain inaccessible    PASS
grommunio Web                       Automount visible for Alice and Bob          PASS
Script                              Idempotency and empty websettings            PASS
Mail flow                           Send-As                                      PASS
Mail flow                           SMTP alias delivery                          PASS
Public folder                       Domain store comparison                      PASS WITH CONDITIONS
Thunderbird 156.0                  Fresh IMAP profile and inbox sync            PASS
Thunderbird 156.0                  Current IMAP GUI screenshot                  PASS
EWS/Outlook                         Validate separately in production            NOT TESTED
EWS/Outlook                         Do not infer from IMAP success               NOT TESTED
EWS/Outlook                         Validate delegated shared mailbox separately NOT TESTED
Outlook                             Manual mounting                              NOT TESTED
Inbox rule                          Move alias mail to Finance automatically     NOT TESTED
```

## What will be added later

The architecture, cross-domain folder ACLs, foldervisible, grommunio Web automount, Send-As, alias delivery and Thunderbird as a separate IMAP account are practically tested. The full Outlook test on Windows, the full Thunderbird EWS delegated path and the final inbox-rule test remain open.

## Conclusion

For shared folders across multiple domains inside one grommunio organization, a functional mailbox is a clear and testable approach. The key is to avoid blanket Full Access permissions and to treat root and parent visibility, target folder permissions, Send-As and aliases as separate controls.

## Hero image

[![grommunio Web showing Alice with the mounted shared mailbox and Finance folder](https://forgeone.solutions/media/grommunio-shared-mailbox-04-alice-web-en.png)](https://forgeone.solutions/media/grommunio-shared-mailbox-04-alice-web-en.png)

## Author

Mathias Rumbold

## Category

- [grommunio & Groupware](https://forgeone.solutions/en/tech/grommunio-public-folder-functional-mailbox-multiple-domains?category=grommunio-groupware)

## Tags

- [Native Exchange Replacement](https://forgeone.solutions/en/tech/grommunio-public-folder-functional-mailbox-multiple-domains?tags=native-exchange-replacement)
- [Collaboration](https://forgeone.solutions/en/tech/grommunio-public-folder-functional-mailbox-multiple-domains?tags=collaboration)
- [Exchange alternative](https://forgeone.solutions/en/tech/grommunio-public-folder-functional-mailbox-multiple-domains?tags=exchange-alternative)
- [Microsoft Exchange](https://forgeone.solutions/en/tech/grommunio-public-folder-functional-mailbox-multiple-domains?tags=microsoft-exchange)
- [Groupware](https://forgeone.solutions/en/tech/grommunio-public-folder-functional-mailbox-multiple-domains?tags=groupware)
- [grommunio](https://forgeone.solutions/en/tech/grommunio-public-folder-functional-mailbox-multiple-domains?tags=grommunio)
- [Keycloak](https://forgeone.solutions/en/tech/grommunio-public-folder-functional-mailbox-multiple-domains?tags=keycloak)
- [SSO](https://forgeone.solutions/en/tech/grommunio-public-folder-functional-mailbox-multiple-domains?tags=sso)
- [MFA](https://forgeone.solutions/en/tech/grommunio-public-folder-functional-mailbox-multiple-domains?tags=mfa)
- [Enterprise Linux](https://forgeone.solutions/en/tech/grommunio-public-folder-functional-mailbox-multiple-domains?tags=enterprise-linux)
- [Upgrade](https://forgeone.solutions/en/tech/grommunio-public-folder-functional-mailbox-multiple-domains?tags=upgrade)

## Plan grommunio shared storage cleanly

ForgeOne helps with public-folder replacement, functional mailboxes, migration, permission design, grommunio Web, Outlook testing and ongoing operations.

[Discuss a grommunio project](https://forgeone.solutions/en/contact)

## grommunio 2026 Schritt für Schritt

Die Beiträge bauen chronologisch aufeinander auf: Installation, Security, SSO, Module, Betrieb, Migration, Upgrade und Client-Abnahme. Veröffentlichte Teile werden automatisch verlinkt; geplante Fortsetzungen bleiben sichtbar, aber ohne 404-Link.

1. [Install grommunio 2026.06.1: From ISO to Working Groupware](https://forgeone.solutions/en/tech/install-grommunio-2026)
2. [grommunio-antispam with Rspamd: Spam Filtering, Learning and Operations Step by Step](https://forgeone.solutions/en/tech/grommunio-antispam-rspamd-2026-step-by-step)
3. [grommunio-auth with Keycloak: SSO and central login step by step](https://forgeone.solutions/en/tech/grommunio-auth-keycloak-2026-step-by-step)
4. [Set up grommunio Meet 2026 without Keycloak and optionally add SSO](https://forgeone.solutions/en/tech/grommunio-meet-2026-step-by-step)
5. [Set Up grommunio Chat 2026: Teams, Channels, Users and Multi-Tenancy Testing](https://forgeone.solutions/en/tech/grommunio-chat-2026-step-by-step)
6. [Set Up grommunio Files and Office: Validate Files, Web Entry and Online Office](https://forgeone.solutions/en/tech/grommunio-files-office-2026-step-by-step)
7. [Set Up grommunio Archive 2026: Archive, Search and Restore Email](https://forgeone.solutions/en/tech/grommunio-archive-2026-step-by-step)
8. [grommunio MDM 2026 step by step: manage ActiveSync devices safely](https://forgeone.solutions/en/tech/grommunio-mdm-2026-step-by-step)
9. [grommunio Multitenancy 2026: organizations, domains and multiple LDAP sources](https://forgeone.solutions/en/tech/grommunio-multitenancy-2026-step-by-step)
10. [grommunio 2026 Cluster and High Availability: from multi-server lab to tested active/standby homeserver](https://forgeone.solutions/en/tech/grommunio-cluster-ha-2026-step-by-step)
11. [grommunio 2026 disaster recovery and single mailbox restore: backup, full DR and targeted mailbox recovery in the lab](https://forgeone.solutions/en/tech/grommunio-disaster-recovery-single-mailbox-restore-2026-step-by-step)
12. [Migrate IMAP mailboxes to grommunio with imapsync](https://forgeone.solutions/en/tech/grommunio-imap-migration-imapsync-2026-step-by-step)
13. [grommunio: Replace Public Folders with a functional mailbox - step by step (current part)](https://forgeone.solutions/en/tech/grommunio-public-folder-functional-mailbox-multiple-domains)
14. [grommunio Web 5.0 in the lab: settings namespace, shared mailboxes and admin impact](https://forgeone.solutions/en/tech/grommunio-web-5-0-in-the-lab)
15. [grommunio 2026.06.2 Upgrade and Technical Acceptance: Keycloak SSO, MFA, AutoDiscover and Mail Flow](https://forgeone.solutions/en/tech/grommunio-2026-06-2-upgrade-keycloak-sso-practice)
16. [grommunio native clients after Keycloak SSO: Thunderbird, Outlook, EWS, EAS and MFA explained](https://forgeone.solutions/en/tech/grommunio-native-clients-after-keycloak-sso)
17. grommunio Monitoring und Alerting im Betrieb
18. grommunio Security Hardening in der Praxis
19. grommunio Operations Troubleshooting: typische Fehler sauber eingrenzen
