I Can confirm, its working for me fine now.
Mar 12 2018
Jan 12 2018
Its also german:
Jan 11 2018
I can confirm, that 2.0.6-beta14 is working and until now, Outlook did not crash :-)
Great work, thanks!
I can also confirm that 2.0.6-beta9 fixes my issue with this too. Also with my own exchange server!
But that's it.
With these Options set and explicitly unchecking Sign & Encrypt before sending I get the exact same behavior that you two describe. Mails are sent unencrypted.
I have now also the error T3662
Will try also 2.0.6-beta9
OK, found the problem now. Its the smime settings. I have set them to sign all outgoing mails. And thats where the problem starts...
If I disable the option "Add digital signature to outgoing messages" I am able to encrypt outgoing messages.
Its not what I wan't, because I want to sing all messages, but hope it helps to find the cause of the error.
@JHohmann can you confirm, that this option is active on your side also?
Ahh, and yes I use a public personal s/mime cert to sign my mails. nothing else.
My too, no outgoing rules.
Jan 9 2018
I sent it to a user on a different Mailserver. On my setup its nothing special... Win 10 Enterprise N en, Office 365 Pro Plus en, Kaspersky Internet Security. Server Win 2012 R2 with Exchange Server 2013 and GFI Mailessentials.
I don't think there is anything special... :-(
I disabled all my add-ins and tested it again. Still the same. Mails are sent unencrypted.
Tried also to send a plain text message
I attached the actual log file
Add-Ins are disabled...
Tried also with full disabled virus protection
and disabled hardware acceleration...
Jan 6 2018
Dec 30 2017
Enabled Logging, and here the results with some Errors inside...