Mail Continually Bounces to one domain, can't figure it out, Exchange 2007 Server

We get the following NDR:

Delivery has failed to these recipients or distribution lists:

user@domain.com
Microsoft Exchange has been trying to deliver this message without success and has stopped trying. Please try sending this message again, or provide the following diagnostic text to your system administrator.

#550 4.4.7 QUEUE.Expired; message expired ##

Please help!  Which diagnostics can i use in Exchange 2007 to see where this message is stopping and what the hold up is.
LVL 1
LB1234Asked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

MesthaCommented:
The message means what it says - it has expired. Could be any number of reasons for that, the bulk of which is outside of your control.

You need to do an nslookup on the domain to get the MX records and then see if you can connect to the MX record host nme using telnet to port 25.


For example... and old lookup for microsoft.com:

C:\>nslookup
Default Server:  server.domain.co.uk
Address:  192.168.1.1

> set type=mx
> microsoft.com
Server:  server.domain.co.uk
Address:  192.168.1.1

Non-authoritative answer:

microsoft.com   MX preference = 10, mail exchanger = mailc.microsoft.com
microsoft.com   MX preference = 10, mail exchanger = maila.microsoft.com
microsoft.com   MX preference = 10, mail exchanger = mailb.microsoft.com

maila.microsoft.com     internet address = 131.107.1.7
maila.microsoft.com     internet address = 131.107.1.6
mailb.microsoft.com     internet address = 131.107.3.123
mailb.microsoft.com     internet address = 205.248.102.77
mailc.microsoft.com     internet address = 205.248.102.78
mailc.microsoft.com     internet address = 205.248.102.79
>

When you have the MX server information, see if you can telnet to port 25 of the remote server.

For example (using the above information)
telnet maila.microsoft.com 25



Simon.
0
LB1234Author Commented:
Thanks Simon, but unfortunately I got the following:

220 Postini ESMTP 260 y6_19_2c0 ready.  CA Business and Professions Code Section
 17538.45 forbids use of this system for unsolicited electronic mail advertiseme
nts.
0
LB1234Author Commented:
So apparently they're blocking us somehow by IP address?
0
Protecting & Securing Your Critical Data

Considering 93 percent of companies file for bankruptcy within 12 months of a disaster that blocked access to their data for 10 days or more, planning for the worst is just smart business. Learn how Acronis Backup integrates security at every stage

MesthaCommented:
That is just the standard Postini banner.
Did you do the test from the Exchange server?

If they were blocking your email you wouldn't get an expired message - expired means Exchange was unable to connect, not that the connection was rejected.

Simon.
0
LB1234Author Commented:
i didn't do the test from the exchange server.  will do so now.  Here is what i get:

220 ***************************************************************************************************************************************************************************************************************************************************************************************************************************************************************
0
MesthaCommented:
You have a PIX, or something like that.
Disable fixup SMTP or whatever it is called on the ASA.

Simon.
0
LB1234Author Commented:
Simon, we actually have two exchange 2007 servers (transitioning from the old box to the newer one).  The mailboxes are all on the new server, but the old server is actually the one that talks to our PIX, and routes mail for the new server.  Could this be part of the problem?
0
MesthaCommented:
As long as the server receiving the email has the hub transport role installed, then it will be fine. Exchange doesn't care which server the email is delivered to. Once it hits Exchange, Exchange deals with the delivery of the message between the servers.

Simon.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
LB1234Author Commented:
The fix for this was strange, and I'm listing it here in hopes that it helps someone else in the future.  Like I mentioned, we had two exchange 2007 servers.  On the newer of the two servers, (but not the one through which mail was making it to the outside world, this was filtered through the older E2k7 server), I had to go to Organization Configuration > Hub Transport > Global Settings > Message Delivery Tab > And here I entered in the IP address of the other E2k7 server.  Then it worked like a charm.  The text related to the IP entry was "Enter the IP addresses of internal SMTP server.  These addressed will be ignored by the Sender ID and connection Filtering:"

0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Email Protocols

From novice to tech pro — start learning today.