NinerNet Communications™
System Status

Server and System Status

Email to Realtime and iWay Africa delayed

7 November 2010 22:33:07 +0000

We’re seeing a fair bit of email queued on the mail servers for email addresses on Realtime domains, and domains hosted by Realtime. Some of this email has been undeliverable for several days, and will be returned to the senders unless the Realtime mail servers come back up soon.

Email to the iwayafrica.com domain continues to be delayed in transit. For several months now we have noticed that email to this domain sits on our mail servers for days before it is delivered.

As always, if you refer people hosted with these companies to NinerNet for reliable and timely delivery of email, we’ll happily credit your account with referral fees! Contact us for details.

Server NC018 removed from SORBS blacklist

20 September 2010 18:40:16 +0000

The IP address of server NC018 has been removed from the SORBS blacklist. However, it could be up to 48 hours before cached information expires. If you have any issues with outgoing email being returned because of this issue, please contact NinerNet support. Thank-you.

Server NC018 SORBS listing

20 September 2010 08:08:32 +0000

We have determined the issue with this listing and made the necessary submissions to have this erroneous listing removed. Unfortunately, when this happens is beyond our control.

Server NC018 in the SORBS email blacklist

20 September 2010 06:33:08 +0000

We have just become aware that the IP address of server NC018 is in the SORBS email blacklist/blocklist. We are investigating this incident and will post an update here when we know more.

Implemented blocklists on server NC020

3 September 2010 21:29:39 +0000

As part of the ongoing reconfiguration of the relay and secondary mail servers on server NC020, we’ve implemented use of blocklists — the same blocklists that have been in use on server NC018 for several years. As expected, we’re already seeing a pay-off from this, with spam being rejected.

This implementation of the blocklists should not result in clients using the relay server being blocked, even if their IP address appears in the blocklists we’re using. However, if you use the relay server to send email and should you experience any problems trying to do so, please contact NinerNet support immediately.

Relay/secondary mail server operating smoothly

2 September 2010 07:34:14 +0000

Based on monitoring over the last three hours or so, the reconfigured relay/secondary mail server on server NC020 is running smoothly. We’ve sent email to the administrative contacts of all clients using this server for these purposes requesting feedback.

As always, if you have any concerns or problems, please contact NinerNet support for assistance. Thanks for your patience as we improve the configuration of this server to better serve you.

Relay/secondary mail server on NC020 running with new configuration

2 September 2010 05:30:14 +0000

The relay/secondary mail server on server NC020 is running with a new configuration. We are monitoring it to make sure it’s working. There are some issues that we are addressing right now. Please contact NinerNet support if you have any issues or concerns.

Problems with delivery to kcm.co.zm domain

12 July 2010 11:37:39 +0000

We have had ongoing problems with delivery to the kcm.co.zm (Konkola Copper Mines) domain since time immemorial. Konkola appears to host their own mail server over a very slow Zamtel connection. This means their connection appears to be extremely limited in what it can handle. While sporadic small emails without attachments generally go through within a day or two (yes, that’s days, not seconds, minutes or even hours), larger emails with attachments either stall or take so long to deliver that they affect delivery of other emails.

That is the case today. Three large emails from two clients to over one hundred kcm.co.zm email addresses effectively plugged up the mail server while it waited for the kcm.co.zm mail server to accept delivery, preventing delivery of hundreds of other emails. We had no choice but to delete these emails. As soon as we did, the backlog of several hundred emails that had built up over the course of about an hour were successfully delivered within minutes.

If you email people on the kcm.co.zm domain, please consider reducing the sizes of attachments and reducing the number of kcm.co.zm email addresses you include in your distribution lists. You might also want to point them to this post so that they might become aware of the problem and therefore do something to fix it.

Email to Microlink delayed

5 July 2010 18:18:22 +0000

It appears that email to microlink.zm email addresses is experiencing delays at the moment. We have quite a few emails queued on the server at the moment going back to 3 July. It seems that the Microlink mail server is currently down.

Blackberry email status update

24 June 2010 22:28:32 +0000

Early this week we started receiving reports from Blackberry users with different wireless carriers on different continents, that late last week they started having problems using their Blackberries to access their email on their domains hosted with NinerNet. However, they could access their email accounts through regular means — i.e., POP (with an email program) or webmail.

An initial look at the problem suggested that the two common denominators were NinerNet and Research in Motion (RIM), the latter being the “Blackberry company” through which all email on Blackberry devices is handled. It was (and is) unlikely that individual carriers were the cause of the problem.

After considerable research and consultation over the course of a couple of days, we did not have (and still do not have) any definitive reason for the problem. One reason for the lack of a definitive cause is the complete lack of information from RIM, who seem not to have any useful information about their email processing methods on their website for hosting companies like NinerNet, and who make it very difficult for people to contact them. (One good thing that can be said about a behemoth like AOL is that they maintain a website and a channel for hosting companies like NinerNet to contact them in the event of email delivery issues, as happened last week. That issue was successfully resolved thanks to dialogue with AOL.)

In the spirit of trial and error we tried two different configuration changes to our mail server based on the connection activity we were seeing from RIM servers. In hindsight we should have implemented these separately to see which one was actually responsible for fixing the issue, but the focus was, of course, on fixing the issue, not messing around. That said, a third issue was that, after making the configuration changes, we restarted the mail server. This had the effect of closing down about two hundred connections to our mail server from RIM servers. About fifty connections were quickly re-established, and we expected this number to grow again to about two hundred … but it didn’t. After more than twenty-four hours the number of connections remains steady at about fifty. This is interesting in itself, as simply restarting the server and not making the configuration changes may actually have fixed the problem anyway, making us wonder why RIM had so many connections open to our server in the first place.

So for now the issue appears to be resolved. We’re continuing to monitor connections to our mail server by RIM servers, and we ask that, if you have any further problems with accessing your NinerNet-hosted email using your Blackberry, you contact us with the details as soon as possible. Thanks very much.

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: