This should work. GpgOL 2010 just queries the Plain Text from outlook and
encrypts that.

KMail (Which is my primary mail client and testing client) works fine with such
mails.

Robert, could you send an example mail created by GpgOL that kmail does not decrypt?

To: aheinecke@intevation.de

My keyid is: C97822F5

You can find it attached.

Appears to be working. I had no reports of more problems with Exchange domain
addresses since 1.2.1

Hi,
sorry for the late reply. Missed this report.

In your debug output I can see that GpgOL appears to cause the crash in the
GetCustomUI function.

This is a very simple and static function that is called very often.

Is this issue reproducable for you? What were you doing exactly when it crashed?

(From the debug output it looks like you've opened the Tasks view but this works
ok for me)

Do you have any other Addins installed in Outlook?

The support for OL2010 is pretty limited compared to what gpgol can do
with earlier versions. The Compendium also notes that you should not
use HTML mails. For example in 13.3 (German version):

  Es ist empfehlenswert, Ihr E-Mail-Programm so einzustellen, dass Sie
  E-Mails nur im "Text"-Format und *nicht* im "HTML"-Format
  versenden. Sollten Sie dennoch HTML für signierte oder
  verschlüsselte E-Mails verwenden, können dabei beim Empfänger die
  Formatierungsinformationen verloren gehen, was zum Bruch der
  Signatur führen kann.

Andre: Do you have time to look into this?

Hi Werner,

now I am confused as to what I just found on Wikipedia about "Gpg4win": http://de.wikipedia.org/wiki/PGP/MIME
Quotes from that page [translated to English]:
"PGP/MIME is – just as the old PGP/INLINE – an encoding to mark an email for mail clients [as encrypted]."

"Mail clients supporting that encoding can detect if an email and its attachments are encrypted and/or signed with PGP/GnuPG."

"With PGP/MIME it's possible to encrypt all attachments along with the message which is the default behavior." And which is
also a major usability improvement.

Because other mail clients (except for e.g. Kmail and probably some others, too) do not support that encoding yet comes the
quote that puzzled me:
"Government-funded by the German agency "Bundesamt für Sicherheit in der Informationstechnik" (BSI) the software Gpg4win was
published."

I'd like you to explain why you rated that bug low and talk it down when on the other hand GPG OL - which is shipped as part
of Gpg4win - is supposed to support that encoding type?

IMO that's a very strong hint for an incomplete feature or bug.

Has it something to do with closed-source Outlook itself and that GPG OL is not able to change the "Content-Type"? In that
case rating the bug down is no right as it would never get fixed anyways.

Regards
Robert

I'm sorry but that's just a poor excuse for several reasons:

• The security issues arising from HTML mails are a totally different attack vectors.
• Your claim that HTML messages would render encryption useless is wrong unless

there's a severe bug in the encryption/decryption algorithm, that triggers a buffer
overflow when reading the message's text.

• The purpose of encryption is to hide the message content while the mail is traveling

through the web.

• Encryption has got to be independent of the encrypted contents. Otherwise, following

your logic, you should drop encryption of attached ZIP, PDF, EXE, and whatever else
files.

As I said at the end of my first comment: I'd like to fund its fixing as that bug is a
real pain when it comes to interoperability across different OS-boxes/mail clients.

HTML mails are a severe security problem and may render the whole encryption
useless. Thus I downgrade this bug.

Yes, that's a confirmed workaround. However, sending HTML-Messages is important
to my business. So the bug remains.

Please disable "HTML and Text" and use "text only" For formatting thge mails.

Please find attached two encrypted mails sent via Kmail. Kmail can detect both as
PGP-encrypted even the "Inline-OpenPGP" formatted one. There must be some
critical difference to encrypted mails received from Outlook with GPG OL that
cause outlook mails not to be detected as encrypted.

This should have been resolved a long time ago. There was a KDE bug about this
but I can't find it anymore.

Thanks for the feedback!

Not sure but everything seems to be working in the 2.2.2-beta relase.

Should be fixed in 1.2.1 (part of gpg4win-2.2.2-beta)

Are you sure that the case sensitivity was the problem here and not the general
Problem that Exchange Addresses were not looked up correctly?

It would be helpful if you could test this with gpgol 1.2.1 (part of
gpg4win-2.2.2-beta) if this is still an issue I'll look into it.

Hi Jon,
can you check this please with the current gpg4win-2.2.2 beta? I've fixed some
object resolution bugs there when Sender / Recipient addresses were not SMTP only.

Thanks

This should be working with gpgOl 1.2.1

As I don't have a test set up I'm setting this to resolved until someone complains.

your debug output points to the same issue that was fixed recently in gpgol
1.2.1 relating to address lookup in Outlook (part of gpg4win-2.2.2-beta)

Please try this version.

Nope; won't be done. We had this in the past and people enabled it and later
complained about disk full stati. And yes, it exposes confidential info.

I did not activate debugging; but also have moved to 2.2.1 of the gpg4win tool
collection and can no longer replicate the problem.

I've upgraded to the gpg4win Oct 7 release (2.2.1, same version of GPGOL), and it
seems to be launching things in a more reliable order; can not reproduce in
2.2.1.

Don't run it under debugger.

Please report a bit more than a shreenshot. We prefer to have at least the key
items reported as plain text so that we can search for it.

Please start kleopatra or gpa first - then start Outlook. Does that work?