|
|
|
date: Sun, 18 May 2008 22:31:17 -0700,
group: microsoft.public.inetserver.iis.smtp_nntp
back
Re: SMTP initial setup
> What is necessary to operate the smtp server?
- A DNS server that can perform recursive lookups
- Proper forward and reverse DNS setup for the PTR-EHLO-A "roundtrip"
test performed, at least in part, by huge numbers of remote servers as
an anti-spam/anti-abuse check (search my posts in the archives of this
list for much more on the "roundtrip")
- A closed relay that allows relaying for SMTP AUTH sessions (with
difficult-to-guess passwords) and/or for known internal IPs, but _not_
from unknown IPs
- Lots of reading, lots of experimenting
- Learning to read your logs
> Must a local DNS server be running?
Local, no. Working, yes. It doesn't matter where your mailserver's DNS
resolver is located (save for performance concerns). What matters is
that that resolver can issue recursive requests over both UDP and TCP
and that its firewall will allow the responses. Likewise, your
mailserver needs to be able to communicate seamlessly with the
resolver. Again, where it is makes no diff.
> Is any authentication necessary?
In a plain setup, authentication will be necessary to send mail to
domains that are neither marked 'Local (Default)' nor 'Alias' in the
IIS Manager, nor marked as 'Remote' with the checkbox 'Allow mail to
be relayed to this domain' checked. In other words: unknown remote
domains.
You can allow relay by (source) IP, instead of simply by SMTP AUTH.
That's a core feature.
> Does anyone have access to some whitepapers or links which describe
> the server's features and functions?
MSDN has quite a bit on the subject. I also would strongly advise
grazing over the archives of this newsgroup!
--Sandy
------------------------------------
Sanford Whiteman, Chief Technologist
Broadleaf Systems, a division of
Cypress Integrated Systems, Inc.
------------------------------------
date: Tue, 20 May 2008 01:55:31 -0400
author: Sanford Whiteman
|
|