Duplicate of T1216

Seems to be duplicated in 1216.

Tested with different mailer of sender:
An OpenPGP encrypted (or encrypted/signed) email sent by OL2007/GpgOL1.1.1 and
Kontact e35 (GNU/Linux).
Same problem for both emails: OL2007 crashes after opening an attachment.

Still the same problem with gpg4win 2.0.2 (aka GpgOL 1.1.1).

There is no RFC. Hal merely posted a notice how PGP implements an Outlook
kludge. OTOH, PGP/MIME is a logn standing standard (rfc3156).

talking about the old 0.9 versions - they are not any longer maintained. Sorry.

gpgol does not use the partioned format - it implements PGP/MIME. If you are
talking about the old 0.9 versions - they are not any longer maintained. Sorry.

There is GpgOL 1.0.1 coming with Gpg4win 2.0.1. Can you give that a try?
Please also state the precise version of Windows and Outlook you are using.

2.0.1 has been released quite some time ago. Closing.

We need to hook into ondelivery because that is the only way which allows us to
change the message class before OL starts processing it. The change you see is
probably due to more elaborate message checking to catch more cases; in
particular we need to cope with the old-stylish cleartext PGP messages and also
handle other buggy messages here. This requires looking at the message body.

Hi Werner,

Hi Werner,

Sorry, we can't do anything about it. This is pureley an Outlook problem.
GpgOL does not know anything about IMAP; all what we do is to use the MAPI
interface.

Werner or Emanuel, any updates on this issues?
Still reproducable witn 2.0.1 (aka GpgOL 1.0.1)?

BTW: There is another short old report about exchange problems here:
http://wald.intevation.org/forum/forum.php?thread_id=624&forum_id=20

Asg: send me an email saying:

Asg, could you test 2.0.1rc1?

ok, please enable s/mime support by default for next release.

See T1137

Duplicate of T1137

It can't do that for technical reasons. We should enable S/MIME support by default.

Yes, this looks very familiar to me, although I thought the problem only occurs
if I both sign and encrypt the message.
I can't remember GpgOL's S/MIME support setting; and I'm unable to verify,
because I uninstalled it in the meantime (switched from OpenPGP to S/MIME
solution). You can mark #1130 a duplicate of #1137 if you like (though mine was
created 10 days earlier).

sorry, jroemmler, I have mixed the issue numbers.
Again: I think your issue is the same problem like T1137 (GpgOL could not
decrypt/verify messages in "sent items" folder if sime support is disabled).
Can you confirm it?

Nope, I'm using MS Outlook 2003 and #1110 crashes in Outlook 2007, whereas his
Outlook 2003 seems to work fine for him.
BTW: My Outlook 2003 doesn't crash, it just shows garbled content in the message
body (but that may be by luck).

Seems to be the same issue like T1110, right?

Still the same problem with Gpg4win 2.0.1-rc1.

Werner needs to try something to make sending MIME emails with Exchange
for the first time.
(So this problem will still be in 2.0.1rc1.)

Asg, could you test 2.0.1rc1?

Hi,
Retested using Gpg4win-2.0.1-RC1 (GpgOL 1.0.1-svn308)
Issue seems to be resolved in that non-encrypted attachments open in a
reasonable timeframe.
Thanks,
Juicefruits.

Duplicate of T1107

Duplicate of T1107

Thsi is the same as issue#1107 . Please see there.

Seems to be resolved with Gpg4win-2.0.1-RC1 (GpgOL 1.0.1-svn308). Needs more
tests of other users. Grandgeorg, can you test again?
(Download from http://gpg4win.org/download.html )

Seams to be resolved with Gpg4win-2.0.1-RC1 (GpgOL 1.0.1-svn308). Needs more
tests of other users. Juicyfruits, can you test again?

Seams to be resolved with Gpg4win-2.0.1-RC1 (GpgOL 1.0.1-svn308). Needs more
tests of other users.