IIS email being rejected by some domains.

[Frustrated Tech]

We have a smtp server on a w2k member server that now gets lots of email
rejected after switching to ATT as our webhosting and email server provider.

I have read all kinds of articles that explain how IIS wors and how it needs
to be configured. But I can't find anything that applies to my problem.

I called my ISP and they help me create mx record for our domain smtp server
now called mail.exampleinc.com, after which he told me to somehow change my
smtp server name from smtp1.example.local to the fqdn mail.example.com.
I cant seem to find any documentation on how to do this, is this even
possible?
Someone told me I needed PTR record..do I do that with ISP or my dns server?

I am not an expert on IIS so if you can provide links that explain how to
implement the solution, would be extremely helpfull.

[Jeff Henkels]

PTR records are used for reverse DNS lookup (i.e. given an IP address, get a
domain name); many sites use this info as an anti-spam measure, to ensure
that the sender is who it claims to be. Usually, at least in my experience
with cable & DSL ISPs, the ISP is responsible for PTR records -- most of the
big ones do it right (or right enough for our purposes).

You could probably go to DNSReport.com or DNSStuff.com and run their free
tools to test/diagnose any issues you may have with DNS.

"Frustrated Tech" <Frustra...@discussions.microsoft.com> wrote in
message news:008CBDE0-A75A-480B...@microsoft.com...

[Sanford Whiteman]

Follow Jeff's advice about the PTR. If your ISP is managing your forward
DNS (MX/A record) as you indicated, then they are surely responsible for
your reverse DNS (PTR) zone as well, and it was lazy of the ISP tech to
not take note of this.

> I called my ISP and they help me create mx record for our domain smtp
> server
> now called mail.exampleinc.com, after which he told me to somehow
> change my
> smtp server name from smtp1.example.local to the fqdn mail.example.com.
> I cant seem to find any documentation on how to do this, is this even
> possible?

The outgoing HELO/EHLO hostname is dictated by the name of the domain
marked Local (Default) in IIS SMTP.

In Win2K, you need to install MetaEdit 2.2 to change this value (or delete
and recreate the SMTP Virtual Server, which you may not be comfortable
with). And you should change it. HELO/EHLO must be a valid FQDN, and
.local will never be valid on the public net.

-- Sandy

------------------------------------
Sanford Whiteman, Chief Technologist
Broadleaf Systems, a division of
Cypress Integrated Systems, Inc.
------------------------------------