Re: ASRG/Filtering List Launch: "Let the games begin!"

   From: John Graham-Cumming <[email protected]>

   > 1. A standard header to be produced by the filters that can be used by 
   > the end-user's MUA. Having a standard header may reduce the complexity 
   > that the user needs to go through when configuring his MUA to parse 
   > filtering results.

   A good starting point might be to review the headers that current 
   implementations are inserting to understand the intent of each header 
   and how it is used.   POPFile adds two headers to each message:

   X-Text-Classification: <class>

CRM114 mailfilter does something similar...

X-CRM114-Status: (Good|SPAM) then some statistics.

Though I am perfectly willing to change it to X-Text-Classification.

We should also include a tag so debugging people can tell what 
happened where.

   > 2. Ways for filters to share information dynamically including possible 
   > standards for formats and protocols. This may encompass dynamic updates 
   > like anti-virus programs do, dynamic sharing of filtering data in 
   > real-time, collaborative filtering etc.

   There's a lot of this going on with checksum updates.  Are any of the 
   checksum/hash systems on this list?

Jonathan Zdziarski and I have a md5sum-and-shared-secret implementation
that we've submitted to the IETF.

(actually, a pair of implementations- both DSPAM and CRM114 now have it.

It's slowly winding it's way through the approvals process.

(and getting good edits on the way.  I'm impressed).

     -Bill Yerazunis