[#9472] Smime not possible if multiple emails in turba
Summary Smime not possible if multiple emails in turba
Queue IMP
Queue Version Git master
Type Bug
State Resolved
Priority 1. Low
Owners slusarz@horde.org
Requester hordetest@trash-mail.com
Created 2010-12-25 (3490 days ago)
Due
Updated 2011-12-06 (3144 days ago)
Assigned 2010-12-28 (3487 days ago)
Resolved 2011-12-06 (3144 days ago)
Milestone
Patch No

Comments
hordetest@trash-mail.com 2010-12-25 21:36:59
I enabled multiple email adresses per contact in turba (email -> 
emails). It seems smime is not able to get the email address for a 
public key. the public key is shown in prefs with empty (). 
view_public_key returns "Invalid email". decrypting of mails is also 
not possible

Git Commit <commits@lists.horde.org> 2010-12-28 17:34:11
Changes have been made in Git for this ticket:

[jan] Fix searching for fields matching an email address if using 
'emails'       attribute instead of 'email' (Bug #9472).

http://git.horde.org/horde-git/-/commit/62901caaa1a717ae1c5a3d63dea776c160e59c82

CVS Commit <cvs@lists.horde.org> 2010-12-28 17:34:58
Changes have been made in CVS for this ticket:

[jan] Fix searching for fields matching an email address if using 'emails'
attribute instead of 'email' (Bug #9472).
http://cvs.horde.org/diff.php/turba/docs/CHANGES?rt=horde&r1=1.181.2.260&r2=1.181.2.261&ty=u
http://cvs.horde.org/diff.php/turba/lib/api.php?rt=horde&r1=1.120.2.71&r2=1.120.2.72&ty=u

Jan Schneider <jan@horde.org> 2010-12-28 17:36:57
Decrypting still fails. Actually encrypting probably fails, I can't 
decrypt those messages in IMP 4 either.

szimszon@oregpreshaz.eu 2011-09-11 19:54:04
Could be related: http://bugs.horde.org/ticket/10497

(json utf-8 encrypt error)

Michael Slusarz <slusarz@horde.org> 2011-09-12 00:08:22
> Could be related: http://bugs.horde.org/ticket/10497
>
> (json utf-8 encrypt error)

This has nothing to do with ticket 10497.

Michael Slusarz <slusarz@horde.org> 2011-12-06 06:52:58
S/MIME works fine, at least of 5.0.16.  Considering this report came 
out before 5.0 was even released, I'm going to assume this has been 
fixed since then.