<?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://opalstackstatus.com/"/>
    <title>IMAP/POP3 (USA) on Opalstack Status</title>
    <link>https://opalstackstatus.com/affected/imap/pop3-usa/</link>
    <description>Incident history</description>
    <generator>github.com/cstate</generator>
    <language>en</language>
    
    <lastBuildDate>2026-07-22T15:02:00+00:00</lastBuildDate>
    <updated>2026-07-22T15:02:00+00:00</updated>
    
    
    
      <atom:link href="https://opalstackstatus.com/affected/imap/pop3-usa/index.xml" rel="self" type="application/rss+xml" />
    
    
      <item>
        <title>[Resolved] US IMAP impacted by scheduled maintenance</title>
        <link>https://opalstackstatus.com/issues/2026-07-22-us-imap-impacted-by-scheduled-maintenance/</link>
        <pubDate>Wed, 22 Jul 2026 15:02:00 +0000</pubDate>
        <guid>https://opalstackstatus.com/issues/2026-07-22-us-imap-impacted-by-scheduled-maintenance/</guid>
        <category>2026-07-23 07:06:11</category>
        <description>&lt;p&gt;&lt;em&gt;Fixed&lt;/em&gt; - The backlog of incoming mail has been delivered. The maintenance is complete. 
  &lt;span class=&#34;faded&#34;&gt;(07:06 UTC — Jul 23)&lt;/span&gt;

&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Watching&lt;/em&gt; - imap1.us.opalstack.com is back online. The backlog of incoming emails is currently being processed. 
  &lt;span class=&#34;faded&#34;&gt;(05:55 UTC — Jul 23)&lt;/span&gt;

&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Investigating&lt;/em&gt; - The upstream management systems are back online and we&amp;rsquo;re now actively working to restore service. 
  &lt;span class=&#34;faded&#34;&gt;(03:47 UTC — Jul 23)&lt;/span&gt;

&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Investigating&lt;/em&gt; - The restoration of service is being delayed by an unfortunately-timed outage in our upstream provider&amp;rsquo;s management systems. We regret the extended downtime and are doing everything that we can to restore service as soon as possible. 
  &lt;span class=&#34;faded&#34;&gt;(02:28 UTC — Jul 23)&lt;/span&gt;

&lt;/p&gt;</description>
        <content type="html">&lt;p&gt;&lt;em&gt;Fixed&lt;/em&gt; - The backlog of incoming mail has been delivered. The maintenance is complete. 
  &lt;span class=&#34;faded&#34;&gt;(07:06 UTC — Jul 23)&lt;/span&gt;

&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Watching&lt;/em&gt; - imap1.us.opalstack.com is back online. The backlog of incoming emails is currently being processed. 
  &lt;span class=&#34;faded&#34;&gt;(05:55 UTC — Jul 23)&lt;/span&gt;

&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Investigating&lt;/em&gt; - The upstream management systems are back online and we&amp;rsquo;re now actively working to restore service. 
  &lt;span class=&#34;faded&#34;&gt;(03:47 UTC — Jul 23)&lt;/span&gt;

&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Investigating&lt;/em&gt; - The restoration of service is being delayed by an unfortunately-timed outage in our upstream provider&amp;rsquo;s management systems. We regret the extended downtime and are doing everything that we can to restore service as soon as possible. 
  &lt;span class=&#34;faded&#34;&gt;(02:28 UTC — Jul 23)&lt;/span&gt;

&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Investigating&lt;/em&gt; - The resolution of this issue is being delayed by an unfortunately-timed outage in our upstream provider&amp;rsquo;s management systems. We do regret the extended downtime and are doing everything we can to restore service as soon as possible. 
  &lt;span class=&#34;faded&#34;&gt;(02:24 UTC — Jul 23)&lt;/span&gt;

&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Investigating&lt;/em&gt; - The data center team is still working to bring the server back online. 
  &lt;span class=&#34;faded&#34;&gt;(00:30 UTC — Jul 23)&lt;/span&gt;

&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Investigating&lt;/em&gt; - The server still has not come back online, the data center team is investigating. 
  &lt;span class=&#34;faded&#34;&gt;(22:33 UTC — Jul 22)&lt;/span&gt;

