Field "X-messaging/xmpp-All" make synchronization fail
WhyNotHugo opened this issue · comments
First of all, let me clarify that I'm testing pycarddav against radicale
When trying to sync my contacts, I get the following output:
$ pycardsyncer
DEBUG:root:Ignoring query:where in configuration file
DEBUG:root:Ignoring default:debug in configuration file
DEBUG:root:Using configuration:
DEBUG:root: accounts:
DEBUG:root: auth: basic
DEBUG:root: name: personal
DEBUG:root: resource: https://radicale.ubertech.com.ar/hugo/contacts.vcf/
DEBUG:root: user: hugo
DEBUG:root: verify: False
DEBUG:root: write_support: False
DEBUG:root: debug: True
DEBUG:root: filename: /home/hugo/.config/pycard/pycard.conf
DEBUG:root: sqlite:
DEBUG:root: path: /home/hugo/.local/share/pycard/abook.db
DEBUG:root: sync:
DEBUG:root: accounts: set(['personal'])
DEBUG:root:start syncing account personal
DEBUG:root:made sure version table exists
DEBUG:root:made sure accounts table exists
DEBUG:root:made sure personal table exists
DEBUG:root:getting /hugo/contacts.vcf/3hrIR5ryD4.vcf etag: "-6083307714833282769"
ERROR:root:VCard /hugo/contacts.vcf/3hrIR5ryD4.vcf could not be inserted into the db
DEBUG:root:At line 10: Failed to parse line: X-messaging/xmpp-All:john.doe@example.com
INFO:root:BEGIN:VCARD
EMAIL:john.doe@example.com
FN:John Doe
N:Doe;John;;;
TEL;TYPE=CELL:+54 11 4444 5555
UID:3hrIR5ryD4
VERSION:3.0
X-KADDRESSBOOK-X-IMAddress:john.doe@example.com
X-RADICALE-NAME:3hrIR5ryD4.vcf
X-messaging/xmpp-All:john.doe@example.com
END:VCARD
DEBUG:root:getting /hugo/contacts.vcf/xTxaFPE9XK.vcf etag: "-2874737880983195933"
[...]
I've replaced the personal details of my contact, but (obviously), kept the general format as-is.
There should be nothing wrong with the "X-messaging/xmpp-All", and, AFAIK, it's as-per standards.
RFC2426 specifies "x-names" as:
x-name = "X-" 1*(ALPHA / DIGIT / "-")
and I guess vobject is rather strict in what it allows. Therefore this won't fix here for some time, not before pycarddav switches to an icalendar (see #48 ) based vcard parser (but you can always try your luck with the vobject developers).
Oh, so it looks like the "/" is invalid. I'll try and see what app added that into my calendar and report the issue there in that case as well then - my calendar DID get non-standardized! :(