<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <link rel="alternate" type="text/html" href="https://status.torproject.org/"/>
    <title>Mailing Lists on Tor Project status</title>
    <link>https://status.torproject.org/affected/mailing-lists/</link>
    <description>Incident history</description>
    <generator>github.com/cstate</generator>
    <language>en</language>
    
    <lastBuildDate>2024-12-03T03:30:00+00:00</lastBuildDate>
    <updated>2024-12-03T03:30:00+00:00</updated>
    
    
    
      <atom:link href="https://status.torproject.org/affected/mailing-lists/index.xml" rel="self" type="application/rss+xml" />
    
    
      <item>
        <title>[Resolved] Router maintenance at Hetzner</title>
        <link>https://status.torproject.org/issues/2024-12-03-hetzner-router-maintenance/</link>
        <pubDate>Tue, 03 Dec 2024 03:30:00 +0000</pubDate>
        <guid>https://status.torproject.org/issues/2024-12-03-hetzner-router-maintenance/</guid>
        <category>2024-12-03 5:30:00 &#43;0000</category>
        <description>Hetzner has planned an emergency maintenance window on all of their routers, which will cause a network outage on all of our hosts in their datacenters. The maintenance window is planned on December 3rd 2024 from 3:30 UTC to 5:30 UTC, during which the network may experience spurious outages.
Services should come back online automatically as soon as network connectivity is restored by Hetzner.</description>
        <content type="html">&lt;p&gt;Hetzner has planned an emergency maintenance window on all of their routers,
which will cause a network outage on all of our hosts in their datacenters. The
maintenance window is planned on December 3rd 2024 from 3:30 UTC to 5:30 UTC,
during which the network may experience spurious outages.&lt;/p&gt;
&lt;p&gt;Services should come back online automatically as soon as network connectivity
is restored by Hetzner.&lt;/p&gt;
</content>
      </item>
    
      <item>
        <title>[Resolved] Mailman 3 upgrade</title>
        <link>https://status.torproject.org/issues/2024-10-29-mailman3-upgrade/</link>
        <pubDate>Mon, 04 Nov 2024 14:00:00 +0000</pubDate>
        <guid>https://status.torproject.org/issues/2024-10-29-mailman3-upgrade/</guid>
        <category>2024-11-04 21:00:00 &#43;0000</category>
        <description>TL;DR: Mailman 3 upgrade happened on November 4th, starting at 14:00 UTC, and ending around 21:00 UTC. Report issues on GitLab.
As mentioned in early October, we&amp;rsquo;re in the process of upgrading our main mail server, which includes upgrading to the shiny new Mailman 3 platform. This will involve short per-list outage as each migrates over to the new server. It&amp;rsquo;s unclear how long the maintenance will last, but assume mailing lists will be disrupted all day, although each migration should only take a couple of minutes each.</description>
        <content type="html">&lt;p&gt;TL;DR: Mailman 3 upgrade happened on November 4th, starting at 14:00
UTC, and ending around 21:00 UTC. Report issues on GitLab.&lt;/p&gt;
&lt;p&gt;As mentioned in early October, we&amp;rsquo;re in the process of upgrading our
main mail server, which includes upgrading to the shiny new Mailman 3
platform. This will involve short per-list outage as each migrates
over to the new server. It&amp;rsquo;s unclear how long the maintenance will
last, but assume mailing lists will be disrupted all day, although
each migration should only take a couple of minutes each.&lt;/p&gt;
&lt;p&gt;We have, right now, a prototype mailman 3 server available at:&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://lists-01.torproject.org/&#34;&gt;https://lists-01.torproject.org/&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;The TPA mailing list has been succesfully migrated already and next
week, I&amp;rsquo;ll start migrating the other mailing lists (including this
one!).&lt;/p&gt;
&lt;p&gt;Be warned that Mailman 3 is a significant upgrade from Mailman 2. There
are some great things (like unified authentication), and some less great
things (like a more complex design and &amp;ldquo;shinier&amp;rdquo; web interface that
might not be everyone&amp;rsquo;s taste).&lt;/p&gt;
&lt;p&gt;As a reminder, we&amp;rsquo;re doing this upgrade a little rushed because the main
mail server is now unsupported for security upgrades. See the details of
the proposal here:&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://gitlab.torproject.org/tpo/tpa/team/-/wikis/policy/tpa-rfc-71-emergency-email-deployments-round-2&#34;&gt;https://gitlab.torproject.org/tpo/tpa/team/-/wikis/policy/tpa-rfc-71-emergency-email-deployments-round-2&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&amp;hellip; with the upgrade work being tracked in this issue:&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://gitlab.torproject.org/tpo/tpa/team/-/issues/40471&#34;&gt;https://gitlab.torproject.org/tpo/tpa/team/-/issues/40471&lt;/a&gt;&lt;/p&gt;
</content>
      </item>
    
      <item>
        <title>[Resolved] Email delivery problems</title>
        <link>https://status.torproject.org/issues/2022-11-30-mail-delivery/</link>
        <pubDate>Wed, 30 Nov 2022 20:00:00 +0000</pubDate>
        <guid>https://status.torproject.org/issues/2022-11-30-mail-delivery/</guid>
        <category>2022-12-15 21:48:00</category>
        <description>We have had repeated reports over the past weeks of delivery failures, particularly at Gmail but it&amp;rsquo;s possible it affects mail delivery across the board.
