Re: And so it begins...

[David Gibbs <david@xxxxxxxxxxxx>]

Joe Pluta wrote:
> Okay, here's a new twist on the blacklist/whitelist concept.

Not new at all, actually.  Just a bit more aggressive.

> I just sent an email to someone.  It didn't get through because the 
> recipient's ISP blocked it.  Why?  Because it didn't recognize me as
> an ISP.  That is, this service no longer accepts mail from "end user"
>  accounts, which pretty much includes anybody running their own SMTP 
> server over a DSL line.

The problem is: The IP addresses for your DSL line are allocated from a
block that are normally used for consumer grade DSL service.

> They give you a number of options, including rerouting your mail
> through your ISP, or getting your ISP to change the PTR record for
> your DSL address.  Otherwise, the user has to turn off spam
> filtering.  As far as I can tell, this is purely a blacklist 
> approach, with no ability to whitelist a domain.  So any small
> business running their own SMTP server over a DSL line is subject to
> this kind of blacklisting.

If changing the PTR records means having your DSL provider point the
reverse IP lookup values, for your IP addresses, to point to your own
domain, then I think that would be a very viable solution.

This is the route I chose when I had a similar problem.

Even though my IP addresses are provided by Covad, and they are
allocated from what would normally be consumer grade dsl service
allocation, I do have them pointing back to my own host names.  If you
do a reverse IP lookup on 69.3.23.26, you'll find it points back to
ip26.midrange.com.

Covad had no problem setting this up ... took about 2 days.  Of course I
am paying for business class service, so YMMV.

david

-- 
David Gibbs
david@xxxxxxxxxxxx

Receipt of this message does not grant you permission to send me
Unsolicited Commercial Email