[Gpg4win-users-en] GPG4WIN Vs Outlook Roadmap

[am.lists]

On 8/21/07, Werner Koch <wk at gnupg.org> wrote:
> On Mon, 20 Aug 2007 19:19, am.lists at gmail.com said:
>
> > I've done some searching and determined that the Outlook Plug-ins
> > don't currently support OL2007. (Has this changed?)
>
> Frankly, I don't know whether it is supported because I have not yet
> used OL2007.  Anywa, we are working towards a new major release of
> Gpg4win and this will include support for OL2007.  Be patient for a 2
> months.
>

That is great news. Perhaps since Google has such a difficult time
returning results that indicate this, maybe some more documentation of
this effort being underway is needed.

> > Since OL2007 isn't officially supported, is there a workaround that
> > someone smarter than the average user could follow to get it working?
>
> I can't tell.  GpgOL is pretty fragile code as it needs to hack around a
> couple of Outlook Plugin problems.  The new code in the code will be
> somehwat different and as a bonus shows attachments the usual way
> without the need to save them.  It will also support S/MIME and PGP/MIME
> (read only).  Verification and decryption using the new code already
> works.  We are currently working on the UI and the encryption and
> signing.
>

Perhaps let me review what I have working versus what doesn't for me:

-OL2007 with Exchange Server and without (POP/IMAP mode) -- GPG4WIN 1.1.2.
-GPG Keys created via WinPT successfully.
-In OL: Go to send a message and "sign" it.  I have to access the
button via the Add-ins ribbon (found it no problem).
-- Type the message and hit send.
-- Key manager comes up and asks which signing key to use.
-- Key manager prompts me for the passphrase for that key.
-- At that point, Outlook crashes and gives me the "Do you wish to
report this error to Microsoft" dialog.
-- I don't have any recipient keys imported yet so all I can do is
sign (not encrypt) so I can't really test that yet. I tried
signing/encrypting a message to myself (a key I have) and the same
crash occurs.

Here's the info on the crash:

AppName: Outlook.exe   AppVer: 12.0.4518.1014  AppStamp: 4542840f
ModName: Gpgol.dll   ModVer: 0.9.91.162   ModStamp: 46c47b24
fDebug: 0   offset: 00019ddd


Hope this helps.

Maybe I'm further than others? Maybe not.


Angelo