from localhost (localhost [127.0.0.1])
	by phobos.labs.netnoteinc.com (Postfix) with ESMTP id B8178440E0
	for <jm@localhost>; Mon, 12 Aug 2002 05:57:11 -0400 (EDT)
from phobos [127.0.0.1]
	by localhost with IMAP (fetchmail-5.9.0)
	for jm@localhost (single-drop); Mon, 12 Aug 2002 10:57:11 +0100 (IST)
from xent.com ([64.161.22.236]) by dogma.slashnull.org
    (8.11.6/8.11.6) with ESMTP id g7BHplb08986 for <jm@jmason.org>;
    Sun, 11 Aug 2002 18:51:47 +0100
from lair.xent.com (localhost [127.0.0.1]) by xent.com (Postfix)
    with ESMTP id 1B4B6294183; Sun, 11 Aug 2002 10:48:06 -0700 (PDT)
from barry.mail.mindspring.net (barry.mail.mindspring.net
    [207.69.200.25]) by xent.com (Postfix) with ESMTP id A0018294182 for
    <fork@xent.com>; Sun, 11 Aug 2002 10:47:31 -0700 (PDT)
from user-119ac86.biz.mindspring.com ([66.149.49.6]) by
    barry.mail.mindspring.net with esmtp (Exim 3.33 #1) id 17dwpN-0008U1-00;
    Sun, 11 Aug 2002 13:48:33 -0400
Fwd: [camram-spam] another framework hashcash related framework
From fork-admin@xent.com  Mon Aug 12 11:10:30 2002

Subject: Fwd: [camram-spam] another framework hashcash related framework
Reply-To: "Usual People List" <usual@espace.net>
Mailing-List: contact camram-spam-help@camram.org; run by ezmlm
Subject: [camram-spam] another framework hashcash related framework
There is a framework for using a hashcash like proof of work function
as a way to frustrate junk mailers in this paper:
"Curbing Junk E-Mail via Secure Classification"
by E. Gabber, M. Jakobsson, Y. Matias, A. Mayer Bell
(Look in the view or download section at the top right, it's
availabile in at least .pdf and .ps formats).
The framework they propose with proxies etc looks a lot like the
current camram architecture, with a proof of work to get on a white
list.  They use target revokable email addresses (basically identical
to the LWPA concept) to implement the white list.
The resulting framework is essentially identical to what I proposed in
Subject: target revokable email addresses, and postage-free tokens
Their idea of including the postage free-token in the email address,
mirrors what is done in LWPA and makes the system exhibit smoother
migration for non-users.  eg. you can use varied sender addresses and
it will still work, you can forward the email address to someone else
They have some software architecture diagrams and suggestions for
installing some of the proxies on a corporate gateway -- "gatekeeper"
For additional commands, e-mail: camram-spam-help@camram.org