regroup alternatives more meaningfully

policy/tpa-rfc-15-email-services.md

@@ -649,6 +649,33 @@ replication for a "warm" spare.
 Multi-primary setups would require "sharding" the users across
 multiple servers and is definitely considered out of scope.
 
+## Status quo
+
+The current status quo is also an option. But it is our belief that it
+will lead to further and further problem in deliverability. We already
+have a lot of problems delivering mail to various providers, and it's
+hard to diagnose issues because anyone can currently send mail
+masquerading as us from anywhere.
+
+There might be *other* solutions than the ones proposed here, but we
+haven't found any good ways of solving those issues without radically
+changing the infrastructure so far.
+
+If anything, if things continue as they are, people are going to use
+their `@torproject.org` email address less and less, and we'll
+effectively be migrating to external providers, but delegating that
+workload to individual volunteers and workers. The mailing list and,
+more critically, support and promotional tools (RT and CiviCRM)
+services will become less and less effective in actually delivering
+emails in people's inbox and, ultimately, this will hurt our capacity
+to help our users and raise funds that are critical to the future of
+the project.
+
+## The end of email
+
+TODO: forum, matrix, etc. quality of participation, community
+organising.
+
 ## External hosting
 
 Other service providers have been contacted to see if it would be
@@ -741,33 +768,6 @@ looked at this, it was a 1750€ setup fee with 2.5€ per user-year.
 
 It's unclear if we could do mass-mailing with this service.
 
-## Status quo
-
-The current status quo is also an option. But it is our belief that it
-will lead to further and further problem in deliverability. We already
-have a lot of problems delivering mail to various providers, and it's
-hard to diagnose issues because anyone can currently send mail
-masquerading as us from anywhere.
-
-There might be *other* solutions than the ones proposed here, but we
-haven't found any good ways of solving those issues without radically
-changing the infrastructure so far.
-
-If anything, if things continue as they are, people are going to use
-their `@torproject.org` email address less and less, and we'll
-effectively be migrating to external providers, but delegating that
-workload to individual volunteers and workers. The mailing list and,
-more critically, support and promotional tools (RT and CiviCRM)
-services will become less and less effective in actually delivering
-emails in people's inbox and, ultimately, this will hurt our capacity
-to help our users and raise funds that are critical to the future of
-the project.
-
-## The end of email
-
-TODO: forum, matrix, etc. quality of participation, community
-organising.
-
 # Deadline
 
 TODO.