Enabled Logging, and here the results with some Errors inside...

As answered in the forum: https://wald.intevation.org/forum/forum.php?thread_id=1837&forum_id=21&group_id=11 :

Unsupported Protocol means that GpgOL can't find your GnuPG installation. Maybe something went wrong during the install of Gpg4win?

Hi @hs,
given that you have used the instructions from the link above to look at the message,
I'll take it that you are using an IMAP/SMTP setup for mail transportation?

A signed but not encrypted message appears in the same way (visible in Sent, empty in Inbox)

Looking at the messages from above using another PC, same Windows 7 and Outlook 2010 but Gpg4Win 2.3.3 :

• received message in Inbox is decrypted shown correctly inline both in preview and opening it
• original message in Sent is not decrypted, but shown as encrypted with gpgolXXX.dat attachment

Hence, it shows the opposite behavior to the 3.0.2 handling.

One problem seems to be that the content of Inbox message differs from this one in the Sent folder (10 vs. 20 KB).
The content of the Inbox is shown as empty, even using the "show source" option. Saving the message as plain text shows a PGP part inside, but this is ignored by Outlook.
I tried this advice:
How to view the message source in Outlook
But the result is the same, after maked as read, the message becomes unreadable.

• fresh install of Gpg4Win 3.0.2
• reboot
• openening Outlook 2010 with only one plugin (GpgOL)
• sending an encrypted email to myself
• trying to open that email (no content)

@aheinecke Because it was mentioned in another comment, I've tried to restart Outlook with the GpgOl plugin enabled, only. Same result. But the fact that I could see the message just after arrival, but not in a second approach may point in a direction that incoming messages are processed by an server-based filter changing potentially vulnerable email content (as embedded links).
I could try to log the complete process of sending an email to myself, decrypting once and failing in a second trail. This would actually increase the size of the log file.

@hs Your log is interesting but I don't yet understand it. We see a "Load" event for an encrypted mail, create our internal data modelling. But later there is a mismatch between the reference Outlook gives us and our internal reference (Failed to find mail in map).
Out of the blue there might be something I could do in that case but it's still somewhat unclear to me why this state occurs.

Just installed Gpg4Win 3.0.2.
Had a very similar effect with Windows 7 / Outlook 2010:

• Sending an encrypted e-mail to myself.
• E-mail will be decypted once after receiving.
• After that, e-mail is shown as "unsecure" and with empty message body (both in preview and own window).
• E-mail in "Sent" folder still decryptable with right content.

I've added gpgol.log for opening Outlook again after receiving the e-mail (with empy body, now).

Correct, this was also the case before, sorry for the misunderstanding.

The HTML in the body below the text on the GpgOL-1.4 side is a known issue of GpgOL-1.x we only added proper HTML handling with GpgOL 2.
GpgOL before 2.0 just appended the text/html mime part to the text/plain mimepart in multipart/alternative mails.

PS: And I can confirm that I have a lot of HTML Garbage in my mail body (on the receiver plain text side):

I can confirm that it works for me, too: Fantastic, thanks!

In my tests it's fixed with: b8276a4f3acecee2e467c0530007aedc9db5936a the plain text body now uses similar code to the html part. Makes sense anyway. The difference was mostly historic as GpgOL before 2.0 did not handle HTML parts at all.

If I send "Nur Text" (plaintext only) under formatting it works as expected. We query Outlook for the Body from the MAPI Data model and just get the wrong value returned. For the HTML part we use the Outlook Object Model (as we had a similar problem there that the MAPI data was not updated properly.)
The fix is obvious. We can use similar code to our handling of the HTML body. This is a workaround for an Outlook bug IMO, why should sending from drafts differ from the usual sending *sigh*

Wow, fast reaction! I'm happy to help evaluate a possible fix for this.

I can reproduce that problem and have opened T3614 for this.

Hi, first of all I want to report back that with beta15 that the following issues did NOT arise anymore, fantastic!

I only installed 3.0.2 this morning so this hasn't had much of a chance to happen.

T2854 is a duplicate of this but contains more up to date information. So I'm closing this issue.

Does this still happen with gpg4win-3.0.2?

Gpg4win 3.0.2 is released which contains even more fixes for GpgOL -> Resolving this. Please let us know if you still have Problems that are not tracked here.

The option now has the following logic:

• If encrypted is selected and the message is not signed.

and

• If the message has no attachments.

and

• If the option for inline sending is enabled

