[GH-ISSUE #259] Can CalDavSynchronizer designate calendars as read-only #251

Closed
opened 2026-02-25 20:31:16 +03:00 by kerem · 4 comments
Owner

Originally created by @jmfoleyjr on GitHub (Jul 17, 2019).
Original GitHub issue: https://github.com/aluxnimm/outlookcaldavsynchronizer/issues/259

I have configured CalDavSynchronizer on Window 7 Outlook 2010, and Windows 10 Outlook 365 to access several CalDAV calendars. The issue is that some of those calendars are read-only on the server end. That is, users can read, but not write to the calendar. On the Outlook end, there is no ability to mark a calendar as read-only. So, if a user happens to try and add an event to a CalDAV calendar to which she has no access, it does put the event on the local screen, but generates a CalDavSynchronizer "Synchronization Report" error report.

Is there a way to mark a calendar as read-only so this error can be avoided?

Originally created by @jmfoleyjr on GitHub (Jul 17, 2019). Original GitHub issue: https://github.com/aluxnimm/outlookcaldavsynchronizer/issues/259 I have configured CalDavSynchronizer on Window 7 Outlook 2010, and Windows 10 Outlook 365 to access several CalDAV calendars. The issue is that some of those calendars are read-only on the server end. That is, users can read, but not write to the calendar. On the Outlook end, there is no ability to mark a calendar as read-only. So, if a user happens to try and add an event to a CalDAV calendar to which she has no access, it does put the event on the local screen, but generates a CalDavSynchronizer "Synchronization Report" error report. Is there a way to mark a calendar as read-only so this error can be avoided?
kerem closed this issue 2026-02-25 20:31:16 +03:00
Author
Owner

@aluxnimm commented on GitHub (Jul 17, 2019):

Outlook folders via IMAP or lokal pst files cant be marked read only. But you should just change the sync direction to Outlook <- Server one way then there won't be any sync errors anyway for readonly resources.

<!-- gh-comment-id:512363083 --> @aluxnimm commented on GitHub (Jul 17, 2019): Outlook folders via IMAP or lokal pst files cant be marked read only. But you should just change the sync direction to Outlook <- Server one way then there won't be any sync errors anyway for readonly resources.
Author
Owner

@jmfoleyjr commented on GitHub (Jul 17, 2019):

Thanks - I'll try that now. What is the difference between "Outlook <- Server (Replicate)" and "Outlook <- Server (Merge)"? I don't get it just based on the terms "Replicate" and "Merge". Does "Replicate" clobber any entries made on the local calendar which are not on the Server calendar? If so, that's what I want.

<!-- gh-comment-id:512568245 --> @jmfoleyjr commented on GitHub (Jul 17, 2019): Thanks - I'll try that now. What is the difference between "Outlook <- Server (Replicate)" and "Outlook <- Server (Merge)"? I don't get it just based on the terms "Replicate" and "Merge". Does "Replicate" clobber any entries made on the local calendar which are not on the Server calendar? If so, that's what I want.
Author
Owner

@jmfoleyjr commented on GitHub (Jul 19, 2019):

OK, I've set the calendars I want to be "read-only" to "Outlook <- Server (Replicate)" (assuming that means clobbering any entries on the local calendar which as not on the Server calendar, as mentioned in my previous post). That does seem to have worked to prevent the big, scarey error windows from popping up. Interestingly, I had to actually delete the existing calendars from Outlook and re-add them or the errors kept popping up.

<!-- gh-comment-id:513217328 --> @jmfoleyjr commented on GitHub (Jul 19, 2019): OK, I've set the calendars I want to be "read-only" to "Outlook <- Server (Replicate)" (assuming that means clobbering any entries on the local calendar which as not on the Server calendar, as mentioned in my previous post). That does seem to have worked to prevent the big, scarey error windows from popping up. Interestingly, I had to actually delete the existing calendars from Outlook and re-add them or the errors kept popping up.
Author
Owner

@jmfoleyjr commented on GitHub (Jul 30, 2019):

See ticket https://sourceforge.net/p/outlookcaldavsynchronizer/tickets/1226. This problem is clearly a bug.

<!-- gh-comment-id:516486277 --> @jmfoleyjr commented on GitHub (Jul 30, 2019): See ticket https://sourceforge.net/p/outlookcaldavsynchronizer/tickets/1226. This problem is clearly a bug.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/outlookcaldavsynchronizer#251
No description provided.