On Jan 31, 2018, at 09:28, Jan Jancar wrote:
> Plugin configuration is done through the Mailman configuration and those
> are read-only through the REST interface. However a plugin might supply
> it's own REST endpoints for example for per-list setup/configuration.
Yep; configuration options are
Hi Jan,
On Wed, Jan 31, 2018 at 19:00 +0100, Jan Jancar wrote:
> >> If you would like to use a Python OpenPGP implementation you could look
> >> at [PGPy] and how I used it in mailman-pgp.
> >
> > It's under consideration here: https://github.com/hpk42/muacrypt/issues/32
> > Are your experiences
>> If you would like to use a Python OpenPGP implementation you could look
>> at [PGPy] and how I used it in mailman-pgp.
>
> It's under consideration here: https://github.com/hpk42/muacrypt/issues/32
> Are your experiences with pgpy indicating it's compatible with
> enigmail and k9-mail? (see th
Hi Jan,
On Wed, Jan 31, 2018 at 15:28 +0100, Jan Jancar wrote:
> Hi all!
>
> On 01/25/2018 12:21 PM, holger krekel wrote:
> > Indeed, i guess a plugin should get us >90% there. Here are my
> > current technical considerations in a quick list:
> >
> > - Autocrypt L1 specifies how to generate an
Hi all!
On 01/25/2018 12:21 PM, holger krekel wrote:
> Indeed, i guess a plugin should get us >90% there. Here are my
> current technical considerations in a quick list:
>
> - Autocrypt L1 specifies how to generate an Autocrypt key, transfer and
> parse public keys and settings through heade
