From dc3f16ce6815f5aa74c88282daad5c9e698ead65 Mon Sep 17 00:00:00 2001
From: Christian Heller <c.heller@plomlompom.de>
Date: Wed, 28 Oct 2020 16:56:43 +0100
Subject: [PATCH] Fix emacs mail setup.

---
 buster/home_files/user/.emacs.d/init.el | 17 +++++++++++++++++
 1 file changed, 17 insertions(+)

diff --git a/buster/home_files/user/.emacs.d/init.el b/buster/home_files/user/.emacs.d/init.el
index 60c7b88..fbec980 100644
--- a/buster/home_files/user/.emacs.d/init.el
+++ b/buster/home_files/user/.emacs.d/init.el
@@ -127,6 +127,23 @@
 (setq mml-secure-openpgp-encrypt-to-self t)
 (add-hook 'message-setup-hook 'mml-secure-sign-pgpmime)
 
+;(setq gnutls-log-level 0)
+
+;; if we don't set this, we get this warning:
+;;   gnutls.c: [1] Note that the security level of the Diffie-Hellman key exchange
+;;   has been lowered to 256 bits and this may allow decryption of the session data
+(setq gnutls-min-prime-bits 1024)
+
+;; there is a WEIRD bug somewhere in /network-stream-open-tls/ that disappears the
+;; stream process, seemingly unless the /message/ function is called at the right
+;; place (earliest in /nsm-verify-connection/ right before the "cond" there, latest
+;; in /network-stream-get-response/ right after "(goto-char start)"; this works
+;; unless /inhibit_message/ is set, indicating that writing to the *Messages*
+;; buffer is not relevant, but maybe writing to the echo area is); activing the
+;; gnutls logging is just a hack to achieve such calls to /message/ in the
+;; /network-stream-open-tls/ flow.
+(setq gnutls-log-level 1) ; miraculously makes smtpmail work
+
 ;; constructs From: domain if mail composer directly called (from without
 ;; notmuch), but we don't actually intend to do that
 ;(setq mail-host-address "plomlompom.com")
-- 
2.30.2