How to tell if Exchange Server 2007 is checking the SPF record

A sender is trying to reach my client. The sender gets a "delivery has been delayed" bounce, and the email never arrives.

The only shortcoming I can find on both the sender's and the recipient's mail servers (according to Microsoft's test wizard) is that the sender's domain has no SPF record.

How can I tell if the recipient's Exchange Server 2007 is not allowing the email to deliver because of lack of SPF record?

Thanks.
Dave
LVL 1
DaveWWWAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

DrDave242Commented:
Do you have an Edge Transport server? If so, it is likely checking the sender's SPF record, as Sender ID checking is enabled by default on Edge Transport servers. However, it is not enabled by default on Hub Transport servers, so if you have no Edge Transport server in your environment (which is the case if you only have a single Exchange server), there's a good chance you're not checking SPF records.

See this article for general information on Sender ID in Exchange 2007, and this article for information on enabling Sender ID checking on a Hub Transport server.
0
NetoMeter ScreencastsCommented:
I don't believe that the lack of an SPF record is the reason for this problem.

Actually, if the "delivery has been delayed" message is sent from the remote sender's domain postmaster - ex. "postmaster@remotesenderdomain.com", then it is quite possible the message is stuck in the queue of the remote email server. Checking the queue or using message tracking will show where exactly the message gets stuck.
0
DaveWWWAuthor Commented:
Thanks, and yes, I had checked the recipient's Exchange Server logs, and there are no search results for the senders domain at all anywhere that I can see.  I'll send a message to the sender's IT folks.
0
Hey MSSPs! What's your total cost of ownership?

WEBINAR: Managed security service providers often deploy & manage products from a variety of solution vendors. But is this really the best approach when it comes to saving time AND money? Join us on Aug. 15th to learn how you can improve your total cost of ownership today!

santhoshuCommented:
Hello there,

Can you let us know from which domain is the Delay Notification Email generated?

From: postmaster@xxx.com

If you notice the Delay Notification Email was generated on your organization server, this means the email has reached your server but delay delivering to another Servers.
 
In that case, we firstly need to check the email stuck on which server (which server generates the Delay  message).
 
Then, calculate the mail route and get the next hop server.
 
At last, check why there is an delay to send to the next hop server:
 
1.    Check DNS setting
2.    Ping the next hop server from the server which the email stuck on.
3.    Telnet to the next hop server from the server which the email stuck on and attempt send an email manually
4.    Check the SMTP log on the server which the email stuck on for more information
0
Alan HardistyCo-OwnerCommented:
It is very unlikely that a lack of SPF would cause message-flow problems.  An incorrect SPF record might, but not a lack of.  More likely is a lack of Reverse DNS record (PTR).

Can the sender test the connection using telnet to see if there are any tell-tale messages from the Exchange 2007 server as that usually can help identify the problem very quickly.

https://support.microsoft.com/en-us/kb/153119

Example:
Telnet mail.exchange2007serverdomain.com 25
ehlo sendingdomain.com
mail from: sender@senderdomain.com
rcpt to: recipient@exchange2007domain.com

Then see if they get an error message and ask them what it is.

Alan
0
Will SzymkowskiSenior Solution ArchitectCommented:
I would also agree with Alan that it is likely a Reverse PTR record casuing the issue. Reverse Record is a minimum requirement for sending email over the internet. If you do not have this set properly you will get flagged as a spammer very quickly.

Reverse Record needs to be setup by the ISP of the domain hosting Exchange.

Will.
0
DaveWWWAuthor Commented:
Sorry, I am going to have to abandon this question, as it is very stale, and the problem has not recurred.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
DaveWWWAuthor Commented:
Question is completely stale now, and the problem did not recur.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.