NinerNet Communications™
System Status

Server and System Status

AOL email update

22 June 2010 03:32:41 +0000

We’ve had the following response from AOL to our query about incoming email from AOL addresses being bounced back to the senders:

We had few issues with our Outbound IP’s timing out with few mail servers last week. Are you still seeing reports of our users not able to connect to your servers? Please send me the headers and I can check the logs at our end. With regards to Spam Flag Yes- we are seeing lots of AOL accounts being compromised forcing us to send mails through our aberrant IP’s. These mails might be rejected at our end too if we suspect compromise but do issue a bounce message.

This would seem to indicate that AOL has solved the issue of legitimate email sent to NinerNet clients being returned as undeliverable. We’ve had no reports of incoming email from AOL senders being bounced for over a week now, so we’ll consider this matter closed.

Server NC020 rebooted

20 June 2010 15:10:59 +0000

Server NC020 was rebooted at 14:34 UTC after it was reconfigured with more RAM.

AOL and Realtime email updates

17 June 2010 06:06:50 +0000

While we have not heard from AOL yet, in recent experiments all email from AOL got through. However, these experiments were on a very small scale, so may not accurately reflect reality.

Domains hosted by Realtime appear to be back up again after being down for about five days. That email backlog has been cleared.

Email to the iwayafrica.com domain appears to be having problems. There isn’t much of this backlogged on the mail servers, but there is some. Same with a couple of domains hosted by Coppernet.

If you’re trying to communicate with people with unreliable email, why not refer them to NinerNet? We pay referral fees!

Issues with incoming email from AOL

14 June 2010 07:43:43 +0000

We have had some reports of incoming email from AOL users being bounced back to the senders. After some extensive research over the last few days we believe we have managed to address this problem, adjusting the configuration of one of our anti-spam measures (greylisting) to allow for the fact that AOL’s handling of outbound email doesn’t play well with greylisting.

If you are a NinerNet client and have any reports from correspondents with AOL email addresses indicating that email from them to you has been returned as undeliverable, please contact support.

Update 2010-06-15 07:28 UTC: Apparently this issue has not yet been resolved. We contacted AOL yesterday to find out why some of their mail servers are bouncing email prematurely and without reason, but their auto-response says it could take seven days or more for them to respond, it at all. We will post updates as they become available.

Zambian email delays

14 June 2010 07:36:10 +0000

Clients sending email to domains hosted by Realtime are advised that messages to these domains have been backing up on our mail servers over the weekend, and are still not being delivered. A cursory analysis would seem to indicate that there is a routing problem at or near the Realtime mail servers. If you have concerns about this, please contact the intended recipients via a medium other than email and have them contact Realtime for an explanation.

Update 2010-06-15 07:26 UTC: This issue seems to be ongoing. Domains hosted by Realtime appear to be down still, and email to them continues to be queued on our mail servers.

FTP issues for some Windows users

29 January 2010 14:53:23 +0000

We’ve had increasing numbers of reports from Windows users that they keep being disconnected from the server when trying to upload files via FTP. We’ve verified that this is a problem when trying to FTP files using a Windows XP machine, using both the native, command-line FTP client and third-party GUI clients. However, when we’ve tested FTP using Mac OS X and Linux machines, there are no problems uploading files via FTP. This indicates that the problem is not on the server, and narrows the problem down to people who use Windows XP at least, but perhaps other versions of Windows too. The sudden appearance of this problem seems to suggest that perhaps a recent Windows Update has changed something that is causing this problem.

We were able to overcome this problem on the Windows XP machine we used for testing by adding the FTP program to the exception list in Windows Firewall. Here’s how you do it:

  1. Open the Control Panel.
  2. Switch to “classic view”.
  3. Double-click on the Windows Firewall icon.
  4. Click on the “Exceptions” tab.
  5. Click the “Add Program…” button.
  6. Find your FTP program in the list and click it.
  7. Click the “OK” button.
  8. Click the “OK” button again.

