[GH-ISSUE #183] CalDav Synchronizer Gmail Exception #646

New issue

Closed

opened 2026-03-01 17:40:38 +03:00 by kerem · 4 comments

kerem commented

2026-03-01 17:40:38 +03:00

Owner

Originally created by @stlfit84 on GitHub (Dec 21, 2016).
Original GitHub issue: https://github.com/aluxnimm/outlookcaldavsynchronizer/issues/183

When synchronizing my Outlook calendar with my Gmail calendar a meeting from Outlook was copied to my Gmail calendar and sent out as an invitation to other participants in the meeting with the organizer being my Gmail address. I want to ensure this does not occur again and would like to root cause what I did to cause it to occur. Any direction you're able to provide is greatly appreciated.

Originally created by @stlfit84 on GitHub (Dec 21, 2016). Original GitHub issue: https://github.com/aluxnimm/outlookcaldavsynchronizer/issues/183 When synchronizing my Outlook calendar with my Gmail calendar a meeting from Outlook was copied to my Gmail calendar and sent out as an invitation to other participants in the meeting with the organizer being my Gmail address. I want to ensure this does not occur again and would like to root cause what I did to cause it to occur. Any direction you're able to provide is greatly appreciated.

kerem closed this issue

2026-03-01 17:40:38 +03:00

kerem commented

2026-03-01 17:40:39 +03:00

Author

Owner

@aluxnimm commented on GitHub (Dec 21, 2016):

and who was the organizer in Outlook? and who are attendees? google doesn't honour the SCHEDULE-AGENT = CLIENT setting abd always sends new meeting invites. you can only disable mapping of organizer and attendees all together in event mapping configuration of the syncprofile to avoid it.

@aluxnimm commented on GitHub (Dec 21, 2016): and who was the organizer in Outlook? and who are attendees? google doesn't honour the SCHEDULE-AGENT = CLIENT setting abd always sends new meeting invites. you can only disable mapping of organizer and attendees all together in event mapping configuration of the syncprofile to avoid it.

kerem commented

2026-03-01 17:40:39 +03:00

Author

Owner

@stlfit84 commented on GitHub (Dec 21, 2016):

The organizer in Outlook was an individual in the company and invitees were
company attendees. I was an attendee in the Outlook entry. My
understanding is, by disabling the mapping, the organizer and attendees
will not populate, rather calendar entry w/ subject and description,
correct?

On Wed, Dec 21, 2016 at 12:17 PM, Alex Nimmervoll notifications@github.com
wrote:

and who was the organizer in Outlook? and who are attendees? google
doesn't honour the SCHEDULE-AGENT = CLIENT setting abd always sends new
meeting invites. you can only disable mapping of organizer and attendees
all together in event mapping configuration of the syncprofile to avoid it.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/aluxnimm/outlookcaldavsynchronizer/issues/183#issuecomment-268599110,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AXjrpHWG91sidlO-sTiXFeBp8qOfujn6ks5rKW0ggaJpZM4LTKyK
.

@stlfit84 commented on GitHub (Dec 21, 2016): The organizer in Outlook was an individual in the company and invitees were company attendees. I was an attendee in the Outlook entry. My understanding is, by disabling the mapping, the organizer and attendees will not populate, rather calendar entry w/ subject and description, correct? On Wed, Dec 21, 2016 at 12:17 PM, Alex Nimmervoll <notifications@github.com> wrote: > and who was the organizer in Outlook? and who are attendees? google > doesn't honour the SCHEDULE-AGENT = CLIENT setting abd always sends new > meeting invites. you can only disable mapping of organizer and attendees > all together in event mapping configuration of the syncprofile to avoid it. > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub > <https://github.com/aluxnimm/outlookcaldavsynchronizer/issues/183#issuecomment-268599110>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/AXjrpHWG91sidlO-sTiXFeBp8qOfujn6ks5rKW0ggaJpZM4LTKyK> > . >

kerem commented

2026-03-01 17:40:39 +03:00

Author

Owner

@aluxnimm commented on GitHub (Dec 21, 2016):

yes everything else will be mapped.

@aluxnimm commented on GitHub (Dec 21, 2016): yes everything else will be mapped.

kerem commented

2026-03-01 17:40:39 +03:00

Author

Owner

@stlfit84 commented on GitHub (Dec 21, 2016):

Thank you!

On Wed, Dec 21, 2016 at 3:01 PM, Alex Nimmervoll notifications@github.com
wrote:

yes everything else will be mapped.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/aluxnimm/outlookcaldavsynchronizer/issues/183#issuecomment-268638542,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AXjrpN-W3J6QdZ0FTxvz3VX2lT0jrjJmks5rKZPDgaJpZM4LTKyK
.

@stlfit84 commented on GitHub (Dec 21, 2016): Thank you! On Wed, Dec 21, 2016 at 3:01 PM, Alex Nimmervoll <notifications@github.com> wrote: > yes everything else will be mapped. > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub > <https://github.com/aluxnimm/outlookcaldavsynchronizer/issues/183#issuecomment-268638542>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/AXjrpN-W3J6QdZ0FTxvz3VX2lT0jrjJmks5rKZPDgaJpZM4LTKyK> > . >