NinerNet Communications™
System Status

Server and System Status

Email migration: Update 7

7 October 2013 10:53:23 +0000

One more note, in case it wasn’t made clear earlier. All new email to migrating and migrated domains is being delivered to your accounts on the new server, unless it is sent by someone using the old server. This means that email from contacts not hosted with NinerNet will arrive in your account on the new server. However, email from clients still hosted on the old server — and from people on migrating/migrated domains who are still using old email settings to send email — is being delivered to the accounts on the old server. Avoiding this overlap is why we had hoped to complete this migration on the weekend, but it will be rectified by the sweep we will make at the end of the day today.

As always, we’re here to help if any of this is confusing. Please contact support if you have questions.

Email migration: Update 6

7 October 2013 10:43:28 +0000

Due to a mis-configuration in a script managing the migration, no email was transferred from the old server to the new, so we have restarted the migration. This means it may not complete until approximately 15:00 UTC on 7 October. At this time email is definitely transferring, and domains starting with “G” have just started migrating. As the day goes on you will notice email from the old server (if you had mail stored there) appear in your mail boxes on the new server.

Because the migrating domains are still active on the old server — they need to be for their mail boxes to be accessed from and transferred to the new server — we’ll be doing a sweep at the end of the day to make sure we transfer over any recently arrived mail. After that all migrated domains will be disabled on the old server, and only the new configuration settings for your email program will work.

Speaking of that, we have had some feedback on the new settings, mostly reports of success. Those where there have been problems were solved by making sure that the settings we have provided to you via email were set EXACTLY. When configuring email settings, there is no such thing as “close enough”. All of the settings are there for a reason and need to be set exactly as they are shown in the configuration instructions — with the one correction we made earlier to set TLS in Outlook rather than SSL. Please keep this in mind if things are not working, and compare your settings very carefully with those we have provided.

Thank-you for working with us to move your email to a new, faster more secure server.

Email migration: Update 5

7 October 2013 03:03:05 +0000

The migration has been in progress for over hour. At this time all new email sent to those domains being migrated is being delivered to the new server. Please follow the instructions you received in your email last week to reconfigure your email program NOW.

As the start of the business day approaches in some times zones please note that, if you were expecting to find old messages in your mail box, they may not be there yet. They will appear over the next few hours.

After the last migration we had some reports that Outlook was downloading multiple copies of old messages. Please note that this is an issue with Outlook, and we have no control over it.

There is also a correction to the instructions you have received: If setting SSL on the outgoing (SMTP) server does not work for you, please use TLS. We had reports that some versions of Outlook only worked with TLS set instead of SSL.

Please contact us if you are having any problems. Please see the email you received with our email address, phone number and Skype user name. If you are not our contact for your company, please deal with the person who is our contact, and we will assist them. If they are unable to help you, they will refer us to you.

Email migration: Update 4

6 October 2013 19:41:37 +0000

We again started experiencing Internet connection issues with our ISP at our office shortly after the scheduled start time of the migration, so we are packing up and moving to a new location. This means that we are again late getting this migration started.

We apologise again for the delays and any inconvenience.

Email migration: Update 3

5 October 2013 23:33:20 +0000

Due to connection issues at our office with our ISP (not at the data centres where the servers are located), we are delaying this migration 24 hours. Although this ISP is generally very reliable, we will be prepared to relocate to use a different ISP tomorrow should the problem with our usual ISP continue.

We apologise for the inconvenience, and will try again at 19:00 UTC on Sunday.

Email migration this weekend

4 October 2013 08:23:20 +0000

Following the successful migration of some email accounts earlier this week, we will be migrating the email for a number of other domains to the new mail server (NC027) this weekend. If your domain will be included in this migration, you will receive an email with details.

This migration will take place at 19:00 on 5 October 2013 UTC. Please check the World Time Server for a conversion to your time zone.

The best news about this is that we will do this migration without shutting down SMTP on the old server (NC018). Therefore there will be no disruption to the accounts remaining on server NC018, or those that have already been migrated.

However, for those domains that will be migrated, there will be changes required to the configurations of your email programs. These details will be provided in the emails we will send to you before the migration starts.

It your domain is included in the migration, you will be moving to a much newer, faster and more secure server.

Updates will be posted here leading up to, during and following the maintenance. Please inform colleagues, employees and anybody else using email on your domain.

If you have any questions, please contact support and we’ll be happy to assist.

Thank-you.

Email maintenance: Update 6

2 October 2013 09:39:44 +0000

SMTP on server NC018 is definitely working again. The problem was fixed at 07:55 UTC. You can once again send email, and most (if not all) incoming email queued on sending servers should have been delivered to your account by now. All email on our own back-up mail server was delivered by 08:13.

Again, we apologise for the length of this maintenance and the inconvenience to you.

Email maintenance: Update 5

2 October 2013 06:28:29 +0000

The maintenance is complete. SMTP on server NC018 is back online. You can send email once again, and email queued on sending servers should arrive in your account soon.

Email maintenance: Update 4

2 October 2013 02:49:00 +0000

After numerous false starts, an email migration for some clients from server NC018 to NC027 got under way at 01:46 UTC on 2 October. Please see “Email maintenance this weekend” for full details.

The main reminder is that clients with email on server NC018 (which is most clients) will not be able to send email until this migration is complete. You will be able to log into your email account, but email sent to you during the migration will not arrive in your account until after the migration is complete.

For any questions during the migration, please email support-september-2013@ninernet.com. Contrary to our earlier post, please do not use the contact form on our website, as we will not see emails sent through that until after the migration completes.

Thank-you for your patience as we work — sometimes day and night — to improve the service that we provide to you.

Email maintenance: Update 3

30 September 2013 23:23:33 +0000

We will complete the email maintenance on Tuesday 1 October 2013 at 01:00 UTC. That’s 18:00 PDT on Monday, 03:00 CAT on Tuesday. (Please see the World Time Server to convert for your time zone.)

We anticipate that the SMTP server will be down for less than an hour at that time.

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: