Groups | Blog | Home
all groups > iis smtp nntp > december 2004 >

iis smtp nntp : "C:\Inetpub\mailroot\Queue" - SCRIPT SOURCE included



Uncle Ben
12/18/2004 5:56:12 AM
[quoted text, click to view]
to send e-mail. For some reason, after executing it, an .EML file is
created in "C:\Inetpub\mailroot\Queue" but it will not send.

What should I do to make it send??

Thank you!


'BEGIN SCRIPT

Set objMessage = CreateObject("CDO.Message")
objMessage.Subject = "Test"
objMessage.Sender = "admin@nospam.com"
objMessage.To = "myemail@myplace.com"
objMessage.TextBody = "This is a test."
objMessage.Send

'END SCRIPT

Uncle Ben
12/18/2004 7:25:00 AM
From the Event Viewer:

"Message delivery to the remote domain 'myplace.com' failed for the
following reason: Unable to bind to the destination server in DNS. "

How do I fix this?


[quoted text, click to view]

Uncle Ben
12/18/2004 3:48:25 PM
Can you tell me where I can correct my DNS?


[quoted text, click to view]

Uncle Ben
12/18/2004 5:49:02 PM
Thank you. DNS has been set and NSLOOKUP.EXE is reporting successfully.

But the *.EML is still not sending and is still sitting in the queue with
the same Event log entry.

Any other suggestions?

Thank you.

[quoted text, click to view]

jeff.nospam NO[at]SPAM zina.com
12/18/2004 6:24:45 PM
On Sat, 18 Dec 2004 07:25:00 -0500, "Uncle Ben" <spamfree@nospam.com>
[quoted text, click to view]

Correct your DNS so it can find the destination server. Try a
NSlookup of the MX record for the destination to test.

Jeff

[quoted text, click to view]
jeff.nospam NO[at]SPAM zina.com
12/18/2004 9:17:46 PM
On Sat, 18 Dec 2004 15:48:25 -0500, "Uncle Ben" <spamfree@nospam.com>
[quoted text, click to view]

It's your DNS client, in Network Connections, Local Connection, TCP/IP
Properties...

Ensure the DNS server you have designated allows the resolution of the
destination. Use NSlookup to test. For info on DNS and NSLookup, try
the DNS groups.

Jeff

[quoted text, click to view]
hector
12/18/2004 11:02:26 PM
[quoted text, click to view]

When all else fails - become a SMTP client by emulating the steps all SMTP
clients must follow.

Given destination address: myemail@myplace.com

Step 1) Lookup the MX host servers for the email domain: myplace.com

NSLOOKUP -QUERYTYPE=MX myplace.com

This will turn all the SMTP SERVERS at myplace.com that are available to
send mail to.

Assuming myplace.com is a valid domain, lets see what NSLOOKUP returns:

V:\bin> nslookup -querytype=mx myplace.com

Server: dns.mia.bellsouth.net
Address: 205.152.144.23

myplace.com
primary name server = trudeau.unitedstates.com
responsible mail addr = aidan.trudeau.unitedstates.com
serial = 2004120210
refresh = 10800 (3 hours)
retry = 3600 (1 hour)
expire = 604800 (7 days)
default TTL = 86400 (1 day)

I'm doing this from my home machine where my provision, bellsouth.net serves
as my DNS server. It returns no MX records.

Per SMTP standard specification, the rule is to TRY each MX domain in the
list returned (no consideration expansion concepts normally done for larger
systems like an AOL.COM), and if there are no MX, then try to connect the IP
address of the email domain directly atleast *ONCE*.

So lets assume again, this is the actual domain you are trying and not just
an example you provided. If this is the case, the IP for myplace.com is
done by getting the A record for it:

V:\bin> nslookup -querytype=A myplace.com

Server: dns.mia.bellsouth.net
Address: 205.152.144.23

Non-authoritative answer:
Name: myplace.com
Address: 64.26.130.103

In this case, it is EXPECTED to be an SMTP server running at that IP
address. Lets see.

