Address Already Exists using icon web link

We are testing with the -rc2 releases of horde, IMP and Turb

Fri, 29 Feb 2008 17:42:26 +0000

We are testing with the -rc2 releases of horde, IMP and Turba (specific list is below). We can receive, read, compose and send email and add, remove & edit entries in our private address book with no problems. However, when reading an email and you click on the icon next to an address in the display (see example link below) to add that address to your default address book that already has one or more entries, we always get the response 'Already Exists' and the address is not added, even though the address is not in the address book. This error only happens after the first address has been added to the address book. There is no problem with an empty address book. The horde.log shows this when it happens Feb 28 10:59:43 HORDE [debug] [imp] Already Exists: 20080227151906.190021pmhi65hbyi@mail.comehome.net [pid 1244 on line 176 of ".../horde/lib/Horde/Notification.php"] --- example link --- --- Horde/IMP/Turba versions --- Horde 3.2-rc2 IMP 4.2-rc2 Turba 2.2-rc2

Can you add new contacts from Turba? What backend are you us

Fri, 29 Feb 2008 22:08:33 +0000

Can you add new contacts from Turba? What backend are you using in Turba?

> Can you add new contacts from Turba? What backend are you

Sat, 01 Mar 2008 10:21:17 +0000

> Can you add new contacts from Turba? What backend are you using in Turba? Chuck, I apologize if I left that out of the original bug description. Yes, we can add, delete and edit address entries with no problem as long as we are using the Turba menus and forms. In fact it was after I had my default address book with 4 entries that we tested the envelope icon link to add an address and that was when we discovered the issue. We are using the LDAP backend. But since we can add, edit and delete using the normal Turba interface, that did not seem to be the problem. Thanks again for looking into this. I gave it a shot at figuring it out myself, but all my experience is with perl and php syntax is close enough, but different enough, to make it incredibly misleading.

FYI, I have just upgraded our code to rc3 (horde 3.2, imp 4.

Mon, 24 Mar 2008 20:24:40 +0000

FYI, I have just upgraded our code to rc3 (horde 3.2, imp 4.2 & turba 2.2) and the problem is still with us. We are using the openLDAP backend. And there are no problems with adding addresses with turba/add.php web page. It is only when there are any addresses in the private address book that adding ANY address using the addressbook_add iconic links when you are reading emails fails with the error "Already exists". A specific example...clicking on the link below with an address (NOT cberry) in the Private address book gives a response "Already exists" and the address is NOT added. If I remove the existing address from the Private address book, clicking on the link works fine. But then adding any other addresses via the addressbook_add link fails after that because the cberry address has been added.

And is searching working properly with your address book set

Fri, 04 Apr 2008 10:09:29 +0000

And is searching working properly with your address book setup? E.g. if you use the autocomplete feature in IMP's compose screen, does it really only return matching contacts?

> And is searching working properly with your address book s

Fri, 04 Apr 2008 16:11:10 +0000

> And is searching working properly with your address book setup? E.g. > if you use the autocomplete feature in IMP's compose screen, does it > really only return matching contacts? Good question. No. When I start to enter an address in the compose form it lists ALL contacts but the contact that is a match IS highlighted in bold text. for example, if I type "my" in the To field I see: addr1 addr2 myaddr (with "my" in bold text) xaddr yaddr zaddr

That explains it. If everything is correct with your LDAP se

Fri, 04 Apr 2008 20:43:15 +0000

That explains it. If everything is correct with your LDAP server, then you probably have some broken setup in sources.php. How does the entry for your LDAP look like. And actually this is probably rather a support request now the belongs on the mailing list. If you find a bug in the searching, we can re-open the bug ticket.

> That explains it. If everything is correct with your LDAP

Mon, 07 Apr 2008 13:06:49 +0000

> That explains it. If everything is correct with your LDAP server, > then you probably have some broken setup in sources.php. How does the > entry for your LDAP look like. > And actually this is probably rather a support request now the > belongs on the mailing list. If you find a bug in the searching, we > can re-open the bug ticket. Jan, thanks for the info. After looking again at my sources.php in turba/config I agree that is probably it. I took the fast/easy way and used the preferences-based address book. And now I see the note that these are not searchable. Good thing this was caught before we started production use of the system. Thanks and we can close this ticket. Sorry for the confusion. -- Andy Dorman Ironic Design, Inc. AnteSpam.com