On 5/19/02 8:28 PM, "Tom Neff" <tneff @
> service. I am looking for something more like a proof of license to send.
Which implies someone/something is required to define "need" or "worth" of
what's being sent. And that's going to fundamentally fail, except on an
As an extreme example -- if a person wants a "proof of license" to send
child pornography, it's going to be rejected by any authority. But on a
fundamental basis, if you want to avoid censorship or bureaucratic biases of
any sort, if the recipient of that e-mail WANTS the kiddie porn, that
license should be granted. To do otherwise simply creates a system where you
no longer have "send it only if I accept it" but a bureaucracy of some sort
that defines "send it only if it's acceptable".
So we wander right back to that "license to send" being issued by the
receiver. So unless you want to create some form of query-respond acceptance
scheme where you send a widget to get permission to send an email, or you
are back as "decide on receipt", which is what we have today, only with some
new wrappings on it to make it seem different.
And as I noted in another message on all this, the query-respond systems
(aka the whitelist with rejection unless you get overt permission to send)
is unacceptable to most people because of the high level of irritation it
causes senders and the high level of false positives it generates for the
So none of these systems really change the status quo of how we decide
whether to accept mail. They just create complications that don't really
affect the end result...
Chuq Von Rospach, Architech
com -- http://www.chuqui.com/
No! No! Dead girl, OFF the table! -- Shrek