2024/05/22

Sync Mac OS X Server with Outlook Contact and Calendar

Sync Mac OS X Server with Outlook 2019/Office 365 Calendar and Contact

In 2024, an increasing number of jobs require remote work due to the ongoing COVID-19 pandemic. For many, syncing calendars, contacts, and tasks from home to coordinate with colleagues has become a challenge, especially for those unfamiliar with the process.

It's time to share some new IT solutions with you. Recently, someone asked me, "How can I sync Outlook Contacts and Calendars with my studio's Mac mini running OS X Server (Catalina)?"

001

Yes, you can do it! It would be ideal if everyone used macOS, but life isn't always that simple. Let's say your friend runs a macOS Server and provides you with access to its CardDAV and CalDAV services, but you only have Microsoft Outlook 2013, 2016, or 2019. How can you share and sync all entries between each other? It’s a challenging task, believe it or not. To be honest, I hadn't found a solution until a few days ago when I visited the EVO Collaborator for Outlook webpage. They've added a new feature that supports macOS Server's WebDAV services. EVO Collaborator for Outlook

eco_icon

In my previous blog post on syncing Gmail contacts and calendars with Outlook using EVO Collaborator, I mentioned how easy it was to add a CardDAV/CalDAV profile. To add a macOS Server profile, there's an extra step: entering the HTTPS address and service port number. For example, use https://<servername>:8443/ or https://<ip address>:8443/. Once the connection is tested and confirmed, it works just like any other profile within ECO. You can now sync your Outlook contacts and appointments with the macOS Server, and ECO will accept your self-signed certificates.
 

What is CardDAV and what is CalDAV protocols


CardDAV and CalDAV are standard protocol APIs defined by IETF's RFC for syncing contacts and calendars. Google and Apple use these APIs to manage contacts and calendars on the backend, meeting their customers' needs for such information. With these standard protocols, users can synchronize all their contact, calendar, and task entries across almost any platform, including PCs, Macs, laptops, tablets, and phones. A single master copy ensures all changes are automatically updated across all devices, eliminating the need to manually replicate changes on different units.
 

Hosting your own calendar and contact server with Windows PC

Mac OS X Server is great for hosting your on-premise server. However, what if you do not have a Mac server? Nevertheless, you can still host your DAV server under Windows OS. For example, EVO Mail Server is another good option that it is easy to set up and configure especially for small and medium size of companies. 

2024.05.23

2024/05/11

Sync Yahoo calendar with Outlook 2016 and Outlook 2019

Import, Export, and Synchronize Yahoo! Contacts and Calendar with Microsoft Outlook

In 2024, an increasing number of jobs require people to work from home due to the COVID-19 pandemic. Syncing calendars, contacts, and tasks remotely from home to collaborate with colleagues has become a challenge for those unfamiliar with the process.

Just a few weeks ago, a friend from high school asked me a question: "My colleagues from the States keep bothering me. They want me to import their Yahoo! Address book and appointment information into Outlook 2016, 2019, and 2013 on their laptops because there's too much crucial information to miss out on. Now, I'm stressed because the old Yahoo! Sync method isn't effective anymore. What should I do?" When I heard about this, I suggested an idea to him: Try EVO Collaborator for Outlook! I previously mentioned to you all how amazing this software is for importing contacts and calendars from Gmail and iCloud, right? Just a few days ago, I came across an update history on the EVO Mail Server website about ECO, and now it can perform read/write/delete synchronization tasks on Yahoo! CardDAV and CalDAV! Let's learn how to sync Yahoo contacts and calendars with Outlook:

  1. Outlook and Download ECO software from EVO's Official Download
  2. Open Outlook and enter ECO’s “Configure Profile(s)”

    eco_gui_config_selected

  3. Select the third profile from the top at the left-hand side: YAHOO!

    yahoo_slot

  4. At the right-hand side, enter your complete Yahoo! E-mail address in “Full e-mail address or Username” field

    yahoo_username_pw

  5. About the password, we need to pay close attention. Yahoo! now requires any third-party application to use a separate password called “App Password” generated within your Yahoo! account settings. With this App Password, such sync application can then access information within the user account.
  6. Please follow Generating App Passwords instruction to create such password and enter this generated password in “Password” field.

    yahoo_pw_generate

  7. Click on “TEST” below. Once a pop-up box showing “Success” appears, click on “Apply” and then “Quit”
  8. At this moment, ECO will initiate an automated addressbook and Calendar synchronization
2024.05.12

2024/05/09

Sync with Synology Contacts and Calendar via CalDAV & CardDAV URL?

In 2024, an increasing number of jobs require people to work from home due to the COVID-19 pandemic. Syncing calendars, contacts, and tasks remotely from home to collaborate with colleagues has become a challenge for those who are new to this setup.

The following article is from the blog website of EVO software production. I found it very useful, so I contacted them to inquire if I could share it here for your information. They replied yes. So, here we go: (By the way, I followed the procedures and steps outlined in this article, and they all worked as intended.)

How can one synchronize Synology Contacts, Calendar, and Tasks with applications like Outlook?

synology_logo
Synology NAS

As Synology announced its DSM 3.2 support of running CardDAV CalDAV services on its NAS product line back in Sept. 7, 2011, everyone in various forums and discussion groups rejoiced. However, if you search “caldav” keyword in Synology Community, most threads of over 80 pages search result for the past almost 8 years are asking how to make CalDAV work as it should even for today’s most recent DSM 6.2 system software. Yet, the only thing that still works is syncing CardDAV contacts with various syncing tool or devices because I hardly heard complaint about CardDAV’s functionality in Synology NAS. Previously in 2014, we wrote an article about how to sync Outlook contact, calendar and task with Synology’s CalDAV and CardDAV. During the past years, Synology has been revising its DSM and stepping from DSM 5.x to the current DSM 6.2. As of today, let’s review if CalDAV and CardDAV services provided by Synology NAS are still in good shape. By the way,  if you are a Baikal user, then you need to be aware of whether newer version of DSM is still compatible with Baikal server. If you are happy at where you are, then do not bother to update to the newest DSM unless you know what you are doing and know how to shuffle things around with database, php, apache and etc. In my post 4 years ago, I also put down how to sync Baikal server on Synology with Outlook. In case you missed that, check it out.

Syncing tools that used to work

After EVO Collaborator for Outlook started to support Synology syncing with Outlook Contact and Calendar back in late 2014, other syncing tools of the same sort gradually started supporting it too, such as gSyncit. Back in the old days, most of the syncing tools were working. As of now, gSyncit is not able to detect server URL and return (404) Not Found error message:
gsyncit_synology_verify_fail
gSyncit 404 Not Found error
Yet, at the beginning of 2019, one of our customers reported that syncing Outlook calendar with Synology’s CalDAV did not work. Our staff experienced the same issue in our lab, so we started to work on it in order to prevent users from facing the same problem. Just a few days ago, the puzzle was finally solved.

From Synology’s official knowledge base…

There is a theory claiming that for every software issue reported by its user, there are actually 1000 users behind it facing the same problem but they just do not report it. Based on the theory above and complaints about CalDAV not working I saw on Synology Community, there are A LOT of Synology users waiting for a solution. Hey, SYNO! Wake up and do something about it! According to instructions on Synology’s Knowledge Base on How to Sync Synology Calendar with CalDAV Clients, syncing calendar entries should work at breeze. Also, another article on Synology’s Knowledge Base on How to host a calendar server using the Synology NAS provides steps on configuring CalDAV clients. However, if you actually test them out practically, both methods will fail.
synology_webdav_calendar_package
Synology WebDAV & Calendar Package
If you look closely on Synology’s DSM UI, you will find there are two places to create CalDAV sharing URLs. One is in Synology’s built-in Calendar app:
synology_calendar_caldav%2Baccount
menu to CalDAV Account
and another is in WebDAV app:
synology_webdav_add_calendar
WebDAV: add calendar
These two places are also mentioned in the two Synology Knowledge Base articles above. Following steps in the articles, it ends up not working. This is how built-in Calendar URL looks like on Synology’s Knowledge Base:
calendar_generated_path_on_knowledge_base
Built-in Calendar version of URL
This is how WeDAV URL looks like on Synology’s Knowledge Base:
synology_webdav_generated_path_on_knowledge_base
WebDAV version of CalDAV URL