&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Watching&lt;/em&gt; - The server is presently rebooting and should be back online soon. 
  &lt;span class=&#34;faded&#34;&gt;(22:13 UTC — Jul 22)&lt;/span&gt;

&lt;/p&gt;
&lt;p&gt;[July 23 05:38 UTC] The maintenance is complete - imap1.us.opalstack.com is back up and running.&lt;/p&gt;
&lt;p&gt;[July 22 15:02 UTC] imap1.us.opalstack.com is currently offline for scheduled maintenance. We&amp;rsquo;ll update this post when the server is back online. 
  &lt;span class=&#34;faded&#34;&gt;(15:02 UTC — Jul 22)&lt;/span&gt;

&lt;/p&gt;
</content>
      </item>
    
      <item>
        <title>[Resolved] Delays in US incoming mail</title>
        <link>https://opalstackstatus.com/issues/2024-04-02-delays-in-us-incoming-mail/</link>
        <pubDate>Tue, 02 Apr 2024 18:04:00 +0000</pubDate>
        <guid>https://opalstackstatus.com/issues/2024-04-02-delays-in-us-incoming-mail/</guid>
        <category>2024-04-02 20:30:26</category>
        <description>&lt;p&gt;&lt;em&gt;Fixed&lt;/em&gt; - All pending incoming US mail has been delivered. 
  &lt;span class=&#34;faded&#34;&gt;(20:30 UTC — Apr 2)&lt;/span&gt;

&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Watching&lt;/em&gt; - The high load condition is resolved and the backlog of pending mail is being delivered. 
  &lt;span class=&#34;faded&#34;&gt;(18:25 UTC — Apr 2)&lt;/span&gt;

&lt;/p&gt;
&lt;p&gt;At this time there is a high load condition on one of our US IMAP servers which is a variety of issues for some US mail customers including:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Delays in the receipt of incoming mail&lt;/li&gt;
&lt;li&gt;Slow performance in IMAP mail clients&lt;/li&gt;
&lt;li&gt;Slow performance in the Opalstack US webmail system&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;We&amp;rsquo;re working to mitigate the problem at this time and will update this post when more information is available. 
  &lt;span class=&#34;faded&#34;&gt;(18:04 UTC — Apr 2)&lt;/span&gt;

&lt;/p&gt;</description>
        <content type="html">&lt;p&gt;&lt;em&gt;Fixed&lt;/em&gt; - All pending incoming US mail has been delivered. 
  &lt;span class=&#34;faded&#34;&gt;(20:30 UTC — Apr 2)&lt;/span&gt;

&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Watching&lt;/em&gt; - The high load condition is resolved and the backlog of pending mail is being delivered. 
  &lt;span class=&#34;faded&#34;&gt;(18:25 UTC — Apr 2)&lt;/span&gt;

&lt;/p&gt;
&lt;p&gt;At this time there is a high load condition on one of our US IMAP servers which is a variety of issues for some US mail customers including:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Delays in the receipt of incoming mail&lt;/li&gt;
&lt;li&gt;Slow performance in IMAP mail clients&lt;/li&gt;
&lt;li&gt;Slow performance in the Opalstack US webmail system&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;We&amp;rsquo;re working to mitigate the problem at this time and will update this post when more information is available. 
  &lt;span class=&#34;faded&#34;&gt;(18:04 UTC — Apr 2)&lt;/span&gt;

&lt;/p&gt;
</content>
      </item>
    
      <item>
        <title>[Resolved] Change to default SPF and DMARC policies</title>
        <link>https://opalstackstatus.com/issues/2024-01-24-change-to-default-spf-and-dmarc-policies/</link>
        <pubDate>Wed, 24 Jan 2024 20:03:12 +0000</pubDate>
        <guid>https://opalstackstatus.com/issues/2024-01-24-change-to-default-spf-and-dmarc-policies/</guid>
        <category>2024-01-24 20:03:12</category>
        <description>&lt;p&gt;On 23 January 2024 we began publishing default SPF and DMARC DNS records for domains that use Opalstack&amp;rsquo;s DNS and mail systems.&lt;/p&gt;
&lt;p&gt;The default policies that we published were somewhat restrictive and were causing mail sent from some customer domains to go to spam so we&amp;rsquo;ve made the following changes to the policies:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;The policy for SPF has been changed from hard fail &amp;ldquo;-all&amp;rdquo; to soft fail &amp;ldquo;~all&amp;rdquo;.&lt;/li&gt;
&lt;li&gt;The policy for DMARC has been changed from &amp;ldquo;quarantine&amp;rdquo; to &amp;ldquo;none&amp;rdquo;.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The net result of these changes is that customer mail is still compliant with SPF and DMARC but with a less-restrictive policy to help legitimate mail arrive in your inbox. 
  &lt;span class=&#34;faded&#34;&gt;(20:03 UTC — Jan 24)&lt;/span&gt;

&lt;/p&gt;</description>
        <content type="html">&lt;p&gt;On 23 January 2024 we began publishing default SPF and DMARC DNS records for domains that use Opalstack&amp;rsquo;s DNS and mail systems.&lt;/p&gt;
&lt;p&gt;The default policies that we published were somewhat restrictive and were causing mail sent from some customer domains to go to spam so we&amp;rsquo;ve made the following changes to the policies:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;The policy for SPF has been changed from hard fail &amp;ldquo;-all&amp;rdquo; to soft fail &amp;ldquo;~all&amp;rdquo;.&lt;/li&gt;
&lt;li&gt;The policy for DMARC has been changed from &amp;ldquo;quarantine&amp;rdquo; to &amp;ldquo;none&amp;rdquo;.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The net result of these changes is that customer mail is still compliant with SPF and DMARC but with a less-restrictive policy to help legitimate mail arrive in your inbox. 
  &lt;span class=&#34;faded&#34;&gt;(20:03 UTC — Jan 24)&lt;/span&gt;

&lt;/p&gt;
</content>
      </item>
    
      <item>
        <title>[Resolved] US webmail performance issues</title>
        <link>https://opalstackstatus.com/issues/2023-03-07-us-webmail-performance-issues/</link>
        <pubDate>Tue, 07 Mar 2023 18:20:00 +0000</pubDate>
        <guid>https://opalstackstatus.com/issues/2023-03-07-us-webmail-performance-issues/</guid>
        <category>2023-03-17 19:18:40</category>
        <description>&lt;p&gt;&lt;em&gt;Fixed&lt;/em&gt; - We&amp;rsquo;ve seen no further performance issues on the US webmail system since implementing the new proxy, so we consider this issue to be resolved. 
  &lt;span class=&#34;faded&#34;&gt;(19:18 UTC — Mar 17)&lt;/span&gt;

&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Watching&lt;/em&gt; - We&amp;rsquo;ve deployed a new IMAP proxy on the US webmail server and the performance seems much better at this time. We&amp;rsquo;ll continue to monitor. 
  &lt;span class=&#34;faded&#34;&gt;(01:20 UTC — Mar 17)&lt;/span&gt;

&lt;/p&gt;
&lt;p&gt;We&amp;rsquo;re aware that the US webmail server has been having intermittent timeout issues, particularly during US business hours.&lt;/p&gt;</description>
        <content type="html">&lt;p&gt;&lt;em&gt;Fixed&lt;/em&gt; - We&amp;rsquo;ve seen no further performance issues on the US webmail system since implementing the new proxy, so we consider this issue to be resolved. 
  &lt;span class=&#34;faded&#34;&gt;(19:18 UTC — Mar 17)&lt;/span&gt;

&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Watching&lt;/em&gt; - We&amp;rsquo;ve deployed a new IMAP proxy on the US webmail server and the performance seems much better at this time. We&amp;rsquo;ll continue to monitor. 
  &lt;span class=&#34;faded&#34;&gt;(01:20 UTC — Mar 17)&lt;/span&gt;