Step 2) Connection to the MX host records or the non-MX single A record.

The easiest way to test a connection is to telnet on port 25, so type:

TELNET 64.26.130.103 25

Lets see what happens.......

Connecting To 64.26.130.103...Could not open a connection to host on port 25
: Connect failed

Ok, so there you have it. If MYPLACE.COM was the actual domain, then there
is NO SMTP SERVER running at this IP address on port 25.

Lets try it for a normal email address, like jeff's address; jeff@zina.com

Again, get the MX host domains for zina.com like illustrated in step 1:

V:\bin>NSLOOKUP -querytype=MX zina.com
Server: dns.mia.bellsouth.net
Address: 205.152.144.23

Non-authoritative answer:
zina.com MX preference = 5, mail exchanger =
inbound.registeredsite.com
zina.com MX preference = 20, mail exchanger = smtp.zina.com

zina.com nameserver = ns3.hosting4u.net
zina.com nameserver = ns.hosting4u.net
zina.com nameserver = ns2.hosting4u.net
inbound.registeredsite.com internet address = 64.224.219.122
smtp.zina.com internet address = 209.15.38.159
ns.hosting4u.net internet address = 209.15.2.3
ns2.hosting4u.net internet address = 209.15.2.4
ns3.hosting4u.net internet address = 209.15.3.1

Ok, there are two MX domains:

zina.com MX preference = 5, mail exchanger =
inbound.registeredsite.com
zina.com MX preference = 20, mail exchanger = smtp.zina.com

The preferences is to contact/try inbound.registeredsite.com first, and if
that fails, try the second one at smtp.zina.com

Now get the A record(s) for inbound.registeredsite.com

V:\bin>nslookup -querytype=A inbound.registeredsite.com
Server: dns.mia.bellsouth.net
Address: 205.152.144.23

Non-authoritative answer:
Name: inbound.registeredsite.com
Address: 64.224.219.122

Now try to telnet to this address on port 25

VIOLA, "Houston! We got a SERVER!"

220 inbound.registeredsite.com ESMTP SMTP Service (NO SPAM/UCE)

Now you begin a normal SMTP session. 220 means the SERVER is ready!
Anything else, means it is not ready to receive your commands.

3) SMTP Session

Once you connect, typically you have 5 commands or steps to follow in
sequence. I will use the simpliest for illustration purposes:

HELO client.machine.domain.name
MAIL FROM: <address of mail sender, not necessarily the author >
RCPT TO: <address of receiver of mail>
DATA start sending your email body ending with a "." line
QUIT

So assuming your example transaction was correct, this what you would type:

C: HELO mail.myplace.com
S: 250 Hi there!
C: MAIL FROM: <admin@nospam.com>
S: 250 mail from accepted
C: RCPT TO: <myemail@myplace.com>
S: 250 user accepted
C: DATA
S: 354 Start mail input; end with <CRLF>.<CRLF>
From: Admin@nospam.com
To: myemail@myplace.com
Date: date of message
Subject: test

This is a test.
.. <<-- note the dot
S: 250 Message accepted
C: QUIT
S: 250 BYE!

Thats basically it!

Have fun!

---
Hector Santos
WINSERVER "Wildcat! Interactive Net Server"
http://www.winserver.com

jeff.nospam NO[at]SPAM zina.com
12/19/2004 3:38:46 AM
On Sat, 18 Dec 2004 17:49:02 -0500, "Uncle Ben" <spamfree@nospam.com>
[quoted text, click to view]

Are you running SMTP on the same server? Microsoft's? Have you
tested it?

See:

HOW TO: Test Windows 2000 IIS SMTP Services Manually
http://support.microsoft.com/default.aspx?scid=kb;en-us;286421
HOW TO: Test SMTP Services Manually in Windows Server 2003
http://support.microsoft.com/default.aspx?scid=kb;en-us;323350

Jeff

[quoted text, click to view]
AddThis Social Bookmark Button