I need help getting our email sending to clients. I get the same following errors when using Outlook and the webmail app.
@centurylink.com I get
[Return Code 550] sid: WibJ1t0014dy4F201 :: SPF Hard Fail: Domain scccinspections.com does not designate 188.8.131.52 as permitted sender.
@yourfriendlybank.com I get
[Return Code 553] sid: WiaR1t0044dy4F201 :: information. (#5.7.1)
Emails to our other clients go through fine. Need this to be resolved ASAP.
You are unable to send email due to your IP not being allowed to send.
Your Current SPF record points to a non existent Domain.
scccinspections.com. 599 IN TXT "v=spf1 mx include:spf.protection.outlook.com -all"
*** Can't find spf.protection.outlook.com: No answer
That link shows the IP Listed in the error message is not allowed to send Email. SPF records were created to help fight spam. The Sender Policy Framework specifies which IP's are allowed to send email for the domain.
You will need to change your SPF record from
v=spf1 mx include:spf.protection.outlook.com -all
v=spf1 ip4:184.108.40.206 -all"
If you have more than one email server sending email on behalf of your domain you will need to make sure all of the Servers are allowed in the SPF Record.
Here's some helpful links for managing SPF Records for a domain.
I'm really hating MS Exchange b/c of this. You guys sold me on it and I knew better than to relent to the MS BS. Their stuff just sucks, takes 47 steps to do anything when Apple only takes three. UNHAPPY.
For Medi1, based on your domain's MX Records, it looks like you're using our Workspace Email accounts. For that type of account, you should have the following value for your SPF record:
v=spf1 mx include:secureserver.net -all
For Randy, it sounds like you're using Office 365. In that case, you'll want to make sure you have the SPF record:
v=spf1 include:spf.protection.outlook.com -all
If that doesn't help, then posting the full error message you're receiving may help.
@randy Sorry. I've never seen that before. If you provide a screen shot of what you're seeing, that may help. Otherwise, I'd highly suggest getting in touch with our support team so they can take a closer look into what's happening.