From ce193f98e2176f53f843d2a73658e13f528df22a Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Antoine=20Beaupr=C3=A9?= <anarcat@debian.org>
Date: Tue, 12 Apr 2022 11:30:55 -0400
Subject: [PATCH] venture a guess at a more general email policy

---
 policy/tpa-rfc-15-email-services.md | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/policy/tpa-rfc-15-email-services.md b/policy/tpa-rfc-15-email-services.md
index e434f9c9..0376b7d7 100644
--- a/policy/tpa-rfc-15-email-services.md
+++ b/policy/tpa-rfc-15-email-services.md
@@ -259,10 +259,10 @@ Possible solutions include:
     
 This goes in hand with the [email policy problem][] which is basically
 the question of what service can be used for (e.g. forwards vs lists
-vs RT).
-
-TODO: formulate a quick guess as to the solution to the email policy
-problem here.
+vs RT). In general, email forwarding causes all sorts of problems and
+we may want to consider, in the long term, other options for many
+aliases, either mailing lists or issue trackers. But that question is
+out of scope of this proposal for now.
 
 ### Incoming mail filtering
 
-- 
GitLab