Tickets :: [#8460] After Update 4.3.3 to 4.3.4 gpg key functions yield in "invalid key"

Summary	After Update 4.3.3 to 4.3.4 gpg key functions yield in "invalid key"
Queue	IMP
Queue Version	4.3.4
Type	Bug
State	Not A Bug
Priority	1. Low
Owners
Requester	hostmaster (at) taunusstein (dot) net
Created	7/28/09 (6100 days ago)
Due
Updated	7/29/09 (6099 days ago)
Assigned
Resolved	7/29/09 (6099 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch	No

07/29/2009 03:58:48 PM	Michael Slusarz	State ⇒ Not A Bug

07/29/2009 06:48:34 AM	hostmaster (at) taunusstein (dot) net	Comment #2	Reply to this comment
Problem disappeared with update from IMAP server Dovecot version 1.2.1 to 1.2.2

07/28/2009 12:05:04 PM	hostmaster (at) taunusstein (dot) net	Comment #1 State ⇒ Unconfirmed Priority ⇒ 1. Low Type ⇒ Bug Summary ⇒ After Update 4.3.3 to 4.3.4 gpg key functions yield in "invalid key" Queue ⇒ IMP Milestone ⇒ Patch ⇒ No	Reply to this comment
After update from 1.2.2 to 1.2.3 a problem with IMP 4.3.4 appeared regarding GnuPG. In IMP 4.3.3 GnuPG behaves as expected: IMP Setting -> PGP -> Public Key details shows key details as expected. After update to IMP 4.3.4 it shows "invalid key".