With new version 0.10.4-svn205
I was able to decrypt a newly arrived inline-PGP mail
exactly once.

With gpg4win svn639 the problem described here is resolved, and
replaced by a different one that is really inside Kleopatra.

Fix confirmed. Resolving.

Yes it also applies to inline PGP. In fact inline PGP is internally converted
to PGP/MIME.

I think most concern is with inline-PGP, not PGP/MIME.
Will the solution apply to this type as well?

We could has a hack to detect PGP/MIME messages right before displaying. This
requires to use code similar to older versions of GpgOL. I hesitate to add such
a hack because it makes the way more complicate and is nto a full solution
because we need anotehr solution for S/MIME anyway.

Frankly, there is no need more for the toolbar button. Decryption does now work
automatically and if a new signature verification is ever needed the menu entry
should be sufficient. I'll remove the toolbar item.

That was a wrong German translation. Fixed with the next SVN commit (r > 201).

I wasn't aware this is true of OpenPGP as well.
I adjusted the subject.

Please use the uiserver keyword to flag problems which are likely related to the
uiserver (i.e. Kleopatra)

This is definitely a Kleopatra error. I am suffering form this for quite some time.

This is similar to the S/MIME case where we can't yet process messages we have
not received with gpgol installed and active. The solution will be the same as
for S/MIME - we talked about this.

I have checked with gpg4win 1.1.3 (GnuPG: 1.4.7, GPGol: 0.9.92) and the
problem is still not solved. It continues to occur exactly the same way.

Thanks!, the problem was I've entered the complite asc key name. When I enter
only the ID of my key everything works OK.

Check that you entered the correct key id in the option dialog. It must be the
key id of your own key (one which has a secret key).

With gpgol 0.9.x you get a file dialog to specify the name of the attachment.
Use that. We won't fix that in 0.9.x.

Sorry, I can't test this now. As I noted in other bug reports, OL2007 may or
may not work. We will make it work later this year using the forthcoming GpgOL
rewrite.

The current - non fully working - code of GpgOL works fine under Vista and
OL2007. This is code more or less a rewrite of the old code; thus I am not sure
whether it makes sense to try making the old code working vor Vista.

Hopefully the last comment T778 (JohnA on Jun 19 2007, 01:03 AM / Roundup) didn't get lost... it should be pretty easy
to verify whether there's a blank line in a signed text!

Installed the latest version of GPG4Win including gpgol 0.9.91. One other
problem was noticed. If I encrypt and sign or just encrypt a text message,
everything is ok. If I just sign a text message, the verification fails when
reading it. I noticed there was no blank line between the Hash: statement and
the first line of the message as there is on other PGP signed messages.
Manually adding a line to the signed message after it has been sent allows it
to verify correctly.

Hello Werner,

Tomo, can you please check this?

Similar to T780 I guess.

I doubt that this is a bug. Do you have several secret keys? Some folks use
wildcard key specifications and gpg needs to do test encryptions using all
available keys.

Does this still happen with gpg4win 1.0.9?

Does this still happen with gpg4win 1.0.9?

That is not a bug - but a feature. For PGP/MIME messages GPGol uses its own
MIME machinery. Running this for the preview window would be too cumbersome.1

Duplicate of T780