I can enable authstrict.. then, if u authenticate as scott(_at_)urdomain, u
are forced to send email as scott(_at_)urdomain, if u don't u'll receive a
nice 453 error message.
On Thu, 19 Aug 2004 22:32:28 -0400, Scott Kitterman
<spf(_at_)kitterman(_dot_)com> wrote:
-----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
Rodolfo Sikora
Sent: Thursday, August 19, 2004 10:28 PM
To: spf-discuss(_at_)v2(_dot_)listbox(_dot_)com
Subject: Re: [spf-discuss] Some thoughts about spam and SPF
The company I work for does exactly this. To provide a outsourced SMTP
service and a incoming filter. Free of forgeries, everybody use smtp
auth and quickly we can find out if someone is doing the wrong thing.
This is working pretty cool and our customer are exactly this kind of
people that uses email as a tool and don't have time to waste with
those problems.
OK. If I sign up and want to send e-mail from my domain, how do you
determine if I'm an authorized user of that domain? What prevents your
other customers from forging my domain? SMTP Auth says that I'm a customer
of yours. It doesn't, in and of itself, say what domains I'm authorized to
send mail from.
Scott Kitterman
-------
Sender Policy Framework: http://spf.pobox.com/
Archives at http://archives.listbox.com/spf-discuss/current/
http://www.InboxEvent.com/?s=d --- Inbox Event Nov 17-19 in Atlanta features
SPF and Sender ID.
To unsubscribe, change your address, or temporarily deactivate your
subscription,
please go to
http://v2.listbox.com/member/?listname=spf-discuss(_at_)v2(_dot_)listbox(_dot_)com