We are in the process of moving to new servers and a new datacentre. This is a newer facility, and in the process we are making our infrastructure more reliable. There may be some disruption, but we will do our best to keep it as unobtrusive as possible. Please let us know if you see anything unexpected, or run into any problems. Thank you for your patience and understanding!
An electrical fire in a UPS belonging to our clocation provider resulted in a power outage for our equipment starting about 02:30EDT Sunday, July 5. Power was restored approximately 80 minutes later. However, our firewalls were incorrectly configured to not automatically reboot when power is restored, resulting in a further delay restoring services. All services were restored by approximately 10:30EDT. We have corrected the configuration error. Please accept our apologies for the longer than necessary outage.
This morning, from about 11:00am to 11:35am, our servers (mail, web, dns) were unreachable. This turned out to have been a networking configuration error by our colocation provider, and they quickly corrected the problem. This was a very unusual occurrence – in the past 6 years, there have been at most 2 or 3 problems at the colocation facility, which we consider to be an exemplary track record, and we remain 100% confident in our choice of provider. Thank you for your understanding, and please accept our apologies for the outage and inconvenience.
The mail server at smtp.syonex.com now supports encrypted connections. We encourage you to use authenticated, encrypted connections to the mail server from your mail client.
Early this morning, the anti-virus software’s automatic update process went crazy and filled up the filesystem that handles mail. This was fixed this morning. We expect to update the anti-virus software in the near future. Please accept my apologies for the inconvenience.
The squirrelmail web interface (via https://secure.syonex.com/ now allows you to compose messages in HTML format.
There were problems getting to the SYONEX sites this afternoon (roughly 4pm to 5pm EST) from locations on the rogers.com network, which have now been fixed. The sites were accessible from other networks during this time. Our understanding (at present) is that it was a problem in the Rogers network.
Shared SSL (HTTPS) web pages are now available for shared hosting customers. Contact us if you’re interested.
The postgrey greylisting software was updated, which also updates the greylisting “whitelist” for sites that don’t respond well to greylisting. (Greylisting is one of the spam-fighting tools we use.)