SMTP mail stuck in queue

[scroce]

well, after browsing millions of similar posts on this item, I'm sorry I have to bore you all with yet another.

I'm Running IIS6 on win2k3 server.

Using CDOSYS, I'm attempting to pull information off a form filled out by the user, which then gets put into SMTP mail to be sent to several email addresses, both internal and external.

My asp code works, although mail is stuck in the queue. I believe port 25 is enabled and working properly, b/c the telnet test worked.

I tested the smtp pickup folder by constructing sample SMTP mail text files in notepad (with no .txt extension), one to an internal address, and one to an external. Both end up stuck in the queue, as do messages generated by the asp page.

In event viewer, the internal mail address warning is:

"Unable to relay for user@internaladdress.org",

and for external, the warning I get is:

"The remote server did not respond to a connection attempt"


DNS seems to be working, because I am able to nslookup resolves any domain (internal and external) that I request.

We are using Exchange Server here, but one question is whether or not that affects anything - Does IIS necessarily HAVE to be configured to route mail thru exchange server in all cases? As long as the server has web access, it should be able to construct an smtp message and send it on it's own shouldn't it? maybe I'm wrong about that.

at this juncture I'm only interested in the outbound portion of the mail to work. There is no need for users to have to respond to the auto-generated mail.

Also what does "smart host" do?

I am a nobody, and nobody is perfect; therefore, I am perfect.

 

[koolage]

are you able to ping the (mail)server?

on your question:"Does IIS necessarily HAVE to be configured to route mail thru exchange server in all cases?"
answer.
NO.

I have SMTP working fine without Exchange.(on Win2k3 & IIS 6.0)

about your smart host:

The IIS SMTP service is commonly used to create a smart host, which is an SMTP server through which all outgoing messages are routed. For example, you can set up a smart host as a stand-alone SMTP server that sits between the Microsoft® Exchange server at your organization and the Internet. In this scenario, the smart host routes all e-mail from the Exchange server to the Internet and provides an added layer of protection between the Internet and the internal network.A smart host can also operate within a network.

~koolage

 

[scroce]

kool -
thanks for the reply. Part of the problem was a firewall setting - I'm not sure if the rest of the problem is still the firewall or the router, but after much noodling, I've gotten thus far:

without smarthost enabled - emails to external addresses arrive, but internal messages get stuck in queue with the "Unable to relay" error

with smarthost enabled, emails to internal addresses arrive, but external messages get stuck in queue with "the remote server...." error.

My workaround has been to use smarthost, with a dummy account in exchange which is set to automatically forward to the outside email addresses that I desire.

I don't think this is the proper way to do it, but I can't get it to work any other way. Any other thoughts?






I am a nobody, and nobody is perfect; therefore, I am perfect.