Created
April 6, 2016 16:56
-
-
Save wmantly/d261c73c8e3bed456ec7cf1e27c0d00d to your computer and use it in GitHub Desktop.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Good morning Richard, | |
| I'll be glad to assist you with this. An SPF record is advised when email sent from us, or any third party, are signed using a domain that is not in our possession (in our case, [email protected]). Large scale email providers, such as Gmail, Yahoo, AOL, and Outlook/Live have adopted a larger array of security measures over the past few years, including the explicit checking of whether an email used as an email's sender matches the server it was sent from. | |
| In your case, our mail server (located at 72.55.140.81) would not be a direct match with the sending domain ([email protected]) of your emails. This has the potential to raise a red flag (spam) with email providers, greatly affecting the successful delivery rate of your email. | |
| Note that SPF records do not have an effect on the sending of emails. Only the successful delivery (showing in the Inbox) of emails. | |
| In order to ensure mail being sent through your custom sender address is sent through normally, we are recommending that clients using our services create an SPF record for their domain. In most cases, the only information you require to achieve this is the IP address provided through the warning message, IP4: 72.55.140.81 | |
| The IP address listed above, and in the warning message, can be provided to your IT department for implementation. If there are any concerns, or more information is needed, please let us know and we'd be more than happy to help! | |
| Regards, | |
| Nikhil. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment