Re: SMTP Service not functioning on IIS 5
- From: Jeff <Jeff@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 8 Jun 2007 11:55:02 -0700
I used the FQDN of the domain because it made sense to me for an intranet
site, i.e. the home page for this domain. I've been using AD since 2000 and
I've never had a problem with doing this, but I didn't know there was
anything inherently risky about it - by default, you are right that AD will
resolve the domain name to a domain controller(s), but I've seen no AD issues
whatsoever. Yes there is a record in DNS that resolves this to the IIS box,
I only mentioned the browser for the example of corp.domain.com as an
intranet site, I didn't configure a domain name anywhere in IIS. I wouldn't
put IIS on a DC ever, but why shouldn't a browser request for a domain name
bring up an intranet home page like an external website? Makes perfect sense
to me
I configured the LDAP routing because AD stores the information on
containers for mailboxes and usernames and can resolve recipients. What does
it do that I am thinking it doesn't? Perhaps an explanation would help, but
I will turn it off as suggested and try it out.
The masquerade domain was added to help in troubleshooting. Since it puts
the masquerade domain in the "Mail From" part of the header, I figured it
might help at some point.
With the smart host, this was something I was testing to see if it would
work. My thinking was that if mail was being sent out and not going anywhere
from the SMTP service, if it went to Exchange and was delivered ok, then I'd
have an idea that mail was at least being sent out properly and there might
be some other issue from the IIS box. I'd be able to check the headers and
see what server it came from.
The purpose: This IIS box is for development of websites and an intranet
site for our employees to post company policies and procedures. It is
strictly internal to our company and doesn't have anything to do with
anything on the outside. We develop a lot of websites and our website
manager asked me to setup SMTP from the webserver to test sending out email
from his scripts and forms.
Hope this helps.
--
Thanks, Jeff
"Sanford Whiteman" wrote:
.We have are running IIS 5 on a Windows 2000 sp4 file server to host
our local intranet as well as local copies of multiple websites used
for testing (copies of live websites). There is only 1 "site"
configured and each local copy is simply a sub-directory off of the
main site. This sites' domain in DNS is the same as our Active
Directory domain ("corp.domain.com") so browser requests for the
local domain go to this server.
Technically speaking, the setup on the server itself is irrelevant to
a remote browser. The browser will use DNS to resolve corp.domain.com
to an IP, and there presumably is an A record for corp.domain.com
pointing to your IIS 5 box. Host headers take over only at that point.
I have to tell you that in an AD environment, your use of the domain
FQDN is quite atypical and risky; the fully-qualified domain name of
the AD domain typically resolves to AD domain controller(s), for very
good reason. However, this is unlikely to be directly pertinent to
your situation with the SMTP service.
- LDAP routing to a Global Catalog Server using Active Directory as the
schema.
LDAP routing doesn't do what you think it does; turn it off.
- in Advanced Delivery, "corp.domain.com" as the masquerade domain
Unless you can justify rewriting envelope information, turn this off,
too. It is not commonly necessary to use this feature, esp. if you are
already using a public DNS TLD like .com when submitting mail. I think
you've overdone the settings a bit... you might reenable some of these
later, but it makes troubleshooting more difficult in your beginning
phase.
FQDN is set to the hostname "host.corp.domain.com" by default.
OK.
- I added our exchange server as a Smart host, with the SMTP service
attempting direct delivery first
Why'd you do that, exactly? That setup is suggesting that you want the
server to use the DNS MX algorithm by default, but to hand off
messages to the Exchange box on failure instead of returning a DSN.
The Exchange box will then be retrying using the same DNS MX
algorithm, so what is the precise use case in which "Direct Delivery
First" will do more than add confusion?
DDF + Smart Host would typically be used if you want to take load off
a busy mail server after the initial attempt to send, so subsequent
retries are done by a secondary server that likely has a much larger
queue, a longer queue retry interval, more horsepower to spare, etc.;
for example, if your primary server were *also* servicing
POP3/OWA/Outlook clients, you would use DDF + SH to ensure the
promptest/cleanest delivery possible when there were no errors
encountered, while on any initial error you would hand off the message
to a dedicated server, accepting the additional log complexity as well
worth it because you've saved your main server's CPU and disk I/O.
Also, you haven't described exactly what you want to do with this SMTP
service. If, as indicated in your "Direct Delivery First" checkbox, it
will be connecting to remote servers, have you made sure it has a
valid Reverse DNS (PTR) record, that in turn has an A record pointing
back to its public IP? Granted, this won't stop the service from
starting, but it is crucial for direct delivery.
--Sandy
- Follow-Ups:
- Re: SMTP Service not functioning on IIS 5
- From: Sanford Whiteman
- Re: SMTP Service not functioning on IIS 5
- References:
- Re: SMTP Service not functioning on IIS 5
- From: Sanford Whiteman
- Re: SMTP Service not functioning on IIS 5
- Prev by Date: Re: Slow RCPT
- Next by Date: Re: IIS 5's SMTP and Stopping NDR's ?
- Previous by thread: Re: SMTP Service not functioning on IIS 5
- Next by thread: Re: SMTP Service not functioning on IIS 5
- Index(es):
Relevant Pages
|
