Tickets :: [#4394] Problem with sending S/MIME encrypted mails due to multiple address books

6.0.0-beta1

9/18/25

Summary	Problem with sending S/MIME encrypted mails due to multiple address books
Queue	Turba
Queue Version	HEAD
Type	Bug
State	Resolved
Priority	2. Medium
Owners	slusarz (at) horde (dot) org
Requester	ditsa (at) ccf (dot) auth (dot) gr
Created	09/07/2006 (6951 days ago)
Due
Updated	09/08/2006 (6950 days ago)
Assigned	09/07/2006 (6951 days ago)
Resolved	09/08/2006 (6950 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch	No

09/08/2006 04:53:09 AM	Michael Slusarz	Comment #4 State ⇒ Resolved	Reply to this comment
Fixed for Turba 2.1.3. You will also need the latest IMP (4.1.4+) to see this fix.

09/08/2006 04:52:16 AM	Michael Slusarz	Comment #3 Version ⇒ HEAD Queue ⇒ Turba State ⇒ Priority ⇒ 2. Medium	Reply to this comment
This is actually an issue with the getField API call in turba. Added an option to return multiple entries - and in IMP we will just ignore the extra entries.

09/07/2006 05:05:43 PM	Chuck Hagenbuch	Comment #2 State ⇒ Feedback Assigned to Michael Slusarz	Reply to this comment
Michael would know. Michael? :)

09/07/2006 05:05:21 PM	Chuck Hagenbuch	Version ⇒ HEAD Queue ⇒ IMP

09/07/2006 01:05:31 PM	ditsa (at) ccf (dot) auth (dot) gr	Comment #1 Priority ⇒ 1. Low Type ⇒ Bug Summary ⇒ Problem with sending S/MIME encrypted mails due to multiple address books Queue ⇒ Turba State ⇒ Unconfirmed	Reply to this comment
We have configured two addressbooks (mysql and ldap). As soon as a recipient is added to the mysql one, attempts to send him an encrypted mail fail with the message: "S/MIME Error: More than 1 entry found" We assume this is because he is found in both the local mysql and the LDAP addressbook. The problem is solved if the user is removed from the mysql addressbook, or the LDAP addressbook is removed from the addressbooks to be searched. We have seen a similar bug for PGP encryption in the past that was resolved. Could there be a similar problem for S/MIME, that has not been fixed? Thanks.