IMAP/POP3 (DE) on Opalstack Status

[Resolved] Unplanned emergency maintenance on imap1.de.opalstack.com

Wed, 27 May 2026 00:37:00 +0000

May 27 00:37 UTC: imap1.de.opalstack.com encountered connectivity issues. We’re currently analyzing the server to get it back to full service.

May 27 01:34 UTC: The server was successfully rebooted and services are operational. We continue to monitor are check for any underlying issues.

May 27 13:30 UTC: We’ve seen no further issues and consider this to be resolved. (00:37 UTC — May 27)

[Resolved] German IMAP/POP3 server offline for scheduled relocation

Tue, 24 Jan 2023 08:05:00 +0000

Fixed - The backlog of incoming mail has been delivered and the relocation is complete. (17:01 UTC — Jan 24)

Watching - The DE mail server is back online at this time and the backlog of incoming mail is now being processed. We’re awaiting the final word from the data center that the relocation is complete. (16:03 UTC — Jan 24)

As previously announced, our German IMAP/POP3 server will be offline for relocation to a new data center facility from 0800 to 1600 UTC on 24 January 2023: https://status.opalstack.com/schedules/38 (08:05 UTC — Jan 24)

[Resolved] Germany mail server offline.

Fri, 01 Apr 2022 08:30:00 +0000

Fixed - All repairs are complete and all DE mailboxes have been restored.

If you are a DE mail customer and are still seeing issues with your IMAP/POP3 email then please email Opalstack support for further assistance. (13:50 UTC — Apr 9)

Watching - The repairs for message dates and mailbox permissions are 75-80% complete. (20:37 UTC — Apr 7)

Watching - The repairs for dates and mailbox permissions are still in progress. We expect them to be completed today. (13:40 UTC — Apr 7)

Watching - The restore is complete.

We’re still working on lingering issues related to message dates and mailbox permissions which may take another day or two to fully resolve.

We’ll continue to post updates until the issues are resolved. (02:32 UTC — Apr 6)

Watching - The restore is 99% complete. (01:42 UTC — Apr 6)

Watching - The restore is 99% complete.

Once the restore has completed, there may be sporadic service disruptions for individual mailboxes as we identify lingering issues and correct them. (00:48 UTC — Apr 6)

Watching - The restore is 98-99% complete. (20:00 UTC — Apr 5)

Watching - The restore is 93-99% complete. (13:29 UTC — Apr 5)

Watching - The recovery is 85-95% complete. (01:22 UTC — Apr 5)

Watching - The recovery is 80-90% complete. (18:29 UTC — Apr 4)

Watching - The recovery is 75-85% complete. (13:28 UTC — Apr 4)

Watching - The recovery is 70-80% complete. (01:33 UTC — Apr 4)

Watching - The recovery is 65-75% complete. Note that there are several parallel restore processes so the overall recovery progress doesn’t reflect a percentage of the alphabet with regard to mailbox names. (19:41 UTC — Apr 3)

Watching - The recovery is 60-70% complete. (15:55 UTC — Apr 3)

Watching - The recovery is 45-60% complete. (02:22 UTC — Apr 3)

Watching - The recovery is 30-40% complete. We have to estimate with a range because of the parallel restore processes. (17:00 UTC — Apr 2)

Watching - The recovery is 24% complete. (13:30 UTC — Apr 2)

Watching - The recovery from backup is still in progress, albeit running slowly at only 12% complete.

We believe that we’ll be able to recover most of the data from the failed server, so we’re restoring that data in parallel with the backup recovery. This should speed up the overall recovery and provide the most recent data from prior to the failure. (04:19 UTC — Apr 2)

Watching - The recovery is in still progress.

We estimate that it is 11% complete and it is currently restoring mailboxes that being with “as”. (21:47 UTC — Apr 1)

Watching - DE webmail access is now working.

The mailbox restore is still in progress. (16:13 UTC — Apr 1)

Watching - We’re still noticing some login issues for webmail and are troubleshooting that now. (15:57 UTC — Apr 1)

