Fix mobile usability issues found on your website http://xxxxxxx.xx

ISSUE: Seems like google Webmaster tools is running a huge email blast to notify their users if a website is compatible with mobile devices, even though 98% if my websites are currently using wordpress. I  have a few sites still using the DotNetNuke CMS system. I plan to migrate them over soon here is a copy of the email that I got form them

Fix mobile usability issues found on

http://yourwebsite.com/

To: webmaster of http://yourwebsite.com/
Google systems have tested XXX pages from your site and found that 100% of them have critical mobile usability errors. The errors on these XXX pages severely affect how mobile users are able to experience your website. These pages will not be seen as mobile-friendly by Google Search, and will therefore be displayed and ranked appropriately for smartphone users.

I will update this post after my migration is complete, and see if I hit any bumps on the road my current migration would be from Managed.com (aka PowerDNN) using DotNetNuke to Godaddy.com using Wordpress.

SPF Record error when sending mail 551 5.0.0 Rejected

If you get the following error when sending a message, as a bounce back NDR notification
Remote Server returned '<mx.mail.google.com #5.0.0 smtp; 551 5.0.0 Rejected, look at http://www.openspf.org/why.html?sender=al@topel.com&ip=69.84.129.239&receiver=mailin1-trm.thomsonreuters.com>'

This means that the recipient server is doing an SPF record check and it doesn't match. 

What needs to match? 

The IP of the server you are using needs to be added to the SPF record also known as a TXT record in your DNS you can perform an SPF look-up by going to: 

http://mxtoolbox.com/SuperTool.aspx?action=spf%3a&run=networktools

Explained: 

Sender Policy Framework Why

Why did SPF cause my mail to be rejected? What is SPF? SPF is an extension to Internet e-mail. It prevents unauthorized people from forging your e-mail address (see the introduction). But for it to work, your own or your e-mail service provider's setup may need to be adjusted. Otherwise, the system may mistake you for an unauthorized sender. Note that there is no central institution that enforces SPF. If a message of yours gets blocked due to SPF, this is because (1) your domain has declared an SPF policy that forbids you to send through the mail server through which you sent the message, and (2) the recipient's mail server detected this and blocked the message. mailin1-trm.thomsonreuters.com rejected a message that claimed an envelope sender address of al@topel.com. mailin1-trm.thomsonreuters.com received a message from zixvpm03.reflexion.net (69.84.129.239) that claimed an envelope sender address of al@topel.com. The domain topel.com has not published an SPF policy. It is possible that the receiving mail server refuses all mail from domains that do not have an SPF policy. How can I reference this web page for explaining SPF results? This web page is a public service of the SPF project. SPF implementations can (and do) use it to help explain the results of SPF checks by presenting to users a parameterized link to this page. See the "Why?" page documentation for details on how this works. Edit text of this page | View other revisions Last edited 2008-04-04 13:27 (UTC) by Frank Ellermann (diff)