Verified Commit 1e7e4855 authored by anarcat's avatar anarcat
Browse files

TPA-RFC-15 was proposed today! 

See team#40363
parent ae63df29

policy.md

+1 −1
Original line number Diff line number Diff line
@@ -14,7 +14,6 @@ and add it to the above list. 


 * [TPA-RFC-3: tools](policy/tpa-rfc-3-tools)

 * [TPA-RFC-11: SVN retirement](policy/tpa-rfc-11-svn-retirement)

 * [TPA-RFC-15: Email services](policy/tpa-rfc-15-email-services)

 * [TPA-RFC-16: Replacing lektor-i18n-plugin](policy/tpa-rfc-16-replacing-lektor-i18n-plugin)

 * [TPA-RFC-17: Disaster recover](policy/tpa-rfc-17-disaster-recovery)

 * [TPA-RFC-18: Security policy](policy/tpa-rfc-18-security-policy)
@@ -23,6 +22,7 @@ and add it to the above list. 


<!-- No policy is currently `proposed`. -->



 * [TPA-RFC-15: Email services](policy/tpa-rfc-15-email-services)

 * [TPA-RFC-23: retire ipv6only.torproject.net](policy/tpa-rfc-23-retire-ipv6only)

 * [TPA-RFC-24: Extend merge permissions for web projects](policy/tpa-rfc-24-extend-merge-permissions-web)

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

+7 −9
Original line number Diff line number Diff line
@@ -374,10 +374,8 @@ Changes in this diagram: 


## Timeline



This timeline is a draft, and will be updated according to when this

proposal is adopted. The changes will be distributed over a year, and

the following is a per-quarter breakdown, starting from when the

proposal is adopted.

The changes will be distributed over a year, and the following is a

per-quarter breakdown, starting from when the proposal is adopted.



Obviously, the deployment will depend on availability of TPA staff and

the collaboration of TPO members. It might also be reordered to
@@ -385,23 +383,23 @@ prioritize more urgent problems that come up. The complaints we 
received from Hetzner, for example should probably be a priority

([issue 40539][]).



 * Q1:

 * 2022 Q2:

   * End-to-end deliverability checks

   * DMARC reports analysis (DMARC record `p=none`)

   * partial incoming mail filtering (bridges, lists, tpo, [issue

     40539][])

   * progressive adoption of submission server

   * Puppet refactoring

 * Q2:

 * 2022 Q3:

   * IMAP and webmail server deployment

   * mail exchanger deployment

   * relay server deployment

   * global incoming mail filtering

   * deadline for adoption of the submission server

 * Q3:

 * 2022 Q4:

   * DKIM and ARC signatures

   * SPF records, "soft" (`~all`)

 * Q4:

 * 2023 Q1:

   * hard DMARC (`p=reject`) and SPF (`-all`) records



## Challenges
@@ -1013,7 +1011,7 @@ the former. 


# Status



This proposal is currently in the `draft` state.

This proposal is currently in the `proposed` state.



# References