Question Locked

Reports of "SMTP Connection Failed" for outsiders emailing to my Exchange

0 helpful
7 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have an Exchange 2003 server that has worked more or less perfectly for literally years.

This week, someone told me a contact they had outside of my company could not email any users at my company. I confirmed this, they are receiving an undeliverable notification of "SMTP Connection Failed."

I have a Barracuda Spam Filter in place, and it has not filtered (or even seen) any recent emails from the user/domain in question. They were able to email my organization about a month ago, but sometime since then they have been receiving this message. The message is obviously generated from their Exchange server, since it never contacts my Exchange Server. This message occurs to both "new" messages and replies to a message from my domain.

What can I look into to double check that it is not something in my configuration?

EDIT: Any other domain I can get a test from seems fine. I'm almost sure it's a problem on their end. Any advice I could forward on to their IT dept?
Thanks in Advance!

7 replies

by robo_dev

if their server is not registered with DNS, your server will do a DNS lookup on their server...it will fail, and all mail will be rejected from them.

The receiving server will get the host name of the sending e-mail server from the SMTP HELO command, perform a simple DNS query (forward DNS lookup) and verify that the IP address is indeed the IP address of the incoming connection. If the resulting IP address does not match the incoming connection IP address (sender's IP address), e-mail is rejected.

by angry_monkey_show

Their DNS entry appears to working (as does my own). Pinging their mail.(domain).com returns a reply from their mail server. I can then open a telnet connection to that address.
Pinging my own mail.(domain).com from an outside source returns the correct IP address.

One thing I noticed, is that in the earlier emails as they passed my spam firewall, it was "received from" an IP ending in 150. When I ping their mailserver, it returns an IP ending in .154. I can telnet 154, but not 150. Could they have changed their IP address and lost some configuration somewhere in the process?

by robo_dev

It's also possible that the other site has:

Missing Reverse DNS record for MX records. It is required by RFC 1912 that you have reverse DNS (PTR) records for all of your mail servers. If you do not have reverse DNS entries, your email may not arrive some of the strict mail servers (e.g. your Barracuda)

send a reverse DNS query to them from
http://www.dnswatch.info/

e.g. 150.x.x.x

Missing SPF record. Many mail servers refuse to accept emails from an IP address without SPF record. Mail servers use SPF record to help prevent spammers from abusing their system.

http://en.wikipedia.org/wiki/Sender_Policy_Framework

by angry_monkey_show

robo_dev seems to have nailed it. The Barracuda by default DOES require a fully qualified domain name. Also, reverse DNS lookups on their IP range fail from several online tools.

So for now, I have turned off the Fully Qualified Domain setting on the barracuda, as well as allowed messages "from senders whose Domain is not in DNS"

I'm waiting to see if that temporarily cures the issue while their IT team hammers out the DNS problems.
I would like to re-enable these settings on my Barracuda.

Again, Thanks to everyone who answered!!

by robo_dev

you would be amazed at how much spoofed mail you may get.

by angry_monkey_show

Is there a free alternative to DNSstuff.com? Looking at their sample, I like it giving a report of exactly what could be wrong with your DNS setup, but I don't want to spend any $$ :)

This discussion is closed to new replies.