NinerNet Communications™
System Status

Server and System Status

NC036: New DNS entries needed for domains hosted with us

20 November 2025 05:41:07 +0000

If any messages you are sending through us result in a bounce messages that reads as follows:

From header sender domain not verified (DOMAIN.COM)
On your Sending > Verified Senders page
verify the sender domain or email to be allowed to send.

This means you are not hosting your DNS with us.

You need to go to your DNS provider and add the following two CNAME records so that your messages get through:

em460536.DOMAIN.COM
s2g-return.niner.net

s460536.domainkey.DOMAIN.COM
s2g-dkim.niner.net

Of course, DOMAIN.COM must be your actual domain.

If you rely on forwarding any messages to another domain, your senders will likely get the same bounce message. The solution is to stop the forwarding.

Please let us know when you have added the two new records, and we will complete the process.

NC036: Mail queue back to normal

14 November 2025 19:46:46 +0000

After about an hour and a half of managing resources on the mail server (NC036), we have cleared the mail queue and processed all of the email that was delayed.

As far as we can tell, these incidents are caused by the mail server being overloaded. Recent statistics showed that at certain times about 80% of the mail received by our mail server was spam. I don’t want to appear like I am cherry-picking statistics to make it look worse than it really is, but the statistics amaze even me, who has been running mail servers for 29 years. At other times the spam load decreases, of course, but at other times, of the 100 messages we receive in any given unit of time, 80 of the messages are spam. So at those times the server cannot keep up with the flow of email into the server, because the server is busy scanning all the messages to determine if they are spam, and while it’s doing that ten more new messages arrive. Then it finishes processing that spam message and starts processing the first of the ten new messages waiting, and so the process goes.

Yes, we could increase the memory on the server, but this isn’t cheap, isn’t instant and can be further disruptive, and we know for some of our bigger clients, your invoices have increased this year. The money available to us is not unlimited, just as your wallets are not unlimited.

The mail server woes are not related to the nameserver work we’re doing. They are three different machines in three different data centres on three different continents. Gone are the days back in the nineties when we ran everything on one physical server, when we had problems communicating with our clients if the one server had a problem unrelated to email; when that happened, the unrelated problem meant we couldn’t also update this server blog (which didn’t exists back then!), so everybody was in the dark until we fixed the problem. Now, we at least have the real-time monitor and this status blog, but even those have limitations; you’ll notice that the statistics for server NC036 (the mail server) show it as having been up for 99.997% in the last 24 hours, which supposedly means the mail server was down for only 2.5 seconds! If that’s all it was down for, people wouldn’t have time to write emails explaining their problems! So the real-time monitor isn’t 100% accurate (even though it is close), and even the monitoring didn’t alert us when it should have. This resulted in the delay in clearing up the mail queue.

The point of this long blog post is to describe the challenges that we face some days, and to let you know we’re not sitting back doing nothing, while you wonder what’s happening to your email. Thank-you for your attention.

NC036: Battling spam on the mail server

14 November 2025 17:15:44 +0000

We are battling an overload of spam on the mail server (NC036). We will have the issue cleared soon and will post an update when we do. Apologies for the inconvenience.

NC036: Mail server recovered

6 November 2025 17:33:55 +0000

Following a slowdown on the mail server, the queue had been cleared and everything is back to normal. Apologies for the interruption.

NC036: Mail server processing email normally

6 October 2025 08:25:00 +0000

We have finished dealing with the temporary problem on the mail server (NC036). All messages are being processed normally.

Thank-you for your patience.

NC036: Mail queue interruptions

6 October 2025 07:17:17 +0000

We are dealing with a temporary problem on the mail server (NC036). Some users might experience temporary interruptions in sending messages. We are actively addressing this problem, and will post an update when the interruption is over.

NC036: Mail delivery delay resolved

2 October 2025 19:09:16 +0000

In the evening UTC of 2 October 2025 our mail server (NC036) got behind on mail delivery. By about 19:00 UTC the mail queue was manually cleared, and the huge amount of spam was manually cleared as well. We apologise for this interruption.

NC036: Conclusion of issue with suspended Windows-based email account and SMTP2GO

16 July 2025 06:34:23 +0000

We were contacted by SMTP2GO late in the morning of the 15th. We weren’t given any more specific information about this particular issue, so we have to assume that this is a new, more proactive approach to preventing spam outbreaks. In our experience, a party that has compromised an email account they intend to use to send spam will sometimes send an initial test message from the account, and that message (if the body can be seen) can be recognised and acted on. We don’t have any easily accessible examples, but the few we have seen essentially identify the compromised account and provide the account’s password. The initiator of that message might be an automated process, or it might be a human. Regardless, if that message is seen the intent is fairly obvious, and the recipient then acts on it by using (and sometimes modifying, as we’ve noted before) the account however they intended to use it.

So I’m not very impressed that they immediately shut down our SMTP account based on one suspicious message, but I am thankful that our account with them allows us to reactivate it. So we reactivated it after disabling the one NinerNet-hosted compromised email account, and none of our clients (except the owner of the compromised account) were affected. Now that we know that we won’t overreact when or if this happens again.

It’s important to note here that we actually have the ability to communicate with SMTP2GO, who provide us the ability to communicate with intelligent, thinking humans who understand how email works and understand that providers like NinerNet do the very best that we can to prevent spam from emanating from our network, but that we are not 100% successful 100% of the time. This stands in stark contrast to providers like Outlook/Hotmail/Microsoft/whatever, Gmail, Yahoo, etc., who all act as if they own the planet and are answerable to nobody … including their own customers whom they inconvenience with their arrogant, scornful and contemptuous attitudes. You don’t actually see that yourself 99% of the time if you’re one of their users, of course — it’s all sunshine and light from their marketing departments — but it’s a painfully known fact amongst small providers like NinerNet who are shunted out of the way, downtrodden and treated like trash.

The point of this separate post (rather than a second update to the last post) is to highlight the excellent behaviour of SMTP2GO. It’s not often in this business that we send good vibes to a supplier, but SMTP2GO deserve any good vibes they get. If they provide any services that you need we couldn’t recommend them more strongly.

NC036: Windows email account suspension

15 July 2025 03:55:05 +0000

This announcement is not about our suspending a Windows-based email account, but the fact that an errant Windows-hosted email account belonging to one of our clients temporarily caused the suspension of an account we maintain with a supplier through which a substantial number of our outbound email messages are delivered every day — our “relay server“. We are still waiting for feedback from our supplier, but this happened after business hours in the Pacific time zone and in the middle of the night in the Central Africa time zone.

In the meantime we have un-suspended our account with our supplier, as we are certain that this suspension was in error. We do not expect this to affect any outbound email today, but we alert you to it in case there is a problem.

However this turns out we will update this post with the outcome, hopefully very soon. Thank-you for your patience.


Update, 2025-07-15: The relay server people (SMTP2GO) have not even acknowledged our ticket yet, so our hopes for a quick update have been dashed. However, the relay server is working as it should as of this moment. As we said, we believe this suspension was in error, so we’re not expecting it to happen again.

NC036: Mail server … again

10 July 2025 20:45:47 +0000

We’ve had reports that emails to and from our mail server are taking a couple of hours or more to get through. We’ve been on the mail server and there is no apparent reason for this — other than the huge amounts of spam the mail server processes every day — but we have rebooted it twice now and we’ve initiated a flush of the mail queue. These actions seem to have finally flushed the mail queue, and all delayed messages have been delivered, both locally and to foreign servers.

There’s never a dull day around here when dealing with email.

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), OPERATIONAL.NC036OperationalUp?
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: