Server and System Status

The aforementioned sweep of all migrated email accounts on the old server has been completed, and all mail accounts on the old server have been deactivated.

If you are having problems sending email, please double and triple check your email configuration against the instructions you’ve been given. We’ll be making phone calls today to check with clients individually to ensure that everything is working.

Please ensure that you correctly follow the instructions you have received for configuring your email program. All problems we have encountered so far are all related to missing a tick, setting the wrong encryption method, spelling mistakes, etc. These are the correct settings:

• User name: you@yourdomain.com
• Password: Your Password
• Password type: Plain
• Incoming (POP) mail server: pop27.niner.net
• Incoming mail server port: 995
• Outgoing (SMTP) mail server: smtp27.niner.net
• Outgoing mail server port: 587
• Authentication: Turned on for SMTP
• Encrypted connection: TLS (if it’s an option in your email program) or SSL (if TLS is not shown as an option)

All of the above settings are important and required. None are optional. Your password has not changed, so if you’re not sure that you remember your password, please don’t edit it in your email program.

Using the above settings you can configure any email program on any computer, phone or tablet, even ones for which we have not provided unique instructions.

However, if you are having problems, please contact us. We are happy to help.

Please also note that the settings for the old server will stop working early in the morning of Tuesday, 8 October, UTC, so please do your best to get the new settings working today.

The migration has completed. After midnight UTC we will perform the sweep mentioned earlier, and then disable migrated domains on the old server.

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.

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.

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.

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.

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.