EWS URI errors in gromox http

AndrewFNelson

I am migrating (or trying to) off of Exchange 2016 to the latest Grommunio. Everything has gone smoothly except Calendars and specifically with Outlook for Mac over EWS. iPhones, iPads, Windows Outlook and Mac native tools seems to all work fine. IMAP and Calendaring with Thunderbird works fine too. The mailboxes were moved with Exchange Migrator from Recovery Tools (https://www.recoverytools.com/exchange-server/migrator/). No issues there and the content seems to all be there.

My problem (I believe) is specifically with EWS and Outlook on Mac (16.98.1). More specifically it is only with Calendar entries and not email, tasks, or reminders. I am seeing a bunch of errors in the gromox http logs complaining about URIs that are missing and they do look like Calendaring like headers. Here are a couple examples:

2025-07-11 16:14:30.386301]: ews: unknown field URI 'calendar:StartTimeZone' (ignored)
[2025-07-11 16:14:30.386423]: ews: unknown field URI 'calendar:EndTimeZone' (ignored)
[2025-07-11 16:14:30.386524]: ews: unknown field URI 'calendar:ModifiedOccurrences' (ignored)
[2025-07-11 16:14:31.839896]: ews: unknown field URI 'calendar:OriginalStart' (ignored)
[2025-07-11 16:14:31.840786]: ews: unknown field URI 'calendar:StartTimeZone' (ignored)
[2025-07-11 16:14:31.840958]: ews: unknown field URI 'calendar:EndTimeZone' (ignored)
[2025-07-11 16:14:31.841081]: ews: unknown field URI 'calendar:ModifiedOccurrences' (ignored)

This seems to be my only issue with migrating of Exchange, but is a bit of a deal breaker as I have a fair amount of Mac's running Outlook.

crpb

AndrewFNelson The mailboxes were moved with Exchange Migrator from Recovery Tools

You know about exchange2grommunio.ps1 ?

And fwiw, i currently have PR on that script as i ran into some issues https://github.com/grommunio/gromox/pull/143

WalterH

AndrewFNelson I have customers that uses MAC. MAC mail works well with EWS. Unfortunately I also see similar messages in journalctl -f, but we simply ignore this messages as MAC mail works.

AndrewFNelson

Thanks. I will check it out. I am not sure the issue is with migrating the data as Webmail, IMAP, and EAS/ActiveSync clients work just fine. EWS just seems not quite ready for prime time - or mainly just the calendaring. Everything else seems to work well (email, tasks, reminders). I just need to figure out this Outlook for Mac and Calendar problem and then I am home free.

AndrewFNelson

WalterH The native Mac Mail and Calendar works fine. My issues are with Outlook for Mac - are they using the O365 client?. That won't sync to the calendars and generates errors on both sides.

WalterH

If you talk about the "New" Outlook, this is not supported.

AndrewFNelson

WalterH That is what I am discovering the hard way - thanks for the confirmation. Not supporting Outlook (any current version) is pretty limiting for any mail server suite.

AndrewFNelson

I tried the gromox-e2ghelper process as well - just on the calendar. That moves the calendar entries over and the outlook client on Mac sees them and syncs, but anything with a reference to another AD user gets stuck. Reminders pop up and cannot be dismissed. The Organizer fields and the Attendees don't come across with email addresses, just long OU=...../User syntax. If you delete those calendar entries (through webmail), then outlook unsticks itself. Not an ideal process either.

WalterH

AndrewFNelson any current version)

Only the "new" Outlook is not supported; the traditional version works. I have customers who use Outlook for Mac and Mac Mail.

CarolineKiel

Unfortunately, we have the exact same issue here.
Just migrated over from Exchange 2019 and have issues with the X500 addresses used before in Exchange (I know, no one likes X500, but I've not programmed Exchange, so don't blame me):
Every calendar item with "internal" sender or recipient (same Exchange Org) is listed with the X500 address, which can't be interpreted by Grommunio and as of such can't be modified (accepted). So they permanently pop up as a reminder without having a chance to dismiss them.
The same is true of mails that were received from within the Exchange org: since the sender (and probably also other recipients) are listed as X500, you cannot reply to those mails.
All this is only true from Outlook (for Mac), not for the Web GUI.

Nevertheless, we neeed a way to "repair" those objects and replace the X500 adresses with SMTP addresses.

And by the way: I can't think of a way to migrate from any current Exchange to Grommunio without having this issue, or am I overseeing something?

WalterH

I did some Exchange migrations but I see X500 addresses only once in a very old mailbox, most mailboxes used the smtp addressing schema. How you did the migration?

Krefti

Hello everybody,
I've found this post during searching for the exact same situation here in my homelab. We're using Mac OS with Outlook Classic and observing the same situation with meeting requests that are not reliable usable in terms of organizing, canceling or accepting. I've observed also that outlook shows e-mails to internal recipients seems to be send two times to the same recipient. One of the entries were shown as invalid e-mail adress. The second one is ok. Both entries are identical and are not from an addressbook (manual entered during editing the e-mail).
Are there any news about this behaviour?
Thanks.