Can't receive mail

[mquinn0908]

We are in the process of setting up an new exchange 2000 server. Exchange is installed and I am able to create mailboxes for users and once I set up their mailbox I went into outlook on the client and set up their account there. My problem is that I am able to send messages but the person that it is sent to never receives them (they just sit on our server) and our clients can not receive any messages at all. When I go into exchange system manager I can see that the user was able to logon to their mailbox and at what time and I can also see how many items are in their mailbox but they are still unable to receive them. What am I missing?

 

[mquinn0908]

one more thing, when someone tries to send a message to one of our users they get it bounced back to them and it says:

209.92.33.155 does not like recipient.
Remote host said: 501 This system is not configured to relay mail from
<their server> to <ours> for 216.136.226.158
Giving up on 209.92.33.155.

 

[vz1518]

I am getting the same problem with Exchange Enterprise 2000. Users can send messages and it gets delivered to the whomever it is sent to but the replies is not comming in.

 

[Marcs41]

is 209.92.33.155 your server?
If the answer is here, mark it, others can benefit from it too.
Free Tip: The F1 Key does NOT destroy your PC!

 

[mquinn0908]

209.92.33.155 is not our server. We use our dns for internal dns and BellSouth for our external name resolution. How do you go about settting up dns on the exchange server to send and receive mail when you have an ISP hosting your dns externally?

 

[Marcs41]

Where or how your DNS is configured does not really matter here.
That 209.92.33.155 is being used to send your mail, but does not like it, because of relay. Is that 209.92.33.155 BellSouth's mail-relay? Or what is it?
You have to either send mail yourself to destinee (use DNS), or use your ISP's relay server. If the answer is here, mark it, others can benefit from it too.
Free Tip: The F1 Key does NOT destroy your PC!

 

[mquinn0908]

this message of 209.92.333.155 is actually comming from someone trying to send a message to one of our users from another isp (yahoo).

when we try to send mail out from our server I get the following message:
A configuration error in the e-mail system caused the message to bounce between two servers or to be forwarded between two recipients. Contact your administrator.

 

[Marcs41]

Ok, I'm a little lost.
You are mixing up things.
1 Step at the time:

1: Can you send message to the internet?
2: Can you receive mail from the internet.

Test this YOURSELF, with a hotmail account or so, do NOT test this with received yahoo mail (could be spam and bounce). If the answer is here, mark it, others can benefit from it too.
Free Tip: The F1 Key does NOT destroy your PC!

 

[mquinn0908]

1. I can send messages to the internet.
2. I can not receive mail from the internet.

 

[Marcs41]

ok, next.
How do you (or are supposed to) receive them?
What is your config? Pushed to port 25 or do you retrieve them (POP3?) ? If the answer is here, mark it, others can benefit from it too.
Free Tip: The F1 Key does NOT destroy your PC!

 

[mquinn0908]

port 25.

One more thing, I am unable to send internally to those in our domain either. When I send to one of our users from another internal client I never get an error message or a bounce back. I can go into the exchange manager and look at the users mailbox and see the messages sitting there and a log on and log off time.

 

[mquinn0908]

Ok here is where we are now.

We have BellSouth for external DNS and they have added an MX record for our domain and now we don't get the message about the system not being configured to relay mail. However, we are still unable to receive mail. I can send mail with no problems and when the person tries to reply to the message they received they never get a bounced message back (like before). What am I missing that will all us to receive mail?

 

[Marcs41]

Hang on there, if the MX record was just added, you need to wait at least 24 hours to make sure all DNS servers are updatet. Test again after that period. If the answer is here, mark it, others can benefit from it too.
Free Tip: The F1 Key does NOT destroy your PC!

 

[mquinn0908]

I will check it sometime tomorrow to see if it is working or not.

Is there anything that I need to add on our DNS or anything else on our side?

 

[Marcs41]

Normally not. If the answer is here, mark it, others can benefit from it too.
Free Tip: The F1 Key does NOT destroy your PC!

 

[mquinn0908]

One more quick thing, our exchange server only has an address on our internal network. Does our server need an address externally as well?

This is our setup:
Our ISP gave us a static IP address for our router which that is IP address that they have our domain name pointed to in their DNS and then the MX record points to our domain name. Is this the correct setup?

 

[Marcs41]

You need a public adress somewhere, and it is the MX Records address that matters, that is the address mail wil be sent to, to port 25.
If your server is behind a router or firewall, forward port 25 to the exchange server. If the answer is here, mark it, others can benefit from it too.
Free Tip: The F1 Key does NOT destroy your PC!

 

[mquinn0908]

Our public address is the router which is what the mx record is pointing to.

What about the internal mail that is oun the server? Why isn't that being delivered?

 

[Marcs41]

Does the router let pass or forward port 25 to the exchange server? If not, make it so. If the answer is here, mark it, others can benefit from it too.
Free Tip: The F1 Key does NOT destroy your PC!

 

[mquinn0908]

I am doing that now. I have forwared port 25 to the exchange server but when I try to telnet to that port on the router it fails.