PGP Encrypted mail with Gpg4win and Kopano from Outlook

fbartels

@robgnu unfortunately our own priorities have not changed since my last reply.

robgnu

@fbartels Thank you for your quick reply. That are very sad news for me.

I have done some tests this morning and I can confirm, that the KOE is not affecting this problem. I created a new ActiveSync account on Outlook 2016 without KOE installed. The problems are exact the same as described above:

Sending encrypted/signed mails does not work.
Sending encrypted/signed mails with attachments does not work.
Fallback to PGP/Inline works without attachments.
Receiving all kind of E-Mails with Outlook/GpgOL works. So only outgoing mails are affected.

All my tests where on Outlook 2016/GpgOL-Extension connected via ActiveSync to Kopano. The test-receiver was an external IMAP-Account with Thunderbird/Enigmail.

My client has a subscription. So I will contact the support on Tuesday. I hope there will be a solution with a higher priority than before.

Regards, Robert.

aheinecke

Hi,
I forgot about this thread but it was recently mentioned again in our tracker.
@fbartels Turned out that my original reporter was not a customer of Kopano but only used it for free, and as he also basically wanted free support from me and you while his company uses both of our work for free… weeel,… software development costs money.

My offer still stands to help resolve this even without a customer from our side, but it’s always a question of priorities. I fully understand that.

And yes this only affects outgoing mails. It’s related how Exchange converts Outlook’s MAPI to MIME and Kopano does this not exactly the same way.

Btw. as an additional workaround, I don’t know if its possible to use Kopano with SMTP in Outlook, but I think this should also work.

Best Regards,
Andre

fbartels

@aheinecke said in PGP Encrypted mail with Gpg4win and Kopano from Outlook:

he also basically wanted free support from me and you while his company uses both of our work for free… weeel,… software development costs money.

Yes, I was kind of expecting this already. Its kind of sad that if you make your software freely available, that people then also expect that your time to fix their own problems is free as well.

Thanks again for your offer. I have reached out internally to check what we can do here.

Yes, one workaround that I could imagine is indeed to configure an additional smtp account and use this one to send out mail. Another alternative would be to write the message instead with our WebApp and use https://www.mailvelope.com/en.