The discovered fact is…

By default, the CaldDAV path locations of both Synology built-in Calendar app and WebDAV configuration are supposedly pointing to the same calendars under the same CalDAV account. Whether you access them from either Synology web-UI or other client software/device, you should see the same entries. Older versions of DSM might have the depicted CalDAV path coherency on both ends, but we don’t know. However, on the most current release of DSM 6.2, it is proven wrong after we tested our current Synology NAS in our lab. The calendars on Synology’s Calendar app and in WebDAV are actually separate entities. Yet, only WebDAV’s version of configuration works after some little tweak, which we will discuss in detail in next section.

Fix it and sync it

After spending hours on comparing differences of both methods on Synology’s Knowledge Base as well as actually experimenting different combination of CalDAV URL paths, hostname, ports on various CalDAV clients, we finally got it working. We will first present the working CalDAV URL path here and then we will talk about the difference between the working path and the paths taught by Synology’s Knowledge Base. The following URLs are the working ones:
  • non-SSL: http://<server_hostname_or_ip>:port/homes/<user_account>/<calendar_folder>/
  • SSL: https://<server_hostname_or_ip>:port/homes/<user_account>/<calendar_folder>/
The actual URLs that apply in our experiment are:
  • non-SSL: http://junkyard2019.ddns.net:5005/homes/junkadmin/calendar/
  • SSL: https://junkyard2019.ddns.net:5006/homes/junkadmin/calendar/
Synology’s built-in Calendar has URL path like this:
synology_calendar_caldav%2Baccount_path
Synology’s built-in Calendar URL path
Comparing between the working URL paths and the built-in Calendar paths, let’s put server host name aside and focus on the path part. Upon browsing through Synology’s hiearachical folder tree, “caldav” is not found anywhere. It means that path here is not working at all. If it does work, then it is only valid within its own territory, not syncing outside of it. Synology’s WebDAV console has URL path like this:
synology_webdav_path_for_quickconnect
Synology’s WebDAV console URL path
calendar_generated_path_on_knowledge_base
CalDAV folder path on Synology Knowledge Base
Comparing between the working URL, WebDAV version of URL of DSM 6.2, and WebDAV version of URL on Synology’s Knowledge Base. Let’s also put server host name aside. Even though DSM 6.2’s URL version matches the working URL, users can hardly find it unless they pause mouse cursor under Location in the screenshot. Otherwise, users would have paid more attention on Knowledge Base’s incorrect URL version. Next, the difference between two WebDAV versions is the folder path. Knowledge Base’s path is:
  • /web/Calendar/Work
Captured URL is:
  • /homes/<user_account>/<calendar_folder>
We think URL path difference is the major cause why users are not able to sync their syncing tools/devices with Synology CalDAV service because syncing tools/devices are not able to discover the new URL path according to auto-discovery scheme of /web/Calendar/<calendar_folder> from the past. The odd thing is that the path from the Knowledge Base version was working for older versions of DSM and syncing tools have used that for years. But, for the current DSM 6.2, it is no longer valid.

Syncing with Synology CardDAV service

synology_carddav_service_icon
Synology DSM CardDAV Server
On Synology NAS, service setting is straight and simple. There is only one place for changing port number and that is all.
synology_carddav-service_UI
Synology NAS CardDAV UI
To synchronize with Synology’s CardDAV service, the server URL syntaxes of the CardDAV are below:
  • non-SSL: http://<server_hostname_or_ip>:port/addressbooks/users/<user_account>/addressbook/
  • SSL: https://<server_hostname_or_ip>:port/addressbooks/users/<user_account>/addressbook/
