Re: [Asrg] Passive Spam Revocation

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

Return-Path: <yaoziyuan@gmail.com>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2371128C1DF for <asrg@core3.amsl.com>; Mon, 26 Oct 2009 02:03:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.779
X-Spam-Level:
X-Spam-Status: No, score=-0.779 tagged_above=-999 required=5 tests=[AWL=1.821, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qhQigLgoIDSq for <asrg@core3.amsl.com>; Mon, 26 Oct 2009 02:03:13 -0700 (PDT)
Received: from mail-fx0-f205.google.com (mail-fx0-f205.google.com [209.85.220.205]) by core3.amsl.com (Postfix) with ESMTP id 1200928C1BC for <asrg@irtf.org>; Mon, 26 Oct 2009 02:03:12 -0700 (PDT)
Received: by fxm1 with SMTP id 1so12377865fxm.7 for <asrg@irtf.org>; Mon, 26 Oct 2009 02:03:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=jVvXvck2s7RN0eEH2GvHXpviLzk2E2KrBu1Yt/eB1jA=; b=In7RqIVfxepYLkD/oo8Jkv/FNd/Pbo4GwWNV01jdDrJghDHBa/nkzhJ26UrBTw8mAk bitdNEl0MRTUJYj1Yt8N4C6BRQ+Pwhgi5vZkwOUYT9Jw4BAfYZ9FFROy5abDAgFgIy4J oc7ES/+lVUwda+vzCj1MrmxivBoRKoNuTt3qQ=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=HQG8KPxhpUJi7ZuaxYw7jOKsb9QmWb084qeEXz2N/iV3Bl9K1lrd9w4fezZPP6ESxn FqpqOOerpTVZqRmbbApNetl5SgdVwNapVCOhvHqZmxREaQWdZFFI59vZqpGxOqLjZ7gW wf5aOLE8+SOjcZzyphVOzJsJAfmfZIKjhA16M=
MIME-Version: 1.0
Received: by 10.204.34.194 with SMTP id m2mr11458056bkd.53.1256547801054; Mon, 26 Oct 2009 02:03:21 -0700 (PDT)
In-Reply-To: <6679e0500910252145j69e51a6frb2cd90c86dff4bb4@mail.gmail.com>
References: <6679e0500910252145j69e51a6frb2cd90c86dff4bb4@mail.gmail.com>
Date: Mon, 26 Oct 2009 17:03:21 +0800
Message-ID: <6679e0500910260203u447614e4w8a7afc73eae8d090@mail.gmail.com>
From: Yao Ziyuan <yaoziyuan@gmail.com>
To: asrg@irtf.org
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [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 09:03:14 -0000

On Mon, Oct 26, 2009 at 12:45 PM, Yao Ziyuan <yaoziyuan@gmail.com> wrote:
> 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
> header:
>    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.)
>    * MESSAGE CONSIDERED NOT SPAM.
>    * PENDING. PLEASE TRY AGAIN LATER.
>    * 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.

Showing a message's spam status to the sender can be bad, if he is
really a spammer. So the page can also return:
    * SPAM STATUS HIDDEN. (A CAPTCHA is also presented below.)
This means the sender can solve the CAPTCHA to see the status and
change it to NOT SPAM.

>
> Like the idea? Here is the official Google group for it:
> http://groups.google.com/group/passive-spam-revocation
>
> Regards,
> Yao Ziyuan
> http://sites.google.com/site/yaoziyuan/
>