Brief MySQL scheduled maintenance September 8, 2017 (completed)

Between 9:00 PM and 11:59 PM Pacific time on Friday, September 8, 2017, the MySQL database software on each of our servers will be upgraded from version 5.6.36 to 5.6.37. This will cause an approximately 60 second interruption of service on each MySQL-using customer website at some point during this period.

This upgrade is necessary for security reasons and to fix bugs in MySQL. We apologize for the inconvenience this causes.

Update 10:21 PM Pacific time: The maintenance was completed as planned and all services are running normally.

PHP 7.0.23 and 7.1.9

The PHP developers recently released versions 7.0.23 and 7.1.9 that fix several bugs. We’ve upgraded the PHP 7.0 and 7.1 series on our servers as a result.

These changes should not be noticeable, but as always, don’t hesitate to contact us if you have any trouble.

Labor Day 2017 holiday hours

Our business offices will be closed on Monday, September 4 to observe the US Labor Day legal holiday. As always, we’ll provide same-day support for time-sensitive issues via our ticket and e-mail systems. However, questions that aren’t time-sensitive (including most billing matters) may not be answered until Tuesday, and telephone support (via callbacks) will be available only for urgent issues.

Brief interruption in service for some sites August 29, 2017

Between 8:41 and 8:44 Pacific time tonight (August 29, 2017), there was a brief load spike on one of our servers that caused errors on some sites.

We’ve identified the cause of this (high NFS disk load caused by an internal tool we use) and fixed it so the problem won’t recur.

We apologize for the inconvenience this caused.

Mailman mailing list software upgraded to version 2.1.24

The authors of the Mailman mailing list software we provide for customers have recently released version 2.1.24 to fix several bugs.

We’ve upgraded the Mailman software on our servers as a result.

Users of Mailman lists shouldn’t notice any changes, but as always, don’t hesitate to contact us if you have any questions or see any problems.

SSL pages for Mailman mailing list software

We’ve added Let’s Encrypt SSL support to many Mailman mailing list pages, including all the pages that ask for passwords or login information.

The use of SSL should be transparent. If you have bookmarks to URLs on your own lists like http://lists.example.com/mailman/admin/listname, you’ll automatically be redirected to the SSL (https) version of that page when you load it.

(New lists may not use SSL immediately when created, but will be switched to SSL when our system is able to obtain an SSL certificate for them. Quicker automation of this is something we’re working to improve.)

Users of Mailman lists shouldn’t notice any changes beyond pages being marked as “secure” in web browsers, but as always, don’t hesitate to contact us if you have any questions or see any problems.

PHP 7.0.22 and 7.1.8

The PHP developers recently released versions 7.0.22 and 7.1.8 that fix several bugs. We’ve upgraded the PHP 7.0 and 7.1 series on our servers as a result.

In addition, ionCube Loader is now available for the PHP 7.1 series, so we’ve made that an option you can enable in our “My Account” control panel.

These changes should not be noticeable, but as always, don’t hesitate to contact us if you have any trouble.

Change to some default SPF mail DNS records (softfail instead of neutral)

This post describes a technical change that most customers can ignore; we’re posting it for advanced users who may be interested.

If you have hosting service with us, we publish a default SPF record in your DNS zone if you don’t provide one yourself.

Read the rest of this entry »

PHP 5.6.31, 7.0.21, and 7.1.7

The PHP developers recently released versions 5.6.31, 7.0.21, and 7.1.7 that fix several bugs. We’ve upgraded the PHP 5.6, 7.0 and 7.1 series on our servers as a result.

These changes should not be noticeable, but as always, don’t hesitate to contact us if you have any trouble.

Read the rest of this entry »

SpamAssassin headers now added to some whitelisted messages

One of the features of our e-mail system is that we add SpamAssassin headers to most incoming mail, as described on our SpamAssassin page.

Until now, we didn’t add SpamAssassin headers to messages that were “whitelisted” because they appear to be from someone you’ve sent a message to.

In recent years there’s been an increase in forged spam claiming to be from addresses you know, though, often because the other person’s address book has been stolen by a virus. Because of that, it can be useful to see SpamAssassin results even for these whitelisted messages, and we’ve changed our mail system to add SpamAssassin headers to them as well.

This doesn’t change the fact that we won’t reject these whitelisted messages, regardless of their SpamAssassin score. The only change is that we now add SpamAssassin headers, allowing customers who want to examine the SpamAssassin score to do so. Customers won’t notice any change unless they have their own systems to examine the SpamAssassin headers.