Clear Consent is when end-user said he wants to receive email from you
(whitelisting of email address or domain). Clear No Consent is when user
specifically said he does not want to receive email from you (blacklisting).
Specifying of other mail filters are consent by user to use specific
technology to filter out email.
Anything that does not get stopped by the filter goes into final step
which specifyies user's preference - either presumed consent or presumed
denial. Denial may also be replaced by request for authorization which
maybe request to "buy" or calculate a stamp, go to specific webpage and
look at the picture (or hear a sound) and aythorize there, send email to
some other address, etc, etc.
And when user provided these settings for filtering this is alot better
then presumed consent filtering by isp based on its own preferences and
its opinion on what consent is.
On Sun, 23 Mar 2003, Jon Kyme wrote:
I'v thought about all this before. I think it might be worth our time to
define standard "mail-filter configuration" protocol. I imagine this
being
as something that would be located on some central database server and
it would have "user configuration" update queries and "mail server check"
read-only queries.
Yes, perhaps.
There was a (short) thread on
"What would consent look like?"
started on
Mon, 10 Mar 2003 10:45:34 +0000
Which might be relevant here.
:-)
--
_______________________________________________
Asrg mailing list
Asrg(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/asrg
_______________________________________________
Asrg mailing list
Asrg(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/asrg