Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion USER_GUIDE.md
Original file line number Diff line number Diff line change
Expand Up @@ -32,7 +32,7 @@ Those commands are made mostly for making `plann` more convenient to use for the
* agenda - list up some of the upcoming events plus some of the upcoming tasks
* interactive manage-tasks - go through your tasks and make suggestions

Note that many of those commands have only been tested on DAViCal (see the [`docs/CALENDAR_SERVER_RECOMMENDATIONS.md`](docs/CALENDAR_SERVER_RECOMMENDATIONS.md) file)
Note that those commands are mostly tested against Xandikos (which plann's functional tests run on) and earlier DAViCal (see the [`docs/CALENDAR_SERVER_RECOMMENDATIONS.md`](docs/CALENDAR_SERVER_RECOMMENDATIONS.md) file).


## Global options
Expand Down
56 changes: 32 additions & 24 deletions docs/CALENDAR_SERVER_RECOMMENDATIONS.md
Original file line number Diff line number Diff line change
@@ -1,14 +1,14 @@
# What CalDAV-server to choose?

Most caldav clients out there syncs the calendar locally and operates on the local copy. Plann is thin client. Some features in plann is dependent on the server having good CalDAV support. Unfortunately the server supporting everything perfectly simply does not exist as of 2026. At least not as far as I'm aware.
Most caldav clients out there sync the calendar locally and operate on the local copy. Plann is a thin client. Some features in plann are dependent on the server having good CalDAV support. Unfortunately the server supporting everything perfectly simply does not exist as of 2026. At least not as far as I'm aware.

## TLDR-summary

**Xandikos** and **Radicale** are python-based calendaring servers designed for single-user setups. They are easy to set up and get started with, and they are also actively developed. I'd go with Xandikos, but YMMV.
**Xandikos** and **Radicale** are python-based calendaring servers for small, typically single-user setups. They are easy to set up and get started with, and they are also actively developed. I'd go with Xandikos, but YMMV.

**DAViCal** and **Cyrus** are solid choices if you need multi-user support and scheduling. DAViCal has been the developer's personal choice (as Xandikos was not quite ready some years ago — will try out Xandikos soon). Cyrus is a full IMAP+CalDAV server with good scheduling support and only minor CalDAV quirks.
**DAViCal** and **Cyrus** are solid choices if you need multi-user support and scheduling. The author used DAViCal for many years and has since moved to Xandikos. Cyrus is a full IMAP+CalDAV server with good scheduling support and only minor CalDAV quirks.

For Cloud/SaaS, there is no obvious winner — all tested providers have significant limitations for heavy plann use. GMX and Purelymail may be worth checking out. I have no idea about Google - it hasn't been tested for ages, it should probably be checked out. iCloud should be avoided.
For Cloud/SaaS, there is no obvious winner — most tested providers have significant limitations for heavy plann use. GMX is the least bad, and Purelymail may be worth checking out. I have no idea about Google - it hasn't been tested for ages, it should probably be checked out. iCloud should be avoided.

## Requirements

Expand All @@ -19,7 +19,7 @@ For Cloud/SaaS, there is no obvious winner — all tested providers have signifi
* Recurring tasks
* Relationships (RELATED-TO property type)

Earlier this list included lots of requirements on how well the server supports searches. The CalDAV library now supports doing client-side filtering when the server doesn't do the job well enough. However, for a huge calendar with lots of obsoleted tasks and events, client-side filtering may involve quite a lot of network overhead. **Also, it may be needed to specify buggy server-side behaviour in the configuration to enforce client-side filtration**.
Earlier this list included lots of requirements on how well the server supports searches. The CalDAV library now supports doing client-side filtering when the server doesn't do the job well enough. However, for a huge calendar with lots of obsoleted tasks and events, client-side filtering may involve quite a lot of network overhead. **Also, it may be needed to specify buggy server-side behaviour in the configuration to enforce client-side filtration** - this is done with the `features` key in the config section, e.g. `"features": "davical"`.

Journals (VJOURNAL component type) are useful for logging completed work, and scheduling support is useful if you want to send and respond to meeting invitations.

Expand All @@ -29,9 +29,9 @@ Journals (VJOURNAL component type) are useful for logging completed work, and sc

https://www.xandikos.org/

Relatively new server written in Python, storing all data in a local git repository. Super-easy to set up and get started with. Quite standard-compliant and well-exercised, as it is included in the python caldav library test suite. Lack of support for recurrences was a show-stopper until 2025.
Server written in Python, storing all data in a local git repository. Super-easy to set up and get started with. Quite standard-compliant and well-exercised, as it is included in the python caldav library test suite. Lack of support for recurrences was a show-stopper until 2025; recurring tasks have been expanded properly since 0.3.7. Basic scheduling support is present.

**Recommended**.
This is what the author uses. **Recommended**.

Xandikos also supports address books (VCARD).

Expand Down Expand Up @@ -77,7 +77,7 @@ Another sabre/dav-based server (same backend as Baikal). Has essentially the sa

### Nextcloud

https://www.nextcloud.com/
https://nextcloud.com/

Nextcloud has many components, including a calendar that appears to be based on sabre/dav. The list of CalDAV limitations is similar to Baikal.

Expand All @@ -87,7 +87,7 @@ Be aware that Nextcloud applies fairly aggressive rate limits, which can break a

https://www.cyrusimap.org/

A mature IMAP/CalDAV server with good scheduling support (both inbox delivery and auto-scheduling). One of the better options in the compatibility matrix with few plann-relevant issues. One of the minor issues worth mentioning is that recurring events/tasks are not found in time-range searches arbitrarily far into the future (same limitation as Baikal/Nextcloud).
A mature IMAP/CalDAV server with good scheduling support (both inbox delivery and auto-scheduling). One of the better options in the compatibility matrix with few plann-relevant issues. One of the minor issues worth mentioning is that recurring events/tasks are not found in time-range searches arbitrarily far into the future (same limitation as Baikal/Nextcloud). **Recommended** for multi-user setups with scheduling.

### SOGo

Expand All @@ -101,19 +101,19 @@ SOGo is probably very good if you want a web-based email and calendaring tool fo

### Zimbra

"Groupware" supporting mail with a rich web interface. The CalDAV support has many limitations and issues. (A couple of happenings from production: 30 participants invited for a recurring meeting, one of the participants removing one instance from their calendar (using other CalDAV clients), whosh the whole recurring event cancelled for all the 30 participants. Reloading a calendar from backup using plann, and whosh Zimbra sent out hundreds of meeting invites by email reminding attendees to come to meetings that happened ten years back in time). **Not recommended**.
"Groupware" supporting mail with a rich web interface. The CalDAV support has many limitations and issues. (A couple of happenings from production: 30 participants invited for a recurring meeting, one of the participants removing one instance from their calendar (using other CalDAV clients), whoosh, the whole recurring event cancelled for all the 30 participants. Reloading a calendar from backup using plann, and whoosh, Zimbra sent out hundreds of meeting invites by email reminding attendees to come to meetings that happened ten years back in time). It also drops RELATED-TO, so task hierarchies do not work, and tasks have to be kept on separate task lists. **Not recommended**.

### Bedework

https://www.bedework.org/
https://github.com/Bedework/bedework

Java-based enterprise calendar system. **Not maintained anymore**. Many issues with the CalDAV support, so **not recommended**.
Java-based enterprise calendar system, still maintained (5.0.0 was released in 2025). Through CalDAV, a client cannot create a task or journal list, text search does not work, and all but the first RELATED-TO line are stripped. **Not recommended** for plann.

### Robur

https://github.com/roburio/caldav (cloud: https://calendar.robur.coop/)
https://github.com/robur-coop/caldav (cloud: https://calendar.robur.coop/)

Does not support relationship attributes, text search is non-functional (returns all elements regardless of filter), journals are rejected (ungraceful), sync-tokens are ungraceful, `get-supported-components` is unsupported. **Not suitable for heavy plann usage**
Does not support relationship attributes, text search is non-functional (returns all elements regardless of filter), journals are rejected (ungraceful), sync-tokens are ungraceful, `get-supported-components` is unsupported. **Not suitable for heavy plann usage**.

### Stalwart

Expand All @@ -123,9 +123,9 @@ All-in-one mail and collaboration server with CalDAV support added in 2024/2025.

### OX App Suite

https://www.open-xchange.com/
https://ox.io/

OX seems to have major limitations, though it could be worth checking if the problems are on the OX side or in the caldav-server-tester tool. The latter adds events and tasks in the year 2000 and tries to do operations on those. OX does tend to ignore all old events and tasks, as well as events and tasks that are far in the future.
OX rejects recurring tasks, mangles RELATED-TO, does not support journals, needs tasks in a calendar of their own and ignores several search filters (including time-range on tasks). Searches only reach a sliding window around today: old events and tasks, and those far in the future, are not found. **Not recommended**.

### Apple CalendarServer (CCS)

Expand All @@ -145,15 +145,15 @@ https://posteo.de has many issues. **Not recommended**

CalDAV at `caldav.gmx.net`.

It has many issues, but none of them are very much relevant for "heavy plann usage". If you want a service provider, GMX is definitively not the worst choice.
It has many issues, but most of them are not very relevant for "heavy plann usage". One quirk worth knowing: a completed task cannot be un-completed. If you want a service provider, GMX is definitely not the worst choice.

### Purelymail

https://purelymail.com

From the name it appears their selling point being that they focus on emails and nothing else - but they do have a CalDAV-complient calendar service.
From the name it appears their selling point is that they focus on emails and nothing else - but they do have a CalDAV-compliant calendar service.

The server has memory indexes that are "lazily" populated — in practice there can be several minutes of delay between doing a change and until it appears in the search results. The compatibility matrix currently shows that quite many features are "fragile", possibly due to this. If using plann first for doing changes and directly afterward trying to take out a fresh list, it will fail to show the updated data. The developers are friendly enough, it could be worth investigating more and also report issues found upstream.
The server has memory indexes that are "lazily" populated — in practice there can be several minutes of delay between making a change and it appearing in the search results. The compatibility matrix currently shows that quite many features are "fragile", possibly due to this. If using plann first for doing changes and directly afterward trying to take out a fresh list, it will fail to show the updated data. The developers are friendly enough, it could be worth investigating more and also report issues found upstream.

Scheduling is reported to be "work in progress".

Expand All @@ -167,20 +167,28 @@ Has not been tested for ages. **TODO**.

### iCloud

Does not officially support CalDAV. The unofficial support is quite broken — no recurrences, no tasks, many other things broken. **Not recommended**.
Does not officially support CalDAV. Tasks work only in a separate task calendar, journals and time-range searches on tasks are unsupported, old objects are invisible to searches, and recurrence searches came back unsupported (possibly an artefact of the search window). **Not recommended**.

### Infomaniak

Hosted calendar based on sabre/dav. Saving and most searches work well. Journals, searches for recurring tasks and AND-combined searches are unsupported. Usable if you don't need journals or recurring tasks.

### Yahoo

Events with a timezone are accepted but cannot be read back, RELATED-TO is refused (400 Bad Request), tasks need a calendar of their own, journals are refused, and recurrence searches are unsupported. **Not recommended**.

## Non-free solutions

### Synology

The compatibility matrix for Synology looks relatively decent, the problems should not be much relevant for heavy plann usage.
Synology's calendar is a modified DAViCal, and its compatibility matrix matches DAViCal's except that calendars cannot be deleted. It looks relatively decent; the problems should not be very relevant for heavy plann usage.

## Conclusion

In 2013, all I wanted to do was to set up a personal calendar and access it easily through the command line ... and I fell down a rabbit hole and have been fighting with the CalDAV protocol and iCalendar format for almost a decade.
In 2013, all I wanted to do was to set up a personal calendar and access it easily through the command line ... and I fell down a rabbit hole and have been fighting with the CalDAV protocol and iCalendar format for more than a decade.

Let me be completely honest: I'm not happy, neither about the CalDAV standard nor the iCalendar standard. The protocols seem not very well thought-through, particularly when it comes to the task support (and using those standards for time tracking - forget about it!). But this is what we have as for now.
Let me be completely honest: I'm not happy, neither about the CalDAV standard nor the iCalendar standard. The protocols seem not very well thought-through, particularly when it comes to the task support (and using those standards for time tracking - forget about it!). But this is what we have as of now.

The CalDAV protocol is designed so that the client can be relatively simple while most of the work is done on the server side (expansions, complex searches, etc). Unfortunately server support for this is often broken. My original plan for plann was always to leave all the complexity to the server, but in practice the client ends up doing a lot of client-side filtering and expansion to paper over server deficiencies.

The best current recommendation for self-hosting is **Xandikos** (version 0.3.7+) if you need a simple single-user setup, or **DAViCal** if you need multi-user and scheduling.
The best current recommendation for self-hosting is **Xandikos** (version 0.3.7+, and the author's own choice) or **Radicale** if you need a simple setup, or **DAViCal** or **Cyrus** if you need multi-user and scheduling.
Loading