After installing gpg4win 2.3.0 (GpgOL 1.3.0) I had no more crashes.
Thanks for your fix.

It was a crash. Outlook has been terminated and restartet automatically (can be
seen in gpgol log).
Now I'm going to start with gpgol enabled and I'll enable all other plugins step
by step.

I installed the new gpg4win 2.3.0 release and activated gpgol. When answering an
email I had another crash reported in ntdll.dll. But I suspect that the crash is
related to gpgol even though it's not directly reported.
Now I'm going to leave gpgol disabled.
The corresponding logs are appended and might be that there are some hints inside.
Best regards
KJ

After installing the lastest beta I had unfortunately several crashes of Outlook.
The crashes are reported for severeal modules. There was no crash in module
gpgol reported, nevertheless I disabled gpgol.
If there are some news - even no more crash - I'll give an update here.

Best regards
KJ

I had all flags enabled (2047) and set it now to 1.

Thanks again.
KJ

Thanks for the quick fix and your detailed answer.

I installed the new version and had nearly no problems: I successfully exported
contacts serveral times (even waiting more than 10 minutes) and de- and
encrypted emails multiple times.

There was only a crash at the very beginning when I started outlook and forwared
an email with encryption to myself. Outlook crashed but module MSPTLS.DLL has
been reported to be the cause of the failure.

In the log file of gpgol I noticed that there is a huge amount of messages
in.lock taken or released and the same for out.lock. Is it possible to disable
selectively these lines because it floods the disk and I'd like to have some
debug lines enabled if some problem might occur.

Best regards
KJ

As a workaround it's possible to disabled gpgol before exporting contacts.
After enabling gpgol it's possible to decrypt/verify encrypted mails without
problems.

I can confirm the behaviour related to time. When gpgol is enabled before
exporting contacts and then disabled I can do this multiple times (for at least
twice). When waited for some time gpgol is unloaded as soon as the "Fertig
stellen" has been clicked, which means beginning the export.
That's really weird...

But I'm happy that you are able to reproduce crash.
Good luck for debugging.

Regards
KJ

forgot the file

Yes that's true, when disabled, all works fine.

In Outlook's folder tree view I select "Kontakte" and then
Datei->Optionen->Erweitert->Exportieren->In Datei exortieren->Weiter->Outlook
Datendatei (.pst)->Weiter->Weiter->specify file name for the export->Fertig
Stellen->OK.
If gpgol is active then Outlook usually crashes at that point or when changing
to the inbox.

I just replay the scenario enabling gpgol and susequently exporting contacts and
it worked - see latest Application view entries and last gpgol debug output.
In the file appended there are the application log entries since Nov. 13th
(Source: Outlook and "Application Error") and the relating gpgol log file if active.

Outlook is exchange based and connected to an AD.

Best regards
KJ

Just a short update. Working with addin-options dialog now works fine with beta104.
But as soon as I'm exporting contacts Outlook crashes again.
Best regards
KJ

Thanks for your notes. gpgol beta 104 now loads again.

Thanks. I found it. WHat's the difference between gpgol in
beta folder and that one in mime-send?
After replacing the dll I tried to enable gpgol but I had bno success so far.
There is a run time error reported when loading the addin. I also ran
ProcessMonitor and there is probably a missing file "C:\Program Files
(x86)\GNU\GnuPG\pub\api-ms-win-appmodel-runtime-l1-1-0.dll".
There are screeen shots in file uploaded.

Kind regards
KJ

Hi,

thanks for your reply. No, there was no crash since disabling gpgol. I even
exported my contacts every day without any problem.

Is there a testversion available?

Kind regards,
KJ

Because I had serveral crashes the last 2 days I decided to disable gpgol add-in.
I'll see what it's going to happen the next days.

