IIS and SMTP - SMTP Virtual Server - Avoiding Being Classified As SPAM

Author

SMTP Virtual Server - Avoiding Being Classified As SPAM

MEB

2004-07-26, 7:57 am

We have an IIS 5 server sending ecommerce transaction
email responses straight out through the IIS SMTP virtual
server. We do not have the ability to pass these messages
through a registered domain or a registered server name.
How can we avoid being classified as a SPAM source? Is a
reverse DNS lookup our only option? If so, should the
reverse lookup be configured at our ISP's end? Our ISP
currently provides our public IPs and internet zone files.

Thanks.

Jeff Cochran

2004-07-26, 5:57 pm

On Mon, 26 Jul 2004 05:15:15 -0700, "MEB"
<anonymous@discussions.microsoft.com> wrote:

>We have an IIS 5 server sending ecommerce transaction
>email responses straight out through the IIS SMTP virtual
>server. We do not have the ability to pass these messages
>through a registered domain or a registered server name.
>How can we avoid being classified as a SPAM source?

To avoid getting balcklisted, make sure you don't relay. If you're
getting identified as spam for another reason, you need to deal with
that reason.

>Is a
>reverse DNS lookup our only option?

Most spam filters are now checking reverse DNS to ensure there is a
lookup, but not necessarily that it goes to a specific domain.

>If so, should the
>reverse lookup be configured at our ISP's end? Our ISP
>currently provides our public IPs and internet zone files.

Then they need to do the reverse DNS zone.

For many filters, an email server configured with just an IP address
and no host name is an indicator of a compromised server and likely to
send spam. So you may need to configure a host/domain name to ensure
getting through.

Jeff

Paul Lynch

2004-07-27, 2:57 am