Please wait for the final release of Gg4win 2.0 which incldues a completely
reworked GpgOL.

I am sorry, but we won't add such a feature for these reasons:

The latest outlook (from gpg4win 1.9.7) properly detects such an Outlook version

Outlook 2000 is not supported by GpgOL. In theory you should get a warning
message, though. Deinstall gpg4win and reinstall without the GpgOL component.

Outlook 2003 SP3

Right, older version of 0.10.x garbled the messages. We now take a copy of the
PR_BODY propery and work on it.

I confirm I can at least decrypt all my test mails
and see signed text.

Fixed in 0.10.9. The detection of multipart/mixed messages with old-style PGP
parts was not implemented. However, the signature verification of the old-style
PGP messages with attachments fail, i.e. they say the signature is bad.

OK, no crashes anymore.
Also, the only encrypted email works, but not the ones
with attachement or signed& encrypted.

Found it. The code to bypass the MIME parser missed to cleared info fields used
to colelct the mime structure. Fixed in svn 235.

The SVN number seems to be from the gpg4win installer. The current GpgOL
revision is 233.

Outlook crashed after import .pst file and double click on the encrypted or
signed+encrypted email.
Signed messages (with/without attachment) don't show cleaned mail body content.
Still the same problem... Tested with svn739.

Decryption works now.

Additional problem is that the test messages don't contain a final LF. This is
a usual problem with PGP armored messages. I have added a hack to overcome this
problem.

Well it depends on what you send. If you start the message with an empty line
everything is fine. If not, it will not be shown because the MIME parser does
not find the body; it skips all header lines. I need to detect this situation
and restart the operation without employing the MIME parser on the plaintext
(which is needed for some message, though (IIRC, CryptoEx). It is all not that
easy because we work in streaming mode. I'll try to save the header lines and
employ a heuristic to detect whether this is a MIME message or plain text.

...some problems with svn 732:
I created testcases with gpg4win 1.1.3
(testcases_InlinePGP_withGpg4win1.1.3.pst sent by PM to werner)
and imported the pst file into outlook.
GpgOL doesn't show cleaned contents of the mails (without BEGIN ... END).
Decryption doesn't work.

Now fixed in SVN 222.

I can confirm that with current release (svn220) it works.
Thus resolving.

Well, not really. IT requires a more complicated solution.

Fixed in svn 217.

No need, I should be able to duplicate this.

Yes, I did create a new signed PGP/MIME email.

On Sat, 19 Jan 2008 00:23, gnupg@bugs.g10code.com said:

Still the same problem with svn212.

I've tried 0.10.4-svn212 and still can oberve problems.

We are talking about Outlook and not about a regular MUA.
Anyway, the current SVN has code some sent messages.

I wonder why the email sent out to recipient is correct
and the copy in the sent-folder is defect.
To me this looks like the error can not be in UI Server Kleopatra
then ... ?

The current SVN (207) might fix this.

I have no idea on how to fix that.

This is still the case for 0.10.4-svn205.

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.