Tickets :: [#12861] Kolab backend: Foreign contacts cause distribution list to vanish

6.0.0-beta1

7/19/25

Summary	Kolab backend: Foreign contacts cause distribution list to vanish
Queue	Turba
Queue Version	Git master
Type	Bug
State	Not A Bug
Priority	1. Low
Owners	jan (at) horde (dot) org
Requester	thomas.jarosch (at) intra2net (dot) com
Created	11/22/2013 (4257 days ago)
Due
Updated	03/07/2014 (4152 days ago)
Assigned	03/06/2014 (4153 days ago)
Resolved	03/06/2014 (4153 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch	No

03/07/2014 11:04:37 AM	Git Commit	Comment #10	Reply to this comment
Changes have been made in Git (master): commit 7604602d4828f47b00de6af305796d033c9a410d Author: Jan Schneider <jan@horde.org> Date: Fri Mar 7 12:01:13 2014 +0100 [jan] Don't remove missing contacts from distributions lists in Kolab backends (~~Bug #12861~~). turba/docs/CHANGES \| 2 ++ turba/package.xml \| 2 ++ 2 files changed, 4 insertions(+), 0 deletions(-) http://git.horde.org/horde-git/-/commit/7604602d4828f47b00de6af305796d033c9a410d

03/06/2014 01:15:38 PM	Thomas Jarosch	Comment #9	Reply to this comment
-> turba strips down the distribution list to existing contacts only. This is correct and intended behavior. Turba distribution lists cannot be mapped one-to-one to Kolab distribution lists. In Turba list members are links to existing contacts, in Kolab members are simple name/email entries. Contacts that can not (longer) be found, will be removed from a distribution list. can't we just keep the unknown ones (in the Kolab driver) for now? I'm pretty sure there will be some users that will be quite angry when we silently remove entries. I know at least one user that organizes large contact groups via distribution lists in another Kolab client. If you want to, you can go on with the release, but this should definitely be resolved in the next release. The same problem occurs when you add a contact from a different addressbook to a distribution list. It's simply not added, probably the same problem. See ~~bug #12860~~ thanks, working!

03/06/2014 12:59:48 PM	Jan Schneider	Comment #8 State ⇒ Not A Bug	Reply to this comment
[Show Quoted Text - 15 lines][Hide Quoted Text] Currently testing with FRAMEWORK_5_1. The behavior changed a bit, but it's still trashing data: Steps to reproduce: - create two contacts - Add these two contacts to a new distribution list - Delete one contact (you can see on the IMAP server that it's still part of the dist list) - Log out - Clear Kolab cache (so everything has to be re-parsed) - Log in - Click on "Edit/View Group Members" of the distribution list -> turba strips down the distribution list to existing contacts only. This is correct and intended behavior. Turba distribution lists cannot be mapped one-to-one to Kolab distribution lists. In Turba list members are links to existing contacts, in Kolab members are simple name/email entries. Contacts that can not (longer) be found, will be removed from a distribution list. The same problem occurs when you add a contact from a different addressbook to a distribution list. It's simply not added, probably the same problem. See ~~bug #12860~~

03/06/2014 11:55:06 AM	Thomas Jarosch	Comment #7 State ⇒ Assigned	Reply to this comment
Currently testing with FRAMEWORK_5_1. The behavior changed a bit, but it's still trashing data: Steps to reproduce: - create two contacts - Add these two contacts to a new distribution list - Delete one contact (you can see on the IMAP server that it's still part of the dist list) - Log out - Clear Kolab cache (so everything has to be re-parsed) - Log in - Click on "Edit/View Group Members" of the distribution list -> turba strips down the distribution list to existing contacts only. The same problem occurs when you add a contact from a different addressbook to a distribution list. It's simply not added, probably the same problem.

03/06/2014 09:04:52 AM	Thomas Jarosch	Comment #6	Reply to this comment
Still cannot reproduce. I'll retry with the current code in master. (once my git devel VM is up and running again today)

03/05/2014 05:03:34 PM	Jan Schneider	Comment #5 State ⇒ Not A Bug	Reply to this comment
Still cannot reproduce.

11/23/2013 12:59:27 PM	Jan Schneider	Comment #4	Reply to this comment
[Show Quoted Text - 9 lines][Hide Quoted Text] I cannot reproduce this. I don't even have a caching backend configured, and whether I delete a distribution list's contact from Turba or directly on the IMAP server, the list still works fine. please try again after clearing your horde cache. IIRC the Kolab IMAP code always caches. Or is $conf['cache'] completely disabled on your box? Yes it is

11/22/2013 03:04:34 PM	Thomas Jarosch	Comment #3	Reply to this comment
I cannot reproduce this. I don't even have a caching backend configured, and whether I delete a distribution list's contact from Turba or directly on the IMAP server, the list still works fine. please try again after clearing your horde cache. IIRC the Kolab IMAP code always caches. Or is $conf['cache'] completely disabled on your box?

11/22/2013 02:48:19 PM	Jan Schneider	Comment #2 State ⇒ Feedback	Reply to this comment
I cannot reproduce this. I don't even have a caching backend configured, and whether I delete a distribution list's contact from Turba or directly on the IMAP server, the list still works fine.

11/22/2013 02:36:00 PM	Thomas Jarosch	Summary ⇒ Kolab backend: Foreign contacts cause distribution list to vanish

11/22/2013 02:33:30 PM	Thomas Jarosch	State ⇒ Assigned Assigned to Jan Schneider

11/22/2013 02:32:59 PM	Thomas Jarosch	Comment #1 Priority ⇒ 1. Low State ⇒ Unconfirmed Patch ⇒ No Milestone ⇒ Summary ⇒ Kolab backend: Foreign contacts case distribution list to vanish Type ⇒ Bug Queue ⇒ Turba	Reply to this comment
Hi, when turba encounters a distribution list that contains a contact that is not present in the current addressbook, the distribution is not shown at all. Steps to reproduce: - create two contacts - Add these two contacts to a new distribution list - Delete one contact - Log out - Clear Kolab cache (so everything has to be re-parsed) - Log in -> Distribution list is not shown anymore. Note: A distribution list can contain an unlimited amount of members which necessarily don't have to be valid contact objects. Cheers, Thomas