On Saturday, May 03, 2003 1:11 PM, Vernon Schryver
[SMTP:vjs(_at_)calcite(_dot_)rhyolite(_dot_)com] wrote:
8<...>8
However, that's not the main problem. Users do not like setting up
filters. They simply will not bother to configure their software to
accept "transactional" messages but not "ads" from Roving Software.
They will block all or none of your messages. It doesn't matter
whether you use per-message content labelling or you do as Topica has
tried, labelling by domain name or Habeas mark. Unless essentially
all of your messages are wanted, all of your messages will be blocked
based only on the fact that you are the sender (like the most recent
edition of the weekly drivel that your organization tries to send me).
Yes, but wouldn't a recipient want a 'confirmation' message that was consented
to always?
Spam won't stop being spam and won't stop being filtered by having an
additional label.
I agree, but what is the solution for legitimate 'large scale' CRM efforts? Is
it perhaps end-user categorization at relationship inception? That has the
possible dual benefit that a) it imposes a 'burden' on the originator to relate
customer/consumer information to customer/consumer stipulated categories; and
b) it allows recipient customer/consumer access to the desired policy
configuration, e.g. I control my spam so from vendor A, but all the others be
damned - I like that idea). That requires labeling per se but it is within the
context of the relational dB of the originator/customer 'system' and not tied
to messages or its transporting/delivery/rendering system. Don't inject what
you can not validate as desired (opt-in?).
-e
_______________________________________________
Asrg mailing list
Asrg(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/asrg