Watching - We do not have high expectations for the outcome of the filesystem check, so we’ve deployed a new DE IMAP server and have re-created all DE mailboxes as new empty mailboxes on that server.

Customers should now be able to log in to our DE mail services to send and receive new mail. No changes to your email client settings should be required.

We’ll begin restoring the original mailbox contents ASAP from the most recent backup made on 30 March 2022 (the failure occurred while the 31 March backup was still in progress). The restore may take several days to complete, so we’ll keep this post updated until it is done.

We’ll attempt to recover mail from 31 March 2022 when the filesystem repairs on the failed server are complete. (15:30 UTC — Apr 1)

At around 08:30 UTC on 1 April 2022 our DE incoming mail server stopped responding, so we initiated an emergency reboot.

The server did not reboot correctly and further analysis identified a failing disk associated with outdated disk controller firmware and a failed disk controller battery.

As of 11:00 UTC the disc controller was repaired and a filesystem check was initiated.

Further updates follow in reverse-chronological order. (08:30 UTC — Apr 1)

[Resolved] German IMAP/POP3 service offline

Wed, 09 Jun 2021 09:28:00 +0000

Fixed - The Germain mail service is back online. The outage was caused by human error when deploying a new certificate. (09:39 UTC — Jun 9)

The German IMAP/POP3 service is currently offline. We’re currently investigating. (09:28 UTC — Jun 9)

[Resolved] DE IMAP service down

Fri, 12 Feb 2021 14:23:21 +0000

Fixed - The DE IMAP/POP3 service has been stable since our last update. (16:25 UTC — Feb 12)

Watching - The DE IMAP/POP3 service is back online with higher process and open files limits. We’ll continue to monitor. (14:55 UTC — Feb 12)

Watching - We’re rebooting time DE IMAP/POP3 server to pick up a configuration change. (14:46 UTC — Feb 12)

Watching - The DE IMAP/POP3 service is back online. We’ll continue to monitor as we look into the cause of the outage. (14:34 UTC — Feb 12)

The IMAP/POP3 service on our DE mail system is currently down. We’re working to restore service. (14:23 UTC — Feb 12)

[Resolved] Incoming mail problems in Germany

Tue, 09 Feb 2021 14:18:31 +0000

Fixed - The disk array rebuild is complete and the server has been stable since our last update. (15:50 UTC — Feb 10)

Watching - The DE mail service is back online at this time. The main issue was heavy load caused by the very high volume of deferred mail the resulted from the mail loop. This was exacerbated by the degraded disk array.

The networking issue was unrelated but has been resolved.

The disk array is still rebuilding but the server is operating normally. We’ll continue to monitor until the rebuild is complete. (18:54 UTC — Feb 9)

Identified - There seems to be multiple issues related to the DE IMAP server:

A forwarding loop was causing delivery delays for the past few hours.
A degraded disk array was impacting system performance
A failed network switch is currently blocking network connectivity

Our data center team is working on restoring connectivity at this time. (15:50 UTC — Feb 9)

Investigating - The DE IMAP server is now offline for a filesystem check. (15:16 UTC — Feb 9)

We’re receiving reports of slow mail delivery in our German mail system. We’re looking into it at this time. (14:18 UTC — Feb 9)

[Resolved] DE IMAP service offline

Wed, 12 Feb 2020 11:30:00 +0000

Fixed - The disk array rebuild is complete. (22:30 UTC — Feb 12)

Watching - The failed disk has been replaced and the DE IMAP service is operational at this time.

Disk performance may be slightly degraded while the disk array rebuilds.

We’ll post a final update when the array rebuild is complete. (17:27 UTC — Feb 12)

Watching - The DE IMAP service is back online. We’ll continue to monitor. (14:31 UTC — Feb 12)

Identified - The DE IMAP server has experienced a disk failure. The storage array is currently rebuilding. We’ll update with an ETA as soon as we have one. (14:20 UTC — Feb 12)

Our IMAP service in Germany has been offline since around 11:30 AM 12 Feb 2020. We’re working to identify the cause at this time. (11:30 UTC — Feb 12)