Closed pbiering closed 7 years ago
This is not in the RFC. Does SOGo Connector still work, if you change VLIST
to VCALENDAR
manually?
If it works we can just add something like the following to check_and_sanitize_item
in storage.py
:
if vobject_item.name == "VLIST":
vobject_item.name = "VCALENDAR"
Sorry, did not understand, the problematic vlf file (address group) is stored in the same "FOLDER.vcf" where all my other vcf files are stored -> why/what should I change to VCALENDAR then?
BEGIN:VLIST
to BEGIN:VCALENDAR
and END:VLIST
to END:VCALENDAR
in file created by SOGo Connector. Does SOGo Connector still recognize the event or does it break in any way?
It's not an event, it (was) SOGo connector for the addressbook (dedicated URL), not for the calendar.
But probably SOGo addressbook connector is buggy here and use not compliant VLIST.
I have SOGo addressbook connector anyhow replaced with CardBook since some time - created now a new list of contacts and it looks like the format is totally different:
BEGIN:VCARD
VERSION:3.0
UID:***
FN:TestListe
N:;;;;
REV:20170719T225210Z
X-ADDRESSBOOKSERVER-KIND:group
X-ADDRESSBOOKSERVER-MEMBER:urn:uuid:***.vc
f
X-THUNDERBIRD-ETAG:0
END:VCARD
I hope this is according to standard...at least radicale stored it without complains.
=> if VLIST is non-standard, then probably that issue can be closed without a resolution.
It's not an event, it (was) SOGo connector for the addressbook (dedicated URL), not for the calendar.
I've no idea how I came to the conclusion that it is an event.
But probably SOGo addressbook connector is buggy here and use not compliant VLIST.
VLIST is a custom format of SOGo Connector for a list of contacts.
I am getting the same error "An exception occurred during PROPFIND request on ....... Failed to parse item ....." in the Radicale log while syncing contacts between 3 clients (2 computers and 1 phone). It started recently (in the past couple of weeks) even though I have not changed Radicale nor Python versions in a few months. So it could be a Windows update. But not sure. Any idea?
Is there a way to add a timestamp to the entries in the log with some option? It would help to know when something has happened.
After migration to radicale-2.1.1 it turns out that VLIST is not supported (anymore):
contents of such VLIST