Sending SMTP mail via IIS

[scroce]

I am under the impression that you do not need to have a full blown email server (exchange or otherwise) to send a simple SMTP mail message through the internet from a scripted page such as ASP - as long as your default SMTP virtual server is configured in IIS

is this right?

The reason I ask, is that I have a simple asp form that I want to send a simple email alert to someone when it is submitted. I am not even requiring a place to receive responses

My company uses MS exchange 2003 server with Outlook, but do I necessarily have to go thru exchange to send this simple notification?

thanks.

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

 

[dennisbbb]

You don't even need SMTP server at all if all you do is send. The SMTP server is only meant to listen in on port 25 of a telnet session.

On your asp form, simply have it send to whereever you want it, your DNS servers will resolve the destination and the receiving server will route your mail to the proper recipient.

 

[scroce]

Thanks dennis - now that that is confirmed, I can reasonably assume that our exchange server is not fouling up the works - the next level of the issue is this:

I must have something in IIS SMTP configured incorrectly, b/c although my mail message gets generated, it doesn't get sent out. It just hangs out in the c:/inetpub/queue folder.

The event log shows one of two errors - if the email generated is internal to where the web server is located, I get "Unable to relay for name@internaldomain.com"

If it's external, I get "The remote server did not respond to a connection attempt"

thru reading the many posts on this topic, I am going to try
going to the Access Tab under properties of the SMTP virtual server and grant access to 127.0.0.1

this is the only thing I can think of, since I believe the rest of my IIS is configured correctly.

Any other suggestions?

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

 

[dennisbbb]

If you are using IIS SMTP to help you relay mail, then go to IIS and open up the properties of your SMTP virtual server, then go to the Access tab, click open "Relay" and configure accordingly.

 

[scroce]

OK - will try that and post back. Thanks

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

 

[scroce]

well, I did the above, and it still isn't working ARRRRGH!! I'm still getting the same two errors respectively with the internal and external email address domains, and in addition, I am now getting another warning in the event viewer that says:

"Unable to deliver the message because the destination address was misconfigured as a mail loop"


help!

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

 

[scroce]

OK - some good news - thru changing some firewall settings, SMTP mail is getting thru to external email addresses.

Internal mail doesn't seem to get routed however. It's still hanging out in the queue.

I've been hunting for more firewall settings, but haven't been able to find one that looks like it applies.

What other reasons could there be for mail on the internal domain getting stuck?

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

 

[scroce]

let me add a clarification to my last post -

the external domain emails get sent OK

the internal domain emails go to queue, stay there for a minute or so (as I believe is set up is IIS), and then end up in the badmail folder with error code 0xc00402c7


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