I can confirm this as 100% reproducible for SOGo Connector 31.0.4 and Thunderbird 52.3.0, running on OpenSuse 42.3.

AFAIK Lightning is out of scope here, as Lightning adds calDAV functionality (Tasks/Events/Calendars) to Thunderbird. Thunderbird already has builtin addressbooks, and only SOGo Connector is needed to add cardDAV connectivity.

This bug has an additional side effect:

Once you "detect" the root cause of the bug (remote deletion not synced/propagated) and delete the contact(s) manually in Thunderbird, Thunderbird's addressbook sync hangs, without and further notice.

Even after a restart the affected addressbook is not synced anymore, as the new sync again hangs. You don't get any sync messages anymore.

I have the same problem. May by Sabredav sends a propstats response for a delete contact but the sogo connector expected an empty response.

See sync.addressbook.groupdav.js near line 1254

From the code at that line, we don't expect an empty response, we check for 200/201 status in it.

Sabredav sends a 418 status if the card should be delete. The Code:

                      if (propstats) {
                          for (let propstat of propstats) {
                              let statusTag = propstat["status"];
                              let itemStatus  = statusTag[0].substr(9, 3);
                              if ((itemStatus == "200"
                                   || itemStatus == "201")
                                  && href != this.gURL) {
                                  handleAddOrModify(key, itemStatus, propstat);
                              }
                              else if (itemStatus == "418" && href != this.gURL) {
                                this.serverDeletes.push(key);
                              }
                          }
                      }

works for me.

Can you please open a pull request for this on https://github.com/inverse-inc/sogo-connector.tb31?

Confirmed also with NextCloud. Setup:

• Thunderbird 52.4.0 (32-Bit)
• Inverse SOGo Connector 31.0.5
• NextCloud 12.0.3 on CentOS 7.4.1708 (Core) x86_64

@digidax
What are you confirming?
The bug, the return code on deletion requests or that the proposed fix works?

https://github.com/inverse-inc/sogo-connector.tb31/commit/26140bc19cf53e68b4ebe355894b9108bfec6ff0