Summary | Turba removes instant messenger data |
Queue | Turba |
Queue Version | FRAMEWORK_5_2 |
Type | Bug |
State | Duplicate |
Priority | 1. Low |
Owners | |
Requester | ramack (at) raphael-mack (dot) de |
Created | 11/10/2017 (2767 days ago) |
Due | |
Updated | 11/12/2017 (2765 days ago) |
Assigned | |
Resolved | 11/12/2017 (2765 days ago) |
Github Issue Link | |
Github Pull Request | |
Milestone | |
Patch | No |
State ⇒ Duplicate
Priority ⇒ 1. Low
State ⇒ Unconfirmed
Priority ⇒ 2. Medium
Type ⇒ Bug
Summary ⇒ Turba removes instant messenger data
Queue ⇒ Turba
Milestone ⇒
Patch ⇒ No
it to horde turba via CardDAV, the entry magically is lost after the
sync. It seems, that horde / Turba uses
X-WV-ID:xxxxxxx@jabber.de
in the card data, while
IMPP;TYPE=WORK;X-SERVICE-TYPE=jabber:xxxxxxx@jabber.de
seems to be standard. It would be great, if you could make the instant
messenger field in turba such that the service is selectable and use
IMPP in the card to allow sync.
I can provide more data if you tell me how to gather it or what to try.
Regards,
Rapha