• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 466
  • Last Modified:

exchange 2003 inbound email

I am unable to recieve email in exchange 2003 server. My domain is puroflux.com. Mail server is mail.puroflux.com. Why is the mail connection timing out when sending to this domain?
1 Solution
Perhaps port 25 is being blocked at the firewall.
What Are the Minimum Requirements for Inbound Mail Flow?
 • Exchange Server must have access to the Internet on port 25. This access should not be blocked by firewalls or other network settings. Anonymous connections should be allowed.

• The Exchange Server SMTP virtual server should be configured to use the default settings. For more information about configuring the Exchange Server SMTP virtual server, see Article 266686: How to Configure a SMTP Virtual Server, Part 1 in the Knowledge Base.

• The public mail exchanger (MX) resource record configured on your public DNS service should be accessible to all other Internet domains. The MX record should point to the Exchange server and must be identified before messages can be sent or received.

• Recipient policies must be configured and applied correctly. Recipient policies will stamp the SMTP virtual server and the recipient's mailbox with the correct e-mail address.

Check the result n let me know

Sorry, I should have been more explicit before posting the comment about the firewall. I had already checked the MX record and then tried telnet to that IP address. It failed to get a response so that suggests the firewall is either blocking port 25 or not forwarding it to the right server. There might be other problems as detailed above, but you need to check the firewall first.
Get your Disaster Recovery as a Service basics

Disaster Recovery as a Service is one go-to solution that revolutionizes DR planning. Implementing DRaaS could be an efficient process, easily accessible to non-DR experts. Learn about monitoring, testing, executing failovers and failbacks to ensure a "healthy" DR environment.

follow the following article to test smtp using telnet, you should try to connect it from any system with in your local lan if it succeeds then you should check that your smtp is listening on both ip's if it is directly connected to the internet or check your firewall configuration, router etc. but first check it from local network to be sure smtp is working on standard port 25. (use internal ip instead of external to check it locally then use external to check both sides)

One other thing to check is antivirus applications, macaffe virus scan 8 blocks port 25 by default.
Everything passes on the DNS report.

The only thing it fails on is what your server is announcing itself as.

Therefore considering the age of the question, I am wondering if you had only recently made the DNS changes and not allowed them to propagate round - which takes 48 hours.


Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now