| Summary | Kolab backend and virtual address books |
| Queue | Turba |
| Queue Version | Git master |
| Type | Bug |
| State | Assigned |
| Priority | 1. Low |
| Owners | Horde Developers (at) |
| Requester | thomas.jarosch (at) intra2net (dot) com |
| Created | 12/13/2012 (4535 days ago) |
| Due | |
| Updated | 01/18/2016 (3404 days ago) |
| Assigned | 01/18/2016 (3404 days ago) |
| Resolved | |
| Milestone | |
| Patch | No |
State ⇒ Unconfirmed
2013-01-16T10:23:07+01:00 ERR: HORDE [turba] Mailbox already exists
[pid 3153 on line 773 of "/datastore/share/pear/Horde/Share/Kolab.php"]
2013-01-16T10:23:07+01:00 EMERG: HORDE [turba] Mailbox already exists
[pid 3153 on line 666 of
"/datastore/share/pear/www/horde/turba/lib/Turba.php"]
Note: This is not from git HEAD
State ⇒ Feedback
when one saves a search query as "virtual" address book, the share
actually gets created on the server. Judging from the code, this
seems to be desired(?). One can even share this virtual address book
to other users, but it does not show anything useful for them.
share it with has permissions to any of the address book(s) that
contain the search results. At least that's how it used to work when
it was first implemented...
Priority ⇒ 1. Low
Type ⇒ Bug
Summary ⇒ Kolab backend and virtual address books
Queue ⇒ Turba
Milestone ⇒
Patch ⇒ No
State ⇒ Unconfirmed
when one saves a search query as "virtual" address book, the share
actually gets created on the server. Judging from the code, this seems
to be desired(?). One can even share this virtual address book to
other users, but it does not show anything useful for them.
Anyhow, if you specify a share name that already exists (user wanted
to update the search), you'll get the white screen of death saying
"Mailbox already exists".
As a quick workaround I've patched out virtual address books for my users.
Thomas