Allow specifying certificate file through account configuration for
source and outgoing connections.
---
 commands/compose/send.go | 13 ++++---
 config/config.go         | 75 +++++++++++++++++++++++++++++++---------
 worker/imap/worker.go    |  9 +++--
 3 files changed, 74 insertions(+), 23 deletions(-)

diff --git a/commands/compose/send.go b/commands/compose/send.go
index f61478f..31cfbdc 100644
--- a/commands/compose/send.go
+++ b/commands/compose/send.go
@@ -3,6 +3,7 @@ package compose
 import (
[message trimmed]

On Mon Feb 22, 2021 at 2:46 PM EET, Reto wrote:
> Better would be cert pinning which is
> https://todo.sr.ht/~sircmpwn/aerc2/329

I have a proof-of-concept implementation of cert pinning. I implemented
that specifically to be able to use aerc with ProtonMail Bridge.

I'm still learning how to use email lists for patches and in general and
therefore hadn't pushed my changes yet anywhere. But since someone else
showed interest in that, I'll push a patch to the list shortly.

---
 niko | 1 +
 1 file changed, 1 insertion(+)
 create mode 100644 niko

diff --git a/niko b/niko
new file mode 100644
index 0000000..c71e388
--- /dev/null
+++ b/niko
@@ -0,0 +1 @@
+Trying git send-email
--
2.26.2
[message trimmed]