Customers who forward their mail to Gmail occasionally tell us that they can’t find a message they know someone sent them, even when they’ve searched Gmail for it.
These messages are often eventually found in the “Spam” or “Trash” folders of Gmail. What’s surprising is that by default, Gmail search doesn’t look in these folders at all, so people are (quite reasonably) sure it’s not there.
Between 10:00 PM and 11:59 PM Pacific time on Saturday, May 24, each of our hosting servers will be restarted. This will cause a brief interruption of service (less than 10 minutes) for each site at some point during this 2 hour period.
Our business offices will be closed on Monday, May 26 to observe the US 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 the next day, and telephone support (via callbacks) will be available only for urgent problems.
If you use the Gravity Forms WordPress plugin, be sure you don’t set it to send mail “from” the e-mail address of the person filling out the form. If you do, you’ll have trouble due to recent “DMARC” anti-forgery changes some companies (including AOL and Yahoo) have made.
To avoid problems, make sure that Gravity Forms (and other such forms) send mail “from” the Web site domain name the form uses. For instance, if your Web site is at www.example.com, you could send mail from “notifications@example.com”. Here’s a helpful page that explains how to properly set up the Gravity Forms address with DMARC in mind.
By the way, this is just a specific case of the general rule of “don’t send mail from addresses you don’t own”. The simple way to think of it is that you’re not (say) AOL or Yahoo, so your Web site shouldn’t send mail claiming it’s from aol.com or yahoo.com addresses. AOL and Yahoo don’t want other people doing that. Always send mail only from your own domain name.
We’ve updated the MySQL database software on our servers from version 5.5.35 to 5.5.37 for security reasons.
Customers should not notice any changes, as the update merely fixes bugs and doesn’t introduce new features. But as always, don’t hesitate to contact us if you have any questions.
We recently upgraded Mailman to fix a problem for Yahoo and AOL users, which has worked well.
Today we found a problem where since the initial upgrade on April 24, people who tried subscribing to a Mailman list by sending an e-mail message (instead of using the more common Web interface) weren’t properly added to the list.
This was caused by an incompatibility between our mail system and one of the Mailman software changes. We didn’t receive a report of this problem until today because few people try to subscribe this way.
We’ve resolved this: Any delayed subscriptions have been correctly handled and the incompatibility has been fixed. We apologize to anyone affected by it.
