Hi;

Reposting to smtp_nntp because the post never showed up here.

I don't know if this is a IIS_SMTP or a SBS_Exchange issue so I am
posting to both.

Here is my network setup:

DSL Modem -> Switch 1 -> IIS & SMTP server, DNS server
-> firewall/NAT -> switch 2 ->
SBS/Exchange server

From the IIS/SMTP server I can telnet on port 25 to the exchange
server. Using telnet I can send an email to my exchange server. So
email can be sent (ie no firewall issues).

Also, email sent to domains other than ours works fine.

I did an "ipconfig /flushdns" and reboot both last night and this
morning to make sure it is all correct on any cached IP addresses.

On the IIS server I have a java program (Tomcat on IIS) that sends
email. It successfully sends email to any domain except our domain.
For our domain it is placed in BadMail.

The log is:
#Fields: date time c-ip cs-username s-sitename s-computername s-ip
s-port cs-method cs-uri-stem cs-uri-query sc-status sc-win32-status
sc-bytes cs-bytes time-taken cs-version cs-host cs(User-Agent)
cs(Cookie) cs(Referer)
2006-02-18 18:08:20 199.45.247.110 simba SMTPSVC1 SIMBA 199.45.247.110
0 EHLO - +simba 250 0 196 10 16 SMTP - - - -
2006-02-18 18:08:20 199.45.247.110 simba SMTPSVC1 SIMBA 199.45.247.110
0 MAIL - +FROM:<support@windward.net> 250 0 45 32 16 SMTP - - - -
2006-02-18 18:08:20 199.45.247.110 simba SMTPSVC1 SIMBA 199.45.247.110
0 RCPT - +TO:<support@windward.net> 250 0 33 30 0 SMTP - - - -
2006-02-18 18:08:20 199.45.247.110 simba SMTPSVC1 SIMBA 199.45.247.110
0 DATA - +<399262.1140286100421.JavaMail.SYSTEM@simba> 250 0 128 281
125 SMTP - - - -
2006-02-18 18:08:20 199.45.247.110 simba SMTPSVC1 SIMBA 199.45.247.110
0 QUIT - simba 240 188 66 4 0 SMTP - - - -

Any ideas? From the log above (250 on all commands) it looks like it
was sent. But the mail ends up in BadEmail and I don't get it.

thanks - dave

david@at-at-at@windward.dot.dot.net
Windward Reports -- http://www.WindwardReports.com
me -- http://dave.thielen.com

david@at-at-at@windward.dot.dot.net
Windward Reports -- http://www.WindwardReports.com

[quoted text, click to view]

It showed up for me. . . .

[quoted text, click to view]

It's an IIS issue, or, rather, it's a DNS issue which becomes
symptomatic when you attempt to send mail using IIS.

[quoted text, click to view]

No, that still is not a DNS test. Unless you are using a smarthost or
delivering mail to the local machine, SMTP intimately uses DNS. In
one of my other replies, I requested that you run an nslookup from the
IIS box and return the results for your MX.

nslookup -q=mx example.com

[quoted text, click to view]

Yeah, quite consistent with the situation I explained in detail in
another response.

[quoted text, click to view]

This would make no difference at all unless you also made DNS changes.

[quoted text, click to view]

That's the log of Tomcat sending to IIS, the zero-hop. That's not the
one you're worried about.

Hi;

I am guessing a DNS issue too. Here is the nslookup result:

C:\Documents and Settings\Administrator>nslookup -q=mx windward.net
Server: windward.net
Address: 199.45.247.110

windward.net MX preference = 0, mail exchanger = mail.windward.net
mail.windward.net internet address = 199.45.247.103

C:\Documents and Settings\Administrator>

This is correct - .110 is the web server box (box this is run on) and
that is our external DNS server. .103 is the external IP address of
our exchange server and is the address I could email to via telnet.

One point I have seen raised here elsewhere - the IP for the name
windward.net is .110. So if the SMTP engine sends to the name
windward.net instead of the mx for windward.net - then it would have
this problem.

Your description of the log makes sense - a good transmission to the
SMTP server (all 250) and since it can never "find" the mail
connection to Exchange - no log entry.

Is it possible it's the entry for windward.net? I want that to point
to the web server because I want http://windward.net to work.

??? - thanks - dave


On Sat, 18 Feb 2006 15:10:44 -0500, Sanford Whiteman
[quoted text, click to view]


