6.0.0-RC7
6/29/26

[#1219] Nag and Kronolith don't show any data on a Kolab account
Summary Nag and Kronolith don't show any data on a Kolab account
Queue Horde Framework Packages
Queue Version HEAD
Type Bug
State Resolved
Priority 1. Low
Owners stuart (at)
Requester a.gungl (at) gmx (dot) de
Created 1/21/05 (7829 days ago)
Due
Updated 2/4/05 (7815 days ago)
Assigned 1/21/05 (7829 days ago)
Resolved 2/4/05 (7815 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch No

History
307 Chuck Hagenbuch Comment #4
State ⇒ Resolved
Reply to this comment
Resolving per user.
187 a (dot) gungl (at) gmx (dot) de Comment #3 Reply to this comment
IMO the ticket can get closed. Other commits made Horde working with 
respect to the described problem.
301 a (dot) gungl (at) gmx (dot) de Comment #2 Reply to this comment
I played a little bit more with my accounts. Although I don't have a 
reproducible pattern at hand, I believe that this issue is bound to 
the way how the user authenticates. So it may be related to #1220
because I can work quite fine without the proposed adjustment if I 
have everything in shape to login with my mail address (user@domain). 
However if I login with my Kolab uid (user), I can't see the data.

The modification of the ACLs is no longer reproducable with this account.
22 Chuck Hagenbuch Assigned to stuart
State ⇒ Assigned
 
232 Chuck Hagenbuch Queue ⇒ Horde Framework Packages
 
502 a (dot) gungl (at) gmx (dot) de Comment #1
State ⇒ Unconfirmed
Priority ⇒ 1. Low
Type ⇒ Bug
Summary ⇒ Nag and Kronolith don't show any data on a Kolab account
Queue ⇒ Horde Base
Reply to this comment
The handling of ACLs is broken. If you delete these lines in Kolab.php 
in function synchroniseShare():



         foreach ($acl as $user => $user_acl) {

              $result = $imap->deleteACL($folder_name, $user);

              if (is_a($result, 'PEAR_Error')) {

                  return $result;

              }

          }



you can use Kronolith and Nag with Kolab to inspect your data.

Saved Queries