-----Original Message-----
From: owner-spf-discuss(_at_)v2(_dot_)listbox(_dot_)com
[mailto:owner-spf-discuss(_at_)v2(_dot_)listbox(_dot_)com] On Behalf Of Joe
Rhett
Sent: April 14, 2004 8:57 PM
To: spf-discuss(_at_)v2(_dot_)listbox(_dot_)com
Cc: spf-discuss(_at_)v2(_dot_)listbox(_dot_)com
Subject: Re: [spf-discuss] first spf-enabled spam
On Wed, Apr 14, 2004 at 06:06:34PM -0600, Aredridel wrote:
Perhaps you should come to North America, then. I've only
heard of
ONE ISP requiring SMTP AUTH from its subscribers, and that ISP
requires it only to relay mail that doesn't have a from
@theirdomain.com.
Make that two. I am one. We implemented it years ago.
Nearly 4 years ago here. And even Earthlink has implemented
this. As far as I know, almost all major ISPs support SMTP
AUTH for using their servers
as an MSA.
The ISPs who haven't implemented AUTH are a minority now. It
just took a long time.
ISPs like Earthlink resell dialups from various providers, though, so they
can't just allow relaying from 1.2.0.0/16 or whatever without also letting
other customers of their wholesale supplier relay through them. That creates
a STRONG incentive to implement things like SMTP AUTH, or before that,
POP-before-SMTP... But what about other providers that have all of their
customers using that ISP's IP space? The latter type of provider is the kind
I was referring to...