PDA

View Full Version : IIS SMTP Trouble


FHalsington
03-21-2007, 12:25 AM
Hi,

I have an XP Pro and I'm running IIS and I have installed the SMTP Service but for some reason no matter what I do I cannot get it to relay a single email message from my contacts page. I have used the very same contacts page on a few different web servers including an IIS server and the messages get relayed just fine. So this leads me to believe that my SMTP Service is either not configured right or my Web Server with Router won't allow IIS to send email. I have a Linksys Router that has a static Internet IP 74.224.160.120 and it routes the IP requests to the local machine that I have serving the website. All my router settings are set properly as I had the Linksys Customer Support walk me through it. So now I am at a loss. I desperately want to have a Contacts page that sends mail and I seriously do not know what I am doing wrong. Does anyone have an idea to help?

Thanks In Advance.

KeZZeR
03-21-2007, 11:17 AM
Funny you say that, I have this exact same issue on a few of my computers at work. I think it's down to permissions for particular domains. The last I remember you had to play around with some IIS settings to allow mail to be sent to/from that domain. Also, under "domains" in the Default SMTP Virtual Server in IIS I believe you have to add the domain you wish to send from.

Have you checked your temporary mail store? There may be mail messages in the queue, and if so that means that it's just IIS not being set up correctly. Check in the folder C:\Inetpub\mailroot\Queue and see if there's any mail messages in there. (I've got over a thousand messages in mine ;))

FHalsington
03-21-2007, 06:50 PM
Well I looked in that directory and you are right, there are tons on EML files in it. So how do I fix this? What settings do I need to change?

Thanks So Much for You Time.
Fred H.

KeZZeR
03-26-2007, 11:21 AM
Usually it's down to out-bound connections not being authorized in IIS. Check the default SMTP virtual server properties, it may be due to access control. Check the authentication properties for that particular virtual server to see if it's granted. Basically check all options under the "access" tab in the properties, there's loads in there which can block traffic.