NinerNet Communications™
System Status

Server and System Status

NC036: Update 8

22 March 2026 18:38:59 +0000

We are exploring ways to get the current mail server working, before giving up and starting an all-new server, because we know that a week of downtime is far from ideal. External mail servers are connecting to our mail server, but our mail server is immediately shutting down the connection, meaning the external mail server cannot deliver its message.

Our mail server is working, but it’s basically as good as the computer on your desktop right now, which is not very good at processing email because it’s not configured to.

Some clients have taken matters into their own hands, which is to be expected, and we have always consciously given you that ability: You have access to the DNS for your domain, which means you can point the DNS for your domain to another mail server. If what is happening right now is not to your liking, understandably, you can do this. We don’t have the time right now to go looking for and provide auth codes so that you can rush off and do the wrong thing.

Speaking of which, the current situation has absolutely no effect on any websites we host, also by design.

NC036: Update 7

21 March 2026 02:31:38 +0000

Updates will now be sequentially numbered.

We’ve marked server NC036 as “degraded”, because that’s what it is. Email within the group of clients for which we are responsible works. With the outside world, it doesn’t.

Our live monitoring indicates that our uptime is 99.998%, but as we’ve indicated before, this is not 100% accurate. Even AI is “accurately inaccurate”.

You still have access to your account(s) on the server. Please do with that information what you consider to be best for your business.

NC036: A luta continua

21 March 2026 00:21:36 +0000

We implemented the permanent fix yesterday. However, the result seems to be the same: NO EMAIL.

I half expected that this would reveal to me that I had made a stupid mistake, and all this palaver was for nothing. That would have been supremely uncomfortable, but at least we’d all be online. But we’re not.

I know you, our clients, have struggled for the last two days. So have we, there is no doubt. I literally feel your pain.

We have two options at this point, but I want to make clear at the outset that your data — your 5.1 million emails, 2.9 terabytes — are safe. Additionally, I am still alive, which could be a positive or a negative for you, depending on how you view the situation.

Option one, and the option I’d prefer under normal circumstances, is to start fresh with a new mail server, and even just verbalising that fills me with that feeling you get at the beginning of a footrace. You don’t know if you’ll come first, or 101st, but goddam, you’re going to race your heart out.

Option two, to put it succinctly, is to know when to quit. It’s not the end I envisioned when I was supposed to hand over the business and our name in May last year, but nothing lasts forever.

Already I hear most of you leaning towards option two. I don’t blame you. Just get out of the way, Craig, and let me get my email and entrust it to someone with a bigger marketing budget.

If I choose option one, it’s going to take at least a week … and that’s being optimistic. So you will not be able to send or receive email for all of next week, and if everything works, you’ll be online by Monday, 30 March 2026 … I hope.

If I choose option two, that would be like giving the order to “abandon ship”; you don’t want to be in the cold water, but the only other option is even less palatable.

I’ve decided, after much soul searching and personal conversations today, to take option one.

Who knows what NinerNet will look like in a week or a month. However, I know what’s most important for me, and that is that you have your access to the 5.1 million emails you have entrusted to us. You will have access to them, and what you do with them will be up to you.

We will, as always, be communicative, and post updates here. We’re not ignoring your emails — which we ironically continue to receive — but our focus must be and is on keeping everyone as informed as possible.

NC036: Further update

20 March 2026 13:34:40 +0000

We continue to receive reports of continued problems from a very few clients.

We essentially addressed the problem on the evening (UTC) of 19 March. We have yet to put in place a permanent fix. The permanent fix is to attach a secondary volume, and move some back-ups onto the secondary volume, to free up space on the primary hard drive to store and process email. We have not done this yet.

However, we have freed up a huge amount of space, so the server is comfortably handling all the email thrown at it. This is the temporary fix.

The reported problems seem to focus on two areas:

  • Bounced email, and
  • Expected but not received emails.

We have been working on the mail server non-stop for about 21 hour now. We have rebooted the server once (in the morning UTC) and restarted applications a few times. During that time foreign mail servers may have been disconnected in the middle of trying to deliver an email, resulting in their bouncing the email with an error that refers to “losing the connection while receiving the initial server greeting”. Given how often this would have happened (not very much) we’re surprised to see this bounce, but it’s obviously happened. We can only expect these events to lessen as things return to normal.

We ourselves have noticed that emails from external/foreign sources have not been arriving lately. We can only expect that these emails are delayed, and we expect to receive them again in the next 24 hours. Please be patient.

If you check your domain at mxtoolbox.com you will find that it should comply with all or most requirement to have your email delivered. Not complying with every requirement is not necessarily a bad thing.

We expect to have the permanent fix in place within the next 12 hours, but the temporary fix is more than enough to keep the email flowing. Thank-you.

NC036: Most email flowing normally

20 March 2026 07:45:21 +0000

It seems, from monitoring our own company email, that email is flowing normally. However, tests I have done to my personal email address are still delayed. This doesn’t really make sense, as our server is not blocking any inbound email. We’re still working on the permanent fix, but in the meantime there is plenty of disk space to take in the biggest of emails.

NC036: Webmail works

19 March 2026 23:00:40 +0000

We have rebooted the mail server, so the webmail is working again. We don’t know how long that was generating an error, but it wasn’t reported by anyone until a few minutes ago.

NC036: Progress update

19 March 2026 18:15:15 +0000

This seems to be a disk space issue. We have freed up enough space that backlogged email has been released. There should be no problems sending and receiving email now, but we are still working to implement a permanent fix. Apologies for the interruption.

We will have further updates as we implement the permanent fix.

NC036: Mail server issues

19 March 2026 16:48:26 +0000

We have been informed that some clients (probably all) are encountering issues with the mail server. We are looking into the cause now.

Problem with latest version of Microsoft Outlook

20 January 2026 19:16:43 +0000

We have been inundated by emails from clients having a problem with the latest version of Outlook. Seems there is no quality control at Microsoft, and they let a bug through their update process.

The problem has been reported to us in different ways by a number of disparate clients. But the solution seems to be to download a new update from Microsoft, and/or to uninstall Outlook and reinstall it. When you reinstall it, Outlook will (or it should) get the configuration information from your domain’s DNS; all it needs from you is your log-in information, namely your email address and password, which you presumably have saved in your password manager.

We hope this helps you. This is not a problem with or caused by NinerNet‘s mail servers.


Updated, 2026-01-20: Believe it or not, there are better email programs out there, despite what Microsoft would have you believe. Unfortunately the email “app” I used to use when I still used Windows is no longer around, but Pegasus is. I intended to try out Pegasus before I switched to Linux (because Eudora was discontinued), but I never did; however, it’s still around and very popular. There’s also Thunderbird, of course, but I have always hated that program. I have used Evolution (which also bills itself as a “personal information manager”, like Outlook) since I switched to Linux and had to leave Eudora.

Updated, 2026-01-21: Again, as we have been telling people over and over, there is nothing we can do on our mail server to fix Microsoft’s screw-up of their email program. If you want to try changing your password, as some have tried to do, you can do that yourself in the control panel or the webmail, but it won’t help. The problem is not our mail server. Please contact Microsoft to have them help you with their software. There is just nothing we can do to fix their software.

Updated, 2026-01-21: Also, please note that no non-Outlook clients have reported any problems since this ongoing palaver with Microsoft has started. I bet Bill Gates won’t be writing us a cheque!

All servers: Company SSL/TLS certificates on all servers renewed and updated

15 January 2026 10:24:37 +0000

The *.niner.net wildcard SSL/TLS certificate has been renewed and updated across our entire infrastructure. This should be seamless for all our clients. However, should you run into a situation in the next 24 hours where you’re told that the certificate has expired, please log out and reload whatever it is you’re trying to do. You may need to reboot, but this would be very unusual. Simply forcing a reload should clear things up. Via FTPS you may need to re-trust our certificate depending on your FTP client.

This doesn’t affect certificates on your own domain on your website, just NinerNet services such as control panels and connecting to the mail and FTP servers. There is also an ongoing issue on dns.niner.net, but bypassing the SSL warning is perfectly safe.

If you have any questions or concerns, please do contact NinerNet support with any error messages you may be seeing. Thank-you.

NinerNet home page

Systems at a Glance:


Loc.SystemStatusPing
Server NC023, London, United Kingdom (Relay server), INTERNAL.NC023InternalUp?
Server NC028, Vancouver, Canada (Monitoring server), INTERNAL.NC028InternalUp?
Server NC031, New York, United States of America (Web server), INTERNAL.NC031InternalUp?
Server NC033, Toronto, Canada (Primary nameserver), OPERATIONAL.NC033OperationalUp?
Server NC034, Lusaka, Zambia (Phone server), INTERNAL.NC034InternalUp?
Server NC035, Sydney, Australia (Secondary nameserver), OPERATIONAL.NC035OperationalUp?
Server NC036, Amsterdam, Netherlands (Mail server), DEGRADED.NC036DegradedUp?
Server NC040, Toronto, Canada (Web server), INTERNAL.NC040InternalUp?
Server NC041, New York, United States of America (Web server), OPERATIONAL.NC041OperationalUp?
Server NC042, Seattle, United States of America (Status website), OPERATIONAL.NC042OperationalUp?

Subscriptions:

RSS icon. RSS

Twitter icon. Twitter

Search:

 

Recent Posts:

Archives:

Categories:

Links

Tags:

.co.zm domains .com.zm domains .zam.co domains back-up bounce messages browser warnings connection issues control panel database dns dos attack dot-zm domains down time email email delivery error messages ftp hardware imap mail mailing lists mail relay mail server microsoft migration nameservers network networking performance php phplist pop reboot shaw shaw communications inc. smtp spam spamassassin ssl ssl certificate tls tls certificate viruses webmail web server

Resources:

On NinerNet: