<?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>Webmail (USA) on Opalstack Status</title>
    <link>https://opalstackstatus.com/affected/webmail-usa/</link>
    <description>Incident history</description>
    <generator>github.com/cstate</generator>
    <language>en</language>
    
    <lastBuildDate>2024-04-02T18:04:00+00:00</lastBuildDate>
    <updated>2024-04-02T18:04:00+00:00</updated>
    
    
    
      <atom:link href="https://opalstackstatus.com/affected/webmail-usa/index.xml" rel="self" type="application/rss+xml" />
    
    
      <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 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] Intermittent errors on webmail</title>
        <link>https://opalstackstatus.com/issues/2021-02-02-intermittent-errors-on-webmail/</link>
        <pubDate>Tue, 02 Feb 2021 17:38:00 +0000</pubDate>
        <guid>https://opalstackstatus.com/issues/2021-02-02-intermittent-errors-on-webmail/</guid>
        <category>2021-02-03 20:59:49</category>
        <description>&lt;p&gt;&lt;em&gt;Fixed&lt;/em&gt; - Webmail has been stable since our last update. 
  &lt;span class=&#34;faded&#34;&gt;(20:59 UTC — Feb 3)&lt;/span&gt;

&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Watching&lt;/em&gt; - We&amp;rsquo;ve adjusted the webmail server configuration to accommodate higher traffic and the server is now stable. We&amp;rsquo;ll continue to monitor. 
  &lt;span class=&#34;faded&#34;&gt;(18:55 UTC — Feb 2)&lt;/span&gt;

&lt;/p&gt;
&lt;p&gt;At this time we&amp;rsquo;re seeing intermittent database errors and 50x responses on &lt;a href=&#34;https://webmail.opalstacked.com/&#34;&gt;https://webmail.opalstacked.com/&lt;/a&gt; - we&amp;rsquo;re investigating and will update this post when more info is available. 
  &lt;span class=&#34;faded&#34;&gt;(17:38 UTC — Feb 2)&lt;/span&gt;

&lt;/p&gt;</description>
        <content type="html">&lt;p&gt;&lt;em&gt;Fixed&lt;/em&gt; - Webmail has been stable since our last update. 
  &lt;span class=&#34;faded&#34;&gt;(20:59 UTC — Feb 3)&lt;/span&gt;

&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Watching&lt;/em&gt; - We&amp;rsquo;ve adjusted the webmail server configuration to accommodate higher traffic and the server is now stable. We&amp;rsquo;ll continue to monitor. 
  &lt;span class=&#34;faded&#34;&gt;(18:55 UTC — Feb 2)&lt;/span&gt;

&lt;/p&gt;
&lt;p&gt;At this time we&amp;rsquo;re seeing intermittent database errors and 50x responses on &lt;a href=&#34;https://webmail.opalstacked.com/&#34;&gt;https://webmail.opalstacked.com/&lt;/a&gt; - we&amp;rsquo;re investigating and will update this post when more info is available. 
  &lt;span class=&#34;faded&#34;&gt;(17:38 UTC — Feb 2)&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] 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] Service disruption in San Francisco</title>
        <link>https://opalstackstatus.com/issues/2020-08-16-service-disruption-in-san-francisco/</link>
        <pubDate>Sun, 16 Aug 2020 13:00:00 +0000</pubDate>
        <guid>https://opalstackstatus.com/issues/2020-08-16-service-disruption-in-san-francisco/</guid>
        <category>2020-08-16 16:17:59</category>
        <description>&lt;p&gt;&lt;em&gt;Fixed&lt;/em&gt; - All SFO servers are now back online. 
  &lt;span class=&#34;faded&#34;&gt;(16:17 UTC — Aug 16)&lt;/span&gt;

&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Identified&lt;/em&gt; - vps15 and mx2.us are back online. 
  &lt;span class=&#34;faded&#34;&gt;(15:54 UTC — Aug 16)&lt;/span&gt;

&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Identified&lt;/em&gt; - The webmail server is back online and is operational with the exception of sending mail. We&amp;rsquo;re still waiting on the remaining servers to come back online. 
  &lt;span class=&#34;faded&#34;&gt;(15:26 UTC — Aug 16)&lt;/span&gt;

&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Identified&lt;/em&gt; - The data center team reports:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;The issue has been identified as a utility power issue. Power is transferred to generators and is currently running stable and network connectivity is restored for the vast majority of the services.&lt;/p&gt;</description>
        <content type="html">&lt;p&gt;&lt;em&gt;Fixed&lt;/em&gt; - All SFO servers are now back online. 
  &lt;span class=&#34;faded&#34;&gt;(16:17 UTC — Aug 16)&lt;/span&gt;

&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Identified&lt;/em&gt; - vps15 and mx2.us are back online. 
  &lt;span class=&#34;faded&#34;&gt;(15:54 UTC — Aug 16)&lt;/span&gt;

&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Identified&lt;/em&gt; - The webmail server is back online and is operational with the exception of sending mail. We&amp;rsquo;re still waiting on the remaining servers to come back online. 
  &lt;span class=&#34;faded&#34;&gt;(15:26 UTC — Aug 16)&lt;/span&gt;

&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Identified&lt;/em&gt; - The data center team reports:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;The issue has been identified as a utility power issue. Power is transferred to generators and is currently running stable and network connectivity is restored for the vast majority of the services.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;We&amp;rsquo;re starting to see the remaining machines come online at this time. 
  &lt;span class=&#34;faded&#34;&gt;(15:08 UTC — Aug 16)&lt;/span&gt;

&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Investigating&lt;/em&gt; - opal3.opalstack.com is back online at this time. Other servers are still offline and we&amp;rsquo;re awaiting a report on the initial investigation from the data center team. 
  &lt;span class=&#34;faded&#34;&gt;(14:19 UTC — Aug 16)&lt;/span&gt;

&lt;/p&gt;
&lt;p&gt;Services in our San Francisco data center are currently disrupted. The following servers are affected:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;community.opalstack.com&lt;/li&gt;
&lt;li&gt;mx2.us.opalstack.com&lt;/li&gt;
&lt;li&gt;opal3.opalstack.com&lt;/li&gt;
&lt;li&gt;smtp2.us.opalstack.com&lt;/li&gt;
&lt;li&gt;vps4.opalstack.com&lt;/li&gt;
&lt;li&gt;vps5.opalstack.com&lt;/li&gt;
&lt;li&gt;vps6.opalstack.com&lt;/li&gt;
&lt;li&gt;vps13.opalstack.com&lt;/li&gt;
&lt;li&gt;vps15.opalstack.com&lt;/li&gt;
&lt;li&gt;vps16.opalstack.com&lt;/li&gt;
&lt;li&gt;vps17.opalstack.com&lt;/li&gt;
&lt;li&gt;vps19.opalstack.com&lt;/li&gt;
&lt;li&gt;vps21.opalstack.com&lt;/li&gt;
&lt;li&gt;vps24.opalstack.com&lt;/li&gt;
&lt;li&gt;vps28.opalstack.com&lt;/li&gt;
&lt;li&gt;webmail.us.opalstack.com&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;We&amp;rsquo;ll update this post as soon as more information is available. 
  &lt;span class=&#34;faded&#34;&gt;(13:00 UTC — Aug 16)&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>
