Sincronizzazione Calendario e Contatti tra Thunderbird e Nextcloud

From RVM Wiki
Jump to navigation Jump to search
  • Per calendario e address book, assicurarsi che Nextcloud risponda agli url
  • Creare i record DNS SRV:
_caldavs._tcp.example.com.   23887   IN      SRV     10 10 443 cloud.example.com
_carddavs._tcp.example.com.   23887   IN      SRV     10 10 443 cloud.example.com
  • Thunderbird si configura in automatico !

Background

A SRV record has the form:

_service._proto.name. ttl IN SRV priority weight port target.
  • service: the symbolic name of the desired service.
  • proto: the transport protocol of the desired service; this is usually either TCP or UDP.
  • name: the domain name for which this record is valid, ending in a dot.
  • ttl: standard DNS time to live field.
  • IN: standard DNS class field (this is always IN).
  • SRV: Type of Record (this is always SRV).
  • priority: the priority of the target host, lower value means more preferred.
  • weight: A relative weight for records with the same priority, higher value means higher chance of getting picked.
  • port: the TCP or UDP port on which the service is to be found.
  • target: the canonical hostname of the machine providing the service, ending in a dot.

An example SRV record in textual form that might be found in a zone file might be the following:

_sip._tcp.example.com. 86400 IN SRV 0 5 5060 sipserver.example.com.

This points to a server named sipserver.example.com listening on TCP port 5060 for Session Initiation Protocol (SIP) protocol services. The priority given here is 0, and the weight is 5.

As in MX records, the target in SRV records must point to hostname with an address record (A or AAAA record). Pointing to a hostname with a CNAME record is not a valid configuration.[1]

Source: https://en.wikipedia.org/wiki/SRV_record

When a client tryes to configure card/cal DAV

Source https://datatracker.ietf.org/doc/html/rfc6764


So configure:

_caldavs._tcp.yourDomain.com.   23887   IN      SRV     10 0 443 mail.yourDomain.com.
_carddavs._tcp.yourDomain.com.  52897   IN      SRV     10 0 443 mail.yourDomain.com.

Eventually, but if you have .well-known on mail.yourdomain.com working, no txt is needed:

_carddavs._tcp      IN TXT     "path=/SOGo/dav/"
_caldavs._tcp       IN TXT     "path=/SOGo/dav/"

Source https://www.axigen.com/documentation/dns-based-service-discovery-p47120690

Riferimenti


Thunderbird 19.1

  • Supporta nativamente Carddav.
  • Aggiungere application password in Nextcloud
  • Da address book aggiungere
 CardDDAV addressbook
  • Vedi biwarden per url calendario
  • Mettere la application password

Versioni precedenti

  • Generare una password applicazione in Nextcloud
  • Open Thunderbird advanced config and set
network.cookie.same-site.enabled = false
  • Restart Thunderbird
  • For this method, you need to have two add-ons installed:
  • When they are installed, if you are on Windows, go to
Edit/Synchronisation settings (TbSync)


  • In the account manager choose “Add account / CalDAV / CardDAV account”
  • In the next window, go with the default called
Automatic configuration

and click next

  • Enter an account name, which you can freely choose,
user name: your email address
password:  THR APPLICATION PASSWORD (IMPORTANT, not the simple password, that is used only for frontend wth otp)
URL of your server: https://www.example.com/nextcloud


  • In the next window, TbSync should have autodiscovered the CalDAV and CardDAV addresses. When it has, click
Finish
  • Now check the box
Enable and synchronize this account
  • TbSync will discover all address books and calenders your account has access to on the server
  • Check the box next to each calender and address book you want to have synchronised, also set how often you want them to be synchronised and push the button sychronize now
  • After the first successful synchronisation is complete, you can close the window.
  • Henceforth, TbSync will do the work for you.


Riferimenti