URGENT : Mail delivery issues, please help

Whew... after all of this, it is still not doing right. Please, any more thoughts??? Anyone???
 
John... I REALLY want you to be able to do this... but I don't think you will be able to get in via SSH. I will use the form to give you the info and maybe you will have better luck than I have getting in remotely. Thank you SO much for your assistance.
 
so far it looks like it *might* be a networking issue. Note how ssh isn't accessible? Well, if we can't get in, the a remote dns query wouldn't be able to get out. Ssh was up at one point, I was able to login, but I just tried again and it's down.

John
 
Whew... I don't think it is hardware... because even when the mail doesn't go out, the websites are displayed properly... MySql seems to be working fine too. This just seems to be an issue with how mail is resolving on the outgoing side.

Now to add to the oddity, over night several messages have gone through the queue and delivered... but I still cannot access the box via SSH (connection refused). This box sits in an office a few miles from here (not behind a hardware firewall) and is connected through a fiber connection. It shouldn't be bottle-necking at all. I have used a simple KISS script to manipulate the iptables. The error seems to have happened after a DA update around two weeks ago... BUT I cannot be sure on some of the issues because I hadn't been into the box via SSH for several weeks. BUT the email delivery is definitely something that has only been happening for a short time.

I have even setup OPENdns servers for the nameservers and tried that but it didn't seem to make a difference. At first I thought my ISP may have had DNS issues upstream... which they deny. So, I have put things back to the way they were using the native servers they gave me because at least some mail seems to make it's way through.
 
Last edited:
Pretty sure this is it. Your server IP is 72.4.44.7, correct? Nothing was working... I went through all service ports to check... port 80 was open. I decided to poke at it, and found this:
Code: 
[root@server]# telnet 72.4.44.7 80
Trying 72.4.44.7...
Connected to 72.4.44.7.
Escape character is '^]'.
HEAD / HTTP/1.1
Host: asdf

HTTP/1.1 200 OK
Date: Sat, 27 Oct 2007 20:24:06 GMT
Server: Apache/2.2.4 (Win32) PHP/5.2.3
X-Powered-By: PHP/5.2.3
Set-Cookie: b49e8b227f0be477e5a89ecf6474076f=-; path=/
Expires: Mon, 26 Jul 1997 05:00:00 GMT
Last-Modified: Sat, 27 Oct 2007 20:24:07 GMT
Cache-Control: no-store, no-cache, must-revalidate
Cache-Control: post-check=0, pre-check=0
Pragma: no-cache
Content-Type: text/html
Can you spot the problem?
Server: Apache/2.2.4 (Win32) PHP/5.2.3
;) A windows box has hijacked your server IP address. Happens if 2 servers on the same subnet decide they want the IP. The last server to ask for it gets it. Contact your datacenter to see who actually owns the IP address.

John
 
Hmmm..... this is in an office with multiple servers... however, the windows boxes are supposed to be on a separate group of IPs. BUT at times some of my cohorts may be doing testing on things that I may not be aware of. If this is all something they created, I will tell you after I beat them to a pulp.

:)
 
woow, i wouldn't even think the machine could be connecting through the internet using an allready used ip... seems they leas each other out... sollution is quite simple :) check the winbox for errors, and change ip ;)
 
Ok People... if you have been following this thread, here is a VALUABLE life lesson. The short answer is just as John at DA discovered. My server had been the victim of an LAN IP conflict. I will explain the situation a bit more below just so people who read this later can have a better picture of the circumstances:

1. This server is in a mixed office / computing environment... both Windows Servers and Linux and Windows XP Pro w/ virtual server & Linux.

2. There is a dual port fiber connection from a common ISP... with plenty of speed.

3. There are several shared IP addresses... some go to my box and some to the LAN.

4. My box started having all of these oddities and we did all of the troubleshooting you see in this thread.

5. I had asked the service manager of the office ( a small regional IT company) if "ANYTHING" had changed in the server room... he said no.

6. I went on "blind faith" that nothing had changed.

7. A technician in the office changed an IP address in the setup to point to a Joomla test server that is used for development... and, you guessed it, he stole MY main server IP address. The service manager didn't know.

8. Once we put the settings back to the way they should be and the DNS propagated globally, the problems went away... amazing isn't it.

LIFE LESSON... always, always check the obvious things first.

I want to thank everyone who made suggestions to assist... specifically Jeff and most especially John at DA Suppport for going beyond the call. It means a lot guys... that is why I stick with DirectAdmin.

Randy Nicholas in Tennessee
 
Glad you figured it all out, great idea to check telnet headers too... I didn't think of that, and now i will ;)

great to have you back up and running :)
 
You must log in or register to reply here.
Back
Top