&lt;/p&gt;
&lt;p&gt;We&amp;rsquo;re aware that the US webmail server has been having intermittent timeout issues, particularly during US business hours.&lt;/p&gt;
&lt;p&gt;We&amp;rsquo;re working to resolve this but we expect that it will take at least a couple of weeks. Our recommended workaround in the interim is to use a desktop mail client or to run your own webmail server separately from our managed webmail instance.&lt;/p&gt;
&lt;p&gt;Desktop email client configuration info is available in our user guide at: &lt;a href=&#34;https://docs.opalstack.com/user-guide/email/#email-client-configuration&#34;&gt;Email Client Configuration&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;If you&amp;rsquo;d like to run your own webmail server setup instructions are available at: &lt;a href=&#34;https://community.opalstack.com/d/1146-howto-run-your-own-roundcube-webmail-server-on-opalstack&#34;&gt;HOWTO run your own Roundcube webmail server on Opalstack&lt;/a&gt; 
  &lt;span class=&#34;faded&#34;&gt;(18:20 UTC — Mar 7)&lt;/span&gt;

&lt;/p&gt;
</content>
      </item>
    
      <item>
        <title>[Resolved] Slow performance on the US IMAP/POP3 service</title>
        <link>https://opalstackstatus.com/issues/2022-11-03-slow-performance-on-the-us-imappop3-service/</link>
        <pubDate>Thu, 03 Nov 2022 17:57:23 +0000</pubDate>
        <guid>https://opalstackstatus.com/issues/2022-11-03-slow-performance-on-the-us-imappop3-service/</guid>
        <category>2022-11-09 20:11:16</category>
        <description>&lt;p&gt;&lt;em&gt;Fixed&lt;/em&gt; - The backup is complete and the server load has returned to normal. 
  &lt;span class=&#34;faded&#34;&gt;(20:11 UTC — Nov 9)&lt;/span&gt;

&lt;/p&gt;
&lt;p&gt;At this time load on our US IMAP/POP3 server is intermittently very high because we&amp;rsquo;re running a full backup of the entire server.&lt;/p&gt;
&lt;p&gt;We expect this to continue until the backup is complete, possible for another day or longer.&lt;/p&gt;
&lt;p&gt;We&amp;rsquo;ll update this post when the backup is complete and load has returned to normal. 
  &lt;span class=&#34;faded&#34;&gt;(17:57 UTC — Nov 3)&lt;/span&gt;

&lt;/p&gt;</description>
        <content type="html">&lt;p&gt;&lt;em&gt;Fixed&lt;/em&gt; - The backup is complete and the server load has returned to normal. 
  &lt;span class=&#34;faded&#34;&gt;(20:11 UTC — Nov 9)&lt;/span&gt;

&lt;/p&gt;
&lt;p&gt;At this time load on our US IMAP/POP3 server is intermittently very high because we&amp;rsquo;re running a full backup of the entire server.&lt;/p&gt;
&lt;p&gt;We expect this to continue until the backup is complete, possible for another day or longer.&lt;/p&gt;
&lt;p&gt;We&amp;rsquo;ll update this post when the backup is complete and load has returned to normal. 
  &lt;span class=&#34;faded&#34;&gt;(17:57 UTC — Nov 3)&lt;/span&gt;

&lt;/p&gt;
</content>
      </item>
    
      <item>
        <title>[Resolved] Slow connections or timeouts on US IMAP/POP3/Webmail</title>
        <link>https://opalstackstatus.com/issues/2022-10-06-slow-connections-or-timeouts-on-us-imappop3webmail/</link>
        <pubDate>Thu, 06 Oct 2022 15:46:25 +0000</pubDate>
        <guid>https://opalstackstatus.com/issues/2022-10-06-slow-connections-or-timeouts-on-us-imappop3webmail/</guid>
        <category>2022-10-06 15:46:25</category>
        <description>&lt;p&gt;There was a ~30 minute period between 14:50 UTC and 15:20 UTC during which system load on our US IMAP server was high. This may have resulted in slow IMAP performance or connection timeouts, including connections from the US webmail system.&lt;/p&gt;
&lt;p&gt;The condition has passed and we&amp;rsquo;re seeing no further issues at this time. 
  &lt;span class=&#34;faded&#34;&gt;(15:46 UTC — Oct 6)&lt;/span&gt;

&lt;/p&gt;</description>
        <content type="html">&lt;p&gt;There was a ~30 minute period between 14:50 UTC and 15:20 UTC during which system load on our US IMAP server was high. This may have resulted in slow IMAP performance or connection timeouts, including connections from the US webmail system.&lt;/p&gt;
