Have done some more testing and still have issue after:-
- Delete Mac Mail account and re-added - no change
- Opened Cache Mode Outlook profile Grommunio server and let sync complete. Checked logs and could see 3 copies of the following entry on initial connection. No further errors were reported. During session.
Oct 24 11:01:20 Grommunio..doamin.com gromox-http[2377]: W-1566: propid 83cch has no matching namedprop
- Exported full mailbox via Outlook to pst. Created new mailbox and imported pst file. Once synced to Grommunio deleted and recreated Mac Mail profile. No change in behaviour. Issue seems totally linked to Mac Mail connections.
- Change gromox-http log level to 5, can now see message subjects but far too many errors (1000's in a few seconds) to investigate thoroughly.
- Started up test server built from 2026.06.2 appliance ISO last weekend. User data was migrated from live server as part of build using rsync, permissions and ownership set, databases rsync'd across and loaded into test server. No MIME errors in log as only gromox-Web has been connected to it as part of port build testing; ie no 3rd party access - Mac Mail/Outlook.
- Connect user Mac Mail to test server and MIME errors start appearing in gromox-http log almost as soon as sync starts.
- Deleted all email accounts from Mac. Deleted all Mac mail accounts (to reset Mac Mail as close to factory settings as possible without factory reset.
- Created new email account profile in Mac Mail to test server. MIME errors again start almost immediately.
Other email accounts on both live server and test server are working normally and were migrated from previous Grommunio server using same method as used in 4 above. All email was originally migrated from Exchange 2016 at least 3 years ago via pst files and Outlook cached mode - this has always worked without issue before.
No sure now were to go to further the testing.
Did some googling and found the following issue reported on Github.
EWS: MIME export fails for PST-imported EX senders, causing Apple Mail crashes #371
Certainly has the same error number, and follows that emails were imported via pst - so seems likely the cause of the issue. Could not see what I might need to do to fix this - my live server now has well > 100000 log entries in the gromox-http log (journalctl) and worried if left unresolved will run out of disc space (runs in a small VM as don't have huge amounts of email in it).
After some searching in the journalctl found issue actually started on 3rd October 2026, just a few minutes after I applied the following updates, so possibly related to one of the updates below.
`Executed : /usr/sbin/grommunio-update check community
Start : Sat 2026-10-03 12:21:20 BST
Operation : Check
▶ Starting Check (zypper ref && zypper lu --allow-vendor-change).
▶ on repository community.
:.
Repository URL = https://download.grommunio.com/community/openSUSE_Leap_16.0/?ssl_verify=no
\x1b[31mNo correct package manager found.\x1b[0m
Retrieving repository 'grommunio' metadata [..
Looking for gpg keys in repository grommunio.
gpgkey=https://download.grommunio.com/community/openSUSE_Leap_16.0/repodata/repomd.xml.key?ssl_verify=no
....done]
Building repository 'grommunio' cache [....done]
Retrieving repository 'openSUSE-Leap-16.0-Oss' metadata [..
Looking for gpg keys in repository openSUSE-Leap-16.0-Oss.
gpgkey=file:/usr/lib/rpm/gnupg/keys/gpg-pubkey-29b700a4-62b07e22.asc
........................done]
Building repository 'openSUSE-Leap-16.0-Oss' cache [....done]
All repositories have been refreshed.
Loading repository data...
Reading installed packages...
S | Repository | Name | Current Version | Available Version | Arch
---+------------------------+-----------------------+------------------------------------+------------------------------------+-------
v | openSUSE-Leap-16.0-Oss | dracut | 059+suse.730.g73d3411aa-160000.1.1 | 059+suse.732.g39fc900f5-160000.1.1 | x86_64
v | grommunio | grommunio-admin-api | 1.21.23.ma1df53c-lp160.86.1 | 1.21.25.m93a0832-lp160.87.1 | noarch
v | grommunio | grommunio-sync | 2.6.2.947f050-lp160.39.1 | 2.6.10.460e571-lp160.42.1 | noarch
v | grommunio | gromox | 3.11.136.mbab55b6-lp160.35.1 | 3.12.36.me1158f5-lp160.10.1 | x86_64
v | grommunio | gromox-debuginfo | 3.11.136.mbab55b6-lp160.35.1 | 3.12.36.me1158f5-lp160.10.1 | x86_64
v | grommunio | gromox-debugsource | 3.11.136.mbab55b6-lp160.35.1 | 3.12.36.me1158f5-lp160.10.1 | x86_64
v | openSUSE-Leap-16.0-Oss | libIex-3_2-31 | 3.2.2-160000.10.1 | 3.2.2-160000.11.1 | x86_64
v | openSUSE-Leap-16.0-Oss | libIlmThread-3_2-31 | 3.2.2-160000.10.1 | 3.2.2-160000.11.1 | x86_64
v | openSUSE-Leap-16.0-Oss | libOpenEXR-3_2-31 | 3.2.2-160000.10.1 | 3.2.2-160000.11.1 | x86_64
v | openSUSE-Leap-16.0-Oss | libOpenEXRCore-3_2-31 | 3.2.2-160000.10.1 | 3.2.2-160000.11.1 | x86_64
v | grommunio | mapi-header-php | 2.3.5.e43e8a9-lp160.2.1 | 2.3.11.c34f8ec-lp160.4.1 | noarch
v | openSUSE-Leap-16.0-Oss | wget | 1.25.0-160000.3.1 | 1.25.0-160000.4.1 | x86_64
▶ Check completed successfully.
▶ Updating postfix configuration with new maps if exist
▶ Checking for pending service restart or reboot
End Check : Sat 2026-10-03 12:21:28 BST`
Anyone have any ideas how I progress from here. Any help welcome!!