View Issue Details

IDProjectCategoryView StatusLast Update
0004476SOGo Connectorwith SOGopublic2018-06-07 16:42
Reporterhugolin69 Assigned To 
PriorityhighSeveritymajorReproducibilityalways
Status newResolutionopen 
Platform[Client] MicrosoftOSWindowsOS Version7
Product Version31.0.5 
Summary0004476: CardDav Server Synology + SoGo 31.0.5 + Thunderbird 52.8 : 403 Error when adding contact
Description

Hi,

I spent a long long time trying to use CardDav Server + SoGo + Thunderbird.
I have 20.000 contacts ++

I manage to make it work a bit with :

Sogo Connector installed
Lightning extension installed
URL : http://xx.xx.xx.xx:port/addressbooks/users/MYUSER/addressbook/

I upload a VCF file into the Syno CardDav server to upload all my contact.

Then I created an empty contact list, but have to use the external IP adress instead of a DNS name, I do not know why, but seems he can not sync with a DNS name, even if he asked the password. Idem if I try to use HTTPs, with the DNS name it do nothing except asking the password (My certificate is valid) or If I use the IP, and accept the fact that the certificate is not valid for the IP, it does not sync.

This is the first problem, I can not use HTTPs, and/or DNS Name.

With HTTP & IP address, it is working for downloading, editing or deleting contact.
BUT, it does not work for creating contact.
I have A 403 Error like this :

Avertissement : « nsIOService::NewChannelFromURI() » est obsolète, veuillez utiliser « nsIOService::NewChannelFromURI2() » sogoWebDAV.js:174:22

PUT http://xx.xx.xx.xx:xxxx/addressbooks/users/MYUSER/addressbook/C8017251-3360-0001-C411-C69071F01DFE.vcf [HTTP/1.1 403 Forbidden 71 ms]

Upload failure uploading card: http://xx.xx.xx.xx:xxxx/addressbooks/users/MYUSER/addressbook/C8017251-3360-0001-C411-C69071F01DFE.vcf.

HTTP Status Code:403

  • card properties:
    0 prop: [xpconnect wrapped nsIProperty]; name: DisplayName; value: test@test.com
    1 prop: [xpconnect wrapped nsIProperty]; name: RecordKey; value: 151905
    2 prop: [xpconnect wrapped nsIProperty]; name: PreferMailFormat; value: 0
    3 prop: [xpconnect wrapped nsIProperty]; name: DbRowID; value: 29607
    4 prop: [xpconnect wrapped nsIProperty]; name: groupDavVersion; value: -1
    5 prop: [xpconnect wrapped nsIProperty]; name: groupDavVersionPrev; value: -1
    6 prop: [xpconnect wrapped nsIProperty]; name: PopularityIndex; value: 0
    7 prop: [xpconnect wrapped nsIProperty]; name: PhotoType; value: generic
    8 prop: [xpconnect wrapped nsIProperty]; name: LowercasePrimaryEmail; value: test@test.com
    9 prop: [xpconnect wrapped nsIProperty]; name: FirstName; value: test@test.com
    10 prop: [xpconnect wrapped nsIProperty]; name: groupDavKey; value: C8017251-3360-0001-C411-C69071F01DFE.vcf
    11 prop: [xpconnect wrapped nsIProperty]; name: CardUID; value: C8017251-3360-0001-C411-C69071F01DFE.vcf
    12 prop: [xpconnect wrapped nsIProperty]; name: PrimaryEmail; value: test@test.com
    13 prop: [xpconnect wrapped nsIProperty]; name: LastModifiedDate; value: 1527669572
    14 prop: [xpconnect wrapped nsIProperty]; name: PreferDisplayName; value: 1
  • done

I saw in a request, that the VCARD sent seems not having parameters N & FN.
Maybe this is the problem.

TagsNo tags attached.

Activities

hugolin69

hugolin69

2018-06-07 16:42

reporter   ~0012910

Could it be related to contact which have no firstname / lastname / displayname ?

Issue History

Date Modified Username Field Change
2018-06-07 14:23 hugolin69 New Issue
2018-06-07 16:42 hugolin69 Note Added: 0012910