Horde_Crypt 2.4.0.

Changes have been made in Git (master):

commit 6defd320c3049fac13514d9555f05452ea05b3da
Author: Michael M Slusarz <slusarz@horde.org>
Date:   Tue Nov 12 18:28:58 2013 -0700

     [mms] Move PGP keyserver code to a separate 
Horde_Crypt_Pgp_Keyserver class.

     [mms] PGP keyserver code now uses Horde_Http_Client to connect to 
the keyserver.
     [mms] Fix submitting PGP keys to a public keyserver (Bug #10931).

  framework/Crypt/lib/Horde/Crypt/Pgp.php            |  199 +++--------------
  framework/Crypt/lib/Horde/Crypt/Pgp/Keyserver.php  |  236 
++++++++++++++++++++
  framework/Crypt/package.xml                        |   26 ++-
  .../Crypt/test/Horde/Crypt/PgpKeyserverTest.php    |   24 +-
  framework/Crypt/test/Horde/Crypt/conf.php.dist     |    2 +-
  5 files changed, 306 insertions(+), 181 deletions(-)

http://git.horde.org/horde-git/-/commit/6defd320c3049fac13514d9555f05452ea05b3da

I confirm that the same situation occur when I try to submit the 
public key generated to the keyserver (pgp.mit.edu).  Horde keeps 
saying "Key already exists on the public keyserver"

While I try search through web interface of pgp.mit.edu, there is no 
such key there.

I don't agree. Key handling and PGP usage should instead be made 
*easier* for users. It's probably debatable whether this is our job, 
but it's as good our job as anyone else's. And if not making it easy 
in a mail client where it's used most often, where else?

I'm thinking about removing keyserver upload completely from 5.1.   
This is one of those features/actions that SHOULDN'T be made 
inherently simple - uploading should only be done when a user fully 
understands the consequences and/or reasoning for doing so.

We have our server properly configured to use pgp.mit.edu.  It does 
appear to automatically get public keys.  But uploads always give the 
incorrect error,

"Key already exists on the public keyserver"

even when the key does not exist.