PGP Encrypted mail with Gpg4win and Kopano from Outlook
-
This post is deleted! -
Hi,
how is the actual state of this point? Is it solved?
I’m wondering if this problem maybe could be a problem of gpb4win and not kopano: there is a alternative gpg plugin existing for outlook 2016 (and other versions) called gpg4o that works perfectly with outlook and kopano.
If you need further data, please let me know…
Kind regards
Rolf
-
@rolf as you can see in the reply from @umgfoin it seems to work now (that is what I also experienced when I tried it the last time)
Regards Felix
Resources:
https://kopano.com/blog/how-to-get-kopano/
https://documentation.kopano.io/
https://kb.kopano.io/Support overview:
https://kopano.com/support/ -
@fbartels thats unfortunately just 50%.
- It still doesnt work when sending crypted (and optionally signed) messages with attachments.
- with attachments it just works when receive
- the way to use pgp/inline is just a workaround and NOT a solution.
sorry, but the bug is still existing and prevents the usage of a lot of pgp usecases.
is there the possibility that this may be solved this year? That’ll be great :-)
Kind regards
Rolf
-
@rolf said in PGP Encrypted mail with Gpg4win and Kopano from Outlook:
thats unfortunately just 50%.
Ah, I wasn’t aware since I just briefly tried it out myself.
@rolf said in PGP Encrypted mail with Gpg4win and Kopano from Outlook:
is there the possibility that this may be solved this year? That’ll be great :-)
PGP currently isn’t a priority for us at Kopano. If an external developer want to dive into this then patches are welcome.
-
Hello,
I just want to ask if there are any news on this topic. I have a client who licensed a new Kopano subscription (30 Users). My client has the same problems as described above. The use of GPG/PGP encryption is a must have in this case.I hope we can find a solution on this topic?
-
@robgnu unfortunately our own priorities have not changed since my last reply.
-
@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.
-
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 -
@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.