The problem was with a special attachment that had no file extension. Fixed now.

I can't reproduce this with the above steps. It is sadly a known issue that moving crypto mails does not work as long as they are viewed. (T3459) But for me opening any unencrypted mail and moving it. Or first opening an encrypted mail and then moving an unencrypted mail works.

This ticket can be closed. No further issue with email decryption after applying the provided patch

I looked into it. The problem is that attachments are opened as "Read Only" so we can't change the message class or handle it ourself. Once opened there is no apparent way to change the message to read only. Only if the message containing the attachment is marked as modifyable:

I tried to reproduce this with current GpgOL and it just worked. Even if I connected Enigmail to Exchange (Outlook.com).

@patoberli This looks very much like a crash I also observed on close and fixed with 1d0660fa53d357247ac84545f9259244a1d9400c the crash has nothing to do with the hang but thanks for the feedback anyway.

I finally had a crash again today, when I tried to close outlook.
I was running the debug log for several days now, until it finally crashed. Using gpg4win 3.0.1.
Here from the debug file:
*removed entries for privacy reasons*
12:28:46/19196/oomhelp.cpp:remove_category: category 'GpgOL: Verschlüsselte Nachricht' not found.
12:28:46/19196/mail.cpp:parsing_done:882: tracepoint
12:28:46/19196/mail.cpp:parsing_done:885: tracepoint
12:28:46/19196/gpgoladdin.cpp:gpgoladdin_invalidate_ui: Invalidating ribbon: 1D363A70
12:28:46/19196/mail.cpp:parsing_done:900: tracepoint
12:28:46/18768/parsecontroller.cpp:~ParseController
12:28:46/18768/mimedataprovider.cpp:~MimeDataProvider
12:28:46/18768/attachment.cpp:~Attachment
12:28:46/18768/mimedataprovider.cpp:~MimeDataProvider
***here I closed Outlook, but Outlook froze. I then killed the process in Windows.
12:34:02/19196/windowmessages.cpp:gpgol_hook: WM_CLOSE windowmessage for explorer. Closing all mails.
12:34:02/19196/mail.cpp:close_all_mails:1084: tracepoint
12:34:02/19196/returned from invoke

I've tested the fix and so far I found no problems with decryption and email rendering.
If you want I can report back here, after using GgpOL several more days testing the fix in day-to-day usage, and then if everything is fine we can close this ticket.
Thank you very much for your time.

We now read the headers as a stream. This fixes the detection of the content type for your example mail. It now correctly fails for me with "No Secret Key".

Received a test message and I understand it now. The header lines in the test mail are so large that they cannot be queried as a single property (out of memory because the max is pretty low, 4k or so) but have to be accessed through a stream interface. Many of the headers relate to Thread and In Reply To etc. so this explains why the problem only happens on reply.
I think I can quickly fix it.

A new installer with an updated libassuan is now available. To download gnupg-2.2.3_171201.exe please go to https://gnupg.org/download/ . If you had the disable-check-own-socket in your gpg-agent.conf, please remove it so that we can really see whether that version fixes the problem.

Many improvements since dec 2016 to gpgol. Latest master is much more stable (needs a Gpg4win release)

Yes please you can send it directly to mailto://aheinecke@intevation.de
If you want to encrypt it my key is 94A5C9A03C2FE5CA3B095D8E1FDF723CF462B6B1

I am very happy to hear that! Thanks.

After a week with the current version, including a registry cleanup, I had no crashes in Outlook. At the moment it seems to be running stable.

To sum up: Outlook can't decrypt a reply, although it can decrypt a direct email from the same sender.
Another thing I just noticed: once Outlook receives the reply (the one it can't decrypt), I can no longer move emails to other folders. If I deactivate GpgOL plugin, I can move the messages again.
Can I pm you the saved message ?

Better to fail loudly instead of silently breaking.

For now I've added messages to make it clear to the user that most actions won't work with G Sync.
Better to fail loudly instead of silently breaking.

I can no longer reproduce this. We had another report about this were we also tested this and it's ok with recent GpgOL 2.x versions. -> Resolved

Does not happen for current GpgOL versions and OL < 2010 support in GpgOL is no longer maintained -> resolved

It would be very helpful if you could export ("Save As") such a mail in Outlook and attach it here / send it to me. I don't have to be able to decrypt it but I would probably be able to figure out why it's not detected as a crypto mail.

The connection is a POP3 connection. Email server is a 3rd party email service provider. I doubt is an Exchange server (I believe they run a Linux server).
Switching to a different mail and back makes no difference - no email body displayed for the encrypted email.

As the crash is fixed and awaits release I think this issue is resolved. But that does not mean that we support G Suite sync. I don't see a quick fix :-/

Priority High as we should decide for the next release in which direction we should move.

Fantastic! I have these following issues:

Thanks for the confirmation.

Hi, sorry for coming back so late due to lack of time - but good news is: With GPGol 2.0.4-beta15 decryption now also works for us, great! Now we only have to check for a Outlook 2016 stability issue...

I tried a bit to find a Workaround. As far as I can tell Outlooks built in S/MIME Support does not even work with GSync. If anyone can send S/MIME encrypted or validly signed mails trough GSync please let me know.

In T3424#106481, @aheinecke wrote:

Noticed one problem already. Google rewrites the PGP/MIME Mails we send into a multipart/mixed mail with the PGP Data as an attachment. I'll see if I can find a workaround :-/

In T3424#106481, @aheinecke wrote:

Noticed one problem already. Google rewrites the PGP/MIME Mails we send into a multipart/mixed mail with the PGP Data as an attachment. I'll see if I can find a workaround :-/

In T3424#106451, @aheinecke wrote:

Already handled the crash in: T3540

I need to get a test setup with google sync. Any chance someone has a test account for me?

I'll try to register myself for the free trial period.

You're the hero!!!!

Noticed one problem already. Google rewrites the PGP/MIME Mails we send into a multipart/mixed mail with the PGP Data as an attachment. I'll see if I can find a workaround :-/

So I went through the google app sync setup and now have a test account.

@aheinecke From a first glimpse, I think we got it. Great work!
I replaced both versions of gpgol.dll as adviced (surprisingly /bin was locked, I expected /bin_64 ).
Thereafter Outlook decrypted all "old" message instantly and without any problems.
Thanks for the effort you spent and the fast reaction time!

Already handled the crash in: T3540

Thanks for the efforts. I will subscribe there to be up to date :-)

Oops I just noticed that this was already reported in T3424 which I somehow overlooked. Let's handle it there as there are more subscribers in that report and it's older.

So both your mails did show the exact same behavior for me. The PGP MESSAGE was shown in the mail and not attempted to decrypt.

Two versions of the same message as shown in the comment of 24th Nov.

I did some experiments with HTML Mails, Leading Text, Trailing Text etc. Everything worked fine for me.

In T3537#106396, @Xv wrote:

I have some progress and a step back.
Turns out that one of the installed plugins was causing the problem: "PDF Converter 7.1 Outlook Add-in".
I disabled all plugins (except GpgOL) and then enabled them back one by one.
With PDF Converter add-in disabled I'm now able to see the decrypted email body (sent from myself).

Can someone please add

Hi, thanks for the test. This sounds a bit like T3378 if the central component "gpg-agent" hangs everything relying on it may also hang. :-/

We have similar reports in our message board.

I put it at high priority because i want to check / fix this before the next release.

Ok I'm pretty sure that the Google MAPI provider is the problem because it likely has some different Data structures.
For Sender we already have three fallbacks as it's saved differently for Exchange over MAPI, Exchange Active Sync and IMAP. So we probably need another fallback for Google Sync >.<

Thank you, too for the report and testing.

Tested GpgOL 2.0.4-beta6 with Outlook 2010 32bit and Outlook 2013 32bit on Win 10 1709 64bit.

I have some progress and a step back.
Turns out that one of the installed plugins was causing the problem: "PDF Converter 7.1 Outlook Add-in".
I disabled all plugins (except GpgOL) and then enabled them back one by one.
With PDF Converter add-in disabled I'm now able to see the decrypted email body (sent from myself).

I use the Google Sync plugin to connect with our company Google Apps account. It also synchronizes the calendar entries as well as all other special stuff.
I'm quite sure that the standard POP/IMAP mechanisms in Outlook might not deliver the sender's address (however the receipient's address is contained in the logs above - my googlemail.com address).

I'm using the same Outlook 16.0.0.8625 on Windows 10 with a Gmail Account over IMAP and I have the Google Apps Sync plugin enabled. Everything works fine :-(
What is your senders account? Is that also GMail or something different. In the log I only see that the recipient is GMail.

I'm currently triaging. I give this high priority even if it is testing. We probably need a new GpgOL release soon as there were already some bugs fixed (e.g. Selecting many messages)