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)

Finally Google Chrome Resolving Host issue resolved!!!

I came across this issue a few weeks ago, were Google Chrome just sits on "Resolving Host" I would see this at the bottom left hand corner, for over 20 seconds sometimes even minutes. I tried everything to Resolve this issue, here is a list of all the things I tried:

1. Change DNS settings to Google 8.8.8.8 secondary  8.8.4.4
2. Tried changing DNS to Comcast (my local ISP) 75.75.75.75 secondary 75.75.76.76
3. Ran AVG Virus scan and Optimization
4. Ran Norton Virus scan and Network Check
5. Tried diffrent Internet Connections Timewarner, and Comcast 
6. MalwareBytes Scan
7. Uninstalled many applications that I thought my interfere with my connection
8. Reset the default settings in Google Chrome
9. Checked the Proxy settings in Chrome and tried several configurations 

Solution: 
None of this worked Here is the only thing that seems to fix it after several frustration hours trying to get this to work. I decided to set a Static IP instead of a dynamic IP inside my connection settings. After doing this my browser went back to Normal or maybe even faster its extremely fast!!! I'm running on a T1 line, Windows 7 with 8GB of RAM I didn't see this type of solution anywhere online so I hope it helps anyone having this issue. 

Overall I don't know exactly what caused the issue, but setting a STATIC IP was the only fix that did the trick.