I clicked on an e-mail today and it got decrypted (although others didn't). This
e-mails have been left decrypted (see T1106). So I wanted to disable gpgol
and when I tried to do so Outlook crashed again.
Because I deinstalled PDF Architect there is no such addin!
Unfortunately there must be another reason.
I'll append gpgol.txt, an excerpt of windows eventlog and screenshots of the
addins still activated in archiv.tar.gpg.

So it seems as if the cause has been found. I uninstalled PDF Architect and
hopefully there will be no more crashes.
Thanks
KJ

The only third party addin besides gpgol (and those of Microsoft) I've installed
is PDF Architect 3 which I disabled. During the step of disabling another
crashed occured. Now I'm going to see waht happens.

Just turned off all addins but gpgol and export of contacts worked. Enabled
again all addins and export of contacts worked without problems. There must be
some other influences.

Now Outlook crashed while trying to modify addins.

Fehler bei der Ausführung des Add-Ins. Outlook ist während des Rückrufs
'OptionsPagesAdd' der Schnittstelle 'ApplicationEvents' beim Aufrufen des
Add-Ins 'GpgOL - The GnuPG Outlook Plugin' abgestürzt.

Name der fehlerhaften Anwendung: OUTLOOK.EXE, Version: 15.0.4763.1000,
Zeitstempel: 0x55f7f203
Name des fehlerhaften Moduls: OUTLOOK.EXE, Version: 15.0.4763.1000, Zeitstempel:
0x55f7f203
Ausnahmecode: 0xc0000005
Fehleroffset: 0x0016ed2c
ID des fehlerhaften Prozesses: 0x2dd0
Startzeit der fehlerhaften Anwendung: 0x01d11321b1369144
Pfad der fehlerhaften Anwendung: C:\Program Files (x86)\Microsoft
Office\Office15\OUTLOOK.EXE
Pfad des fehlerhaften Moduls: C:\Program Files (x86)\Microsoft
Office\Office15\OUTLOOK.EXE
Berichtskennung: 3d154856-7f1e-11e5-920b-2c4138a83b6e

The eventlog messages as of today are:

Fehler bei der Ausführung des Add-Ins. Outlook ist während des Rückrufs
'0x0000FAB5' der Schnittstelle 'ApplicationEvents' beim Aufrufen des Add-Ins
'GpgOL - The GnuPG Outlook Plugin' abgestürzt.

followed by

Name der fehlerhaften Anwendung: OUTLOOK.EXE, Version: 15.0.4763.1000,
Zeitstempel: 0x55f7f203
Name des fehlerhaften Moduls: OUTLOOK.EXE, Version: 15.0.4763.1000, Zeitstempel:
0x55f7f203
Ausnahmecode: 0xc0000005
Fehleroffset: 0x0016ed2c
ID des fehlerhaften Prozesses: 0x1704
Startzeit der fehlerhaften Anwendung: 0x01d112f3b4588f4c
Pfad der fehlerhaften Anwendung: C:\Program Files (x86)\Microsoft
Office\Office15\OUTLOOK.EXE
Pfad des fehlerhaften Moduls: C:\Program Files (x86)\Microsoft
Office\Office15\OUTLOOK.EXE
Berichtskennung: 700aef2d-7f14-11e5-920b-2c4138a83b6e

I'm to check exporting contaxts by disabling addins as you suggested.

Now it's definitely exporting contacts. Today I didn't even switch to inbox.

Had another crash today. The last steps were: exported contacts to a local file
and when done I switched to inbox folder. Then Outlook crashed and restarted itself.
Please see windows evenlog entry and gpgol log file.
Best regards kj

I just installed the version and as soon as there are new results I'll come back
to you.
Thanks

Thanks for the answer. Is there another (beta) dll for download or should I wait
for the next release?
TIA KJ

Outlook reported the problem and a message box appeared stating "searching for
the cause of the problem". Outlook then restarted itself. After terminating
Outlook I assembled the log files.

The most interesting lines should be around line # 3152 which is presumably the
very last line before/during the crash.

So I'll wait for the new version :-)

I just had another crash using your latest provided gpgol.dll.
See gpgol logfile and corresponging windows eventlog entry in the file included.

Thanks for your quick reponse.

Just to give an update:

since June I had 24 messages of type without any encryption/decryption

Fehler bei der Ausführung des Add-Ins. Outlook ist während des Rückrufs
'GetCustomUI' der Schnittstelle 'IRibbonExtensibility' beim Aufrufen des Add-Ins
'GpgOL - The GnuPG Outlook Plugin' abgestürzt.

and one of the folling two

Fehler bei der Ausführung des Add-Ins. Outlook ist während des Rückrufs
'btnDecryptLarge' der Schnittstelle 'IRibbonControl' beim Aufrufen des Add-Ins
'GpgOL - The GnuPG Outlook Plugin' abgestürzt.

Fehler bei der Ausführung des Add-Ins. Outlook ist während des Rückrufs
'btnDecrypt' der Schnittstelle 'IRibbonControl' beim Aufrufen des Add-Ins 'GpgOL

• The GnuPG Outlook Plugin' abgestürzt.

Hi, any plans for the next release?
Best regards
KJ

So I'm going to wait for a new release with more tracing capabilites.
Thanks so far.
KJ

Hi,

since April there are 14 crashes recorded in windows event log, one occurred in
function btnDecryptLarge all others in function GetCustomUI.

It happens occasionally when changing between views. So it's not easy to
reproduce the behaviour. Even the log is not very useful because there are no
timestamps in the log entries to check it against windows event log.

There are other 6 active plugins installed.

If you need more info’s, please let me know.

KJ

I remember that I had a similar problem in a previous version which I reported
but I can't remember on which site/community. In a following version the bug has
been fixed and I never had this problem again up to and including version 0.9.92.
That's strange beacause you said that's is an existing problem since years.

Hmmm. I didn't notice the hint at the first startup.

I received an encrypted email (encrypted by gpgol 0.9.92) which used to work in
OL2003. When decrypting the email I had to pass the passphrase and the email has
been display decrypted in the very same window. Closing the window the email was
still left encrypted.
Using gpgol 1.0.0 the email has been decrypted the first time. Since then when
moving to the email no text could be seen, the passphrase has to entered (the
first time visiting the email) and the email was display decrypted as long as I
didn't close OL. Since deinstalling gpg4win the email is decrypted! The only
difference I noticed is that the icon changed from "read mail" to "unread mail"
and even doesn't change to "read" when the email is left.

The installation also was Exchange based.

I'm using an Exchange base account.

Once the problem occured you have to restart Outlook. The Option has to be
disabled *before* decrypting the message.

Duplicate of T735

Duplicate of T729

Duplicate of T748

When "Ansicht->Format" (German version) is being disabled decryption works fine.

Wow! That's great. How did you find out the workaround.
Besides: on my machine the workaround only works if the extended bar is disabled.
If it's enabled it doesn't work no matter of ir's position relative to the
standard box.

I opened the encrypted mail, clicked the decryption icon but outlook's window
still contains the encrypted text. The corresponding lines in gpgol_0.9.91.txt
are from 1 to 35.
The versions are as follows:
WinXP SP2, Outlook 2003 SP2 (11.8010.8107), gpgwin 1.0.8 (gpgol 0.9.91, gpg 1.4.6)

It seems to be a charset problem. I installed WinPT 1.0.0-pre0 and modified the
passphrase replacing international characters with correspondig characters of
the 7 bit character codes: e.g. replacing ä by a. Using these characters only
decryption works with the very same keyrings.
Hence I'd suggest to
a) display the default characterset along with --version option
b) provide an option to display the charcter set being used
c) clarify the scope of the character set (reading stdin, file, passphrase, etc...)

