[GH-ISSUE #454] Common Name (CN) Tag removed from ORGANIZER #436

New issue

Open

opened 2026-02-25 20:31:37 +03:00 by kerem · 0 comments

kerem commented

2026-02-25 20:31:37 +03:00

Owner

Originally created by @mceurytos on GitHub (Jul 8, 2025).
Original GitHub issue: https://github.com/aluxnimm/outlookcaldavsynchronizer/issues/454

When an event is created in Outlook, the ORGANIZER field is formatted with a CN (Common Name) value:

ORGANIZER;CN="First Last":mailto:first.last@gmail.com

However, when Google Calendar returns this event via CalDAV, it omits the CN attribute, responding with:

ORGANIZER:mailto:first.last@gmail.com

This change causes Outlook (via CalDavSynchronizer) to no longer recognize the user as the event organizer. As a result the event becomes read-only in Outlook.

CalDavSynchronizer shall have an option to force CN tag for inbound updates from server (i.e. Google Calendar)

Originally created by @mceurytos on GitHub (Jul 8, 2025). Original GitHub issue: https://github.com/aluxnimm/outlookcaldavsynchronizer/issues/454 When an event is created in Outlook, the ORGANIZER field is formatted with a CN (Common Name) value: `ORGANIZER;CN="First Last":mailto:first.last@gmail.com` However, when Google Calendar returns this event via CalDAV, it omits the CN attribute, responding with: `ORGANIZER:mailto:first.last@gmail.com` This change causes Outlook (via CalDavSynchronizer) to no longer recognize the user as the event organizer. As a result the event becomes read-only in Outlook. CalDavSynchronizer shall have an option to force CN tag for inbound updates from server (i.e. Google Calendar)