Outlook undeliverable code #554 5.7.1 failed SPF

Your message wasn't delivered due to a permission or security issue - Resolution with screenshots

Outlook undeliverable code #554 5.7.1 failed SPF - Resolution with screenshots

Situation: We are running Exchange 2010. Last night we upgraded the router firmware. Reboot both Exchange mail server and router. After that, some users receive Undeliverable message with this error: “Your message wasn't delivered due to a permission or security issue. It may have been rejected by a moderator, the address may only accept e-mail from certain senders, or another restriction may be preventing delivery”. Only a few users receive this message. DNS lookup and MX record looks good. What could be the problem?

Here is the original message:

mail.mvps.org rejected your message to the following e-mail addresses:

'username@mvps.org' (username@mvps.org) <mailto:username@mvps.org>

mail.mvps.org gave this error:

failed SPF: (ref: msg-33809-06647 43C0FC5C)

Your message wasn't delivered due to a permission or security issue. It may have been rejected by a moderator, the address may only accept e-mail from certain senders, or another restriction may be preventing delivery.

Diagnostic information for administrators:

Generating server: EXCH-CAS01.chicagotech.net

username@mvps.org

mail.mvps.org #554 5.7.1 failed SPF: (ref: msg-33809-06647 43C0FC5C) ##

Original message headers:

Received: from EXCH-MAIL01.chicagotech.net ([fe80::b950:3c18:43b5:7048]) by

EXCH-CAS01.chicagotech.net ([fe80::30da:44dd:6d90:469d%15]) with mapi id

14.01.0218.012; Thu, 9 May 2013 16:06:52 -0500

From: Bob <Username@chicagotech.net>

To: "'username@mvps.org'" <username@mvps.org>

Subject: test 1

Thread-Topic: test 1

Thread-Index: Ac5M+R+nBr7OWIrqSb24GOHRtlbeKg==

Date: Thu, 9 May 2013 21:06:52 +0000

Message-ID: <1B3D217B49865E43BEB0C617B572A0C3366768E1@EXCH-MAIL01.chicagotech.net>

Accept-Language: en-US

Content-Language: en-US

X-MS-Has-Attach:

X-MS-TNEF-Correlator:

x-originating-ip: [10.0.6.50]

Content-Type: multipart/alternative;

boundary="_000_1B3D217B49865E43BEB0C617B572A0C3366768E1EXCHMAIL01chica_"

MIME-Version: 1.0

Troubleshooting: Finally, we found the problem is we change our DNS record recently. That causes the problem. We are planning to move to Office 365. To test it, we cerate TXT value on our DNS manager. The value is v=spf1 include: spf.protection.outlook.com -all.

After we remove the TXT Value, the email goes through.

Contact a consultant