&lt;p&gt;The condition has passed and we&amp;rsquo;re seeing no further issues at this time. 
  &lt;span class=&#34;faded&#34;&gt;(15:46 UTC — Oct 6)&lt;/span&gt;

&lt;/p&gt;
</content>
      </item>
    
      <item>
        <title>[Resolved] Mail server certificates expired</title>
        <link>https://opalstackstatus.com/issues/2021-09-30-mail-server-certificates-expired/</link>
        <pubDate>Thu, 30 Sep 2021 14:43:09 +0000</pubDate>
        <guid>https://opalstackstatus.com/issues/2021-09-30-mail-server-certificates-expired/</guid>
        <category>2021-09-30 15:10:18</category>
        <description>&lt;p&gt;&lt;em&gt;Fixed&lt;/em&gt; - The issue is now resolved. The root cause was an obsolete root certificate on our servers. The certificate has been updated. 
  &lt;span class=&#34;faded&#34;&gt;(15:10 UTC — Sep 30)&lt;/span&gt;

&lt;/p&gt;
&lt;p&gt;The SSL certificates used by Opalstack&amp;rsquo;s mail servers are expired. We&amp;rsquo;re working to correct that at this time and should have it resolved shortly. 
  &lt;span class=&#34;faded&#34;&gt;(14:43 UTC — Sep 30)&lt;/span&gt;

&lt;/p&gt;</description>
        <content type="html">&lt;p&gt;&lt;em&gt;Fixed&lt;/em&gt; - The issue is now resolved. The root cause was an obsolete root certificate on our servers. The certificate has been updated. 
  &lt;span class=&#34;faded&#34;&gt;(15:10 UTC — Sep 30)&lt;/span&gt;

&lt;/p&gt;
&lt;p&gt;The SSL certificates used by Opalstack&amp;rsquo;s mail servers are expired. We&amp;rsquo;re working to correct that at this time and should have it resolved shortly. 
  &lt;span class=&#34;faded&#34;&gt;(14:43 UTC — Sep 30)&lt;/span&gt;

&lt;/p&gt;
</content>
      </item>
    
      <item>
        <title>[Resolved] IMAP1US Offline</title>
        <link>https://opalstackstatus.com/issues/2021-03-24-imap1us-offline/</link>
        <pubDate>Wed, 24 Mar 2021 09:50:00 +0000</pubDate>
        <guid>https://opalstackstatus.com/issues/2021-03-24-imap1us-offline/</guid>
        <category>2021-03-24 15:00:22</category>
        <description>&lt;p&gt;&lt;em&gt;Fixed&lt;/em&gt; - The US IMAP server has been back online since 2021-03-24 10:30 UTC. 
  &lt;span class=&#34;faded&#34;&gt;(15:00 UTC — Mar 24)&lt;/span&gt;

&lt;/p&gt;
&lt;p&gt;The IMAP1US server is currently down and we are working to restore access. 
  &lt;span class=&#34;faded&#34;&gt;(09:50 UTC — Mar 24)&lt;/span&gt;

&lt;/p&gt;</description>
        <content type="html">&lt;p&gt;&lt;em&gt;Fixed&lt;/em&gt; - The US IMAP server has been back online since 2021-03-24 10:30 UTC. 
  &lt;span class=&#34;faded&#34;&gt;(15:00 UTC — Mar 24)&lt;/span&gt;

&lt;/p&gt;
&lt;p&gt;The IMAP1US server is currently down and we are working to restore access. 
  &lt;span class=&#34;faded&#34;&gt;(09:50 UTC — Mar 24)&lt;/span&gt;

&lt;/p&gt;
</content>
      </item>
    
      <item>
        <title>[Resolved] US IMAP scheduled maintenance</title>
        <link>https://opalstackstatus.com/issues/2021-02-01-us-imap-scheduled-maintenance/</link>
        <pubDate>Mon, 01 Feb 2021 03:02:00 +0000</pubDate>
        <guid>https://opalstackstatus.com/issues/2021-02-01-us-imap-scheduled-maintenance/</guid>
        <category>2021-02-02 00:47:35</category>
        <description>&lt;p&gt;&lt;em&gt;Fixed&lt;/em&gt; - All mailboxes have been synced. 
  &lt;span class=&#34;faded&#34;&gt;(00:47 UTC — Feb 2)&lt;/span&gt;

&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Fixed&lt;/em&gt; - The US IMAP service is now up and running on the new hardware.&lt;/p&gt;
&lt;p&gt;Mail received in the past 48-72 hours may not be immediately visible on the new hardware but will appear automatically as we perform a final sync over the next several hours.&lt;/p&gt;
&lt;p&gt;We&amp;rsquo;ll post a final update here when the sync is complete. 
  &lt;span class=&#34;faded&#34;&gt;(05:30 UTC — Feb 1)&lt;/span&gt;

&lt;/p&gt;</description>
        <content type="html">&lt;p&gt;&lt;em&gt;Fixed&lt;/em&gt; - All mailboxes have been synced. 
  &lt;span class=&#34;faded&#34;&gt;(00:47 UTC — Feb 2)&lt;/span&gt;

&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Fixed&lt;/em&gt; - The US IMAP service is now up and running on the new hardware.&lt;/p&gt;
&lt;p&gt;Mail received in the past 48-72 hours may not be immediately visible on the new hardware but will appear automatically as we perform a final sync over the next several hours.&lt;/p&gt;
&lt;p&gt;We&amp;rsquo;ll post a final update here when the sync is complete. 
  &lt;span class=&#34;faded&#34;&gt;(05:30 UTC — Feb 1)&lt;/span&gt;

&lt;/p&gt;
&lt;p&gt;The US IMAP service is currently undergoing &lt;a href=&#34;https://status.opalstack.com/schedules/18&#34;&gt;scheduled maintenance&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;IMAP connectivity may be sporadic or unavailable for the next ~3 hours.&lt;/p&gt;
&lt;p&gt;We&amp;rsquo;ll update this post when the maintenance is complete. 
  &lt;span class=&#34;faded&#34;&gt;(03:02 UTC — Feb 1)&lt;/span&gt;

&lt;/p&gt;
</content>
      </item>
    
      <item>
        <title>[Resolved] US IMAP service not responding</title>
        <link>https://opalstackstatus.com/issues/2021-01-29-us-imap-service-not-responding/</link>
        <pubDate>Fri, 29 Jan 2021 20:30:23 +0000</pubDate>
        <guid>https://opalstackstatus.com/issues/2021-01-29-us-imap-service-not-responding/</guid>
        <category>2021-01-29 21:49:30</category>
        <description>&lt;p&gt;&lt;em&gt;Fixed&lt;/em&gt; - The US IMAP server is back online. 
  &lt;span class=&#34;faded&#34;&gt;(21:49 UTC — Jan 29)&lt;/span&gt;

&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Investigating&lt;/em&gt; - We&amp;rsquo;re rebooting the US IMAP server at this time. 
  &lt;span class=&#34;faded&#34;&gt;(20:38 UTC — Jan 29)&lt;/span&gt;

&lt;/p&gt;
&lt;p&gt;The US IMAP service is currently not responding, we&amp;rsquo;re looking into it. 
  &lt;span class=&#34;faded&#34;&gt;(20:30 UTC — Jan 29)&lt;/span&gt;

&lt;/p&gt;</description>
        <content type="html">&lt;p&gt;&lt;em&gt;Fixed&lt;/em&gt; - The US IMAP server is back online. 
  &lt;span class=&#34;faded&#34;&gt;(21:49 UTC — Jan 29)&lt;/span&gt;

&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Investigating&lt;/em&gt; - We&amp;rsquo;re rebooting the US IMAP server at this time. 
  &lt;span class=&#34;faded&#34;&gt;(20:38 UTC — Jan 29)&lt;/span&gt;

&lt;/p&gt;
&lt;p&gt;The US IMAP service is currently not responding, we&amp;rsquo;re looking into it. 
  &lt;span class=&#34;faded&#34;&gt;(20:30 UTC — Jan 29)&lt;/span&gt;

&lt;/p&gt;
</content>
      </item>
    
      <item>
        <title>[Resolved] US IMAP service performance degraded</title>
        <link>https://opalstackstatus.com/issues/2021-01-19-us-imap-service-performance-degraded/</link>
        <pubDate>Tue, 19 Jan 2021 20:35:00 +0000</pubDate>
        <guid>https://opalstackstatus.com/issues/2021-01-19-us-imap-service-performance-degraded/</guid>
        <category>2021-01-19 21:22:14</category>
        <description>&lt;p&gt;&lt;em&gt;Fixed&lt;/em&gt; - The US IMAP server is back online and is operating normally. We&amp;rsquo;ll be upgrading the server in February to avoid future problems. 
  &lt;span class=&#34;faded&#34;&gt;(21:22 UTC — Jan 19)&lt;/span&gt;

&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Watching&lt;/em&gt; - We&amp;rsquo;ve rebooted the US IMAP server and are monitoring. 
  &lt;span class=&#34;faded&#34;&gt;(20:57 UTC — Jan 19)&lt;/span&gt;

&lt;/p&gt;
&lt;p&gt;The IMAP service on our US mail system is currently running very slowly. We&amp;rsquo;re working to correct that at this time.&lt;/p&gt;
&lt;p&gt;This is also causing timeouts and errors for users accessing Opalstack webmail, including users of our German mail system. 
  &lt;span class=&#34;faded&#34;&gt;(20:35 UTC — Jan 19)&lt;/span&gt;

&lt;/p&gt;</description>
        <content type="html">&lt;p&gt;&lt;em&gt;Fixed&lt;/em&gt; - The US IMAP server is back online and is operating normally. We&amp;rsquo;ll be upgrading the server in February to avoid future problems. 
  &lt;span class=&#34;faded&#34;&gt;(21:22 UTC — Jan 19)&lt;/span&gt;

&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Watching&lt;/em&gt; - We&amp;rsquo;ve rebooted the US IMAP server and are monitoring. 
  &lt;span class=&#34;faded&#34;&gt;(20:57 UTC — Jan 19)&lt;/span&gt;

&lt;/p&gt;
&lt;p&gt;The IMAP service on our US mail system is currently running very slowly. We&amp;rsquo;re working to correct that at this time.&lt;/p&gt;
&lt;p&gt;This is also causing timeouts and errors for users accessing Opalstack webmail, including users of our German mail system. 
  &lt;span class=&#34;faded&#34;&gt;(20:35 UTC — Jan 19)&lt;/span&gt;

&lt;/p&gt;
</content>
      </item>
    
      <item>
        <title>[Resolved] rebooting US IMAP server</title>
        <link>https://opalstackstatus.com/issues/2021-01-11-rebooting-us-imap-server/</link>
        <pubDate>Mon, 11 Jan 2021 18:04:34 +0000</pubDate>
        <guid>https://opalstackstatus.com/issues/2021-01-11-rebooting-us-imap-server/</guid>
        <category>2021-01-11 19:02:37</category>
        <description>&lt;p&gt;&lt;em&gt;Fixed&lt;/em&gt; - The US IMAP server is back online. 
  &lt;span class=&#34;faded&#34;&gt;(19:02 UTC — Jan 11)&lt;/span&gt;

&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Investigating&lt;/em&gt; - The US IMAP server is not coming back from the reboot. We&amp;rsquo;re working with our provider to restore service ASAP. 
  &lt;span class=&#34;faded&#34;&gt;(18:27 UTC — Jan 11)&lt;/span&gt;

&lt;/p&gt;
&lt;p&gt;We&amp;rsquo;re doing an emergency reboot of the US IMAP server. Service should be restored in a moment. 
  &lt;span class=&#34;faded&#34;&gt;(18:04 UTC — Jan 11)&lt;/span&gt;

&lt;/p&gt;</description>
        <content type="html">&lt;p&gt;&lt;em&gt;Fixed&lt;/em&gt; - The US IMAP server is back online. 
  &lt;span class=&#34;faded&#34;&gt;(19:02 UTC — Jan 11)&lt;/span&gt;

&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Investigating&lt;/em&gt; - The US IMAP server is not coming back from the reboot. We&amp;rsquo;re working with our provider to restore service ASAP. 
  &lt;span class=&#34;faded&#34;&gt;(18:27 UTC — Jan 11)&lt;/span&gt;

