I just want to shed some light onto "TbSync" which has been mentioned in
this thread.
Until a few weeks ago, it was a plain ActiveSync AddOn, but with the
sogo-connectors missing support for Thunderbird 60, one of my clients
asked me to add CardDAV support. So I did. Last week its description
changed and is now officially supporting CardDAV.
I think users of the SOGo groupware should stick to the
sogo-connector/integrator, because TbSync is "just" following the
sabre/dav specs, but does not do any of the special stuff for SOGo. It
does however support shared resources with read-only rights.
TbSync works a bit different from sogo-connector: Users do not need to
know the URLs, TbSync uses the discovery service to find all address
books and calendars and lets the user select which one to sync via UI.
The CalDAV sync is delegated to lightning, which means it has the same
problems when it comes to syncing calendars of different users on the
same server. My CardDAV implementation does not have a problem with that.
Best regards,
John
Am 03.09.2018 um 14:31 schrieb Marcio Vogel Merlone dos Santos
(marcio.merl...@a1.ind.br):
Em 01/09/2018 05:07, "Kai-Uwe Rommel" (kai-uwe.rom...@ars.de) escreveu:
users-requ...@sogo.nu wrote on 30.08.2018 16:41:49:
> Plain calendar sync isn't the issue here as (at least)
> CalDAV sync is built into Lightning anyways.
Given that with the built-in Lightning and with CardBook I can also
work with SOGo's calendar and contacts, I see no advantage in the
SOGo connector. In both cases, I need to manually add the SOGo
calendar and contacts to Thunderbird with the SOGo CalDAV and CardDAV
URLs and account data.
Odd. You should not need anything but the password with SOGo.
Or did I miss something about the SOGo
connector?
I think so. Even in a small company the automation provided with SOGo
connector is a must.
If you are just an end user and not admin, you are right.
--
*Marcio Merlone*
--
users@sogo.nu
https://inverse.ca/sogo/lists
--
users@sogo.nu
https://inverse.ca/sogo/lists