Using Virtual PC I installed a fresh Windows XP Professional version including
SP2 and gpg4win 1.0.6. I can only confirm the behaviour mentioned before:

• Encryption of clipboard (WinPT) works fine
• Decryption of clipboard (WinPT) fails
• Decryption with gpg (1.4.5 gpg4win package) command line (cmd.exe) fails
• Decryption with gpg (1.4.5 gpg4win package) command line (cmd.exe) with

--passphrase-fd 0 (don't know how to get it working: neither pipe nor typing in
works)

• Decryption with gpg (1.4.5 gpg4win package) command line (CygWin) fails
• Decryption with gpg (1.4.5 gpg4win package) command line (CygWin) with

--passphrase-fd 0 option succeeds.

It seems as if I hit the same problem (see T704).
The only way I get decryption working is to run gpg in CygWin environment and
piped the passphrase to gpg.
Example:
PW='secret passphrase'
echo $PW | gpg --passphrase-fd 0 -d <encrypted file> or
cat - | gpg --passphrase-fd 0 -d <encrypted file>

I tried to descrypt with different versions of gpg. But all failed. The only one
working is 1.4.2.1 from the cygwin package. Then I reinstalled version 1.4.5
from gpg4win 1.0.6 package. Typing in the passphrase constantly fails, but when
the passphrase is stored in an environment variable and piped into gpg (called
with --passphrase-fd 0) then decryption works fine. My passphrase contains some
special characters of the iso88591 characterset for security reasons. But this
should not make any difference. But I suspect it's a matter of charactersets
when reading the passphrase. I suppose it's not being read from stdin (fd 0)...

I had no other idea how to narrow down the problem. Decryption used to work with
WinPT. Because it no longer worked as of version 1.0 I tried to decrypt directly
calling gpg that came along with gpg4win (which didn't work either). So I tried
to use an older version of gpg in order to proof if the keyrings are ok and working.
I had no copy of gpg version 1.4.4. As far as I remember it worked up to and
including gpg 1.4.4. Cygwin's gpg proved that the keyring's and the passphrase
are working.
Hence I concluded that it must be a problem of gpg 1.4.5