&lt;/p&gt;
&lt;p&gt;We&amp;rsquo;re doing an emergency reboot of the US IMAP server. Service should be restored in a moment. 
  &lt;span class=&#34;faded&#34;&gt;(18:04 UTC — Jan 11)&lt;/span&gt;

&lt;/p&gt;
</content>
      </item>
    
      <item>
        <title>[Resolved] Slow IMAP performance</title>
        <link>https://opalstackstatus.com/issues/2020-12-14-slow-imap-performance/</link>
        <pubDate>Mon, 14 Dec 2020 21:14:00 +0000</pubDate>
        <guid>https://opalstackstatus.com/issues/2020-12-14-slow-imap-performance/</guid>
        <category>2020-12-19 22:17:12</category>
        <description>&lt;p&gt;&lt;em&gt;Identified&lt;/em&gt; - The US IMAP service is currently under heavy load while importing mail for new customers. 
  &lt;span class=&#34;faded&#34;&gt;(02:15 UTC — Dec 23)&lt;/span&gt;

&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Fixed&lt;/em&gt; - All pending mail imports have been completed and the IMAP servers are operating normally. 
  &lt;span class=&#34;faded&#34;&gt;(22:17 UTC — Dec 19)&lt;/span&gt;

&lt;/p&gt;
&lt;p&gt;At this time we&amp;rsquo;re importing hundreds of gigabytes of mail for new customers migrating from WebFaction. This is causing heavy load on our IMAP servers so you may see slow performance in our webmail system, IMAP clients, and POP3 downloads over the next few days.&lt;/p&gt;</description>
        <content type="html">&lt;p&gt;&lt;em&gt;Identified&lt;/em&gt; - The US IMAP service is currently under heavy load while importing mail for new customers. 
  &lt;span class=&#34;faded&#34;&gt;(02:15 UTC — Dec 23)&lt;/span&gt;

&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Fixed&lt;/em&gt; - All pending mail imports have been completed and the IMAP servers are operating normally. 
  &lt;span class=&#34;faded&#34;&gt;(22:17 UTC — Dec 19)&lt;/span&gt;

&lt;/p&gt;
&lt;p&gt;At this time we&amp;rsquo;re importing hundreds of gigabytes of mail for new customers migrating from WebFaction. This is causing heavy load on our IMAP servers so you may see slow performance in our webmail system, IMAP clients, and POP3 downloads over the next few days.&lt;/p&gt;
&lt;p&gt;We&amp;rsquo;ll update this post when the imports are complete. 
  &lt;span class=&#34;faded&#34;&gt;(21:14 UTC — Dec 14)&lt;/span&gt;

&lt;/p&gt;
</content>
      </item>
    
      <item>
        <title>[Resolved] Cron mail not working</title>
        <link>https://opalstackstatus.com/issues/2020-06-14-cron-mail-not-working/</link>
        <pubDate>Sun, 14 Jun 2020 22:24:11 +0000</pubDate>
        <guid>https://opalstackstatus.com/issues/2020-06-14-cron-mail-not-working/</guid>
        <category>2020-06-16 20:58:39</category>
        <description>&lt;p&gt;&lt;em&gt;Fixed&lt;/em&gt; - Mail from cron jobs should be working normally now. 
  &lt;span class=&#34;faded&#34;&gt;(20:58 UTC — Jun 16)&lt;/span&gt;

&lt;/p&gt;
&lt;p&gt;At the present time mail is not being sent by cron jobs on our web servers. We&amp;rsquo;re looking into the cause. 
  &lt;span class=&#34;faded&#34;&gt;(22:24 UTC — Jun 14)&lt;/span&gt;

&lt;/p&gt;</description>
        <content type="html">&lt;p&gt;&lt;em&gt;Fixed&lt;/em&gt; - Mail from cron jobs should be working normally now. 
  &lt;span class=&#34;faded&#34;&gt;(20:58 UTC — Jun 16)&lt;/span&gt;

&lt;/p&gt;
&lt;p&gt;At the present time mail is not being sent by cron jobs on our web servers. We&amp;rsquo;re looking into the cause. 
  &lt;span class=&#34;faded&#34;&gt;(22:24 UTC — Jun 14)&lt;/span&gt;

&lt;/p&gt;
</content>
      </item>
    
  </channel>
</rss>
