Loading policy/tpa-rfc-15-email-services.md +13 −7 Original line number Diff line number Diff line Loading @@ -159,6 +159,10 @@ This proposal doesn't address the fate of Schleuder or Mailman (or, for that matter, Discourse, RT, or other services that may use email unless explicitly mentioned). We have *some* consideration for high availability situations, which have been explicitly requested in [issue tpo/tpa/team#40604](https://gitlab.torproject.org/tpo/tpa/team/-/issues/40604), but it's not a mandatory part of the work described here. ## Affected users This affects all users which interact with `torproject.org` and its Loading Loading @@ -249,9 +253,9 @@ training would require extra server resources and staff time for deployment. User support might require more time than with a plain forwarding setup, however. Extra care should be taken to consider the possibility of providing a high availability setup, with mailboxes replicated across two sites, to survive outages. We *may* consider the possibility of providing a high availability setup, with mailboxes replicated across two points of presence, to survive outages, if time permits. Therefore, it is estimated that deploying mailboxes would require an extra 2 weeks setup time, with high uncertainty. Ongoing costs would Loading Loading @@ -294,20 +298,22 @@ be evaluated as part of this work to see if it is a viable alternative. ### New mail exchangers This is the configuration of two new "mail exchanger" (MX) server with This is the configuration of new "mail exchanger" (MX) server(s) with TLS certificates signed by a public CA, most likely Let's Encrypt for incoming mail, replacing a part of `eugeni`. Those servers should be setup in two redundant points of presence. Those servers may be setup in two redundant points of presence, if time permits. ### New mail relay This is configuration of two new "mail relay" server to relay mails from This is configuration of new "mail relay" server(s) to relay mails from servers that do not send their own email, replacing a part of `eugeni`, similar to current submission server, except with TLS authentication instead of password. Those should equally be distributed in two redundant locations. Those servers may be setup in two redundant points of presence, if time permits. ### Puppet refactoring Loading Loading
policy/tpa-rfc-15-email-services.md +13 −7 Original line number Diff line number Diff line Loading @@ -159,6 +159,10 @@ This proposal doesn't address the fate of Schleuder or Mailman (or, for that matter, Discourse, RT, or other services that may use email unless explicitly mentioned). We have *some* consideration for high availability situations, which have been explicitly requested in [issue tpo/tpa/team#40604](https://gitlab.torproject.org/tpo/tpa/team/-/issues/40604), but it's not a mandatory part of the work described here. ## Affected users This affects all users which interact with `torproject.org` and its Loading Loading @@ -249,9 +253,9 @@ training would require extra server resources and staff time for deployment. User support might require more time than with a plain forwarding setup, however. Extra care should be taken to consider the possibility of providing a high availability setup, with mailboxes replicated across two sites, to survive outages. We *may* consider the possibility of providing a high availability setup, with mailboxes replicated across two points of presence, to survive outages, if time permits. Therefore, it is estimated that deploying mailboxes would require an extra 2 weeks setup time, with high uncertainty. Ongoing costs would Loading Loading @@ -294,20 +298,22 @@ be evaluated as part of this work to see if it is a viable alternative. ### New mail exchangers This is the configuration of two new "mail exchanger" (MX) server with This is the configuration of new "mail exchanger" (MX) server(s) with TLS certificates signed by a public CA, most likely Let's Encrypt for incoming mail, replacing a part of `eugeni`. Those servers should be setup in two redundant points of presence. Those servers may be setup in two redundant points of presence, if time permits. ### New mail relay This is configuration of two new "mail relay" server to relay mails from This is configuration of new "mail relay" server(s) to relay mails from servers that do not send their own email, replacing a part of `eugeni`, similar to current submission server, except with TLS authentication instead of password. Those should equally be distributed in two redundant locations. Those servers may be setup in two redundant points of presence, if time permits. ### Puppet refactoring Loading
