Messages not being to delivered to certain domains

[hbgpensfan]

We have a brand new exchange server that recently has been put online. Email works to a majority of domains, however there are 15-20 that we do not get through to. What happens is when we send mail, we first get a message from the postmaster saying that delivery has been delayed. Then after about 48 hours we get a message stating that it could not be delivered. I've look over our settings and I don't see anything that should be blocking out these domains. I'm having trouble finding any information on what to do or check. Any help would be appreciated.

Thanks-
Bill Swanson, MCP

 

[hbgpensfan]

I'm going to see if I'm up to date. I know I am as far as service packs but I need to look on their site.

One question about setting up the connectors, you created one connector for every IP address? I think I would have close to 11 then.

Thanks for the tips.

 

[brontosaurus]

By the way, since my last post, GHF.ORG has corrected their MX entry, so you should find it easier to reach them now.

 

[hbgpensfan]

Yeah, thanks I actually called and let them know now it works fine. Could you look at these two though, I can't see anything wrong with them.

ugi.com
deringconsulting.com

I use a website

http://www.checkdns.net

and I don't see anything wrong with these.

Thanks though, it was very nice to tell the people at ghf.org that it wasn't my problem. They've been all over us for about a month.

 

[brontosaurus]

Both have correct DNS entries. Couple of things to note though...both only have ONE mail exchanger, so if that server is down for any reason, you may experience delivery delays on your side as opposed to the mail being delivered and queueing on their secondary mail exchanger. The other thing is (and this may be my network, but i doubt it), it took about 30 seconds to open a Telnet session to port 25 for deringconsulting. Your server may get annoyed with that...

 

[Silv3rfish]

No their DNS isnt correct. Both of their MX records point to a CNAME record (alias) of another machine. MX records must point to an A record.
ie deringconsulting.com, their MX points to mail.itech.net, which is a CNAME for mustang.itech.net.

What they should have is an A record that just points to the same IP.

By the way, yes I made a connector for each domain that our mail didn't go to (only 6 here), but haven't had to put one in for about a year now, which is why I wonder if it has been patched.

-- silverfish.

 

[brontosaurus]

You are absolutely correct Silverfish, I need to put on my glasses. Sorry about that.

 

[hbgpensfan]

Okay, I'm losing it now. Where can I see what service pack I'm running on Exchange 2000?

Thanks for everything you two.

 

[hbgpensfan]

Ok so I forgot you could tell by build number. I had SP2 installed originally before we rolled it out, however I wiped out the server because we were having troubles with the Exchange Agent of Arcserve. I installed SP2 and it appears that does fix most of the problems. The messages are no longer getting stuck in the categorizer. Thank you for all your help.