[Webinar] Streamline your web hosting managementRegister Today

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 299
  • Last Modified:

Can't send mail to a server with a bad MX record

CompanyA running Exchange Server 2000 and attempting to send mail but getting delivery failures to CompanyB which has two MX records:

mail1.companyb.com, preference 5
mail2.companyb.com, preference 10

If I telnet to port 25 of mail1.companyb.com, it responds with:
550 Requested action not taken: mailbox unavailable
Then it drops the connection.

CompanyA's Exchange server never attempts to go to mail2.companyb.com to deliver mail.  Instead, it just issues all users at CompanyA a delay, and then eventually a failure.  

I have other clients running Exchange 2003 server, and they can deliver mail to CompanyB.  Is there a setting on the Exchange 2000 server?
0
jasonkthomas
Asked:
jasonkthomas
1 Solution
 
SembeeCommented:
The remote server isn't sending back a failure message that the Exchange server recognises, or something is stopping it from being received correctly.
Exchange doesn't know that the message has a fatal failure, and therefore continues to try the primary MX record.
There is no setting to change in Exchange, because Exchange is doing what it is designed to do.

What do you have between the server and the internet? A firewall of some kind? Does it have SMTP scanning capabilities?
Anything else that could be interfering with SMTP traffic? Antivirus, Antispam etc?

Simon.
0

Featured Post

Get expert help—faster!

Need expert help—fast? Use the Help Bell for personalized assistance getting answers to your important questions.

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