Re: [Evolution-hackers] Support for Autocrypt?

2018-01-02 Thread Martin Owens
On Wed, 2018-01-03 at 01:55 +0100, Ángel wrote: > - Adding a UI option of "encrypt with autocrypt" (?) > - Figure out how and where to implement in the composer the option to > encrypt or not, it needs querying the autocrypt backend in order to > show > a state of enabled/available but

Re: [Evolution-hackers] Support for Autocrypt?

2018-01-02 Thread Milan Crha
On Tue, 2018-01-02 at 16:32 +0100, Tobias Mueller wrote: > How feasible is it, though, to implement this as a plugin to > Evolution? > AFAIU it would need to be able to get the context in terms of what > headers the currently replied-to email has. Hi, I read the project page only briefly,

Re: [Evolution-hackers] Support for Autocrypt?

2018-01-02 Thread Milan Crha
On Tue, 2018-01-02 at 10:12 -0500, Martin Owens wrote: > On Tue, 2018-01-02 at 13:45 +0100, Milan Crha wrote: > > thus there's a problem with interoperability (at the moment) > > and basically no use for it in corporate environments (read: with > > Outlook users), thus definitely no high priority

Re: [Evolution-hackers] Support for Autocrypt?

2018-01-02 Thread Philip Whitehouse
On 2018-01-02 12:45, Milan Crha wrote: On Mon, 2017-12-18 at 21:25 +0100, Anna Marei wrote: What about Evoulution? thus there's a problem with interoperability (at the moment) and basically no use for it in corporate environments (read: with Outlook users) Pitching it as a chicken and egg

Re: [Evolution-hackers] Support for Autocrypt?

2018-01-02 Thread Tobias Mueller
Hi. On Tue, 2018-01-02 at 13:45 +0100, Milan Crha wrote: > The > biggest problem is that the whole thing depends on the mail > applications, as both ends should use clients which understand the > feature, thus there's a problem with interoperability (at the moment) > and basically no use for it

Re: [Evolution-hackers] Support for Autocrypt?

2018-01-02 Thread Martin Owens
On Tue, 2018-01-02 at 13:45 +0100, Milan Crha wrote: > thus there's a problem with interoperability (at the moment) > and basically no use for it in corporate environments (read: with > Outlook users), thus definitely no high priority for me. Once you > have > a feature request filled you can also