By looking at the URLs above, it is the same as EVO Collaborator for Outlook’s syntax configuration for Synology CardDAV service back in 2014. On Synology’s Knowledge Base, there are only two webpages of description on parameters in Synology’s DSM and that is all! There is entirely no instruction or whatsoever on how to configure iOS, macOS, Thunderbird, Outlook and etc. This is disappointing.

Issues on synchronizing with Synology CardDAV server

Case #1 Here is one trivial issue for your information. A majority of address books included in various mail client software applictions, such as Thunderbird, Outlook, iOS’s Mail and etc have dedicated fields for each part of a complete address.
synology_outlook_original_address
Outlook Address Before
However, once contact entries are synchronized with Synology CardDAV server, all fields will be merged into a single address field on Synology’s CardDAV server.
synology_one_line_address
One-Line Address on Synology
Please make sure that you DO NOT modify the address on Synology address book. Otherwise, this dramatic change will be synced back to your address book client software.
synology_outlook_one_line_address_after%2Bsync
One-Line Address on Outlook after sync
As a result, all address-related fields except street on your local address book will be wiped out. What is left is the all-in-one street field. Case #2 Here is one more issue. If your client software is Outlook and like to sync with Synology CardDAV server, when you save a phone number, do not use some general phone entry, such as Primary in this case.
synology_issue_primary_phone_number
Outlook phone entry – Primary
On Synology’s end, do not use general phone entry, such as Telephone and Preferred.
synology_issue_telephone_preferred_number
Synology phone entry – Telephone & Preferred
During our test, there are patterns like the following:
  1. Once Primary entry is synchronized to Synology’s address book, it was initially assigned to Telephone. If you modify Telephone entry, once the synchronization takes place, the Primary entry will disappear on Outlook.
  2. Telephone entry is not synchronized to Outlook at all.
  3. Preferred entry is synchronized to Outlook and takes Primary entry. But, if Primary entry is modified and being synced back to Synology, then Preferred entry is gone and the Telephone entry is displaying Primary‘s content. It will go back to #1 that Primary will disappear if modifying Telephone entry takes place.
  4. In case of both Telephone and Preferred entries exist on Synology’s address book, modifying Preferred entry or Primary entry are supposed to sync each other. But, the outcome is that Preferred will disappear and content of Primary entry will go to Telephone entry. If Telephone entry is modified, then it will go back to #1’s result.
All experiments above are like never-ending loops. Hence, to eliminate the chance of data loss, do not use these three entries or any other phone number entry that sounds general.

Syncing Synology CalDAV and CardDAV with different client software/platforms

Let’s start checking if some of the popular syncing tools can do the job on various platforms.

Syncing Synology CalDAV and CardDAV with Outlook

For both CalDAV and CardDAV of Synology to sync with Outlook, EVO Collaborator for Outlook can wrap these two tasks at once. This example covers Outlook 2007, 2010, 2013, 2016, 2019 as well as Office 365. Here is the step-by-step:
  1. Open Outlook.
  2. Click on Configure Profile(s).
    eco_config_profile
    Configure Profile(s)
  3. Click on Profile #21 at lower-left.
    eco_profile_21
    Click on Profile #21
  4. Enter server host name in the fashion of:
    • Sync via non-SSL connection: http://<server_hostname_or_ip>:8008
    • Sync via SSL connection: https://<server_hostname_or_ip>:8443
      eco_server_hostname_url
      Enter server hostname URL
  5. Enter username and password.
    eco_enter_username_password
    Enter username and password
  6. Upon clicking on TEST button, server URLs for contacts, calendar and tasks will be auto-discovered in URL space.
    eco_click_test_and_apply_button_before_test
    Click on TEST button to authenticate
    eco_auto_discovery_result
    Auto-discovery result
  7. Also, multiple calendars and tasks are supported, so click on folder icon next to the URLs to select folders from the popup list.
    eco_calendar_task_folder_list
    Calendar/Task Folder List
  8. Click on Apply button to save.
    eco_click_test_and_apply_button
    Click on Apply to save

There are a few things you need to be aware of:

  1. In order for auto-discovery to work under EVO Collaborator for Outlook, all non-SSL and SSL ports for CardDAV and CalDAV must be kept their default values on Synology NAS:
    • CardDAV: non-SSL: 8008, SSL:8443.
    • CalDAV: non-SSL: 5005; SSL:5006.
  2. To sync via non-SSL connection, port 8008 must be used in Server Hostname field.To sync via SSL connection, port 8443 must be used in Server Hostname field.
    eco_port_8008_hostname
    Enter port 8008 for non-SSL connection
    eco_port_8443_hostname
    Enter port 8443 for SSL connection
  3. If CalDAV and CardDAV ports on Synology NAS are different from their default values for some reason, then keep Server Hostname space blank and manually generate URLs according syntax rules given earlier. After entering URLs, simply click on TEST button to test it and click on Apply button to save it. 
    synology_eco_server_url_empty_configure_manually
    Manual configuration in ECO profile

Syncing Synology CalDAV and CardDAV with macOS

For macOS, it has always been an issue of “Unable to verify account name or password.” for CalDAV and CardDAV. I googled it and found many answers. The most commonly seen possibility has something to do with server certificate.
synology_macos_addcaldav_account_failed
Unable to verify account name or password
Anyway, I have done a thorough test under several environments for your reference. This test tries to add Synology’s CardDAV and CalDAV accounts on Mojave under three conditions :
  1. A default certificate self-signed by Synology off factory
  2. Import a third-party self-signed certificate on Synology
  3. Import a CA-signed certificate on Synology
In most cases for #1 and #2, the same error message in above screenshot would appear no matter I add them through Manual Setup or Advanced Setup in macOS. On the other hand, with #3, I can always add both CardDAV and CalDAV accounts in Advanced Setup. During trials on #1 and #2, I encountered a popup message of “Internet Accounts (System Preferences) can’t verify the identity of the server “junkyard2019.ddns.net”.” Then, I started to pay attention on how to import self-signed certificates under macOS and let macOS always trust them. Once self-signed certificates are trusted by macOS, everything went smoothly as #3 where the CA-signed certificate was imported into Synology NAS. Now, I conclude that there are separate and necessary steps before actually adding CardDAV and CalDAV accounts in macOS:
  1. If using Synology’s self-signed certificate, export it to macOS:
    • Export the self-signed certificate from Synology NAS to a crt file.
      01_export_self_sign_cert
      Export Self-signed Certificate
    • Import the crt file under macOS.
      02_import_self_sign_to_macos
      Import Self-signed Certificate to macOS
    • Make the imported certificate to be always trusted.
      03_get_info_on_cert
      Right-click on certificate and click on Get Info
      04_make_cert_always_trust
      Select Always Trust to override Use System Defaults
  2. If using an existing CA-signed certificate, import it to Synology:
    1. Follow steps in How to setup mail server in Windows to obtain a CA-signed SSL certificate.
      05_getting_ca-sign_tutorial_screeshot
      Get CA-signed certificate tutorial
    2. Click on Control Panel/Security
      06_control_panel_security
      Control Panel / Security
    3. Click on Certificate tab.
      07_certificate_tab
      Certificate tab
    4. Click on Add button.
      08_add_new_certificate
      Add button and Add a new certificate
    5. Click on Add a new certificate and click on Next in window of screenshot above.
    6. Click on Import certificate and click on Next
      09_import_certificate
      Import certificate
    7. Click on Browse button to browse to the folder where you save your certificate files.
      10_browse_ca_signed_cert
      Browse certificate files location and import them
    8. As shown in screenshot above, respectively import Private Key, Cerificate, and Intermediate certificate and click on OK.
Once certificate import/export above is complete, in DSM, click on Configure button and assign the dedicated certificate to CardDAV Server and WebDAV Server through the pull-down certificate list.
11_select_certificate_as_default_for_carddav_webdav
 Select certificate for CardDAV and WebDAV default cert
