-----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 Guy
Sent: vrijdag 19 november 2004 10:00
To: spf-discuss(_at_)v2(_dot_)listbox(_dot_)com
Subject: RE: [spf-discuss] Electronic Frontier Foundation
(EFF) Article On Anti-Spam Technologies Mentions SPF
I think you just refuse to understand.
The domain owner is setting the policy. Your domain will not
allow you to do what you want to do. It is not your option.
Who owns the domain? Who "authorized" you? The only way to
"authorize" you is to fix the spf records.
Or to offer a "trusted mechanism" for relay. From the early days of SPF,
Meng has pointed to the need for SMTP AUTH. And a good SPF implementation
(not the libs itself, but the milter/mta using those libs) provides for an
SPF "pass" for SASL/STARTTLS authenticated IP addresses. Mine
(sendmail-milter-spf) certainly does; as I'm sure others do.
And yes, if you borrow a friend's cell phone, you can't forge
you own phone number. You must make the call using his number.
Or, if his phone requires a pin-code, and you do not know the pin, you
have no grounds for complaining if it will not let you make a call. That
is neither unreasonable, nor a "false" rejection.
- Mark
System Administrator Asarian-host.org
---
"If you were supposed to understand it,
we wouldn't call it code." - FedEx