The following is an amalgam of responses to various people.
To once again clarify how erroneous bounces will be filtered:
Any email system that allows a user to generate a white list will be able to
readily
generate a 'bounce white list' composed of all addresses that the user had sent
mail to within the past few hours. The bounces generated by my system will
be identified as bounces by a universally recognized tag. The user will
only see the bounces that are contained on the bounce white list.
Every time a proposal comes up one of the key weaknesses in all of them
becomes getting EVERYONE to use the system for it to work.
My system can be activated once email account at a time. Simultaneous world
wide
adoption is completely unnecessary. Some attributes of my system (previously
described)
are improved as more and more email providers update their systems.
But more
importantly I think a LOT of people are resisting, because your "solution"
isn't really a solution at all, it's a "system" for dealing with spam not
solving it. And more than anything it's not a solution, because it requires
human interaction to work.
Our perspectives clearly differ, since I view it as a solution because it
requires human interaction. I believe that this human interaction is as
limited and as non-disruptive as it can possibly be while still maintaining
an extreme degree of efficacy. A solution that provides similar
efficacy while requiring zero human interaction would be far superior, but
this "solution" just doesn't seem to exist.
No innocent user will ever get an erroneous bounce if a few of the
large consumer ISP adopt the system;
[???]
I was unclear. What I meant was that it would be a simple matter for
and email provider to recognize a bounce sent via my system.
Yes, though it's questionable whether anyone would want to implement
special-case recognition for every new C/R challenge out there. I
certainly am not interested in doing so.
I'm not arguing that every C/R system be accommodated, I'm just arguing for my
system.
Anyway the world would be a better place if a standard was adopted so that every
bounce-like message (such as my system, traditional C/R systems, vacation
messages)
came with a universally recognized tag. Then my bounce white list filtering
system
would prevent everyone from getting any kind of erroneous bounce.
Perhaps this needs to be another FUSSP criterion: "it assumes it's the
only system in use, or at least that everyone will be willing to add
special cases for it".
I suggest that the following be removed from the FUSSP list:
"Spammers can't automate puzzle solving, character recognition,
or or other hoops in the FUSSP that legitimate users must jump manually."
One day it may need to be re-added, but it should be removed for now.
ASRG got a pointer to my own system a while back:
http://www.vsta.org/spam/
It has a lot of similarities to your own
Your system is very similar to Zoemail, and my system incorporates
many of the techniques of Zoemail. My website details the
differences/advantages my system has over Zoemail.
Michael Kaplan
--
_______________________________________________
Find what you are looking for with the Lycos Yellow Pages
http://r.lycos.com/r/yp_emailfooter/http://yellowpages.lycos.com/default.asp?SRC=lycos10
_______________________________________________
Asrg mailing list
Asrg(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/asrg