Category: Security

DKIM Signing Outbound Email

We began signing outbound mail flows for and several weeks ago and have started to sign all customer owned domains this morning. This should be seamless for most customers, however, in some cases you may receive special instructions from us in order to enable it for your domains. Having aligned DKIM and SPF has become increasingly important to ensure reliable email delivery, especially into large providers like Gmail, Yahoo and Microsoft. We have chosen not to add DMARC records to customer domains at this time.

Please note, that if you use a third-party service provider such as Mailchimp, Constant Contact, Salesforce or Shopify to send email from either your or hosted domain you will most likely need to take action to ensure this email will continue to be delivered as expected. Importantly, you will not be able to send mail through a third-party service from a “” address. (These messages can, of course, have a reply-to to your “” address.) If you do use a third-party service, you will need to work with their customer service to ensure your mail flows will not be affected.

Please direct any questions or comments to

SPF record added to domains with Sonic DNS & Email hosting

Today on August 22, 2022, we added a default SPF (Sender Policy Framework) record to every customer domain name that has Sonic DNS hosting and email hosted with Sonic.

On August 15th, we emailed everyone who would be impacted by this change. The email subject was “Important information about your Sonic domain email hosting” and included a list of domain names that would be updated.

If you did not receive the email or do not have domain email and DNS hosting with Sonic, this notification does not apply to you.

If you received the above notification email and did not opt out or add an SPF record before today, the following SPF record was added to your domain:

"v=spf1 ~all"

For more information, please see our help document SPF and Sonic. To learn more about SPF, see Sender Policy Framework on Wikipedia.

We made this change to fight spam & phishing and to help ensure reliable email delivery for our domain email customers. SPF tells other email providers that Sonic is authorized to send email on behalf of these hosted domain names.

System Maintenance

Update: Maintenance complete

Starting at 11:59pm this evening, SOC will be running updates to multiple customer facing services. The following may experience hiccups during the maintenance window:

  • Webmail interfaces
  • Membertools
  • Forums

This post will be updated when the maintenance is complete.


System Maintenance

Update: Maintenance Complete


Tonight at 11:59 pm we will be running a maintenance window to apply software updates to multiple customer facing systems. The following services may experience brief interruptions:

  • Customer tools (Webmail, Membertools)
  • Hosted MySQL Databases.
  • IPv6 Tunnels

The maintenance window is expected to last 1 hour.


SSL Certificate Issues

UPDATE: Our CA has reissued our certificates, and they have been installed.

The Extended Validation (EV) certificates we installed last week have blocked a small, but significant, subset of users from accessing our websites due to the use of Elliptic Curve Cryptography (ECC).  In most cases, using Firefox instead of IE, Safari or Chrome resolves the problem.  We recognize this isn’t always and acceptable solution and have asked the Certificate Authority (CA) to reissue the certs using RSA and will install them as they become available.  However, we strongly encourage customers using Windows XP or old version of OSX to upgrade their operating systems to a modern supported version.  Using an old unsupported browser from an old unsupported operating system is a “Bad Idea.”  It is also exceedingly likely that future steps taken to ensure the privacy and security of our customers at large will cause similar issues for these old systems.

System Maintenence Tonight.

Update: Maintenance complete

Tonight starting at 11:59pm SOC will be updating software on some of our core systems. The following services may experience brief interruptions:

  • Website hosting
  • IPv6 tunnels
  • Incoming and outgoing mail

We will also be upgrading the SSL certificate for from SHA1 to SHA256. This is the last of our SSL certificates that we need to upgrade so we don’t expect most clients to have problems, but very old mail clients may not support the new certificate.


-Grant, Joe, and SOC

Connectivity Issues to Santa Rosa Datacenter

This morning, beginning around 3:45 AM, a host within our Santa Rosa datacenter became the target of a very large DDoS attack. We are currently in the process of battling this attack and users may notice reachability problems to services such as our email servers and member tools during this time.

– Robbie

The Heartbleed Bug and You: Change Your Passwords!

We always keep your privacy and security in mind.

By now you’d be hard pressed to have missed coverage of The Heartbleed bug in OpenSSL.  At this point, is joining many other providers and recommending that you change your passwords for your online services.  This is important for high value accounts like banking and finance or other accounts that protect your personal information and data.  Do not forget to change your ISP and email account passwords!  These are especially important since access to your email account can be used to gain access into most of your online services.

We do not have any reason to believe that we, or any of our users, were targeted.  However, this attack was undetectable and the cautious response is to assume that sensitive information has been leaked.  In the interest of full disclosure we are providing a complete list of affected services and systems.  It should be noted that all of the vulnerable services support PFS wherever possible and should our private keys have been leaked, they cannot be used to decrypt any past traffic in most cases.

Customers may change their passwords in the membertools using the password tool.

If you have any questions, please post them in our forums.

As of 21:45 on April 7th,  all vulnerable systems had received an update to fix this bug.

The following sites and services were vulnerable:

  • (login credentials were not vulnerable, only keys)
  • (login credentials were not vulnerable, only keys)
  • (login credentials and mailflow in/out)
  • (used by mobile apps)
  • (used by our wholesale partners and customers)
  • (used by our wholesale partners)

All of these systems have had their certificates replaced except for the following which are still pending reissue by our CAs:

UPDATE: All systems have had their keys replaced.


The following sites and services were not vulnerable due to running an early version of OpenSSL:

  • (inbound mail)

OpenSSL Heartbleed Bug

A serious bug in OpenSSL was announced this afternoon known as the Heartbleed Bug.  An attacker, armed with the ability to exploit this bug is able to remotely read the contents of the memory of a vulnerably server.  This exposes the potential for an attacker to acquire the private key used to both encrypt the traffic and identify the server allowing them to eavesdrop on traffic as well as impersonate the server.  For a more in depth explanation of the bug and its affects see  We have updated our servers with a local version of OpenSSL that disables Hearbeats to prevent an exploit pending new packages released by our OS upstream which fully resolves the issue.   -Kelsey

Update: April 8th, 17:35.  All affected public web and application servers received the fix from our OS upstream shortly after the original MOTD was posted yesterday.  Today, we’ve worked on wrapping up the upgrades on less critical systems and have reissued certificates for the bulk of the systems which had potentially exposed private keys. Ironically, we’re still waiting for all of our EV certs to be reissued.  The severity of this exploit can’t be underestimated as even earlier today Yahoo’s servers we’re still vulnerable exposing user names and passwords for the taking with little effort.  All users who run secure services should ensure that their systems are properly patched and consider having their certificates reissued by their CA.  -Kelsey and Grant