Cannot send email but can receive

[valicon]

I have Exchange 2000 on a W2k advanced server with AD. Dns is also on the same server with forwarding enabled using the DNS servers of my ISP. I have also added the same DNS servers into System Manager. My MX records are fine. I am receiving mail. However when I send email through Outlook it goes and you can see it leave the outbox, then when I look in the queue in System Manager the email is there and it says the domainname.com (remote delivery) and shows as active. Any one know whats wrong?

 

[valicon]

Update: I have changed the DNS servers and still the same issue. Anyone know how to fix this or what can be wrong?

 

[Marcs41]

Switch your deliver using your ISP as Smart Host (look in the Help how to do that).
It may be the ISP does not let you send directly for some reason.
You can switch back if you want afterwards.

How to Set a Smart Host:
In Exchange System Manager, click the virtual server that you want to configure.
On the Action menu, click Properties.
Click the Delivery tab, and then click Advanced.
In the Advanced Delivery dialog box, type a host name or IP address (type the IP address in square brackets []) for the smart host.
Click to select the Attempt direct delivery before sending to smart host check box if you want the virtual server to attempt to deliver messages to the destination before the virtual server sends messages to the smart host.
Click OK, and then click OK again to close the virtual server properties.

See also:

http://support.microsoft.com/default.aspx?scid=kb;EN-US;266686

Marc
_{If 'something' 'somewhere' gives 'some' error, expect random guesses or no replies at all. Please specify details.
Free Tip: The F1 Key does NOT destroy your PC!}

 

[valicon]

Okay I made that change but the email still goes into the queue and sits there, the server says (retry) but nothing. I cant seem to figure out whats wrong....any other suggestions, what could it be?

 

[2cornot2c]

Are you only having this problem sending to all domains or a particular one? How long has this Exchange server been up and running. We had this problem several months ago when me switched from a POP3 server to Exchange. We spent 16 hours troubleshooting the problem and the entire time it was not even our problem. It turns out that our ISP forgot to update their DNS. Resulting in use being able to send but not receive.

Check with your ISP if they have updated all of their records.

 

[Marcs41]

The connection settings can be tested with Outlook Express or whatever client. Use the same settings you filled in on the server. If you cannot send, the messages are easier to read.

Marc
_{If 'something' 'somewhere' gives 'some' error, expect random guesses or no replies at all. Please specify details.
Free Tip: The F1 Key does NOT destroy your PC!}

 

[valicon]

okay...still the same problem. I did telnet into port 25 and tried to send email that way to test but I get:

550 5.7.1 Unable to relay for cageek@hotmail.com

Anyone know how to resolve this? I am new to Exchange. Thanks.

 

[Marcs41]

A Telnet? From where to where?


Marc
_{If 'something' 'somewhere' gives 'some' error, expect random guesses or no replies at all. Please specify details.
Free Tip: The F1 Key does NOT destroy your PC!}

 

[valicon]

from a server in NY to the server in Florida, I did it this way so it is outside the network

 

[Marcs41]

Ok, now you are confusing things.
The Telnet you did is to test INCOMING mail.
You stated you cannot SEND mail.
Which one is it now?

Marc
_{If 'something' 'somewhere' gives 'some' error, expect random guesses or no replies at all. Please specify details.
Free Tip: The F1 Key does NOT destroy your PC!}

 

[valicon]

no, I telnetted into port 25 and tried to send mail from the exchange server and I received the error above. As far as receiving mail its no problem.

 

[Marcs41]

That is not sending, that is relaying you are testing.
Which did not work, and it is good it does not or you would be open for relay abuse.

Can you send from your LAN to the outside or not?

Marc
_{If 'something' 'somewhere' gives 'some' error, expect random guesses or no replies at all. Please specify details.
Free Tip: The F1 Key does NOT destroy your PC!}

 

[valicon]

nope, it still hits the queue and sits there

 

[Marcs41]

ok. Forget the Telnet, that has nothing to do with this.
Did you do the test with Outlook (Express) or so as asked before?

The connection settings can be tested with Outlook Express or whatever client. Use the same settings you filled in on the server. If you cannot send, the messages are easier to read.

What does that say?

 

[valicon]

yes and it connects fine, Outlook can send and receive with no errors. It is when the email gets to the server it is then queued.

 

[Marcs41]

You will need to double-check your smtp settings then.

http://support.microsoft.com/default.aspx?kbid=265293

Marc
_{If 'something' 'somewhere' gives 'some' error, expect random guesses or no replies at all. Please specify details.
Free Tip: The F1 Key does NOT destroy your PC!}

 

[jbud]

As I understand your situation, on your Exchange server, all the outbound mail ends up sitting in queues. When you look at the status of the queue on its property pages, it says "Retry". It seems that you have taken the advice above to configure Smarthosts.

So, the question is, why can't the Exchange server connect to outside SMTP servers that are your Smarthosts?

Can you get a terminal services or console session on this server? Can you open a command prompt? If you can, try telneting from the Exchange server to port 25 on one of the smart hosts. You may want to try this using both fqdn and ip addresses, in order to test name resolution. Can you get an SMTP banner response? If you can't, perhaps there's a firewall in the way.