Update, 2022-12-05: we are deploying emergency workarounds, see issue tpo/tpa/team#40981 for progress updates.
Update, 2022-12-14: DMARC, SPF records and DKIM signatures on outgoing mail hosts deployed, reputation improved. May impact negatively users not using the submission server.
Update, 2022-12-15: mail services considered restored, see TPA-RFC-45 or further improvements.</description>
        <content type="html">&lt;p&gt;We have had repeated reports over the past weeks of delivery failures,
particularly at Gmail but it&amp;rsquo;s possible it affects mail delivery
across the board.&lt;/p&gt;
&lt;p&gt;Update, 2022-12-05: we are deploying emergency workarounds, see &lt;a href=&#34;https://gitlab.torproject.org/tpo/tpa/team/-/issues/40981&#34;&gt;issue
tpo/tpa/team#40981&lt;/a&gt; for progress updates.&lt;/p&gt;
&lt;p&gt;Update, 2022-12-14: DMARC, SPF records and DKIM signatures on outgoing
mail hosts deployed, reputation improved. May impact negatively users
&lt;em&gt;not&lt;/em&gt; using the submission server.&lt;/p&gt;
&lt;p&gt;Update, 2022-12-15: mail services considered restored, see
&lt;a href=&#34;https://gitlab.torproject.org/tpo/tpa/team/-/issues/41009&#34;&gt;TPA-RFC-45&lt;/a&gt; or further improvements.&lt;/p&gt;
</content>
      </item>
    
      <item>
        <title>[Resolved] routing issues at main provider</title>
        <link>https://status.torproject.org/issues/2022-01-25-routing-issues/</link>
        <pubDate>Tue, 25 Jan 2022 06:00:00 +0000</pubDate>
        <guid>https://status.torproject.org/issues/2022-01-25-routing-issues/</guid>
        <category>2022-01-27 18:58:00 &#43;0000</category>
        <description>We are experiencing intermittent network outages that typically resolve themselves within a few hours. Preliminary investigations seem to point at routing issues at Hetzner, but we have yet to get a solid diagnostic. We&amp;rsquo;re following that issue in issue 40601.</description>
        <content type="html">&lt;p&gt;We are experiencing intermittent network outages that typically
resolve themselves within a few hours. Preliminary investigations seem
to point at routing issues at Hetzner, but we have yet to get a solid
diagnostic. We&amp;rsquo;re following that issue in &lt;a href=&#34;https://gitlab.torproject.org/tpo/tpa/team/-/issues/40601&#34;&gt;issue 40601&lt;/a&gt;.&lt;/p&gt;
</content>
      </item>
    
      <item>
        <title>[Resolved] Email delivery problems to Google</title>
        <link>https://status.torproject.org/issues/2021-01-25-gmail-bounce/</link>
        <pubDate>Mon, 25 Jan 2021 21:40:00 +0000</pubDate>
        <guid>https://status.torproject.org/issues/2021-01-25-gmail-bounce/</guid>
        <category>2021-01-25 21:40:00</category>
        <description>Google mail servers are currently bouncing some emails coming from @torproject.org, as sent from our main mail server (eugeni) and third-party servers. This includes lists but may not include all our mail servers (the donation platform, for example, seems to still work).
We are still investigating the problem, followup in issue 40149.
Update, 22:16UTC: it looks like only some emails are being bounced, especially a particular email from a particular sysadmin which made him jump the gun and post this disruption notice.</description>
        <content type="html">&lt;p&gt;Google mail servers are currently bouncing some emails coming from
&lt;code&gt;@torproject.org&lt;/code&gt;, as sent from our main mail server (&lt;code&gt;eugeni&lt;/code&gt;) and
third-party servers. This includes lists but may not include all our
mail servers (the donation platform, for example, seems to still
work).&lt;/p&gt;
&lt;p&gt;We are still investigating the problem, followup in &lt;a href=&#34;https://gitlab.torproject.org/tpo/tpa/team/-/issues/40149&#34;&gt;issue 40149&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Update, 22:16UTC&lt;/strong&gt;: it looks like only &lt;em&gt;some&lt;/em&gt; emails are being
bounced, especially a particular email from a particular sysadmin
which made him jump the gun and post this disruption notice. We might
actually be in our normal &amp;ldquo;somewhat disrupted&amp;rdquo; delivery
situation. &lt;a href=&#34;https://en.wikipedia.org/wiki/Buddy_Holly_(song)&#34;&gt;Stay tuned for more happy days&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Update, 2021-01-27 16:51UTC&lt;/strong&gt;: it turns out this was a false alarm,
and concerns only a single Google group that is refusing
emails. Emails are being delivered to Google fine.&lt;/p&gt;
</content>
      </item>
    
  </channel>
</rss>
