[Davical-general] CardDAV and SOGo Connector

classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

[Davical-general] CardDAV and SOGo Connector

Marc Patermann
Hi,

I connected an iPhone successfully to Davical 1.0.2 with CardDAV.
Now I tried with Thunderbird 10 ESR, Lightning and SOGo Connector.

On Thunderbird startup there is a connection to davical which is
responded to with 207:

192.168.178.20 - - [18/Jul/2012:17:31:42 +0200] "PROPFIND
/davical/caldav.php/[hidden email]/addresses/ HTTP/1.1" 401 60
"-" "Mozilla/5.0 (X11; Linux x86_64; rv:10.0.4) Gecko/20120421
Thunderbird/10.0.4 Lightning/1.2.1"
192.168.178.20 - [hidden email] [18/Jul/2012:17:31:58 +0200]
"PROPFIND /davical/caldav.php/[hidden email]/addresses/
HTTP/1.1" 207 435 "-" "Mozilla/5.0 (X11; Linux x86_64; rv:10.0.4)
Gecko/20120421 Thunderbird/10.0.4 Lightning/1.2.1"

Here is the davical log:

[Wed Jul 18 17:31:58 2012] [error] [client 192.168.178.20] davical: LOG:
:Response status 207 for PROPFIND
/davical/caldav.php/[hidden email]/addresses/
[Wed Jul 18 17:31:58 2012] [error] [client 192.168.178.20] davical: LOG:
:***************** Response Header ****************
[Wed Jul 18 17:31:58 2012] [error] [client 192.168.178.20] davical: LOG:
headers:-->X-Powered-By: PHP/5.2.6
[Wed Jul 18 17:31:58 2012] [error] [client 192.168.178.20] davical: LOG:
headers:-->Server: 1.1
[Wed Jul 18 17:31:58 2012] [error] [client 192.168.178.20] davical: LOG:
headers:-->DAV: 1, 2, 3, access-control, calendar-access, calendar-schedule
[Wed Jul 18 17:31:58 2012] [error] [client 192.168.178.20] davical: LOG:
headers:-->DAV: extended-mkcol, bind, addressbook, calendar-proxy
[Wed Jul 18 17:31:58 2012] [error] [client 192.168.178.20] davical: LOG:
headers:-->ETag: "8f84b9690ca34fbfcecd9c394e4d9d65"
[Wed Jul 18 17:31:58 2012] [error] [client 192.168.178.20] davical: LOG:
headers:-->X-DAViCal-Version: DAViCal/1.1.0; DB/1.2.11
[Wed Jul 18 17:31:58 2012] [error] [client 192.168.178.20] davical: LOG:
headers:-->Content-type: text/xml; charset="utf-8"
[Wed Jul 18 17:31:58 2012] [error] [client 192.168.178.20] davical: LOG:
:******************** Response ********************
[Wed Jul 18 17:31:58 2012] [error] [client 192.168.178.20] davical: LOG:
response:--><?xml version="1.0" encoding="utf-8" ?>
[Wed Jul 18 17:31:58 2012] [error] [client 192.168.178.20] davical: LOG:
response:--><multistatus xmlns="DAV:"
xmlns:C="urn:ietf:params:xml:ns:carddav"
xmlns:C1="http://calendarserver.org/ns/">
[Wed Jul 18 17:31:58 2012] [error] [client 192.168.178.20] davical: LOG:
response:--> <response>
[Wed Jul 18 17:31:58 2012] [error] [client 192.168.178.20] davical: LOG:
response:-->
<href>/davical/caldav.php/testuser.1%40fa-test1.foo/addresses/</href>
[Wed Jul 18 17:31:58 2012] [error] [client 192.168.178.20] davical: LOG:
response:-->  <propstat>
[Wed Jul 18 17:31:58 2012] [error] [client 192.168.178.20] davical: LOG:
response:-->   <prop>
[Wed Jul 18 17:31:58 2012] [error] [client 192.168.178.20] davical: LOG:
response:-->    <resourcetype>
[Wed Jul 18 17:31:58 2012] [error] [client 192.168.178.20] davical: LOG:
response:-->     <collection/>
[Wed Jul 18 17:31:58 2012] [error] [client 192.168.178.20] davical: LOG:
response:-->     <C:addressbook/>
[Wed Jul 18 17:31:58 2012] [error] [client 192.168.178.20] davical: LOG:
response:-->    </resourcetype>
[Wed Jul 18 17:31:58 2012] [error] [client 192.168.178.20] davical: LOG:
response:-->    <supported-report-set>
[Wed Jul 18 17:31:58 2012] [error] [client 192.168.178.20] davical: LOG:
response:-->     <supported-report>
[Wed Jul 18 17:31:58 2012] [error] [client 192.168.178.20] davical: LOG:
response:-->      <report>
[Wed Jul 18 17:31:58 2012] [error] [client 192.168.178.20] davical: LOG:
response:-->       <principal-property-search/>
[Wed Jul 18 17:31:58 2012] [error] [client 192.168.178.20] davical: LOG:
response:-->      </report>
[Wed Jul 18 17:31:58 2012] [error] [client 192.168.178.20] davical: LOG:
response:-->     </supported-report>
[Wed Jul 18 17:31:58 2012] [error] [client 192.168.178.20] davical: LOG:
response:-->     <supported-report>
[Wed Jul 18 17:31:58 2012] [error] [client 192.168.178.20] davical: LOG:
response:-->      <report>
[Wed Jul 18 17:31:58 2012] [error] [client 192.168.178.20] davical: LOG:
response:-->       <principal-search-property-set/>
[Wed Jul 18 17:31:58 2012] [error] [client 192.168.178.20] davical: LOG:
response:-->      </report>
[Wed Jul 18 17:31:58 2012] [error] [client 192.168.178.20] davical: LOG:
response:-->     </supported-report>
[Wed Jul 18 17:31:58 2012] [error] [client 192.168.178.20] davical: LOG:
response:-->     <supported-report>
[Wed Jul 18 17:31:58 2012] [error] [client 192.168.178.20] davical: LOG:
response:-->      <report>
[Wed Jul 18 17:31:58 2012] [error] [client 192.168.178.20] davical: LOG:
response:-->       <expand-property/>
[Wed Jul 18 17:31:58 2012] [error] [client 192.168.178.20] davical: LOG:
response:-->      </report>
[Wed Jul 18 17:31:58 2012] [error] [client 192.168.178.20] davical: LOG:
response:-->     </supported-report>
[Wed Jul 18 17:31:58 2012] [error] [client 192.168.178.20] davical: LOG:
response:-->     <supported-report>
[Wed Jul 18 17:31:58 2012] [error] [client 192.168.178.20] davical: LOG:
response:-->      <report>
[Wed Jul 18 17:31:58 2012] [error] [client 192.168.178.20] davical: LOG:
response:-->       <sync-collection/>
[Wed Jul 18 17:31:58 2012] [error] [client 192.168.178.20] davical: LOG:
response:-->      </report>
[Wed Jul 18 17:31:58 2012] [error] [client 192.168.178.20] davical: LOG:
response:-->     </supported-report>
[Wed Jul 18 17:31:58 2012] [error] [client 192.168.178.20] davical: LOG:
response:-->     <supported-report>
[Wed Jul 18 17:31:58 2012] [error] [client 192.168.178.20] davical: LOG:
response:-->      <report>
[Wed Jul 18 17:31:58 2012] [error] [client 192.168.178.20] davical: LOG:
response:-->       <C:addressbook-query/>
[Wed Jul 18 17:31:58 2012] [error] [client 192.168.178.20] davical: LOG:
response:-->      </report>
[Wed Jul 18 17:31:58 2012] [error] [client 192.168.178.20] davical: LOG:
response:-->     </supported-report>
[Wed Jul 18 17:31:58 2012] [error] [client 192.168.178.20] davical: LOG:
response:-->     <supported-report>
[Wed Jul 18 17:31:58 2012] [error] [client 192.168.178.20] davical: LOG:
response:-->      <report>
[Wed Jul 18 17:31:58 2012] [error] [client 192.168.178.20] davical: LOG:
response:-->       <C:addressbook-multiget/>
[Wed Jul 18 17:31:58 2012] [error] [client 192.168.178.20] davical: LOG:
response:-->      </report>
[Wed Jul 18 17:31:58 2012] [error] [client 192.168.178.20] davical: LOG:
response:-->     </supported-report>
[Wed Jul 18 17:31:58 2012] [error] [client 192.168.178.20] davical: LOG:
response:-->    </supported-report-set>
[Wed Jul 18 17:31:58 2012] [error] [client 192.168.178.20] davical: LOG:
response:-->    <C1:getctag>"140006c70b309a14f4c9a1fb7f3d8eb4"</C1:getctag>
[Wed Jul 18 17:31:58 2012] [error] [client 192.168.178.20] davical: LOG:
response:-->   </prop>
[Wed Jul 18 17:31:58 2012] [error] [client 192.168.178.20] davical: LOG:
response:-->   <status>HTTP/1.1 200 OK</status>
[Wed Jul 18 17:31:58 2012] [error] [client 192.168.178.20] davical: LOG:
response:-->  </propstat>
[Wed Jul 18 17:31:58 2012] [error] [client 192.168.178.20] davical: LOG:
response:--> </response>
[Wed Jul 18 17:31:58 2012] [error] [client 192.168.178.20] davical: LOG:
response:--></multistatus>
[Wed Jul 18 17:31:58 2012] [error] [client 192.168.178.20] davical: LOG:
response:-->

