holger krekel

maybe we need to change this and allow configurations where we don't have the secret key ourselves. originally we wanted to have an "autocrypt only keystore" but i guess the...

On Mon, May 21, 2018 at 15:23 -0700, Olivier Mehani wrote: > On Mon 21 May 2018 at 08:34:47 -0700, holger krekel wrote: > > The quoted code is currently...

or the other way round: make everything use keyhandles (or rather fingerprints) and keep a chain with all public keys (own, peer, dkim). this might also help with #73

Autocrypt/Mailman design discussions take place on https://github.com/autocrypt/autocrypt/issues/357 for now. Here it's going to be more about implementation (once it starts), and potential relations to #29

From @j08ny i got some links relevant for mailman / muacrypt / autocrypt integration: - django configuration app using mailman REST plugin endpoints: https://gitlab.com/J08nY/django-pgpmailman - mailman-pgp: https://gitlab.com/J08nY/mailman-pgp - mailman-rest-events: https://gitlab.com/J08nY/mailman-rest-events

Would adding an "--account ACC" option to process-incoming help? This would shortcut the determination of which account to process an email with.

in the new "scandir-incoming" there is new logic which does not look at Delivered-To anymore, other places (in process-incoming) need to be adapted accordingly. The problem with delivered-to is that...

yes, keys are not deleted from the keyring. still the bot should use your latest key unless there is a logical processing problem (in the autocrypt processing logic). muacrypt keeps...

testing against real-life inboxes i consider more a question of a custom helper script that walks through all messages and attempts decryption through the respective APIs. I thus don't plan...

Heart from @j08ny that https://pgpy.readthedocs.io/en/latest/progress.html summarizes where pgpy stands. Reading partial-length packets works but writing them does not. For encrypted e-mail processing that's probably sufficient. Now what remains is trying...