import .vcf file in contacts
systux last edited by systux
Is there a way to import contacts in kopano ? I have a .vcf file from thunderbird with
lots of addresses that needs to be imported . The “Import to folder” menu item for attachments suggets it should be possible , but actual results of that import are rather disappointing.
It shows a file in contacts , containg the content of the .vcf file, which is nice , but rather useles.
Hi @systux ,
as an admin you can easily import such data through python-kopano. An example script can be found at https://stash.kopano.io/projects/KC/repos/kopanocore/browse/swig/python/kopano/scripts/import_rfc.py
The “Import to folder” menu item for attachments suggets it should be possible , but actual results of that import are rather disappointing.
I’m sure my webapp colleges would be happy if you could elaborate on that a bit. Importing vcf files is something that was recently being worked on as far as I remember.
mcostan last edited by
Otherwise another easy way that I use without having to run a command is to email yourself the contacts on an Android phone (perhaps it works on iPhone) and provided you have z-push installed, you can just import the contacts in that account, and they will make their way back to Kopano via z-push. Works perfectly.
I was looking for such a solution, too. I stumbled over this thread but unfortunately it didn’t work for me, neither with the “right-click onto a .vcf file” --> “import” within WebApp and nor with the suggested python script. My .vcf contains about 30 contacts in this syntax:
BBEGIN:VCARD VERSION:3.0 FN:George Penny (nickname) N:Penny (nickname);George;;; EMAIL;TYPE=HOME:email@example.com ADR;TYPE=HOME,PREF:;;Example St. 1;Berlin;;12345;DE END:VCARD BEGIN:VCARD VERSION:3.0 FN:John Doe N:Doe;John;;; BDAY:1950-01-01 EMAIL;TYPE=HOME:firstname.lastname@example.org EMAIL;TYPE=HOME:email@example.com END:VCARD [ ...] and so on ...
if you import this .vcf file only the first contact is imported into Kopano WebApp, the rest is ignored.
any clues how to fix that?
Thanks for feedback. Workaround will be funny if you want to this for 300 contacts :) so I guess we need to wait for the implementation as suggested on the ticket you showed me.