On Wed, Oct 15, 2003 at 08:33:12AM -0400, RKML wrote:
Yes, though many of the same problems still apply. It's not always
clear who is to blame for spam in an SPF world:
* Spammer misuses his ISP's SPF-protected SMTP server:
Is the ISP at fault. Can spamtraps put the ISP on automated
block lists?
This is simple. Just report the abuse to the SPF-Protected
ISP's Admin and therefore let them shut down the client if
People are talking about automatically blacklisting sources
of spam. Since the ISP is the SPF-validated source in this
case your suggestion contradicts that.
However, with SPF-Protected sites,
there is absolutely no need to password protect a mailing list
as the sender is 99% the true sender.
I think you are expecting far too much from SPF. If I am an
evil spammer and I have a throwaway domain I can do much more
damage by spamming 1000 mailing lists than 1000 normal addresses
(in the time I have before I am discovered and my throwaway domain
is rendered useless).
The general problem here is that it's impossible to discern
whether the SMTP server you are getting the mail from actually
got it from an SPF-checked source, or whether it is just
claiming to have done so.
Again, report the issue and let them know that their
forwarding service is prone to being banned.
Sounds like a reputation based system to me, but:
Reputation system will not work well as it is too high maintenance.
--
Erik Corry erik(_at_)arbat(_dot_)com
A: Because it messes up the order in which people normally read text.
Q: Why is top-replying such a bad thing?
A: Top-replying.
Q: What is the most annoying thing in email?
-------
Sender Permitted From: http://spf.pobox.com/
Archives at http://archives.listbox.com/spf-discuss/current/
To unsubscribe, change your address, or temporarily deactivate your
subscription,
please go to
http://v2.listbox.com/member/?listname(_at_)©#«Mo\¯HÝÜîU;±¤Ö¤Íµø?¡