I have a client that recently changed their Internet provider and thus obtained a new Public Static IP address for their router. This of course means that the mail coming from the mail server will be send using this new address. The client has Exchange 2003 for their mail server and ever since the change in Static IP we have been getting quite a few "Message has been delayed" errors coming back when users attempt to email familiar domains that they had emailed regularly prior to the change. I have verified that the PTR records are all set correctly and we don't have any problems emailing the big boys such as AOL.com or Gmail.com, it's only the more private domains associated with their client domains that seem to be a problem. They rarely even get an NDR related to this problem, the emails just seem to never go through after retrying several times. I want to know if there is a test I can do on our server to verify if the issue is indeed something that needs to be fixed on our end or if it is possibly an issue on the recievers end. It doesn't seem like it could be on their end since we were the one that made the changes. Is there a way for me to do a manual email send test from our mail server so that we can determine what the problem might be in recieving mail from our server? The biggest problem with this issue is the lack of any errors to follow up on. I have looked in the Error logs and can't find anything to tell me why these messages are being delayed and eventually not delivered. I would assume that if the reciever is rejecting our messages that there sould be an error someplace to look at and be able to understand why it's happening. Any help would be greatly appreciated.

It would appear from the symptoms that their IP address is blacklisted. Perhaps if, from your client's Exchange server, you try to send a message manually by doing a telnet to port 25, you might get a clue what's going on. For example: Telnet mail.targetdomain.com 25 helo you.ourxchange.com mail from:you@ourxchange.com rcpt to:them@targetdomain.com data <?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" /><o:p> </o:p> This is a test. . quit Yes, that's a blank line after the "data". -- Ed Crowley MVP "There are seldom good technological solutions to behavioral problems." . "Rickdvr2002" wrote in message news:6deac093-8e55-40c5-b65e-29eadd0baaeb... I have a client that recently changed their Internet provider and thus obtained a new Public Static IP address for their router. This of course means that the mail coming from the mail server will be send using this new address. The client has Exchange 2003 for their mail server and ever since the change in Static IP we have been getting quite a few "Message has been delayed" errors coming back when users attempt to email familiar domains that they had emailed regularly prior to the change. I have verified that the PTR records are all set correctly and we don't have any problems emailing the big boys such as AOL.com or Gmail.com, it's only the more private domains associated with their client domains that seem to be a problem. They rarely even get an NDR related to this problem, the emails just seem to never go through after retrying several times. I want to know if there is a test I can do on our server to verify if the issue is indeed something that needs to be fixed on our end or if it is possibly an issue on the recievers end. It doesn't seem like it could be on their end since we were the one that made the changes. Is there a way for me to do a manual email send test from our mail server so that we can determine what the problem might be in recieving mail from our server? The biggest problem with this issue is the lack of any errors to follow up on. I have looked in the Error logs and can't find anything to tell me why these messages are being delayed and eventually not delivered. I would assume that if the reciever is rejecting our messages that there sould be an error someplace to look at and be able to understand why it's happening. Any help would be greatly appreciated.Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Hi You can use www.mxtoolbox.com to check your IPs if they are blacklisted Give us some feedback when it's doneJonas Andersson MCTS: Microsoft Exchange Server 2007/2010 | MCITP: EMA 2007/2010 | MCSE/MCSA Blog: http://www.testlabs.se/blog