Re: IIS - SMTP - CDONTS

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Kristofer Gafvert (kgafvert_at_NEWSilopia.com)
Date: 05/02/04 

Date: Mon, 3 May 2004 00:22:45 +0200

You should always be able to get a connection, no matter if authentication
is required or not. So the domain where this was not successful, you can
expect problems with the SMTP server. (or did you mean that you tried
another mx record, but for the same domain?)

What we did was more or less what the SMTP server do. So it really suprises
me that all this was successful (atleast for one domain you were having
problems to send emails to).

Can you please try to restart the machine, and see if the emails starts to
send? All domains you could do the below steps successfully, should work to
send to using the SMTP server.

Is this a general problem for _all_ domains? Or does it only happen for some
domains? If this is an SMTP server used for this website only, there is a
big risk that it is not considered to be a trustworthy email server (because
you have probably not done all the required steps involved, such as
configuring reverse lookup for example), and considered to be used for
spamming. Many email servers will reject a connection from your SMTP server
for this reason. That is why many people use smart hosts, so it looks like
the email is coming from a "real" email server, that can be trusted. When
the other server drops the connection, is not defined, and a connection
using telnet might therefore be successful. You should however (depending on
if the remote email server was kind enough) get a message logged in the SMTP
log (c:\windows\system32\logfiles\smtp...something like this, you should see
where it is located if you look in the SMTP properties, i dont have a
machine with SMTP installed right now). 

-- 
Regards,
Kristofer Gafvert - IIS MVP
http://www.ilopia.com - When you need help!
"Alan Garny" <someone@somewhere.com> wrote in message
news:c73nui$2cr$1@news.ox.ac.uk...
> "Kristofer Gafvert" <kgafvert@NEWSilopia.com> wrote in message
> news:%231gA1LGMEHA.1556@TK2MSFTNGP10.phx.gbl...
> > Please also do this, and tell me where it fails:
> >
> > On the SMTP server, do this:
> >
> > Open a cmd prompt.
> > Type
> >
> > nslookup ENTER
> >
> > --- INFO ---
> > You should get something like:
> > Default server: name.com
> > Address: 123.123.123.123
> > --- END INFO ---
>
> That's what I got, i.e. the name of my DNS server and its IP address,
> indeed.
>
> > set type=mx ENTER
> > remoteDomain.com ENTER
> >
> > --- INFO ---
> > This should give you information about the remote domain, including MX
> > records.
> > --- END INFO ---
>
> Agreed, that's what I got.
>
> > exit ENTER
> > telnet mx-remoteDomain.com 25
> >
> > --- INFO ---
> > You should not get an empty window
> > --- END INFO ---
>
> I have tried that with the domain of the two e-mail addresses to which I
> tried to send an e-mail via IIS. In one case, the connection failed. I
> believe that it might be because that domain normally requires
> authentication. Would that make sense? Otherwise, it worked fine with the
> second domain.
>
> > ehlo yourhost ENTER
> >
> > --- INFO ---
> > If it drops the connection, try another telnet connection, but this time
> > write:
> > --- END INFO ---
> >
> > helo yourhost ENTER
>
> Both commands work fine and in both cases, it replied something along the
> lines of "250-mx-remoteDomain.com Hello MyHost [MyIPAddress], pleased to
> meet you".
>
> > - remoteDomain.com is the remote domain you are trying to send email to,
> but
> > fails.
> > - mx-remoteDomain.com is the MX record for the domain you are trying to
> send
> > to. If more than one exists, and the first one drops the connection, try
> the
> > other ones. You get this information from the nslookup command.
> > - yourhost is your hostname.
> > - ENTER means press the enter button on the keyboard.
> >
> > So, what did we do? We first verified that the SMTP server can lookup
the
> > domain. If this works, we then tried to get a connection to the remote
> > domain. If this works, then please look in the Event Log. It should tell
> you
> > more about the problem. If something failed on the way, we know if it is
> > related to DNS, or connection.
>
> Well, since nothing failed, I believe that everything works "fine",
besides
> the fact that I cannot send e-mail via IIS...
>
>     Alan.
>
>

Relevant Pages

  • Re: Conversion to 64 bit server
    ... their database report scripts are broken. ... The problem is I can't get the email connection to work. ... The email code works in a 64bit command prompt. ... SMTP server to connect to. ...
    (microsoft.public.scripting.vbscript)
  • Re: Need OE Help!!
    ... With dial-up connection, however, I ... > not connect the smtp server to send e-mails out. ... Email scanning slows down Receiving, sometimes enough that OE times out. ... "Disabling email protection does not leave you vulnerable to viruses and ...
    (microsoft.public.windows.inetexplorer.ie6_outlookexpress)
  • Re: Cannot send emails using Windows Mail
    ... of that SMTP server or the name of the connection provider. ... Ask your home ISP if they have a port other than '25' for SMTP. ... address accounts. ...
    (microsoft.public.windows.vista.mail)
  • Re: Error Number: 0x800CCC0E
    ... Mobile Broadband I needed to update the SMTP Server to the 3 Mobile Server. ... Ask Virgin if they have a port other than '25' for SMTP. ... Substitute the SMTP server belonging to your '3' connection. ...
    (microsoft.public.windows.vista.mail)
  • Re: IIS - SMTP - CDONTS
    ... for which the mx server doesn't respond. ... Many email servers will reject a connection from your SMTP ... to work until I decided to uninstall and reinstall the SMTP server. ... > if the remote email server was kind enough) get a message logged in the ...
    (microsoft.public.inetserver.iis)