So I think there is simply no real address data in the respond at all.
What is wrong here?


Marc

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Davical-general mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/davical-general
Reply | Threaded
Open this post in threaded view
|

Re: CardDAV and SOGo Connector

Andrew McMillan
On Wed, 2012-07-18 at 18:15 +0200, Marc Patermann wrote:
> Hi,
>
> I connected an iPhone successfully to Davical 1.0.2 with CardDAV.
> Now I tried with Thunderbird 10 ESR, Lightning and SOGo Connector.
>
> On Thunderbird startup there is a connection to davical which is
> responded to with 207:

Yes.  "207 multistatus" is the normal response code to a PROPFIND or
REPORT request (and some others also).  In fact if you see a 200
response to one of these it indicates something has gone wrong.

>
> 192.168.178.20 - - [18/Jul/2012:17:31:42 +0200] "PROPFIND /davical/caldav.php/[hidden email]/addresses/ HTTP/1.1" 401 60 "-" "Mozilla/5.0 (X11; Linux x86_64; rv:10.0.4) Gecko/20120421 Thunderbird/10.0.4 Lightning/1.2.1"
> 192.168.178.20 - [hidden email] [18/Jul/2012:17:31:58 +0200] "PROPFIND /davical/caldav.php/[hidden email]/addresses/ HTTP/1.1" 207 435 "-" "Mozilla/5.0 (X11; Linux x86_64; rv:10.0.4) Gecko/20120421 Thunderbird/10.0.4 Lightning/1.2.1"
>
> Here is the davical log:
>
> [Wed Jul 18 17:31:58 2012] [error] [client 192.168.178.20] davical: LOG:
> :Response status 207 for PROPFIND
> /davical/caldav.php/[hidden email]/addresses/
> [Wed Jul 18 17:31:58 2012] [error] [client 192.168.178.20] davical: LOG:
> :***************** Response Header ****************
> headers:-->X-Powered-By: PHP/5.2.6
> headers:-->Server: 1.1
> headers:-->DAV: 1, 2, 3, access-control, calendar-access, calendar-schedule
> headers:-->DAV: extended-mkcol, bind, addressbook, calendar-proxy
> headers:-->ETag: "8f84b9690ca34fbfcecd9c394e4d9d65"
> headers:-->X-DAViCal-Version: DAViCal/1.1.0; DB/1.2.11
> headers:-->Content-type: text/xml; charset="utf-8"
> :******************** Response ********************
> response:--><?xml version="1.0" encoding="utf-8" ?>
> response:--><multistatus xmlns="DAV:" xmlns:C="urn:ietf:params:xml:ns:carddav" xmlns:C1="http://calendarserver.org/ns/">
> response:--> <response>
> response:--> <href>/davical/caldav.php/testuser.1%40fa-test1.foo/addresses/</href>
> response:-->  <propstat>
> response:-->   <prop>
> response:-->    <resourcetype>
> response:-->     <collection/>
> response:-->     <C:addressbook/>
> response:-->    </resourcetype>
> response:-->    <supported-report-set>
> response:-->     <supported-report>
> response:-->      <report>
> response:-->       <principal-property-search/>
> response:-->      </report>
> response:-->     </supported-report>
> response:-->     <supported-report>
> response:-->      <report>
> response:-->       <principal-search-property-set/>
> response:-->      </report>
> response:-->     </supported-report>
> response:-->     <supported-report>
> response:-->      <report>
> response:-->       <expand-property/>
> response:-->      </report>
> response:-->     </supported-report>
> response:-->     <supported-report>
> response:-->      <report>
> response:-->       <sync-collection/>
> response:-->      </report>
> response:-->     </supported-report>
> response:-->     <supported-report>
> response:-->      <report>
> response:-->       <C:addressbook-query/>
> response:-->      </report>
> response:-->     </supported-report>
> response:-->     <supported-report>
> response:-->      <report>
> response:-->       <C:addressbook-multiget/>
> response:-->      </report>
> response:-->     </supported-report>
> response:-->    </supported-report-set>
> response:-->    <C1:getctag>"140006c70b309a14f4c9a1fb7f3d8eb4"</C1:getctag>
> response:-->   </prop>
> response:-->   <status>HTTP/1.1 200 OK</status>
> response:-->  </propstat>
> response:--> </response>
> response:--></multistatus>
> response:-->
>
> So I think there is simply no real address data in the respond at all.
There was not any address data requested, although in any case address
data will never be returned in response to a PROPFIND request, but this
PROPFIND request was clearly sent with a "Depth: 0" header, in order to
retrieve collection properties, rather than the properties of resources
within the collection.

