[Asrg] Passive Spam Revocation

Yao Ziyuan <yaoziyuan@gmail.com> Mon, 26 October 2009 04:45 UTC

Return-Path: <yaoziyuan@gmail.com>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost []) by core3.amsl.com (Postfix) with ESMTP id DA1073A689C for <asrg@core3.amsl.com>; Sun, 25 Oct 2009 21:45:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.711
X-Spam-Level: **
X-Spam-Status: No, score=2.711 tagged_above=-999 required=5 tests=[AWL=2.710, BAYES_50=0.001]
Received: from mail.ietf.org ([]) by localhost (core3.amsl.com []) (amavisd-new, port 10024) with ESMTP id ZEPD0SnijaZH for <asrg@core3.amsl.com>; Sun, 25 Oct 2009 21:45:00 -0700 (PDT)
Received: from mail-fx0-f205.google.com (mail-fx0-f205.google.com []) by core3.amsl.com (Postfix) with ESMTP id A149F3A67AD for <asrg@irtf.org>; Sun, 25 Oct 2009 21:45:00 -0700 (PDT)
Received: by fxm1 with SMTP id 1so12270086fxm.7 for <asrg@irtf.org>; Sun, 25 Oct 2009 21:45:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=kxBaEEvDV6jA5C94EK8bVe/2Xv9W7yz22t9E8BJFDeg=; b=v6Sm9OseysclCkmrPUzsGGhKkZT0kXCyZCF9VC14TY3r79Eu5H0h1f77xhh+N5BQke 5sAAn+O2Tv9bNRewGf5DvEbiOAgQOIglJlPyD88G6meeLKkDvvx2s+cTAQrhPdtLm7N6 4T9fvBrY6qO9kMO8PuLmMNa3FPkmJoSZSWn04=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=pjaXdCXSfxyzO0EutU2XbCQlPEoQbT4HXhzRt5ReL+b1cg7cvQdPtl5LzDdOoktu+5 /fnqNSM49yS+X59olBP1d9kvuKYYpA5FkbBt2oSF1MqEPiVXJTBkRD3tppXHwGLRaOij zLaJ9ScsZEzfD0ELs5lOLkA4p9f2Yn6wlP0WE=
MIME-Version: 1.0
Received: by with SMTP id l23mr5506948bkw.135.1256532312195; Sun, 25 Oct 2009 21:45:12 -0700 (PDT)
Date: Mon, 26 Oct 2009 12:45:12 +0800
Message-ID: <6679e0500910252145j69e51a6frb2cd90c86dff4bb4@mail.gmail.com>
From: Yao Ziyuan <yaoziyuan@gmail.com>
To: asrg@irtf.org
Content-Type: text/plain; charset=UTF-8
Subject: [Asrg] Passive Spam Revocation
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Oct 2009 04:45:58 -0000

Passive Spam Revocation (PSR)

Currently almost all mail systems (e.g. Hotmail and Gmail) use a spam
filter, which can drop good and important messages.

I propose an optional feature for current mail systems. The main idea
is if a message is considered spam, this spam status can be tracked by
the sender (but not sent to him directly, as the From field can be
faked). The message can be re-marked as "not spam" if the sender can
solve a CAPTCHA.

STEP 1: A is going to send B a message. A's mail client generates a
random code and puts it in a custom field in the outgoing message's
    PSR-Code: <random code>
STEP 2: A's mail client sends the message, waits 30 seconds, and then visits:
    https://spamstatus.<B's mail domain>/?msgid=<Message-ID>&code=<PSR-Code>
This page displays one of these possible "spam statuses":
    * MESSAGE CONSIDERED SPAM. (A CAPTCHA is also presented below.)
    * All other responses mean B's mail system doesn't support this feature.
In the first case, A's mail client will report the status and the
CAPTCHA to A. A can choose to solve the CAPTCHA to prove the message
is not spam.

Like the idea? Here is the official Google group for it:

Yao Ziyuan