Then, proceed to steps below to configure macOS:
  1. On macOS, open System Preferences / Internet Accounts.
    12_system_preference_internet_accounts
    System Preferences / Internet Accounts
  2. Click on Add Other Account…:
    • Click on CardDAV account for CardDAV
    • Click on CalDAV account for CalDAV.
      13_add_other_account_selection
      Select CalDAV account or CardDAV account
  3. Select Advanced from Account Type pull-down list, then enter: 
    14_advanced_account_type
    Advanced Account Type
    • User Name, example: junkadmin
    • Password, example: *********
    • Server Address:
      • format: server_host.domain.com
      • example: junkyard2019.ddns.com
    • Server Path:
      • For CardDAV:
        • format: /addressbooks/users/<username>/addressbook/
        • example: /addressbooks/users/junkadmin/addressbook/
      • For CalDAV
        • format: /homes/<username>/<calendar_folder>/
        • example: /homes/junkadmin/appointment/
    • Port:
      • 8443 for CardDAV
      • 5006 for CalDAV
    • Use SSL: Keep it checked.
      15_carddav_advanced_setting_demo
      Advanced settings for CardDAV
      16_caldav_advanced_setting_demo
      Advanced settings for CalDAV
      17_both_dav_accounts_added
      Final account added result
  4. Click on Sign In to conitnue login
Here is the synchronized result:
synology_macos_address_book
Mac address book sync result
19_macos_calendar_sync_demo
macOS Calendar sync result

Syncing Synology CalDAV and CardDAV with iOS (iPhone & iPad)

For the past years, Apple’s iOS on both iPhone and iPad is known to be the most compatible platform to sync with almost every CalDAV, CardDAV, Exchange, and other sync services on the market. In the following example, we tested iPhone XS based on iOS 12.2, which is the newest release yet. I cannot really remember if it is iOS 10 or 11? Apple started to force mail, CalDAV and CardDAV accounts to be created using SSL/TLS protocol only. For the new iOS 12.2, non-SSL protocol still will not work. For CardDAV, iOS smoothly detects server URL as soon as server (no need to enter port), user name and password are entered. Then, everything is all set.
iphone_carddav_summary
 CardDAV settings summary
For CalDAV, there is a workaround since iOS devices seem unable to find correct URL’s folder path initially:
  1. On iPhone, for example, go to Settings/Passwords & Accounts.
    iphone_password_account
    iPhone Passwords & Accounts
  2. Scroll to the bottom and tap on Add Account.
    iphone_add_button
    iPhone Add Account
  3. Tap on Other
    iphone_account_template_selection
    Other Account Template
  4. Tap on Add CalDAV Account.
    iphone_other_template_selection
    CalDAV Account Template
  5. Enter server hostname, user name and password as requested and tap on Next.
    iphone_enter_server_username_password
    Enter server, username, password
  6. A warning message of “Cannot Connect Using SSL“. At the moment, tap on Cancel and OK.     
    iphone_caldav_unable_ssl_warning
    Cannot Connect Using SSL
    iphone_caldav_cannot_verify
    Unable to verify account information
  7. Tap on Advanced Settings.
    iphone_caldav_advanced_settings
    Advanced Settings
  8. iOS used to have this Account URL fully detected with no further configuration, but it is now unable to detect full URL for Synology’s CalDAV service. So, we enter complete server URL according to what we learned earlier in this article. In this example, it is:
    • https://junkyard2019.ddns.net:5006/homes/junkadmin/appointment
      iphone_caldav_advanced_change_url
      Change CalDAV server URL
  9. Tap on < CalDAV at top-left shown in the screenshot above.
  10. Tap on Next at top-right.
    iphone_next_top_right
    Tap on Next
  11. There will appear check marks and next screen lets you enable or disable calendar and task.  
    iphone_caldav_settings_verified
    Server info verified
  12. Tap on Save at top-right to save settings.
    iphone_caldav_save_settings
    Save settings
With a little tweak, it is still possible to sync Synology contacts, calendar and tasks with iOS devices.
iphone_caldav_summary
 CalDAV account summary

Syncing Synology CalDAV and CardDAV with Thunderbird

For CalDAV, Lightning can be used to sync Synology’s CalDAV calendar. Steps are as below:
  1. Open Thunderbird and make sure it is updated to the latest release, which is currently 60.5.3 at time of writing. 
    thunderbird_website
    Thunderbird website download
  2. Mouse right-click on space below Calendar area and select New Calendar….
    synology_thunderbird_add_calendar_menu
    New Calendar… menu
  3. Click on radial of On the Network and click on Next.   
    synology_thunderbird_lightning_on_network
    On the Network radial
  4. Click on radial of CalDAV and enter server URL according to what we learned earlier in this article and click on Next. In this example, it is:
    • https://junkyard2019.ddns.net:5006/homes/junkadmin/appointment/ 
      synology_thunderbird_lightning_create_new_calendar
      CalDAV radial and enter calendar URL
  5. Enter a name for this calendar. Confirm Email for invitation purpose. Click on Next.
    synology_thunderbird_lightning_name_calendar
    Name calendar and enter email for invitation purpose
  6. In the popup window of Add Security Exception, click on Confirm Security Exception.
    synology_thunderbird_lightning_confirm_certificate
    Confirm Synology certificate
  7. At the moment, click on Synchronize from pull-down menu to proceed synchronization.
    synology_thunderbird_click_on_synchronize_calendar
    Click on Synchronize button to proceed
  8. Authentication Required” window pops up. Enter username and password and click on OK.
    synology_thunderbird_lightning_enter_username_password
    Enter username and password
  9. Click on Finish to wrap up adding Synology calendar.
    synology_thunderbird_lightning_complete
    Calendar configuration complete
  10. Lastly, the sync is done.
    synology_thunderbird_lightning_sync_complete
    Calendar sync complete
For CardDAV, SOGo connector for Thunderbird can be used to sync Synology’s CardDAV address book. Steps are as below:

synology_thunderbird_sogo_connector_addressbook_button

  1. Open Thunderbird and make sure SOGo connector for Thunderbird has been installed. Click on circled 60.0.2 to download.
    synology_thunderbird_sogo_connector_download
    Download SOGo Connector for Thunderbird
  2. Open Address Book in Thunderbird.
    synology_thunderbird_sogo_connector_addressbook_button
    Click on Address book
  3. Click on File at top-left and select New / Remote Address Book.
    synology_thunderbird_sogo_connector_remote_address_book
    File / New / Remote Address Book
  4. In the popup window, enter Address Book name and CardDAV URL according to what we learned earlier in this article and click on Next. In this example, it is:
    • https://junkyard2019.ddns.net:8443/addressbooks/users/junkadmin/addressbook/ 
      synology_thunderbird_sogo_connector_enter_url_info
      Enter Calendar Name and URL
  5. In the popup window of Add Security Exception, click on Confirm Security Exception.
    synology_thunderbird_sogo_connector_confirm_ssl
    Confirm Security Exception
  6. Right-click on the calendar and select Synchronize.
    synology_thunderbird_sogo_connector_click_sync_button
    Click on Synchronize to proceed
  7. At the moment, an “Authentication Required” window pops up. Enter username and password and click on OK.
    synology_thunderbird_sogo_connector_enter_user_password
    Enter username and password
  8. Last, the sync is done.
    synology_thunderbird_sogo_connector_sync_done
    Address book sync complete

Some thoughts on Synology’s CalDAV and CardDAV feature

Synology has been a decent NAS solution for users ranging from individuals to enterprise. It is good to have such CalDAV and CardDAV features built-in so we can save some bucks from building a dedicated server for that. However, I pinned out a few flaws, such as incoherency between calendars on two locations, address fields being merged into one line, and CalDAV server URL not being updated in its Knowledge Base. Disregard all the above, it eventually works through some tweaks and minor syntax modification. Well, not a bad solution after all.