[imp] gpg/ pgp seems a bit buggy

Chris H. fbsd at 1command.com
Wed Apr 26 17:36:30 PDT 2006

Hello, and thank you for your response.

Quoting Michael M Slusarz <slusarz at horde.org>:

> Quoting "Chris H." <fbsd at 1command.com>:
>> Hello, and thank you very much for your reply.
>> In all cases it recognizes it as a pgp/gpg signed message; as indicated
>> by the lock in the upper left hand corner of the message after I open it.
>> Here is an example: I have imported both my private & public keys into
>> IMP. I have Sign Messages as the default option for sending email. I
>> send a message to this group for example. I am prompted for the password
>> after I hit send. When the message I sent arrives, sometimes it has a
>> locked envelope icon, sometimes it has the paperclip next to the envelope
>> icon. In all cases, I am using my same keys. When I open the message,
>> sometimes I see the lock and the text indicating this is a pgp/gpg signed
>> message and the confirmation that it is valid. But sometimes I see the lock
>> and the text indicating that it is a pgp/gpg signed message and the
>> confirmation text indicating that it is valid *and* my name and email
>> address. *However*, the difference is not consistent, nor does it
>> corospond in any way with the differences in the locked envelope, or
>> paperclip envelope. There is no distinct pattern that I can find. So I
>> was hoping that those who know, could shed some light on these anomolies.
> IMP will recognize this MIME message as encrypted/signed on the  
> mailbox screen:
> multipart/encrypted (or multipart/signed)
>   + encrypted data
> IMP will *not* recognize this MIME message as encrypted/signed:
> multipart/mixed
>   + multipart/encrypted (or multipart/signed)
>   + text/plain
> Or this one:
> text/plain
>   + inline PGP data
> the mailbox screen is not going to do complex gymnastics to try to  
> figure out if an encrypted part exists somewhere in the body text.  
> If  the base MIME part is not multipart/signed (or encrytped) then 
> you  won't see an indication.

OK. Well Horde/ IMP is doing the signing using the prefs and options provided
by Horde/ IMP. So I shouldn't think Horde/ IMP have any unrealistic
obsticals, other than those that they impose themselves.

So I guess my next question should be:
How do I teach IMP to sign messages in such a way that when I recieve
one, it has a "locked envelope" icon next to it and not the "paperclip"
icon next to it?

Thank you again for your reply.

--Chris H.

> michael
> ___________________________________
> Michael Slusarz [slusarz at horde.org]
> -- 
> IMP mailing list - Join the hunt: http://horde.org/bounties/#imp
> Frequently Asked Questions: http://horde.org/faq/
> To unsubscribe, mail: imp-unsubscribe at lists.horde.org

Shameless self-promotion follows...
... or does it?

FreeBSD 5.4-RELEASE-p12 (SMP - 900x2) Tue Mar 7 19:37:23 PST 2006

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: PGP Digital Signature
Url : http://lists.horde.org/archives/imp/attachments/20060426/7bea2f63/attachment-0001.bin

More information about the imp mailing list