How is mobile optimization calculated?

Mobile optimization rates are calculated by detecting how an email renders at a pixel width of 400px — approximating the width of a mobile phone. The actual emails themselves are loaded into a browser and rendered in both a desktop- and mobile-width scenario. If the email itself responds to a width of 400px, it is identified as being mobile optimized. However, if the email gets clipped at the narrower width, the message is identified as not mobile optimized.


What does it mean when an email passes or does not pass a DKIM or SPF check?

You can get 3 scores for DKIM and SPF checks:

  • Pass: 100%
  • Neutral: 50%
  • Fail: 0%

Here is what each of these mean (source):

  • Pass = ‘The message was signed, the signature or signatures were acceptable, and the signature(s) passed verification tests.’ This is the result you want to see. Everything worked perfectly.
  • Neutral = ‘The message was signed but the signature or signatures contained syntax errors or were not otherwise able to be processed.’  The message was signed, but it was not formed correctly. This is possibly a configuration error on the sending domain side.
  • Fail = ‘The message was signed and the signature or signatures were acceptable, but they failed the verification test(s).’ This means that the message had a signature, and the signature was formed correctly, but didn’t match the signature of the sending domain. This probably means the message was modified somewhere along the way.

In terms of how we get this data, this comes from our inbound email processor (which we use to process all of the emails we receive).