Re: [Asrg] request for review for a non FUSSP proposal

Jose-Marcio Martins da Cruz <Jose-Marcio.Martins@mines-paristech.fr> Wed, 24 June 2009 09:55 UTC

Return-Path: <Jose-Marcio.Martins@mines-paristech.fr>
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 43B113A682D for <asrg@core3.amsl.com>; Wed, 24 Jun 2009 02:55:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.249
X-Spam-Level:
X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35]
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 ar3IrXILRvor for <asrg@core3.amsl.com>; Wed, 24 Jun 2009 02:55:02 -0700 (PDT)
Received: from boipeva.ensmp.fr (cobra.ensmp.fr [194.214.158.101]) by core3.amsl.com (Postfix) with ESMTP id 53D643A6B24 for <asrg@irtf.org>; Wed, 24 Jun 2009 02:55:02 -0700 (PDT)
Received: from localhost.localdomain (minho.ensmp.fr [10.3.5.5]) (authenticated bits=0) by boipeva.ensmp.fr (8.14.3/8.14.3/JMMC-11/Feb/2009) with ESMTP id n5O9tDhj016757 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 24 Jun 2009 11:55:13 +0200 (MEST)
Message-ID: <4A41F87F.4040506@mines-paristech.fr>
Date: Wed, 24 Jun 2009 11:57:19 +0200
From: Jose-Marcio Martins da Cruz <Jose-Marcio.Martins@mines-paristech.fr>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.21) Gecko/20090507 Fedora/1.1.16-1.fc11 SeaMonkey/1.1.16
MIME-Version: 1.0
To: Ian Eiloart <iane@sussex.ac.uk>
References: <20090623213728.1825.qmail@simone.iecc.com> <4A41D773.50508@telmon.org> <4A41E506.2010106@mines-paristech.fr> <008E8EE8BFAAE1C24E4F75DF@lewes.staff.uscs.susx.ac.uk>
In-Reply-To: <008E8EE8BFAAE1C24E4F75DF@lewes.staff.uscs.susx.ac.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Miltered: at boipeva with ID 4A41F801.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 4A41F801.000/10.3.5.5/minho.ensmp.fr/localhost.localdomain/<Jose-Marcio.Martins@mines-paristech.fr>
Cc: Anti-Spam Research Group - IRTF <asrg@irtf.org>
Subject: Re: [Asrg] request for review for a non FUSSP proposal
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Jose-Marcio.Martins@mines-paristech.fr, 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: Wed, 24 Jun 2009 09:55:03 -0000

Ian Eiloart wrote:

> 
> He uses a secretary to filter his email. If only we all had that 
> resource. Instead, my 12,000 users have me and a bunch of rules that I 
> maintain.

An automated secretary...

> A better example of consent is spamcop. If you want to report a spam 
> message to them, you can send it to an email address like 
> submit.xxxxxxxxxxxxxxxx@spam.spamcop.net where xxxxxxxxxxxxxxxx is an 
> apparently random string. Perhaps it carries some cryptographic 
> authentication which prevents others from using it, perhaps not, so I've 
> obfuscated it. I can't remember how I got the string - probably from a 
> web form - I just keep it in my address book.

Well, you submited my message to spamcop... ;-). Their address was in the list of 
recipients...

> I wonder whether creating a standard just makes the idea easier to 
> attack through automated means. I have, for example, a mechanism that 

That's a good point.

> prevents people spoofing local email (ie pretending the sender is in our 
> domain when the recipient is in our domain). I could have used something 
> clever, but went for something simple and very easy to attack. However, 
> it's still working some years later, and has in the meantime kept our 
> internal email pretty spam free. If someone does attack it, I'll do 
> something more principled.

You're right. A standard will just work till the moment it will be cracked. And after that 
the standard will be droped down and people will go back to their own home made rules.

Either way, a good point to think when proposing a standard is if people is open to it. 
E.g., is spamcop open to replace their consent mechanism by a standard one ?

JM