david@at-at-at@windward.dot.dot.net
Windward Reports -- http://www.WindwardReports.com

On Sat, 18 Feb 2006 15:10:44 -0500, Sanford Whiteman
[quoted text, click to view]

Hi;

Below is the output from smtpdiag - everything looks fine except:
1. The domain controller error - this is not a domain system so I
think this is to be expected.
2. I have the SMTP server set to send only but it seems to be ok with
a sender address.
3. the check remote domain records does not list the A record for the
UDP DNS check - is this an issue?
4. I think it shows it is sending an email - but I never receive it.
And it's not in the queue or badmail.

Any ideas?

thanks - dave


C:\temp\SmtpDiag>SmtpDiag.exe david@thielen.com david@windward.net /v

Searching for Exchange external DNS settings.
Computer name is SIMBA.
Failed to connect to the domain controller. Error: 8007054b

Checking SOA for windward.net.
Checking external DNS servers.
Checking internal DNS servers.

Checking TCP/UDP SOA serial number using DNS server [199.45.247.110].
TCP test succeeded.
UDP test succeeded.
Serial number: 125

Checking TCP/UDP SOA serial number using DNS server [206.168.112.1].
TCP test succeeded.
UDP test succeeded.
Serial number: 125
SOA serial number match: Passed.

Checking local domain records.
Starting TCP and UDP DNS queries for the local domain. This test will
try to
validate that DNS is set up correctly for inbound mail. This test can
fail for
3 reasons.
1) Local domain is not set up in DNS. Inbound mail cannot be
routed to
local mailboxes.
2) Firewall blocks TCP/UDP DNS queries. This will not affect
inbound mail,
but will affect outbound mail.
3) Internal DNS is unaware of external DNS settings. This is a
valid
configuration for certain topologies.
Checking MX records using TCP: thielen.com.
MX: mail.thielen.com (0)
A: mail.thielen.com [199.45.247.103]
Checking MX records using UDP: thielen.com.
MX: mail.thielen.com (0)
A: mail.thielen.com [199.45.247.103]
Both TCP and UDP queries succeeded. Local DNS test passed.

Checking remote domain records.
Starting TCP and UDP DNS queries for the remote domain. This test will
try to
validate that DNS is set up correctly for outbound mail. This test can
fail for
3 reasons.
1) Firewall blocks TCP/UDP queries which will block outbound mail.
Windows
2000/NT Server requires TCP DNS queries. Windows Server 2003 will use
UDP
queries first, then fall back to TCP queries.
2) Internal DNS does not know how to query external domains. You
must
either use an external DNS server or configure DNS server to query
external
domains.
3) Remote domain does not exist. Failure is expected.
Checking MX records using TCP: windward.net.
MX: mail.windward.net (0)
A: mail.windward.net [199.45.247.103]
Checking MX records using UDP: windward.net.
MX: mail.windward.net (0)
Both TCP and UDP queries succeeded. Remote DNS test passed.

Checking MX servers listed for david@windward.net.
Connecting to mail.windward.net [199.45.247.103] on port 25.
Received:
220 windward.net Microsoft ESMTP MAIL Service, Version: 6.0.3790.1830
ready at
Mon, 20 Feb 2006 15:14:08 -0700


Sent:
ehlo thielen.com

Received:
250-windward.net Hello [199.45.247.110]
250-TURN
250-SIZE
250-ETRN
250-PIPELINING
250-DSN
250-ENHANCEDSTATUSCODES
250-8bitmime
250-BINARYMIME
250-CHUNKING
250-VRFY
250-X-EXPS GSSAPI NTLM LOGIN
250-X-EXPS=LOGIN
250-AUTH GSSAPI NTLM LOGIN
250-AUTH=LOGIN
250-X-LINK2STATE
250-XEXCH50
250 OK


Sent:
mail from: <david@thielen.com>

Received:
250 2.1.0 david@thielen.com....Sender OK

Sent:
rcpt to: <david@windward.net>

Received:
250 2.1.5 david@windward.net

Sent:
quit

Received:
221 2.0.0 windward.net Service closing transmission channel

Successfully connected to mail.windward.net.

C:\temp\SmtpDiag>


david@at-at-at@windward.dot.dot.net
Windward Reports -- http://www.WindwardReports.com

[quoted text, click to view]

No, that's a non-issue and typical behavior for SMTPDIAG.