[SOLVED] Mail bouncing after server move

[blackpuma]

The weekend before last I moved my mail server (which lives in a VMware virtual machine). I've done this before with this same VM without a hitch.

Zimbra Version:

Release 6.0.8_GA_2661.RHEL5_20100820051652 CentOS5 FOSS edition.


I continued to receive logging e-mail and didn't think about the fact that no other mail has been received since.

If I send e-mail from the Zimbra web client to another account on the machine, it works fine. If I manually telnet to port 25 and do the HELO etc. by hand, it works.

If I send mail from outside of the server, e.g. gmail or Yahoo, I get the following:

This message was created automatically by mail delivery software.

A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:

foo@bar.com
retry time not reached for any host after a long failure period

(Where foo@bar.com is obviously not the actual e-mail address.)

I'm at a bit of a loss here, since I can manually telnet to port 25 and deposit mail, but everybody else is getting bounced.

Where should I be looking to diagnose the problem?

[phoenix]

The weekend before last I moved my mail server (which lives in a VMware virtual machine).

What do you mean by 'moved', what exactly did you do?

[blackpuma]

What do you mean by 'moved', what exactly did you do?

Just that, moved. The VM resided on physical hardware on the west coast, and was moved to physical hardware in the mid-west. IP address &c. changed.

It was freaking strange behaviour, but I did finally resolve the problem. It was a combination of three things. A Zimbra tweak, a misbehaving DNS server, and a bad NS record.

It just so happened that they were broken just enough to not exhibit any trouble in their old state, but as soon as the VM was moved, the problems came to the surface. After Zimbra started receiving mail on all the other domains besides the problem domain, I figured Zimbra itself was working, and started working my way down the pipeline to find the DNS trouble.