Update April 2023:
GRID legacy access domains starting with s#### will be retired.
Earlier this year we notified you that the Grid's legacy Access Domains would retire along with the Grid infrastructure. This is an update that the Grid infrastructure is scheduled to be decommissioned on April 28, 2023.
To prevent any disruption in service, please update your Access Domains before April 28, 2023.
Settings are here:
=============================================
After approximately 15 years GRID Mail will be sunset, and all mailboxes will be transitioned to a new platform powered by Open Exchange. We expect this transition to take place the first week of February and will have more details coming as the time gets closer.
This is being done by our datacenter as they are retiring the GRID platform. If you are a GRID email customer and have any questions about this please email us or open a support ticket via our support portal.
If you wish to be migrated to our Smartermail service ahead of this transition we can do that for you at no cost in January and recommend this for many of our customers.
January 2023 Update
As we migrate the last customers from our legacy Grid service to our new Shared Hosting, we are preparing to retire the Grid's infrastructure on March 31, 2023.
Upon retirement of the Grid, you will no longer have access to the Grid's legacy access domains. An access domain is a unique hostname that is assigned to a particular service that is designed to always resolve to your service, regardless of whether any other domains have DNS pointing to the service. This allows for various preview and connection functions.
For Grid, the legacy access domains render as s0000.gridserver.com where "s" stands for "site" and 0000 is a unique number assigned to your account and server.
To prevent interruption to your web and email connections using access domains, we advise all current and former Grid customers to follow the instructions below:
GRID EMAIL
If you are using Grid email with an email client, you will need to verify your client is configured to use your email access domain associated with your account. If not, you must update your client to point to the new XXXX-XXXX.accessdomain.com URL associated with your account.
You can find the correct URL for your service by following the instructions provided in this KB article: