From 2764c8c73f6f8c2e83cf9de81002c2d3a8f778ea Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Antoine=20Beaupr=C3=A9?= <anarcat@debian.org>
Date: Tue, 24 Aug 2021 15:26:33 -0400
Subject: [PATCH] link to the SPF/DKIM issue in the roadmap
it's just one possible solution on the deliverability issue, which
will probably require a TPA-RFC to officialize
---
roadmap/2021.md | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/roadmap/2021.md b/roadmap/2021.md
index 9d1736d8..d2e79531 100644
--- a/roadmap/2021.md
+++ b/roadmap/2021.md
@@ -28,7 +28,9 @@ attention. In general, the over-arching goals are therefore:
* [ ] systematically followup on and respond to abuse complaints (https://gitlab.torproject.org/tpo/tpa/team/-/issues/40168)
* [ ] diagnose and resolve delivery issues (e.g. [Yahoo](https://gitlab.torproject.org/tpo/tpa/team/-/issues/34134),
[state.gov](https://gitlab.torproject.org/tpo/tpa/team/-/issues/40202), [Gmail](https://gitlab.torproject.org/tpo/tpa/team/-/issues/40170), [Gmail again](https://gitlab.torproject.org/tpo/tpa/team/-/issues/40149))
- * [ ] provide reliable delivery for users ("my email ends up in spam!")
+ * [ ] provide reliable delivery for users ("my email ends up in
+ spam!"), possibly by following newer standards like SPF,
+ DKIM, DMARC... ([issue 40363](https://gitlab.torproject.org/tpo/tpa/team/-/issues/40363))
* [ ] possible implementations:
* [ ] setup a new MX server to receive incoming email, with
"real" (Let's encrypt) TLS certificates, routing to
--
GitLab