Server and System Status

Unless you have been advised otherwise, all domains with mixed-case user names have now been migrated to server NC027.

Again, using Bob@example.com as an example:

• People can still send email to Bob@example.com and you can still use it as a return email address.
• However, when logging into your account on server NC027, you must log in as bob@example.com, not Bob@example.com.

Passwords have remained the same.

Please also remember to update your email program’s configuration per the instructions at docs.niner.net/email.

The mail migration is, for the most part, finally complete. As mentioned in our previous post, you will know that your domain has been migrated if you can no longer access email accounts on the old server. If that is the case, please start using the settings for the new server.

The only domains left to migrate are those that have user names with mixed- or upper-case letters, and domains that are changing — i.e., where an old primary domain is being replaced by what was once a secondary domain. We will take the opportunity to migrate the remaining domains outside of the business hours of the clients affected, which differ according to the time zones in which they are located, over the next two days.

There are a few additional notes to be aware of or to emphasise, in addition to those contained in Email migration: Update 1:

• Email addresses with mixed- or upper-case user names have been migrated with their user names changed to lower-case letters. This only affects logging in, and not delivery of email. If you used to have a user name with mixed- or upper-case letters, please change your log-in information to use all lower-case letters — e.g., AB@example.com changes to ab@example.com, and BobSmith@example.com changes to bobsmith@example.com. It is generally best practice to create email addresses in all lower-case letters. Your password has not changed, so please do not edit the password saved by your email program.
• Auto-responders are now managed through the webmail; they are no longer managed through the control panel. As such they have not been recreated on the new server. If you had an auto-responder in place on the old server, you will need to recreate it.
• As mentioned previously, accounts that were already over quota on the old server were not migrated. The accounts have been created on the new server, but the contents have not been transferred.
• If you had what the control panel on the old server referred to as a “redirect” in place, please check to ensure that it has been properly created to your requirements on the new server.

In addition to that last specific issue, please check over your accounts yourself to ensure that all is set up and working as it should be. If you need assistance with anything that you cannot address yourself through the control panel, please contact support and we will be happy to help you.

Thank-you again for your patience during this migration, and our apologies again for the fact that it took longer than we had planned.

Due to the many gigabytes of email saved on server NC018, the migration is still ongoing.

We are disabling domains on server NC018 as they are migrated to server NC027. What this means to you is that, if you find that you can no longer access your email account, it has probably been transferred and you should start using the settings for server NC027. Please see the “Things you need to do” heading in the Email migration: Update 1 post for that information.

Thanks for your patience.

The mail migration is definitely underway this time. We will post updates here as necessary.

We have resolved the network issue preventing the mail migration. We have rescheduled the migration to start at 00:01 UTC on Wednesday 26 August. (As always, please check the World Time Server to convert to your time zone.)

Our apologies again for the delay.

We are definitely postponing the mail migration for at least another 24 hours. Please carry on as usual!

Based on the lack of progress on resolving the connectivity issue at this point, we’re going to say that completing the migration tonight is unlikely. However, on the off chance that there’s a breakthrough before then, we’re keeping our options open.

We will post more here as soon as we know.

We were not able to overcome the last hurdle — and I do mean the very last hurdle, and an unexpected one at that — to completing this migration on time this weekend, so we have decided to postpone it before the server enters its usual busy Monday morning.

We plan to figure out whatever is causing the last hurdle — a networking issue between the old and new servers — and recommence the migration at 22:00 UTC on 24 January. (Please check the World Time Server to convert to your time zone.) We expect (and certainly hope) that the issue will be resolved by then.

Confirmation of the rescheduled time will be posted here within the next few hours.

We sincerely apologise for the delay in completing this migration.

The migration was halted during the early morning (UTC) of 23 August while we worked out some complications. Work on the migration will continue during the afternoon of the 23rd. It is our intention to complete the migration on Sunday.

In summary, nothing has changed yet. All email that is planned to be migrated has not yet been migrated.

Work on the email migration has started. We will post updates here as required.