Server NC023 was down between 20:06 and 20:23 UTC while a patch for the Spectre vulnerability was applied.
Server NC023 was down between 20:06 and 20:23 UTC while a patch for the Spectre vulnerability was applied.
Server NC031 was down between 05:03 and 05:17 UTC while a patch for the Spectre vulnerability was applied.
The maintenance on server NC027 is complete, and it was brought back online at 22:17 UTC. Thank-you for your patience.
While we did this maintenance we also patched the server for the Spectre vulnerability. This means that the maintenance to do that on 1 May is no longer necessary, and has been cancelled.
If you have any questions or concerns, please contact support.
Server NC027 went down for maintenance at 21:05 UTC. We will post updates here as the work progresses and when the server is back online again.
We heard back from Microsoft/Outlook.com, and they have removed the relay server’s IP address from their blacklist. Thanks for your patience.
Good news! NC027‘s IP address has been removed from the blacklist it was in, so at 12:41 UTC we switched mail processing back to the primary server. NC027 is in no blacklists of which we are aware.
Please note that the events of the last couple of days have pushed the notices we issued of upcoming scheduled maintenance on three of our servers down the page. If you have missed them please see:
Thank-you for your patience over the last 24 hours. If you have any questions or concerns, please do let us know.
It has come to our attention that some email from the IP address of our secondary mail server (NC023) is being blocked at Outlook.com. It seems that only email sent to Outlook.com domains — e.g., outlook.com, hotmail.com, msn.com — is being blocked, but email sent to other domains hosted by Outlook.com is not being blocked. It’s unclear why the differentiation.
We do have an account with Microsoft for the purpose of monitoring reports about mail sent from our IP addresses to Outlook.com mail servers. However, although the account tells us that the IP address is blocked, it doesn’t tell us why or provide us with any statistics, as it does for our other IP addresses.
We have contacted Outlook.com to determine what is happening here, as this too is a situation we’ve never seen before.
As explained yesterday, a client’s compromised email account sent out thousands of spam emails before it was detected and stopped. This has happened before, but the circumstances this time are different.
Most blacklists are automated, both in adding IP addresses to the blacklist and in removing them. This is a double-edged sword. On the plus side, IP addresses that are the source of spam are quickly added, making it less likely that spam will get through in subsequent attempts from the same IP address. Most, if not all, automated blacklists then remove the bad IP address fairly quickly after the spam stops. They realise that stuff happens, and when the spam stops they assume the problem is fixed and remove the IP address. There is short-term pain, but it’s measured in hours and the block is generally removed within your business day.
On the negative side, organisations and people that run blacklists are generally unwilling to manually remove IP addresses before they automatically expire. In and of itself this isn’t actually a bad thing; many blacklist wouldn’t be able to function if they had to field pleas and demands that IP addresses be removed. Quick, automated removal when the problem that caused the listing in the first place is fixed is the cure.
Unfortunately this situation has exposed a blacklist that actually seems to be designed to punish mail servers that have had a temporary problem, even after the problem has been stopped. This is unusual in our experience, as it makes the blacklist less useful, by blocking legitimate email long after the problem has been addressed. Information on their website states that it could be “a week or more” before an IP address is removedif they determine the spam outbreak to be severe enough — without defining “severe” — even though it has stopped. And since the addition and removal of IP addresses is automated, “you cannot” get your IP address removed manually. Full stop.
Since this blacklist is still blocking our mail server’s IP address almost 24 hours later, at 05:01 UTC we started relaying all mail sent by clients through our relay mail server (NC023), which has a different IP address. We will continue to monitor the blacklist in question and reverse this once our IP address is removed.
It seems that most of the mail servers we’ve seen using this blacklist are in South Africa. Mail bounced using this blacklist will show a message like the following, using real email addresses, domains and IP addresses of course:
<destination@example.com>: host something.co.za[1.2.3.4] said: 550-rejected because 212.71.255.195 is in a black list at truncate.gbudb.net 550 http://www.gbudb.com/truncate/ [212.71.255.195] (in reply to RCPT TO command)
If you’ve seen this, we suggest that you contact the person to whom you sent the email and suggest that they tell their hosting company that they should stop using blacklists that don’t operate within the norms of most blacklists. Feel free to point them to this blog post.
With all of the above said, we will be setting up a new mail server and migrating all accounts to it within the next couple of weeks. The new server will be better equipped to spot and stop these outbreaks automatically before they become “severe”.
As always, we appreciate your patience, and we also appreciate those clients that keep their anti-virus software up to date. If you have any questions, please feel free to contact us. Thank-you.
We have cleaned up the mail server (NC027) after an email account was compromised. This has resulted in the mail server being placed in at least one blacklist. The email account in question has been disabled pending resolution by the client of the root cause of this issue, but it will be a few hours before restrictions on our primary mail server’s IP address put in place by this blacklist expire.
These incidents usually arise after a client’s computer has been infected with a virus. The virus then sends the email password back to the person or organisation controlling the virus, and they then use that information to compromise that email account on the mail server, using it to send thousands of spams from the account. Please ensure that you install, use and update an anti-virus program on your computers and any other devices to ensure that this doesn’t happen to your email account.
We apologise for this incident. Please contact us if you have any questions. Thank-you.
Due to the growing need for more and bigger email accounts, we need to add more disk space to server NC027. This will require us to take the mail server offline during our regular weekly maintenance window for approximately four hours starting at 20:00 UTC on Saturday 28 April 2018. (Please click that link to determine when this will be in your time zone.)
During this maintenance you will not be able to send or receive email. Incoming email to your domain will be held on the sending servers until our mail server is back online, and will then be delivered to your accounts. No email will be lost.
Please note that email to NinerNet will also be down during the maintenance on server NC027.
This is phase one in a two-phase plan to ensure that long, disruptive maintenance windows like this become a thing of the past. We will post more details about this in the coming days.
Systems at a Glance:
Loc. | System | Status | Ping |
---|---|---|---|
NC023 | Internal | Up? | |
NC028 | Internal | Up? | |
NC031 | Internal | Up? | |
NC033 | Operational | Up? | |
NC034 | Internal | Up? | |
NC035 | Operational | Up? | |
NC036 | Operational | Up? | |
NC040 | Internal | Up? | |
NC041 | Operational | Up? | |
NC042 | Operational | Up? |
Subscriptions:
Search:
Recent Posts:
Archives:
Categories:
Links
Tags:
Resources:
On NinerNet: