Re: [SOGo] ThunderBird limiting contacts to two email addresses, sync risk?
On 03/09/13 18:17, Christian Mack wrote: > Hello Daniel Pocock > > > Am 2013-08-31 17:20, schrieb Daniel Pocock: >> >> Now that I've got sync working, I've realised that ThunderBird / Icedove >> address book only seems to support 2 email addresses, while some of my >> contacts have 3 addresses. >> >> Is there any risk of data loss when there is a sync of the address book >> as a whole, or a sync involving a local change to one of those contacts? >> >> All three addresses are visible for the same contacts in Evolution or >> using Android. >> > > If you change the contact in Thunderbird or SOGo, the third email > address will vanish. > This is also true for more than 2 telephone numbers. > At least it did in our tests with SOGo 1.3.x some time ago. > > So we added them in the note field. Thanks for this feedback - this leaves me feeling I should just use the connector in read-only mode for now. For extra safety, maybe read-only mode should be the default or it should require some hidden preference to enable write mode until the TB address book is more flexible? Are any other clients known to be like this? -- users@sogo.nu https://inverse.ca/sogo/lists
[SOGo] more SOGo Connector issues / observations
Just a few more observations after further testing: - Some LDAP-based users are using user@domain as their login username, the server automatically creates resources such as https://server/davical/caldav.php/u...@example.org/addressbook In Evolution, I insert that URL and it automatically converts from @ to %40 e.g. https://server/davical/caldav.php/user%40example.org/addressbook but in ThunderBird / SOGo Connector, it seems to choke, no attempt to sync, no hits in the apache.log. I can manually edit the URL to insert %40 and then it is working. - after making that change, I noticed it went into some loop continually hitting the server, getting a 401 response and never prompting for a password - I'm guessing there is some bug in the authentication/password prompt logic for scenarios where somebody changes the URL after account setup. On restarting IceDove, it prompts for the password at startup and immediately logs in correctly. - in the password prompt, it is not clear what it wants to log in to (it should mention the address book name probably) - for somebody with multiple address books, or somebody who has multiple test environments, this makes a big difference. - the password prompt appeared twice for me (I've often had that problem, even with older versions of the connector running against OGo) So, it is working, but with some improvement it could be more polished. I have seen problems in the past where Lightning/iceowl-extension went into a loop hitting the server too, I was doing a demo of Ganglia at the time and was pleased to have a real crisis to demonstrate (the Postgres SQL host running red hot on the Ganglia cluster summary page). It wasn't immediately obvious that Lightning was the culprit either but didn't take long to track it down. -- users@sogo.nu https://inverse.ca/sogo/lists
[SOGo] ThunderBird limiting contacts to two email addresses, sync risk?
Now that I've got sync working, I've realised that ThunderBird / Icedove address book only seems to support 2 email addresses, while some of my contacts have 3 addresses. Is there any risk of data loss when there is a sync of the address book as a whole, or a sync involving a local change to one of those contacts? All three addresses are visible for the same contacts in Evolution or using Android. -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] SOGO connector problems on Debian 7
On 27/08/13 14:45, Daniel Pocock wrote: > On 27/08/13 14:39, Christian Mack wrote: >> Hello Daniel Pocock >> >> >> Am 2013-08-27 13:18, schrieb Daniel Pocock: >>> I have the following setup: >>> >>> - client and server machines Debian 7 >>> - server has DAViCal >>> - client is icedove (with iceowl-extension) which is basically >>> ThunderBird 10 >>> >>> and I downloaded today's nightly SOGO Connector for ThunderBird 10 and >>> installed it. >>> >>> In the address book, I add a new "Remote Address Book" and configure the >>> DAViCal URL: >>>https://my-server/davical/caldav.php/username/home/ >>> >>> Address Book tells me "Total contacts in sogotest: 0" and I can't see >>> any of the addresses I created. >>> >>> However, >>> - my iceowl/lightning calendar is working with the same URL >>> - Evolution's address book works with the same URL - I have two clients >>> running Evolution, I was able to create an address with one of them and >>> view it from the other, but icedove still tells me there are no >>> addresses in the address book >>> >>> Should this work? Should I try another nightly build, is today's build >>> faulty or something? Or is it only working with ThunderBird 17? >>> >>> Is there any possibility that the Address Book and the Lightning client >>> can share the same server settings so that users don't have to enter the >>> URL in two places? >>> >>> Also, is there any plan for an official Debian package of SOGO Connector? >>> >> I don't know Davical at all, but address books are accessed by carddav >> not caldav. >> >> So you perhaps should use: >> https://my-server/davical/carddav.php/username/home/ > > I had thought about that myself - but there is no carddav.php in DAViCal > > Here is the DAViCal source for Debian: > http://repo.or.cz/w/davical.git/tree/HEAD:/htdocs > > Evolution seems to be able to read/write the address book through the > caldav.php URL > I've now solved this issue, SOGo Connector is working with DAViCal after all, however: a) in my initial attempt, there was only one resource username/home and it was configured for calendar entries only. Nonetheless, Evolution was able to insert vCards there. Not sure if that is a fault in Evolution or in DAViCal (or both) but other clients (such as SOGo Connector) seem to dislike that combined address book/calendar on a single URL. b) when I realised this, I created a separate resource called username/addressbook (using the DAViCal web UI). I explicitly ticked the box to make it an address book and removed the tick for allowing calendar entries. SOGo Connector is working with that resource now and I was able to insert entries in it and view them in Evolution, etc. For importing my old vCards, I found it much more convenient importing with Evolution, the icedove/Thunderbird import seems slightly more fragile. -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] debugging the SOGo connector?
On 29/08/13 19:11, Jean Raby wrote:
> On 13-08-29 1:07 PM, Daniel Pocock wrote:
>>
>> Hi,
>>
>> Is there any way to get a debug log file from the SOGo Connector?
> To get debugging output of the TB plugins, enable the javascript
> dump() function by setting this TB preference:
> browser.dom.window.dump.enabled = true
>
> And then run thunderbird from the console
> thunderbird.exe -console
Thanks, I've enabled that and now I get some debugging output
I've tried 3 versions of the URL
1. https://server/davical/caldav.php/daniel/home/
(works in TB/Lightning Calendar plugin and also works in
Evolution for contacts)
2. https://server/davical/caldav.php/daniel/
3. https://server/davical/caldav.php/
For all URLs, I see PROPFIND requests and 207 responses in the Apache
access log. Sometimes DAViCal challenges with 401 and the next log
entry is 207, so I believe SOGo connector is authenticating successfully.
On my last attempt with URL (1), the final console log output was:
server 'https://server/davical/caldav.php/daniel/home/' is not a valid
groupdav collection
I notice that one of the Android clients becomes upset because it
receives calendar and task entries from DAViCal, but Evolution seems to
be able to get the vCard entries using the same URL. Should SOGo
Connector work that way too?
*** new sync: 1
1/sync with https://server/davical/caldav.php/daniel/home/...
no interface in sogoWebDAV named {48b5bf16-e0c7-11e1-b28e-91726188709b}
no interface in sogoWebDAV named {081e31e0-a144-11d3-8c7c-00609792278c}
no interface in sogoWebDAV named {09b54ec1-d98a-49a9-bc95-3219e8b55089}
no interface in sogoWebDAV named {48b5bf16-e0c7-11e1-b28e-91726188709b}
no interface in sogoWebDAV named {9b283337-097d-4fa8-a2da-916318eaf828}
no interface in sogoWebDAV named {a430d870-df77-4502-9570-d46a8de33154}
no interface in sogoWebDAV named {85cd2640-e91e-41ac-bdca-1dbf10dc131e}
no interface in sogoWebDAV named {081e31e0-a144-11d3-8c7c-00609792278c}
no interface in sogoWebDAV named {09b54ec1-d98a-49a9-bc95-3219e8b55089}
sogoWebDAV: trapped exception: [Exception... "Component returned failure
code: 0x80040111 (NS_ERROR_NOT_AVAILABLE)
[nsIHttpChannel.responseStatus]" nsresult: "0x80040111
(NS_ERROR_NOT_AVAILABLE)" location: "JS frame ::
chrome://inverse-library/content/sogoWebDAV.js :: :: line
476" data: no]
xmlRequest: received status 499 for url:
https://server/davical/caldav.php/daniel/home/
Unacceptable status code: 499. We abort.
SCCommandSynchronizeCallback
url: https://server/davical/caldav.php/daniel/home/
code: 499
1/sync with https://server/davical/caldav.php/daniel/home/ has ended.
*** new sync: 2
2/sync with https://server/davical/caldav.php/daniel/...
no interface in sogoWebDAV named {48b5bf16-e0c7-11e1-b28e-91726188709b}
no interface in sogoWebDAV named {081e31e0-a144-11d3-8c7c-00609792278c}
no interface in sogoWebDAV named {09b54ec1-d98a-49a9-bc95-3219e8b55089}
no interface in sogoWebDAV named {48b5bf16-e0c7-11e1-b28e-91726188709b}
no interface in sogoWebDAV named {9b283337-097d-4fa8-a2da-916318eaf828}
no interface in sogoWebDAV named {a430d870-df77-4502-9570-d46a8de33154}
no interface in sogoWebDAV named {85cd2640-e91e-41ac-bdca-1dbf10dc131e}
no interface in sogoWebDAV named {081e31e0-a144-11d3-8c7c-00609792278c}
no interface in sogoWebDAV named {09b54ec1-d98a-49a9-bc95-3219e8b55089}
sogoWebDAV: trapped exception: [Exception... "Component returned failure
code: 0x80040111 (NS_ERROR_NOT_AVAILABLE)
[nsIHttpChannel.responseStatus]" nsresult: "0x80040111
(NS_ERROR_NOT_AVAILABLE)" location: "JS frame ::
chrome://inverse-library/content/sogoWebDAV.js :: :: line
476" data: no]
xmlRequest: received status 499 for url:
https://server/davical/caldav.php/daniel/
Unacceptable status code: 499. We abort.
SCCommandSynchronizeCallback
url: https://server/davical/caldav.php/daniel/
code: 499
2/sync with https://server/davical/caldav.php/daniel/ has ended.
*** new sync: 3
3/sync with https://server/davical/caldav.php/...
no interface in sogoWebDAV named {48b5bf16-e0c7-11e1-b28e-91726188709b}
no interface in sogoWebDAV named {081e31e0-a144-11d3-8c7c-00609792278c}
no interface in sogoWebDAV named {09b54ec1-d98a-49a9-bc95-3219e8b55089}
SCCommandSynchronizeCallback
url: https://server/davical/caldav.php/
code: 207
3/sync with https://server/davical/caldav.php/ has ended.
--
users@sogo.nu
https://inverse.ca/sogo/lists
[SOGo] debugging the SOGo connector?
Hi, Is there any way to get a debug log file from the SOGo Connector? Regards, Daniel -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] SOGO connector problems on Debian 7
Can anybody else comment on this for icedove and/or with DAViCal server? On 27/08/13 14:45, Daniel Pocock wrote: > On 27/08/13 14:39, Christian Mack wrote: >> Hello Daniel Pocock >> >> >> Am 2013-08-27 13:18, schrieb Daniel Pocock: >>> I have the following setup: >>> >>> - client and server machines Debian 7 >>> - server has DAViCal >>> - client is icedove (with iceowl-extension) which is basically >>> ThunderBird 10 >>> >>> and I downloaded today's nightly SOGO Connector for ThunderBird 10 and >>> installed it. >>> >>> In the address book, I add a new "Remote Address Book" and configure the >>> DAViCal URL: >>>https://my-server/davical/caldav.php/username/home/ >>> >>> Address Book tells me "Total contacts in sogotest: 0" and I can't see >>> any of the addresses I created. >>> >>> However, >>> - my iceowl/lightning calendar is working with the same URL >>> - Evolution's address book works with the same URL - I have two clients >>> running Evolution, I was able to create an address with one of them and >>> view it from the other, but icedove still tells me there are no >>> addresses in the address book >>> >>> Should this work? Should I try another nightly build, is today's build >>> faulty or something? Or is it only working with ThunderBird 17? >>> >>> Is there any possibility that the Address Book and the Lightning client >>> can share the same server settings so that users don't have to enter the >>> URL in two places? >>> >>> Also, is there any plan for an official Debian package of SOGO Connector? >>> >> I don't know Davical at all, but address books are accessed by carddav >> not caldav. >> >> So you perhaps should use: >> https://my-server/davical/carddav.php/username/home/ > I had thought about that myself - but there is no carddav.php in DAViCal > > Here is the DAViCal source for Debian: > http://repo.or.cz/w/davical.git/tree/HEAD:/htdocs > > Evolution seems to be able to read/write the address book through the > caldav.php URL > -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] SOGO connector problems on Debian 7
On 27/08/13 14:39, Christian Mack wrote: > Hello Daniel Pocock > > > Am 2013-08-27 13:18, schrieb Daniel Pocock: >> I have the following setup: >> >> - client and server machines Debian 7 >> - server has DAViCal >> - client is icedove (with iceowl-extension) which is basically >> ThunderBird 10 >> >> and I downloaded today's nightly SOGO Connector for ThunderBird 10 and >> installed it. >> >> In the address book, I add a new "Remote Address Book" and configure the >> DAViCal URL: >>https://my-server/davical/caldav.php/username/home/ >> >> Address Book tells me "Total contacts in sogotest: 0" and I can't see >> any of the addresses I created. >> >> However, >> - my iceowl/lightning calendar is working with the same URL >> - Evolution's address book works with the same URL - I have two clients >> running Evolution, I was able to create an address with one of them and >> view it from the other, but icedove still tells me there are no >> addresses in the address book >> >> Should this work? Should I try another nightly build, is today's build >> faulty or something? Or is it only working with ThunderBird 17? >> >> Is there any possibility that the Address Book and the Lightning client >> can share the same server settings so that users don't have to enter the >> URL in two places? >> >> Also, is there any plan for an official Debian package of SOGO Connector? >> > I don't know Davical at all, but address books are accessed by carddav > not caldav. > > So you perhaps should use: > https://my-server/davical/carddav.php/username/home/ I had thought about that myself - but there is no carddav.php in DAViCal Here is the DAViCal source for Debian: http://repo.or.cz/w/davical.git/tree/HEAD:/htdocs Evolution seems to be able to read/write the address book through the caldav.php URL -- users@sogo.nu https://inverse.ca/sogo/lists
[SOGo] SOGO connector problems on Debian 7
Hi, I have the following setup: - client and server machines Debian 7 - server has DAViCal - client is icedove (with iceowl-extension) which is basically ThunderBird 10 and I downloaded today's nightly SOGO Connector for ThunderBird 10 and installed it. In the address book, I add a new "Remote Address Book" and configure the DAViCal URL: https://my-server/davical/caldav.php/username/home/ Address Book tells me "Total contacts in sogotest: 0" and I can't see any of the addresses I created. However, - my iceowl/lightning calendar is working with the same URL - Evolution's address book works with the same URL - I have two clients running Evolution, I was able to create an address with one of them and view it from the other, but icedove still tells me there are no addresses in the address book Should this work? Should I try another nightly build, is today's build faulty or something? Or is it only working with ThunderBird 17? Is there any possibility that the Address Book and the Lightning client can share the same server settings so that users don't have to enter the URL in two places? Also, is there any plan for an official Debian package of SOGO Connector? Regards, Daniel -- users@sogo.nu https://inverse.ca/sogo/lists
