Everybody already has policies restricting other mail server. We have
blacklist for open relays, we have delayed smtp response for offenders. We
have data throttling for any domain that sends too many emails and we have
temporary blacklist for senders who send to too many unknown users.
We will add to that blacklisting domains with excessive ip ranges in the spf
records and especially for spf records that include the entire ip space.
----- Original Message -----
From: "Ernesto Baschny" <ernst(_at_)baschny(_dot_)de>
To: <spf-discuss(_at_)v2(_dot_)listbox(_dot_)com>
Sent: Wednesday, July 28, 2004 8:42 AM
Subject: [spf-discuss] Re: Military
Hi!
In my eyes, nobody should dictate others "policies" for email. The domain
owner has this right, as he was the one who owns the domain and will be
liable for any email send using his domain that conforms to his own SPF
policies.
Passing the SPF test doesn't necessarily mean that a mail is not spam.
This just tell us that the owner of the domain allowed this mail to go
out. If we end up having huge amount of spam from this particular lax
policy, the domain *will* end up in a domain-blacklist and we will have
other measures to prevent if from happening again. Maybe this blacklisting
will bring make the original domain owner to rethink his policy.
But we as a receiver should not dictate what is a "valid" and an "invalid"
policy, this is called *sender* policy framework.
Cheers,
Ernesto
-------
Sender Policy Framework: http://spf.pobox.com/
Archives at http://archives.listbox.com/spf-discuss/current/
Send us money! http://spf.pobox.com/donations.html
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