In particular the value of 'getctag' has been requested, which is an
opaque token which will change when the content of the collection
changes.  Quite likely a previous request has fetched the collection
contents (probably a report) and this request is just checking that
nothing has changed.

> What is wrong here?

None of the above.

Cheers,
                                        Andrew.

--
------------------------------------------------------------------------
andrew (AT) morphoss (DOT) com                            +64(272)DEBIAN
         Flexibility is overrated.  Constraints are liberating.
------------------------------------------------------------------------


------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Davical-general mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/davical-general

signature.asc (853 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: CardDAV and SOGo Connector

Christoph Steidl
In reply to this post by Marc Patermann
hi,

--On Mittwoch, Juli 18, 2012 18:15:35 +0200 Marc Patermann
<[hidden email]> wrote:
>
> So I think there is simply no real address data in the respond at all.
> What is wrong here?

sine i know SOGo-Connector for thunderbird, and tested it with davical, it
never worked correctly!

SOGo is NO carddav i think. if i'm correctly, it does some WebDAV(?)
instead...

only way for me to use carddav-data on desktop is carddav-mate
(web-interface). as far as i know, there is no really working
carddav-implementation for desktop addressbooks.


cheers,
chris

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Davical-general mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/davical-general
Reply | Threaded
Open this post in threaded view
|

Re: CardDAV and SOGo Connector

mgia
In reply to this post by Marc Patermann
Hi,

Are you using IMAP authentication in Davical?

-
Mgia



------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Davical-general mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/davical-general
Reply | Threaded
Open this post in threaded view
|

Re: CardDAV and SOGo Connector

Marc Patermann
Mgia,

mgia schrieb (20.07.2012 14:47 Uhr):

> Are you using IMAP authentication in Davical?
No, LDAP.

Marc

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Davical-general mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/davical-general
Reply | Threaded
Open this post in threaded view
|

Re: CardDAV and SOGo Connector

mgia
Marc,

> No, LDAP.
Try using the default's Davical authentication method and check if it's
working.

-
Mgia



------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Davical-general mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/davical-general