Re: [Asrg] DNS-based Email Sender Authentication Mechanisms: aCritical Review

Jose-Marcio Martins da Cruz <Jose-Marcio.Martins@mines-paristech.fr> Mon, 25 May 2009 21:19 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 B6DD83A6AC7 for <asrg@core3.amsl.com>; Mon, 25 May 2009 14:19:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, URIBL_GREY=0.25]
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 WjQoxCQOLEfd for <asrg@core3.amsl.com>; Mon, 25 May 2009 14:19:13 -0700 (PDT)
Received: from boipeva.ensmp.fr (cobra.ensmp.fr [194.214.158.101]) by core3.amsl.com (Postfix) with ESMTP id BB78D3A6A08 for <asrg@irtf.org>; Mon, 25 May 2009 14:19:12 -0700 (PDT)
Received: from localhost.localdomain (joe.j-chkmail.org [88.168.143.55]) (authenticated bits=0) by boipeva.ensmp.fr (8.14.3/8.14.3/JMMC-11/Feb/2009) with ESMTP id n4PLKltK028291 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <asrg@irtf.org>; Mon, 25 May 2009 23:20:48 +0200 (MEST)
Message-ID: <4A1B0C0C.5010703@mines-paristech.fr>
Date: Mon, 25 May 2009 23:22:20 +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.fc10 SeaMonkey/1.1.16
MIME-Version: 1.0
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
References: <003d01c9dd01$bf3531d0$800c6f0a@china.huawei.com> <4A1A45BA.5030704@swin.edu.au> <3be421270905250718y5d62f6d5odb6f2bebecf418d0@mail.gmail.com> <6684E747-55CB-4BB3-B838-9F4FE906AFE7@mail-abuse.org> <3be421270905251345l1bbe8ce9je5554b727e7440a7@mail.gmail.com>
In-Reply-To: <3be421270905251345l1bbe8ce9je5554b727e7440a7@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Miltered: at boipeva with ID 4A1B0BAF.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 4A1B0BAF.000/88.168.143.55/joe.j-chkmail.org/localhost.localdomain/<Jose-Marcio.Martins@mines-paristech.fr>
X-Mailman-Approved-At: Tue, 26 May 2009 14:57:28 -0700
Subject: Re: [Asrg] DNS-based Email Sender Authentication Mechanisms: aCritical Review
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: Mon, 25 May 2009 21:20:20 -0000

Amir Herzberg wrote:
> On Mon, May 25, 2009 at 6:54 PM, Douglas Otis <dotis@mail-abuse.org 
> <mailto:dotis@mail-abuse.org>> wrote:
> 
>     http://amir.herzberg.googlepages.com/somerecentpapers
> 
>     This paper refers to DNS poisoning without fully exploring how SPF
>     might be used to enable DNS poisoning.  SPF might be checked by MUAs
>     in some cases.   More than just resolvers associated with MTAs are
>     affected, so separate resolvers for MTAs, which themselves might
>     become poisoned, does not represent a good solution. 
> 
> 
> Sorry - I simply was not aware of SPF checks being invoked by MUAs. I 
> actually find it a bit strange that MUAs would do SPF validations, 
> considering they don't get MAIL FROM, but human ingenuity is endless and 
> I apologize for this ignorance. Doug, can you give me specific examples 
> - preferably of common MUA clients and if possible, of appropriate 
> documentation so I can read about it and/or test it? Tks!

Well. Me too, I don't understand why it could be interesting to check SPF in the MUA. It 
may be interesting to check SPF when one have access to both sender domain and IP address 
of the SMTP client connecting to the MTA. This information isn't usually available to the 
MUA, unless it will trust on data available on headers.