Some on-going email maintenance is currently causing some of the mail servers to feel slow. We are currently expanding our email servers to make things even faster. Unfortunately, until this completes, some of the backups and copying of e-mails are causing some time-outs. We are hoping this to be complete soon. We shall post further updates as soon as this has completed.
10th February 2017, at 2:57PM
10th February 2017, at 3:52PM
Connection to the server is currently unavailable. Our engineers are currently investigating the issue
10th February 2017, at 8:17AM
10th February 2017, at 11:46AM
We're currently seeing a network issue form one of our primary network providers. We are working to resolve this as soon as possible and will post further updates as we have them available.
7th February 2017, at 1:27PM
8th February 2017, at 10:54AM
Prohost16 will be unavailable for a few minutes whilst some security patches are applied. Email services will be unaffected.
6th February 2017, at 10:22AM
6th February 2017, at 11:23AM
We are currently performing some essential maintenance on the Atmail mail service storage servers as such all services relating to this will be taking offline shortly , this is expected to last 20-30 minutes.
31st January 2017, at 9:40PM
31st January 2017, at 10:01PM
The host machines, for containers on the WordPress Platform will be rebooted later this evening in planned maintenance. The reboot is required after security patches have been applied. During this time sites will briefly appear offline while the host reboots and the containers come back online. Engineers will be working to keep disruption to a minimum during this period.
19th January 2017, at 2:00PM
19th January 2017, at 10:52PM
Prohost20, Prohost21, Prohost22 have all stopped responding. We are currently rebooting these and expect them back online any minute. Hopefully we can find out some more information then.
17th January 2017, at 4:39PM
17th January 2017, at 5:38PM
As per notification emails sent during December and January, legacy SMTP users (i.e. those that use the domain name only and not the FULL email address as the user) are now disabled.
Users who are able to receive mail fine but are suddenly not able to send should check the user name and password they are sending with and select the option "use same settings as incoming server".
Resellers on our OLD platform (these are the ones using Plesk 8.x) should additionally check the DNS records. of any domain that experiences issues. Any smtp record pointing to smtp.xenserve.com should be changed to an A record that points to the IP address of the reseller server itself (you can confirm this by looking at the other A records for the domain).
13th January 2017, at 10:29AM
13th January 2017, at 10:29AM
The planned removal of the CRAM-MD5 authentication method from the 34SP.com SMTP servers has taken place this morning.
If you are having difficulty sending e-mail following this change please consult our guide to disabling CRAM-MD5 authentication here:
https://www.34sp.com/kb/158/how-to-remove-cram-md5-authentication-from-your-e-mail-client' target='_blank'>https://www.34sp.com/kb/158/how-to-remove-cram-md5-authentication-from-your-e-mail-client
10th January 2017, at 7:59AM
10th January 2017, at 7:59AM
Some containers running Staging sites, PHP-FPM services are currently failing. The problem has been identified and a new build is correcting and restarting the service.
4th January 2017, at 1:57PM
4th January 2017, at 2:04PM