You will find a document which outlines an idea I've had for a while.
The thrust of the document is that while we don't know what the silver
bullet solution for spam is we do know some of the characteristics
which we expect it to exhibit.
We also know that very many ideas are presented on the firstname.lastname@example.org list which
fail to meet one or more of those criteria, this draft is intended to
provide a reference which describes those criteria, and could be used
as a partial statement of requirements for a technique to solve the
problem of spam.
Obviously this is just my own 2c at the moment, so let me know, preferably on the asrg list) what
your opinions are and I'll modify, abandon or replace this as
FYI the abstract reads:
"The Internet Research Task Force Anti-Spam Research Group (ASRG) is
frequently presented with proposals for techniques for managing spam
from authors who wish to elicit an expert critique of their
proposals. In many cases proposals fall foul of issues and risks
which are well known and understood by members of the ASRG. This
Internet Draft is intended to enumerate and explain a number of the
more important of the criteria which tend to be applied. This
document will then serve as a normative checklist for anyone wishing
to present a technique to the ASRG."
- ► 2010 (20)
- ► 2009 (59)
- ► 2008 (50)
- The past is another country; but you can see it fr...
- Criteria for judging proposed "solutions" to the p...
- Is spam going to kill SMTP?
- jSPF passes all the tests
- Mailet API getting some independance
- 123 - I love you
- Consumer hell
- labels and post by email
- USB Turntable
- .. and finally ... how I got it all together (or w...
- Demolition III
- ... From my phone, at last!
- blog by mail from my mobile
- New address same old nonsense
- Mailet Annotations - Proof of concept.
- VERP, Mailet, and James
- More Uninformative Exceptions (in the sense of mo...
- I want a phoney Phd
- ClassCastException - why so coy?
- Did I ever do that? How about searchable commit me...
- Apache James at Apachecon EU 2007 ?
- ▼ January (23)
Thursday, January 18, 2007
Securing Apache Hadoop Distributed File System (HDFS) - part IV - This is the fourth in a series of blog posts on securing HDFS. The first post described how to install Apache Hadoop, and how to use POSIX permissions and ...14 hours ago
The Apache Software Foundation Announces Apache® cTAKES™ v4.0 - *Widely adopted Open Source biomedical data extraction, annotation, and clinical information management platform now faster and easier to use.* *Forest Hil...1 day ago
ApacheCon Seville 2016 – Building a Container Solution on Top of Apache CloudStack- Steve Roles - Building a Container Solution on Top of Apache CloudStack- Steve Roles Cloud native applications running in containerised environments look set to create a...2 months ago
You’re invited to help us celebrate an unlikely pairing in open source - We are just days away from reaching a significant milestone for our team and the open source and open standards communities: the first anniversary of Micro...4 years ago
I know nothing, I'm not a fortune teller, and you'd be insane to think that I am. This disclaimer was cribbed from an email footer I once received. It is so ridiculous I had to have it for myself.
Statements in this blog that are not purely historical are forward-looking statements including, without limitation, statements regarding my expectations, objectives, anticipations, plans, hopes, beliefs, intentions or strategies regarding the future. Factors that could cause actual results to differ materially from the forward looking statements include risks and uncertainties such as any unforeseen event or any unforeseen system failures, and other risks. It is important to note that actual outcomes could differ materially from those in such forward-looking statements.
Danny Angus Copyright © 2006-2013 (OMG that's seven years of this nonsense)