Below is a picture of what the “Exceptions” tab looks like on the Windows XP test machine, showing two FTP programs: the native “File Transfer Program” that comes with Windows, and FileZilla:

Windows Firewall "Exceptions" tab.

Windows Firewall "Exceptions" tab.

If you have problems uploading files to your website via FTP, please try adding your FTP program to the Windows Firewall exceptions list as described above. If you have any questions, please contact support. Thanks.

Server NC020 IP address removed from Spamhaus PBL

15 November 2009 08:54:33 +0000

The IP address of server NC020 has been removed from the Spamhaus Policy Block List. All email issues are resolved, and server configurations will return to normal.

If you have any questions concerning this incident, please contact support. We appreciate your patience.

Temporary resolution of Spamhaus PBL issue

15 November 2009 03:23:58 +0000

While the IP address of server NC020 is still in the Spamhaus PBL, we have made a number of configuration changes to all of our mail servers which address three of the four issues mentioned in our original post on this matter:

  • All email sent through server NC020 (known as “the relay server” to those of our clients who use it as such) is now routed to server NC018 before finally being delivered to destination mail servers. This means that email will no longer be delayed or rejected by destination mail servers.
  • All email is (and has been since the first post on this matter) flowing from server NC020 to NC018.
  • We are once again using the PBL to block spam on server NC018, so spam defences are back at 100%. We have simply exempted server NC020 from this block.
  • Mail to domains using NC020 as a secondary mail server is still a concern. We’ll be monitoring this and reacting as necessary.

Server NC020 is also used for some custom mailing lists. Email sent to these lists will also be handled as detailed in the first bullet point above.

We still anticipate that the IP address of server NC020 will be removed from the PBL at some point, at which point the configurations of all mail servers will revert to what they were before this incident. Further details will be posted here as necessary.

Update on server NC020 in the Spamhaus PBL

14 November 2009 20:42:44 +0000

Server NC020’s IP address is still in the Spamhaus PBL. We have been unable to make any progress on having it removed yet. This may be because it’s the weekend, or it may be that we’re just one of thousands of companies that have been affected by this action, and so we just have to be patient. In the meantime, we are trying to have our case looked at sooner rather than later.

We’re also going to take steps to have mail from server NC020 routed through NC018 as a temporary measure. We will post here again when this has been put into place.

Server NC020 is in the Spamhaus Policy Block List

14 November 2009 09:19:23 +0000

Within the last few hours, the IP address of server NC020 has been added to the Spamhaus Policy Block List (PBL). This is well-known, major and useful anti-spam block list operated by a reputable anti-spam organisation, and we ourselves use this block list to protect our clients from spam. However, this affects our clients in four ways:

  • Clients who use the relay server (NC020) may find that some of their outbound email will be delayed or rejected by destination servers. This is our primary concern at the moment, and we are working with the data centre (the company that actually owns the IP address) and, through them, Spamhaus to have the IP address removed from the PBL. Unfortunately, because this situation has just arisen with no notice, things are in a state of flux at the moment so we don’t have any idea when this will happen.
  • Because there is a lot of email traffic from server NC020 (the relay server) to NC018 (our primary server), and because server NC018 uses the PBL to block spam, some clients sending email through the relay server to domains hosted by us would have found that their email was not delivered in the last few hours. We have since stopped using the PBL to block spam on server NC018, and so that email is flowing again. Any email that was delayed has now been delivered, and was not deleted or bounced.
  • Because we have stopped using the PBL to block spam on server NC018, that means that clients with email hosted on that server (most of you) have just a little bit less spam protection than before. However, we use a number of effective block lists, and hopefully the temporary removal of just one of them won’t have a major impact. Once this situation is resolved, we will reinstate use of the PBL to protect you from spam.
  • Finally, if you are operating your own mail server and are using the PBL, we suggest that you disable use of the PBL for now so that you can receive email that passes through server NC020. This would apply to you if you are using our back-up mail server (MX) service.

We will, of course, post further updates here as we learn more and as the situation progresses. We appreciate your patience.

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: