
From msk@cloudmark.com  Sat Nov 12 21:29:25 2011
Return-Path: <msk@cloudmark.com>
X-Original-To: asrg@ietfa.amsl.com
Delivered-To: asrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5588911E808C for <asrg@ietfa.amsl.com>; Sat, 12 Nov 2011 21:29:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.805
X-Spam-Level: 
X-Spam-Status: No, score=-102.805 tagged_above=-999 required=5 tests=[AWL=-0.206, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WjD8Tm32YFiy for <asrg@ietfa.amsl.com>; Sat, 12 Nov 2011 21:29:24 -0800 (PST)
Received: from ht2-outbound.cloudmark.com (ht2-outbound.cloudmark.com [72.5.239.36]) by ietfa.amsl.com (Postfix) with ESMTP id EB98D11E8089 for <asrg@irtf.org>; Sat, 12 Nov 2011 21:29:24 -0800 (PST)
Received: from EXCH-C2.corp.cloudmark.com ([172.22.1.74]) by spite.corp.cloudmark.com ([172.22.10.72]) with mapi; Sat, 12 Nov 2011 21:29:24 -0800
From: "Murray S. Kucherawy" <msk@cloudmark.com>
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
Date: Sat, 12 Nov 2011 21:27:38 -0800
Thread-Topic: [Asrg] Greylisting BCP
Thread-Index: AcyTxCnkpuRxwrUdRa+YWoof2u7z4QOAJZzg
Message-ID: <F5833273385BB34F99288B3648C4F06F19C6C14FF0@EXCH-C2.corp.cloudmark.com>
References: <F5833273385BB34F99288B3648C4F06F19C6C14AC6@EXCH-C2.corp.cloudmark.com> <alpine.LFD.2.00.1110181539140.27058@nber7.nber.org> <4E9E07D2.4090304@xplornet.com> <18B53BA2A483AD45962AAD1397BE1325382F2CC6A6@UK-EXCHMBX1.green.sophos> <F5833273385BB34F99288B3648C4F06F19C6C14C10@EXCH-C2.corp.cloudmark.com> <4EA7D6FA.5070602@mines-paristech.fr>
In-Reply-To: <4EA7D6FA.5070602@mines-paristech.fr>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [Asrg] Greylisting BCP
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.12
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/options/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: Sun, 13 Nov 2011 05:29:25 -0000

> -----Original Message-----
> From: Jose-Marcio Martins da Cruz [mailto:Jose-Marcio.Martins@mines-paris=
tech.fr]
> Sent: Wednesday, October 26, 2011 2:47 AM
> To: Anti-Spam Research Group - IRTF
> Cc: Murray S. Kucherawy
> Subject: Re: [Asrg] Greylisting BCP
>=20
> You should take some care with this. Ressource usage varies a lot with di=
fferent implementations :
> you'll find in memory chained lists, some RDBMS (e.g. MySQL) or ISAM/B-Tr=
ee/HASH (e.g. BerkeleyDB).
> Some implementations are smarter than others about ressources needes :
> e.g. how to expire old entries or how to aggregate them. And this makes
> a big difference on how expensive the filter is.
>=20
> Put simply, when talking about greylisting, expensive or not is more
> related to the implementation and to some tuning (e.g. delays) than to
> the method itself. I'm not even talking about poor programming
> practices...

The point is that there is a range of expenses based on the implementation,=
 the cost is rarely zero or even close to it.  I don't think it's necessary=
 to run up a full bill of materials for each possible implementation in the=
 BCP, but merely to make it clear that the benefits have a definite cost as=
sociated with them in terms of resources.

From msk@cloudmark.com  Sat Nov 12 21:29:26 2011
Return-Path: <msk@cloudmark.com>
X-Original-To: asrg@ietfa.amsl.com
Delivered-To: asrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6ABD311E8097 for <asrg@ietfa.amsl.com>; Sat, 12 Nov 2011 21:29:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.303
X-Spam-Level: 
X-Spam-Status: No, score=-103.303 tagged_above=-999 required=5 tests=[AWL=0.296, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pARwwJErLKx3 for <asrg@ietfa.amsl.com>; Sat, 12 Nov 2011 21:29:26 -0800 (PST)
Received: from ht1-outbound.cloudmark.com (ht1-outbound.cloudmark.com [72.5.239.35]) by ietfa.amsl.com (Postfix) with ESMTP id EE5D811E8089 for <asrg@irtf.org>; Sat, 12 Nov 2011 21:29:25 -0800 (PST)
Received: from EXCH-C2.corp.cloudmark.com ([172.22.1.74]) by malice.corp.cloudmark.com ([172.22.10.71]) with mapi; Sat, 12 Nov 2011 21:29:25 -0800
From: "Murray S. Kucherawy" <msk@cloudmark.com>
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
Date: Sat, 12 Nov 2011 21:28:33 -0800
Thread-Topic: [Asrg] Greylisting BCP
Thread-Index: AcyTxhP3WGiUIiGESmqLDfbGw+A3dwN/ux3g
Message-ID: <F5833273385BB34F99288B3648C4F06F19C6C14FF1@EXCH-C2.corp.cloudmark.com>
References: <F5833273385BB34F99288B3648C4F06F19C6C14AC6@EXCH-C2.corp.cloudmark.com> <alpine.LFD.2.00.1110181539140.27058@nber7.nber.org> <4E9E07D2.4090304@xplornet.com> <18B53BA2A483AD45962AAD1397BE1325382F2CC6A6@UK-EXCHMBX1.green.sophos> <F5833273385BB34F99288B3648C4F06F19C6C14C10@EXCH-C2.corp.cloudmark.com> <4EA7D6FA.5070602@mines-paristech.fr> <4EA7D80E.7090107@pscs.co.uk>
In-Reply-To: <4EA7D80E.7090107@pscs.co.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [Asrg] Greylisting BCP
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.12
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/options/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: Sun, 13 Nov 2011 05:29:26 -0000

> -----Original Message-----
> From: asrg-bounces@irtf.org [mailto:asrg-bounces@irtf.org] On Behalf Of P=
aul Smith
> Sent: Wednesday, October 26, 2011 2:51 AM
> To: Anti-Spam Research Group - IRTF
> Subject: Re: [Asrg] Greylisting BCP
>=20
> On the other hand, if it stops a reasonable amount of spam, it reduces
> bandwidth, processing time and storage requirements, as well as human
> time & annoyance handling the spam.
>=20
> It's up to the implementer to decide whether the cost of implementing
> greylisting is more or less than the cost of not implementing it.

Right.  Enumerating such tradeoff considerations is ideal material for a do=
cument such as this one.

From msk@cloudmark.com  Sat Nov 12 21:51:09 2011
Return-Path: <msk@cloudmark.com>
X-Original-To: asrg@ietfa.amsl.com
Delivered-To: asrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4739321F88B7 for <asrg@ietfa.amsl.com>; Sat, 12 Nov 2011 21:51:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.306
X-Spam-Level: 
X-Spam-Status: No, score=-103.306 tagged_above=-999 required=5 tests=[AWL=0.293, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id K7NpeblNMNid for <asrg@ietfa.amsl.com>; Sat, 12 Nov 2011 21:51:08 -0800 (PST)
Received: from ht1-outbound.cloudmark.com (ht1-outbound.cloudmark.com [72.5.239.35]) by ietfa.amsl.com (Postfix) with ESMTP id 9486121F84AB for <asrg@irtf.org>; Sat, 12 Nov 2011 21:51:07 -0800 (PST)
Received: from EXCH-C2.corp.cloudmark.com ([172.22.1.74]) by malice.corp.cloudmark.com ([172.22.10.71]) with mapi; Sat, 12 Nov 2011 21:51:07 -0800
From: "Murray S. Kucherawy" <msk@cloudmark.com>
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
Date: Sat, 12 Nov 2011 21:51:06 -0800
Thread-Topic: [Asrg] Microsoft takes over British Telecom
Thread-Index: AcyWG/6gzjtdSRqQTZ+mMp8R9kIC0gLq0qJg
Message-ID: <F5833273385BB34F99288B3648C4F06F19C6C14FF2@EXCH-C2.corp.cloudmark.com>
References: <F5833273385BB34F99288B3648C4F06F19C6C14AC6@EXCH-C2.corp.cloudmark.com> <029601cc9007$f2b94260$4001a8c0@gateway.2wire.net> <45A794EA-C3C4-4BB1-82EB-E8BA4781C947@blighty.com> <4EA4270F.7000304@tana.it> <28CC846A-5815-4179-BABF-A2007B7E6242@blighty.com> <4EA48445.4080001@pscs.co.uk> <6F5BD180-6BB6-4B2E-9D2A-BF47ADE204CA@blighty.com> <4EA4AF0D.2000000@pscs.co.uk> <4EA5328D.8060100@tana.it> <4EA71EE5.2010603@mail-abuse.org> <4EA7F768.6040100@tana.it> <4EAAF44D.4020705@mail-abuse.org> <4EAB5911.9010203@pscs.co.uk> <4EABC46B.3010903@pscs.co.uk>
In-Reply-To: <4EABC46B.3010903@pscs.co.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [Asrg] Microsoft takes over British Telecom
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.12
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/options/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: Sun, 13 Nov 2011 05:51:09 -0000

> -----Original Message-----
> From: asrg-bounces@irtf.org [mailto:asrg-bounces@irtf.org] On Behalf Of P=
aul Smith
> Sent: Saturday, October 29, 2011 2:16 AM
> To: Anti-Spam Research Group - IRTF
> Subject: Re: [Asrg] Microsoft takes over British Telecom
>=20
> I've been thinking about forwarding
>=20
> If you have A -> B, then server B forwards to server C, C can't do any
> authentication based on A, because A doesn't know about the forwarding
> (or it would, presumably, just send to C directly).
>=20
> So, all sender domain authentication fails (without return path
> rewriting)

There's an alternative proposal under development.  The idea is that B eval=
uates the message from A (be that with SPF or DKIM, or something else), and=
 then applies an Authentication-Results (RFC5451) field with its findings. =
 When it relays toward C, it DKIM-signs the augmented message first.  When =
C gets it, it verifies B's signature, and then it can use the contents of t=
he Authentication-Results field that B added to determine whether use of A'=
s domain was authorized, even if A's signature no longer validates (and pre=
sumable A's SPF policy is guaranteed to fail at this point).  There must, o=
f course, be an out-of-band arrangement that C trusts what B claims already=
 in place for this to work.

That's the theory.  The specific mechanics and abuse defenses are still evo=
lving.  The term "transitive trust" is being batted around as a label for t=
he concept.  It's actually in production at a couple of large mailbox provi=
ders already.

I've spoken to people at IETF about the DANE idea, and it's universally con=
sidered a dead end, mostly because it simply doesn't scale and is ineffecti=
ve against infected machines that otherwise can get authorization in the fi=
rst place.  DANE is really designed to authorize use of domain names with r=
espect to web pages, I believe, and not to authenticate clients.

-MSK

From johnl@iecc.com  Mon Nov 14 01:42:04 2011
Return-Path: <johnl@iecc.com>
X-Original-To: asrg@ietfa.amsl.com
Delivered-To: asrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5FD6E21F8F3E for <asrg@ietfa.amsl.com>; Mon, 14 Nov 2011 01:42:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.569
X-Spam-Level: 
X-Spam-Status: No, score=-102.569 tagged_above=-999 required=5 tests=[AWL=0.031, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cRgECKvqcNaY for <asrg@ietfa.amsl.com>; Mon, 14 Nov 2011 01:42:01 -0800 (PST)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id 53D2721F8D70 for <asrg@irtf.org>; Mon, 14 Nov 2011 01:40:54 -0800 (PST)
Received: (qmail 41716 invoked from network); 14 Nov 2011 09:40:51 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:mime-version:content-type:vbr-info:user-agent:cleverness; s=a2f3.4ec0e223.k1111; bh=BCZyBz1qfx5y5llfMEohYJbDfmtiw7Ffm+jmIUK6rZ4=; b=ZZgb1K3mQy/4qBzceUe/D2ZWDhH7mPBesB+X7/o4CSjNsHq6UGC3bkbm/jX5sYb8ZRPQ7seSUvO8YcPi+SePvLMegiiP6JNH8GQ7NatJmX2g9cMJ6jtaEgz8E28pN44WMslZXpk9Y4VLvoavvvv+DTSt11ZgYvVh8OV3/fkuOHE=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Received: (ofmipd 127.0.0.1) with (DHE-RSA-AES256-SHA encrypted) SMTP; 14 Nov 2011 09:40:28 -0000
Date: 14 Nov 2011 17:40:49 +0800
Message-ID: <alpine.BSF.2.00.1111141740230.2169@joyce.lan>
From: "John R. Levine" <johnl@iecc.com>
To: "Anti Spam Research Group" <asrg@irtf.org>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
Cleverness: None detected
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Subject: [Asrg] anti-spam updates for ISOC from the ASRG (fwd)
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.12
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/options/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, 14 Nov 2011 09:42:04 -0000

---------- Forwarded message ----------
Date: Mon, 14 Nov 2011 16:16:23 +0800
From: Joel M Snyder <Joel.Snyder@Opus1.COM>
Subject: anti-spam updates for ISOC from the ASRG

I am working with Sally Wentworth at ISOC on an update to ISOC's 
anti-spam web pages.  I wonder if the ASRG folks would be willing to take a 
look at what Sally sent out and offer up any comments or suggestions?

Sally's motivation is that some ITU Member States are proposing to define spam 
and include provisions related to spam in the ITR treaty at the WCIT.  In 
preparation for this, she thought it was time to update ISOC's anti-spam 
websites to highlight what the technical, policy and commercial communities are 
doing to combat spam and unwanted traffic (without the "assistance" of a 
treaty).

Here are the questions I have. I don't know whether you're comfortable with 
just passing them along (which would be fine with me) or whether you think I 
should try and connect more directly or whether you think  I should just go 
away and be quiet?

We are looking for short statements and pointers to work in the following 
areas:

- general description of the spam problem, including definitions, statistics, 
academic research in the area, and other general overview discussion.  The less 
commercial the better.

- general discussion of technical solutions to spam, such as CPE filtering, 
cloud filtering, reputation systems,   Any overview descriptions, comparisons, 
research, surveys.  Again, nothing product-comparative.  Remember, short 
statements and/or pointers to other people's work.

- pointers to product lists, if they are current and generally comprehensive.

- ISOC activities (including IETF, etc.).  A single statement and a pointer to 
an RFC, paper, document, working group, etc.

- architecture of a policy-based anti-spam solution; components of the solution 
and how they fit together.  Short statements, or pointers to discussions.

- current players (other than ISOC) in the policy-based anti-spam front.  This 
would include governmental and NGO policy groups helping to craft policy, 
industry groups, etc.  Anyone, in short, who is hoping to help write or 
influence legislation, regulation, or policy regarding spam.

- current anti-spam policies/legislation/regulation AND a statement of 
evaluation.  (e.g,, pointer to CAN-SPAM and an admission that it doesn't seem 
to have done anything)

Thanks for any help, guidance, or advice you might have!

jms

-- 
Joel M Snyder, 1404 East Lind Road, Tucson, AZ, 85719
Senior Partner, Opus One       Phone: +1 520 324 0494
jms@Opus1.COM                http://www.opus1.com/jms

From johnl@iecc.com  Mon Nov 14 01:56:57 2011
Return-Path: <johnl@iecc.com>
X-Original-To: asrg@ietfa.amsl.com
Delivered-To: asrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 893611F0C9E for <asrg@ietfa.amsl.com>; Mon, 14 Nov 2011 01:53:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.571
X-Spam-Level: 
X-Spam-Status: No, score=-102.571 tagged_above=-999 required=5 tests=[AWL=0.029, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 39DVkLo6IPTX for <asrg@ietfa.amsl.com>; Mon, 14 Nov 2011 01:52:37 -0800 (PST)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id 00C4321F8F65 for <asrg@irtf.org>; Mon, 14 Nov 2011 01:46:45 -0800 (PST)
Received: (qmail 43012 invoked from network); 14 Nov 2011 09:46:11 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:mime-version:content-type:vbr-info:user-agent:cleverness; s=a801.4ec0e363.k1111; bh=OX87s38hext3NeIg6Y7Vy8o98CQ2fVCtCt+EmSrbS1U=; b=QmCHBqSo3olT43soJy+fLwihoZGyHC+6o7dxJ+wT/LBtewuyAd6LmCbNlRbyip2aHXgePJs5pBmd0RGca/zZ0+XyBS+7B6aR4W3Y2WHGv2lMiTwDov0mdEK09DKWOBFHyJKgE1gw2iLl/acTULhEcPA0saUiLTvUT69qRWzOBRw=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Received: (ofmipd 127.0.0.1) with (DHE-RSA-AES256-SHA encrypted) SMTP; 14 Nov 2011 09:45:48 -0000
Date: 14 Nov 2011 17:46:09 +0800
Message-ID: <alpine.BSF.2.00.1111141745290.2169@joyce.lan>
From: "John R. Levine" <johnl@iecc.com>
To: "Anti Spam Research Group" <asrg@irtf.org>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
Cleverness: None detected
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Subject: Re: [Asrg] anti-spam updates for ISOC from the ASRG (fwd)
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.12
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/options/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, 14 Nov 2011 09:56:57 -0000

I sent this initial response to Joel.  Please cc him on any traffic here 
since he's not currently on the list.

R's,
John

---------- Forwarded message ----------
Date: Mon, 14 Nov 2011 16:59:02 +0800 (CST)
From: John R. Levine <johnl@iecc.com>
To: Joel M Snyder <Joel.Snyder@Opus1.COM>

> We are looking for short statements and pointers to work in the following 
> areas:

This stuff is all available (other than perhaps a useful list of anti-spam 
products, since there's a vast number, mostly lousy) but it's a considerable 
amount of work to pull it all together.

> - current players (other than ISOC) in the policy-based anti-spam front. This 
> would include governmental and NGO policy groups helping to craft policy, 
> industry groups, etc.  Anyone, in short, who is hoping to help write or 
> influence legislation, regulation, or policy regarding spam.

Hmmm.  The OECD has a fairly good anti-spam framework which is getting old but 
that they're starting to revise.  I'd start with that.

> - current anti-spam policies/legislation/regulation AND a statement of 
> evaluation.  (e.g,, pointer to CAN-SPAM and an admission that it doesn't seem 
> to have done anything)

CAN SPAM hasn't been very useful, not so much because it's opt-out, but because 
the effort to bring suit is enormous.  The FTC has whacked some spammers, 
there's been a handful of criminal and civil cases, but not a whole lot.

The EU's spam directive, which has been implemented to a greater or lesser 
degree in all the member countries, has been pretty effective against spam 
that's not wholly criminal.  AU and NZ have pretty good laws, CA has a new one 
based on the earlier ones.

The majority of spam these days is utterly illegal just about everywhere, sent 
using stolen resources advertising fraudulent stuff.  That doesn't so much need 
new laws as it needs better coordination among law enforcement in various 
countries, cooperation between network operators and LE as well as identifying 
and dealing with a relatively small numbers of networks that are run for or by 
crooks.

Regards,
John Levine, johnl@iecc.com, Primary Perpetrator of "The Internet for Dummies",
Please consider the environment before reading this e-mail. http://jl.ly

From vesely@tana.it  Mon Nov 14 02:22:17 2011
Return-Path: <vesely@tana.it>
X-Original-To: asrg@ietfa.amsl.com
Delivered-To: asrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 38A9B21F8468 for <asrg@ietfa.amsl.com>; Mon, 14 Nov 2011 02:22:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.582
X-Spam-Level: 
X-Spam-Status: No, score=-4.582 tagged_above=-999 required=5 tests=[AWL=0.137,  BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5Z-IUPs6h+yn for <asrg@ietfa.amsl.com>; Mon, 14 Nov 2011 02:22:13 -0800 (PST)
Received: from wmail.tana.it (wmail.tana.it [62.94.243.226]) by ietfa.amsl.com (Postfix) with ESMTP id BA1A821F8446 for <asrg@irtf.org>; Mon, 14 Nov 2011 02:22:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=test; t=1321266131; bh=HL5fR9IbH+gOqbpNP8aUCZYbRURABsmk+KCQWXEHMuw=; l=1259; h=Message-ID:Date:From:MIME-Version:To:References:In-Reply-To: Content-Transfer-Encoding; b=TR0ldjbOyfAMA0ND0EWwv8uq5sIkpyGHXMROsIKbk8hLwW3btbDeO+NWpR+7MQXDu 1DWBnZITznxMfGs0rKsJ0bc0KwX0iU2lNDbr24R11yTPgXYPLKX5bErrXHLMna+tCu FaotUNPt87BSbQ/DyAMzp8TcZou93y4gQ95ykE24=
Received: from [172.25.197.158] (pcale.tana [172.25.197.158]) (AUTH: CRAM-MD5 515, TLS: TLS1.0,256bits,RSA_AES_256_CBC_SHA1) by wmail.tana.it with ESMTPSA; Mon, 14 Nov 2011 11:22:11 +0100 id 00000000005DC039.000000004EC0EBD3.00006160
Message-ID: <4EC0EBD2.2070201@tana.it>
Date: Mon, 14 Nov 2011 11:22:10 +0100
From: Alessandro Vesely <vesely@tana.it>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: asrg@irtf.org
References: <F5833273385BB34F99288B3648C4F06F19C6C14AC6@EXCH-C2.corp.cloudmark.com> <029601cc9007$f2b94260$4001a8c0@gateway.2wire.net> <45A794EA-C3C4-4BB1-82EB-E8BA4781C947@blighty.com> <4EA4270F.7000304@tana.it> <28CC846A-5815-4179-BABF-A2007B7E6242@blighty.com> <4EA48445.4080001@pscs.co.uk> <6F5BD180-6BB6-4B2E-9D2A-BF47ADE204CA@blighty.com> <4EA4AF0D.2000000@pscs.co.uk> <4EA5328D.8060100@tana.it> <4EA71EE5.2010603@mail-abuse.org> <4EA7F768.6040100@tana.it> <4EAAF44D.4020705@mail-abuse.org> <4EAB5911.9010203@pscs.co.uk> <4EABC46B.3010903@pscs.co.uk> <F5833273385BB34F99288B3648C4F06F19C6C14FF2@EXCH-C2.corp.cloudmark.com>
In-Reply-To: <F5833273385BB34F99288B3648C4F06F19C6C14FF2@EXCH-C2.corp.cloudmark.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: Re: [Asrg] Microsoft takes over British Telecom
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.12
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/options/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, 14 Nov 2011 10:22:17 -0000

On 13/Nov/11 06:51, Murray S. Kucherawy wrote:
>> From: irtf.org On Behalf Of Paul Smith
>> 
>> If you have A -> B, then server B forwards to server C, C can't do any
>> authentication based on A, because A doesn't know about the forwarding
>> (or it would, presumably, just send to C directly).
> 
> There's an alternative proposal under development.

Is participation open?

> B [...] applies an Authentication-Results (RFC5451) field.  When it
> relays toward C, it DKIM-signs the augmented message first.  When C
> gets it, it can use the contents of the Authentication-Results field
> that B added [...] There must, of course, be an out-of-band
> arrangement that C trusts what B claims already in place for this
> to work.

The out-of-band arrangement should be standardized so as to require
the final recipient's as the sole human intervention.  Does this suit
that idea? http://fixforwarding.org/wiki/forwarding_agreement

> That's the theory.  The specific mechanics and abuse defenses are
> still evolving.  The term "transitive trust" is being batted around
> as a label for the concept.  It's actually in production at a
> couple of large mailbox providers already.

A couple?  I thought transitivity implied at least three :-/

From vesely@tana.it  Mon Nov 14 09:53:30 2011
Return-Path: <vesely@tana.it>
X-Original-To: asrg@ietfa.amsl.com
Delivered-To: asrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B9D9311E8329 for <asrg@ietfa.amsl.com>; Mon, 14 Nov 2011 09:53:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.588
X-Spam-Level: 
X-Spam-Status: No, score=-4.588 tagged_above=-999 required=5 tests=[AWL=0.131,  BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lM1SrVoz+djf for <asrg@ietfa.amsl.com>; Mon, 14 Nov 2011 09:53:30 -0800 (PST)
Received: from wmail.tana.it (wmail.tana.it [62.94.243.226]) by ietfa.amsl.com (Postfix) with ESMTP id 01D0C11E8328 for <asrg@irtf.org>; Mon, 14 Nov 2011 09:53:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=test; t=1321293207; bh=AwN0404IEIoqYZHrP2LZ7mOd+/bs1WvAHoa0PsUGD4U=; l=1605; h=Message-ID:Date:From:MIME-Version:To:CC:References:In-Reply-To: Content-Transfer-Encoding; b=IcrUXp7cL/hfkEac9q34rDHRt4Ela+rx4+oE6su02BkcHicBpNeaTaiuB4JfatFmW 9ViGvpg7o0VrfCNuov5FoQk+QIXn241s8NBTQCFywNYUi5sucYnSr44rOzv2mJU6rT 7JyLx9Spaj2YJ/eNZFONdkhVR1b01+0TsBJQpa8c=
Received: from [172.25.197.158] (pcale.tana [172.25.197.158]) (AUTH: CRAM-MD5 515, TLS: TLS1.0,256bits,RSA_AES_256_CBC_SHA1) by wmail.tana.it with ESMTPSA; Mon, 14 Nov 2011 18:53:27 +0100 id 00000000005DC042.000000004EC15597.000032B1
Message-ID: <4EC15597.6020601@tana.it>
Date: Mon, 14 Nov 2011 18:53:27 +0100
From: Alessandro Vesely <vesely@tana.it>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: Joel M Snyder <Joel.Snyder@Opus1.COM>
References: <alpine.BSF.2.00.1111141745290.2169@joyce.lan>
In-Reply-To: <alpine.BSF.2.00.1111141745290.2169@joyce.lan>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Cc: Anti-Spam Research Group - IRTF <asrg@irtf.org>
Subject: Re: [Asrg] anti-spam updates for ISOC from the ASRG (fwd)
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.12
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/options/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, 14 Nov 2011 17:53:30 -0000

>> - current anti-spam policies/legislation/regulation AND a statement
>> of evaluation.  (e.g,, pointer to CAN-SPAM and an admission that it
>> doesn't seem to have done anything)
> 
> [...]
> 
> The EU's spam directive, which has been implemented to a greater or
> lesser degree in all the member countries, has been pretty effective
> against spam that's not wholly criminal.

It is more of an annoyance than an effective practice, IME.

It seems EU is about to revise their Data Protection Directive to make
it tighter[1].  I have no idea how to tell them that in order to work
in Internet, the idea of getting a user's consent has to be
implemented with an adequate protocol.  As an exercise, I tried and
describe how such a protocol could be conceived[2].

[1] http://www.google.com/search?q=%22Reding%22+Aigner&hl=en
[2] http://fixforwarding.org/

Perhaps, if Google and Facebook are willing to comply, they can push
for having a compliable law...

> The majority of spam these days is utterly illegal just about
> everywhere, sent using stolen resources advertising fraudulent stuff. 
> That doesn't so much need new laws as it needs better coordination
> among law enforcement in various countries, cooperation between
> network operators and LE as well as identifying and dealing with a
> relatively small numbers of networks that are run for or by crooks.

Although that's true, I don't think end users are able to distinguish
those categories of spam.  So the bottom line is that they cannot
defend their rights.  Isn't this sufficient to say the law is ineffective?

From martijn.grooten@virusbtn.com  Wed Nov 16 07:18:40 2011
Return-Path: <martijn.grooten@virusbtn.com>
X-Original-To: asrg@ietfa.amsl.com
Delivered-To: asrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A8C2821F90A7 for <asrg@ietfa.amsl.com>; Wed, 16 Nov 2011 07:18:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U1H62-OFbWEA for <asrg@ietfa.amsl.com>; Wed, 16 Nov 2011 07:18:34 -0800 (PST)
Received: from mx2.sophos.com (mx2.sophos.com [145.253.124.138]) by ietfa.amsl.com (Postfix) with ESMTP id 3A14421F8FED for <asrg@irtf.org>; Wed, 16 Nov 2011 07:18:33 -0800 (PST)
Received: from mx2.sophos.com (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id 3E4401881C6 for <asrg@irtf.org>; Wed, 16 Nov 2011 15:18:31 +0000 (GMT)
Received: from uk-exch1.green.sophos (uk-exch1.green.sophos [10.100.199.16]) by mx2.sophos.com (Postfix) with ESMTPS id EAF1E18815E for <asrg@irtf.org>; Wed, 16 Nov 2011 15:18:30 +0000 (GMT)
Received: from UK-EXCHMBX1.green.sophos ([fe80:0000:0000:0000:e1bd:d3c1:23.222.229.221]) by uk-exch1.green.sophos ([10.100.199.16]) with mapi; Wed, 16 Nov 2011 15:18:30 +0000
From: Martijn Grooten <martijn.grooten@virusbtn.com>
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
Date: Wed, 16 Nov 2011 15:18:28 +0000
Thread-Topic: Phishing and domain reputation
Thread-Index: Acykcv4KVfHIjnElSjKwazuj54+mKA==
Message-ID: <18B53BA2A483AD45962AAD1397BE1325382F703703@UK-EXCHMBX1.green.sophos>
Accept-Language: en-US, en-GB
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [Asrg] Phishing and domain reputation
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.12
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/options/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, 16 Nov 2011 15:18:40 -0000

The anti-phishing working group (APWG) published a report on phishing in th=
e first half of 2011:

  http://www.apwg.org/reports/APWG_GlobalPhishingSurvey_1H2011.pdf

Lots of statistics on phishing, such as a significant rise in attacks compa=
red to the previous six months, which was largely due to attacks on Chinese=
 organisations and their customers.

One thing I found interesting, and which prompted me to post about it here,=
 is that only 2% of the phishing domains contained the brand name of a vari=
ation thereof (e.g. paypaI dot com) and they've only seen two examples of p=
hishing attacks using IDNs and homographs (e.g. f=E1cebook dot com) in sinc=
e 2007.

Also, only 18% of the domains used (down from 28%) were registered by the p=
hishers themselves; the other domains were hacked or compromised.

It suggests that phishers do care about the reputation of domains as used b=
y email/web filters (does the domain have a history of legitimate content?)=
, but little about reputation among users (does the domain look like the on=
e I expect for this site?).

I'm not sure about their definition of 'phishing'. This could have some inf=
luence on their statistics.

Martijn.



Virus Bulletin Ltd, The Pentagon, Abingdon, OX14 3YP, England.
Company Reg No: 2388295. VAT Reg No: GB 532 5598 33.

From christian.grunfeld@gmail.com  Thu Nov 17 10:30:09 2011
Return-Path: <christian.grunfeld@gmail.com>
X-Original-To: asrg@ietfa.amsl.com
Delivered-To: asrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C041D11E80C8 for <asrg@ietfa.amsl.com>; Thu, 17 Nov 2011 10:30:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U00W90FpUFJ2 for <asrg@ietfa.amsl.com>; Thu, 17 Nov 2011 10:30:09 -0800 (PST)
Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by ietfa.amsl.com (Postfix) with ESMTP id 0A00C11E8086 for <asrg@irtf.org>; Thu, 17 Nov 2011 10:30:08 -0800 (PST)
Received: by faap15 with SMTP id p15so2609935faa.13 for <asrg@irtf.org>; Thu, 17 Nov 2011 10:30:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; bh=SHWngY/X+Yigzw5ZzkDiowNs1jrnN39+UepPR8dvZwk=; b=gsa83s2nOpFF4pzPEJTZ8BHttKv3Vmkt77OSfHaPCzDBtk7NngW1UJZC3j940GybFK 0QOm1MZ4q5dry6a/ov/bJ6O9jXHsF/DlDBaGlhC513RZVP4chNQucPpanEmYNcvrM1sf 7tO/o8mn25VNpc9CdiyrlgFuKYchPVNww2LAU=
MIME-Version: 1.0
Received: by 10.182.216.105 with SMTP id op9mr11917090obc.57.1321554607805; Thu, 17 Nov 2011 10:30:07 -0800 (PST)
Received: by 10.182.47.103 with HTTP; Thu, 17 Nov 2011 10:30:07 -0800 (PST)
Date: Thu, 17 Nov 2011 15:30:07 -0300
Message-ID: <CAFdugamtPXjEHiwuJ3N2xyaXK+E0yCJfQi6vOey3jyff1UVvgw@mail.gmail.com>
From: Christian Grunfeld <christian.grunfeld@gmail.com>
To: asrg@irtf.org
Content-Type: text/plain; charset=ISO-8859-1
Subject: [Asrg] antiphishing idea
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.12
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/options/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: Thu, 17 Nov 2011 18:32:57 -0000

Hi,

I dont know if this is exactly the right place for discussing my idea
but I want to do a little bit of brainstorming with experts. I come
with a "crazy" thing but the logic is not so bad ! Please dont tell me
"you are crazy" ! .....at least at first time! :p

Users believe in what they read in the header from of the mail ! Users
don't also know about the existence and differences between envelope
and header From. And they also don't know that those addresses can be
forged. They blindly believe !

My idea is to invert the logic of DNSBLs. That is, instead of asking
third parties about spam/phishing why not asking the domain involved
in envelope and header itself about non-spam ?

Domains should have to publish in their DNSs the message-id (among any
other thing) through a TXT or A record of any legit mail sent by them.
The TTLs of those records can be adjusted to compensate for queued
mails, etc.

When you receive a mail from A and "aparently" from B you can query A
and B DNSs looking for the message-id the mail has. If you have a
nxdomain or whatever error from them you can score the mail as
phishing! ..on the other hand if you have a hit from at least one of
them you can be confident that this is the real domain that sends that
mail or it sends it on behalf the real address!

The check against both is to account for multi identities in what one
mailer sends in behalf of another (like gmail). You can also check
against any internal hop in the Received: chain in order to avoid
breaks in the trust chain by means of plain forwarding (as happens in
SPF without SRS).

I know this requires all to implement it in order to work (also like
SPF and DKIM).

Time to think !

Cheers !

From martijn.grooten@virusbtn.com  Thu Nov 17 11:58:25 2011
Return-Path: <martijn.grooten@virusbtn.com>
X-Original-To: asrg@ietfa.amsl.com
Delivered-To: asrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AA6AD1F0C53 for <asrg@ietfa.amsl.com>; Thu, 17 Nov 2011 11:58:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fFhr1JWao9CJ for <asrg@ietfa.amsl.com>; Thu, 17 Nov 2011 11:58:25 -0800 (PST)
Received: from mx6.sophos.com (mx6.sophos.com [213.31.172.36]) by ietfa.amsl.com (Postfix) with ESMTP id 1F05F1F0C44 for <asrg@irtf.org>; Thu, 17 Nov 2011 11:58:23 -0800 (PST)
Received: from mx6.sophos.com (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id 1D36775159C for <asrg@irtf.org>; Thu, 17 Nov 2011 19:58:22 +0000 (GMT)
Received: from uk-exch2.green.sophos (uk-exch2.green.sophos [10.100.199.17]) by mx6.sophos.com (Postfix) with ESMTPS id EEAC9751594 for <asrg@irtf.org>; Thu, 17 Nov 2011 19:58:21 +0000 (GMT)
Received: from UK-EXCHMBX1.green.sophos ([fe80:0000:0000:0000:e1bd:d3c1:23.222.229.221]) by uk-exch2.green.sophos ([10.100.199.17]) with mapi; Thu, 17 Nov 2011 19:58:22 +0000
From: Martijn Grooten <martijn.grooten@virusbtn.com>
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
Date: Thu, 17 Nov 2011 19:58:19 +0000
Thread-Topic: [Asrg] antiphishing idea
Thread-Index: AcylV1yYBmNp5tMeRGKRIi1O8GllsAACf31g
Message-ID: <18B53BA2A483AD45962AAD1397BE1325382F75FA87@UK-EXCHMBX1.green.sophos>
References: <CAFdugamtPXjEHiwuJ3N2xyaXK+E0yCJfQi6vOey3jyff1UVvgw@mail.gmail.com>
In-Reply-To: <CAFdugamtPXjEHiwuJ3N2xyaXK+E0yCJfQi6vOey3jyff1UVvgw@mail.gmail.com>
Accept-Language: en-US, en-GB
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [Asrg] antiphishing idea
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.12
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/options/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: Thu, 17 Nov 2011 19:58:25 -0000

> Domains should have to publish in their DNSs the message-id (among any
> other thing) through a TXT or A record of any legit mail sent by them.
> The TTLs of those records can be adjusted to compensate for queued
> mails, etc.

I take it you mean the message-id is somehow converted into a domain name a=
nd a DNS lookup is performed against that DNS and if the A or TXT record fo=
r that domain is some kind of affirmative value, this means that this is a =
'valid message-id'?

I've got many doubts about this: do people who fall for such scams care abo=
ut the value of From? Doesn't this have the same issues as SPF -all and ADS=
P? Does this scale? But my most important concern is: wouldn't it be trivia=
l to perform a relay attack using this method?

> When you receive a mail from A and "aparently" from B you can query A
> and B DNSs looking for the message-id the mail has. If you have a
> nxdomain or whatever error from them you can score the mail as
> phishing! ..on the other hand if you have a hit from at least one of
> them you can be confident that this is the real domain that sends that
> mail or it sends it on behalf the real address!

I don't get this. Are you saying that if I send an email with MAIL FROM: ex=
ample.com and Header From: paypal.com and the message-id on example.com tha=
t I can then get this message-id validated simply because I happen to contr=
ol example.com?

Martijn.

Virus Bulletin Ltd, The Pentagon, Abingdon, OX14 3YP, England.
Company Reg No: 2388295. VAT Reg No: GB 532 5598 33.

From clewis+ietf@mustelids.ca  Thu Nov 17 13:38:38 2011
Return-Path: <clewis+ietf@mustelids.ca>
X-Original-To: asrg@ietfa.amsl.com
Delivered-To: asrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BE1B91F0C6B for <asrg@ietfa.amsl.com>; Thu, 17 Nov 2011 13:38:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.048
X-Spam-Level: 
X-Spam-Status: No, score=-1.048 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kBZR+Q6A0OvY for <asrg@ietfa.amsl.com>; Thu, 17 Nov 2011 13:38:38 -0800 (PST)
Received: from mail.mustelids.ca (unknown [174.35.130.2]) by ietfa.amsl.com (Postfix) with ESMTP id 4355E1F0C69 for <asrg@irtf.org>; Thu, 17 Nov 2011 13:38:38 -0800 (PST)
Received: from [192.168.0.2] (stoat.mustelids.ca [192.168.0.2]) (authenticated bits=0) by mail.mustelids.ca (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id pAHLcbdW007107 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <asrg@irtf.org>; Thu, 17 Nov 2011 16:38:37 -0500
Message-ID: <4EC57EDD.30808@mustelids.ca>
Date: Thu, 17 Nov 2011 16:38:37 -0500
From: Chris Lewis <clewis+ietf@mustelids.ca>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.8.1.23) Gecko/20090812 Thunderbird/2.0.0.23 Mnenhy/0.7.6.666
MIME-Version: 1.0
To: asrg@irtf.org
References: <CAFdugamtPXjEHiwuJ3N2xyaXK+E0yCJfQi6vOey3jyff1UVvgw@mail.gmail.com> <18B53BA2A483AD45962AAD1397BE1325382F75FA87@UK-EXCHMBX1.green.sophos>
In-Reply-To: <18B53BA2A483AD45962AAD1397BE1325382F75FA87@UK-EXCHMBX1.green.sophos>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [Asrg] antiphishing idea
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.12
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/options/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: Thu, 17 Nov 2011 21:38:38 -0000

On 11/17/2011 02:58 PM, Martijn Grooten wrote:
>> Domains should have to publish in their DNSs the message-id (among any
>> other thing) through a TXT or A record of any legit mail sent by them.
>> The TTLs of those records can be adjusted to compensate for queued
>> mails, etc.
> 
> I take it you mean the message-id is somehow converted into a domain name and a DNS lookup is performed against that DNS and if the A or TXT record for that domain is some kind of affirmative value, this means that this is a 'valid message-id'?

I got the impression from the original that he was not doing that, and
looking up the _whole_ Message-ID.

Which implies rather more tightly coupled MTA/DNS servers than is
probably feasible.  High volume mail servers would have a horrendous
problem with DNS bloat and at the same time, require very low TTLs.  Ouch.

Even if you only used a domain name same problem.

There's no easy transition either - you'd never know if whom you were
doing these queries actually implemented this stuff, and NXDOMAIN could
mean either "BAD! BAD! discard!" or "I don't implement that feature".

> I've got many doubts about this: do people who fall for such scams care about the value of From? Doesn't this have the same issues as SPF -all and ADSP? Does this scale? But my most important concern is: wouldn't it be trivial to perform a relay attack using this method?

It's trying to make "SPF -all" survive forwarding, but not as well as
DKIM would (absent message mangulation).

>> When you receive a mail from A and "aparently" from B you can query A
>> and B DNSs looking for the message-id the mail has. If you have a
>> nxdomain or whatever error from them you can score the mail as
>> phishing! ..on the other hand if you have a hit from at least one of
>> them you can be confident that this is the real domain that sends that
>> mail or it sends it on behalf the real address!
> 
> I don't get this. Are you saying that if I send an email with MAIL FROM: example.com and Header From: paypal.com and the message-id on example.com that I can then get this message-id validated simply because I happen to control example.com?

He's suggesting asking _both_ A and B.  So both paypal.com and
example.com would have to say "Yup, I know that Message-ID".

So, you'd have to control example.com and have one (presumably recent)
sample Message-ID from paypal.com, and you could send as many as you
want with any contents you want.

[Few (if any) MTAs enforce unique Message-IDs on inbound email.]

Neither SPF or DKIM are perfect, but it behooves us to not try to
bandaid their defects with something like this.  Patching a hole in a
submarine with window screening comes to mind as a suitable analogy ;-)

From christian.grunfeld@gmail.com  Thu Nov 17 14:04:44 2011
Return-Path: <christian.grunfeld@gmail.com>
X-Original-To: asrg@ietfa.amsl.com
Delivered-To: asrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3296A21F94E4 for <asrg@ietfa.amsl.com>; Thu, 17 Nov 2011 14:04:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.305
X-Spam-Level: 
X-Spam-Status: No, score=-3.305 tagged_above=-999 required=5 tests=[AWL=0.294,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LiuZoPm1OnJi for <asrg@ietfa.amsl.com>; Thu, 17 Nov 2011 14:04:43 -0800 (PST)
Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by ietfa.amsl.com (Postfix) with ESMTP id 7434D21F94E1 for <asrg@irtf.org>; Thu, 17 Nov 2011 14:04:43 -0800 (PST)
Received: by faap15 with SMTP id p15so3015190faa.13 for <asrg@irtf.org>; Thu, 17 Nov 2011 14:04:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=PodkZiOg5rz1DLY/5eSgdrbKE5xuqXPJON7VVRQyeOg=; b=T96BUUXORkqJD4ZHWXirPLwBiUzVNITE47RMf4oTHTaUsYmzr7xyRfPhrRDTrWgqqY d9yl71qjc7Hf8Wb9/0jyUQVvNSg7bae4vqsOUQLcCN7xAqrdGUjEzLp0YVlabjNSei1K f69KoAJMoBPIQkMecDoA28w9ynX2YwyEFeKoo=
MIME-Version: 1.0
Received: by 10.182.216.105 with SMTP id op9mr90371obc.57.1321567481068; Thu, 17 Nov 2011 14:04:41 -0800 (PST)
Received: by 10.182.47.103 with HTTP; Thu, 17 Nov 2011 14:04:40 -0800 (PST)
In-Reply-To: <18B53BA2A483AD45962AAD1397BE1325382F75FA87@UK-EXCHMBX1.green.sophos>
References: <CAFdugamtPXjEHiwuJ3N2xyaXK+E0yCJfQi6vOey3jyff1UVvgw@mail.gmail.com> <18B53BA2A483AD45962AAD1397BE1325382F75FA87@UK-EXCHMBX1.green.sophos>
Date: Thu, 17 Nov 2011 19:04:40 -0300
Message-ID: <CAFdugak9PqRtouPvm-BtnF1Vp00ZtzhBRcTRz2XFuC6+Tg_+_Q@mail.gmail.com>
From: Christian Grunfeld <christian.grunfeld@gmail.com>
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: Re: [Asrg] antiphishing idea
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.12
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/options/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: Thu, 17 Nov 2011 22:04:44 -0000

> I take it you mean the message-id is somehow converted into a domain name=
 and a DNS lookup is performed against that DNS and if the A or TXT record =
for that domain is some kind of affirmative value, this means that this is =
a 'valid message-id'?

message-id is already close in that form. It has
something_random_unique_time_process@domain

> I've got many doubts about this: do people who fall for such scams care a=
bout the value of From? Doesn't this have the same issues as SPF -all and A=
DSP? Does this scale? But my most important concern is: wouldn't it be triv=
ial to perform a relay attack using this method?
>

SPF checks against envelope MAIL FROM: ...users dont know even that
this thing exists ! they blindly trust on mail header From:
How would be a relay attack? evils dont know every random message-id
of a mail server legit mail. Are they going to query "every" random
string? ....now you can query what you want on a DNS server...what is
the difference?


> I don't get this. Are you saying that if I send an email with MAIL FROM: =
example.com and Header From: paypal.com and the message-id on example.com t=
hat I can then get this message-id validated simply because I happen to con=
trol example.com?

sorry, I meant both of them ! you are obviously going to get the
validation from the evil domail but you also need one from phished
domain. The last one is only true if the mail was sent by paypal.com

From johnl@iecc.com  Thu Nov 17 14:14:17 2011
Return-Path: <johnl@iecc.com>
X-Original-To: asrg@ietfa.amsl.com
Delivered-To: asrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 24C5B21F9502 for <asrg@ietfa.amsl.com>; Thu, 17 Nov 2011 14:14:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -111.037
X-Spam-Level: 
X-Spam-Status: No, score=-111.037 tagged_above=-999 required=5 tests=[AWL=0.162, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rMzqToXaSyxF for <asrg@ietfa.amsl.com>; Thu, 17 Nov 2011 14:14:11 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [64.57.183.53]) by ietfa.amsl.com (Postfix) with ESMTP id 19D0121F9572 for <asrg@irtf.org>; Thu, 17 Nov 2011 14:14:10 -0800 (PST)
Received: (qmail 17582 invoked from network); 17 Nov 2011 22:14:09 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 17 Nov 2011 22:14:09 -0000
Date: 17 Nov 2011 22:13:46 -0000
Message-ID: <20111117221346.27300.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: asrg@irtf.org
In-Reply-To: <CAFdugamtPXjEHiwuJ3N2xyaXK+E0yCJfQi6vOey3jyff1UVvgw@mail.gmail.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
Subject: Re: [Asrg] antiphishing idea
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.12
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/options/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: Thu, 17 Nov 2011 22:14:17 -0000

>Domains should have to publish in their DNSs the message-id (among any
>other thing) through a TXT or A record of any legit mail sent by them.
>The TTLs of those records can be adjusted to compensate for queued
>mails, etc.

Maybe I'm missing something, but why would you want to do this rather
than a DKIM signature?  DKIM validates against the DNS, and protects
the whole message.

R's,
John

From christian.grunfeld@gmail.com  Thu Nov 17 14:19:15 2011
Return-Path: <christian.grunfeld@gmail.com>
X-Original-To: asrg@ietfa.amsl.com
Delivered-To: asrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 499FB21F95CA for <asrg@ietfa.amsl.com>; Thu, 17 Nov 2011 14:19:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.364
X-Spam-Level: 
X-Spam-Status: No, score=-3.364 tagged_above=-999 required=5 tests=[AWL=0.235,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wLufb5sfHUvf for <asrg@ietfa.amsl.com>; Thu, 17 Nov 2011 14:19:14 -0800 (PST)
Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by ietfa.amsl.com (Postfix) with ESMTP id 63A1B21F95C2 for <asrg@irtf.org>; Thu, 17 Nov 2011 14:19:14 -0800 (PST)
Received: by faap15 with SMTP id p15so3042691faa.13 for <asrg@irtf.org>; Thu, 17 Nov 2011 14:19:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=TyiCBlhXfaWeRTT3kXTUKHKvJg6PsWuHre5hRRs4dWY=; b=VYLeYHnYJOTuipnpAyWpPgSWA+1Yr72cHd2b4x7f6mwByMfAKaJFEHXhcmWNztojBo Iw8H1nvxczcjjcPVi1XNVBRE6U6PiTq/CDpMO+wnZ+z7/mgj7S18tm6QCDCPCKWIwj1F WmgFByPUdJ33mTjLL0GI3C+g5ymB2lzs/EcOY=
MIME-Version: 1.0
Received: by 10.182.169.34 with SMTP id ab2mr118018obc.27.1321568352863; Thu, 17 Nov 2011 14:19:12 -0800 (PST)
Received: by 10.182.47.103 with HTTP; Thu, 17 Nov 2011 14:19:12 -0800 (PST)
In-Reply-To: <20111117221346.27300.qmail@joyce.lan>
References: <CAFdugamtPXjEHiwuJ3N2xyaXK+E0yCJfQi6vOey3jyff1UVvgw@mail.gmail.com> <20111117221346.27300.qmail@joyce.lan>
Date: Thu, 17 Nov 2011 19:19:12 -0300
Message-ID: <CAFduganLWiFQSRP9uG4auEr-bXsHcKSQV=2+C2pEF4AK3QGdKw@mail.gmail.com>
From: Christian Grunfeld <christian.grunfeld@gmail.com>
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: Re: [Asrg] antiphishing idea
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.12
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/options/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: Thu, 17 Nov 2011 22:19:15 -0000

2011/11/17 John Levine <johnl@taugh.com>:
>>Domains should have to publish in their DNSs the message-id (among any
>>other thing) through a TXT or A record of any legit mail sent by them.
>>The TTLs of those records can be adjusted to compensate for queued
>>mails, etc.
>
> Maybe I'm missing something, but why would you want to do this rather
> than a DKIM signature? =A0DKIM validates against the DNS, and protects
> the whole message.

because I can have a proper configured domain, I can properly sign my
mails but I can send you an email with From: paypal.com header !
DKIM does not protect you against this ! DKIM says that evil.com signs
correctly the email and no alarms will trigger. The average user only
see and "trust" the From: paypal.com mail header !

From christian.grunfeld@gmail.com  Thu Nov 17 14:25:56 2011
Return-Path: <christian.grunfeld@gmail.com>
X-Original-To: asrg@ietfa.amsl.com
Delivered-To: asrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5F5731F0C4F for <asrg@ietfa.amsl.com>; Thu, 17 Nov 2011 14:25:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.403
X-Spam-Level: 
X-Spam-Status: No, score=-3.403 tagged_above=-999 required=5 tests=[AWL=0.196,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bJ16CgYQl25Q for <asrg@ietfa.amsl.com>; Thu, 17 Nov 2011 14:25:56 -0800 (PST)
Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by ietfa.amsl.com (Postfix) with ESMTP id A71581F0C4C for <asrg@irtf.org>; Thu, 17 Nov 2011 14:25:55 -0800 (PST)
Received: by faap15 with SMTP id p15so3053748faa.13 for <asrg@irtf.org>; Thu, 17 Nov 2011 14:25:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=pNtSEuYyf9yRgFSwyU7BgV7UXxSjSOWZebuNg2XsGHY=; b=aqJJ9OTaziTnjeWTM7eb7fLNJNeYPl1WMKyGW2FLyvfSxtCpYhsXVkjFMCb0GtI7dP JWJPrSNZrgNt97Pivprw7y5nSPhP8/MdG+bYwQraqjUFZrH75GEuRXvNUj5Dt5JIZpjZ 3nK0Wz5e4iWxJPFAk9n8nbbkTOFHcjZrrRkQU=
MIME-Version: 1.0
Received: by 10.182.59.49 with SMTP id w17mr116342obq.37.1321568754545; Thu, 17 Nov 2011 14:25:54 -0800 (PST)
Received: by 10.182.47.103 with HTTP; Thu, 17 Nov 2011 14:25:54 -0800 (PST)
In-Reply-To: <4EC57EDD.30808@mustelids.ca>
References: <CAFdugamtPXjEHiwuJ3N2xyaXK+E0yCJfQi6vOey3jyff1UVvgw@mail.gmail.com> <18B53BA2A483AD45962AAD1397BE1325382F75FA87@UK-EXCHMBX1.green.sophos> <4EC57EDD.30808@mustelids.ca>
Date: Thu, 17 Nov 2011 19:25:54 -0300
Message-ID: <CAFduga=LDU7tSPV-Tbjp8iSvhApx+8enmrCXd2E=9YYqoQuTNw@mail.gmail.com>
From: Christian Grunfeld <christian.grunfeld@gmail.com>
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: Re: [Asrg] antiphishing idea
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.12
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/options/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: Thu, 17 Nov 2011 22:25:56 -0000

> I got the impression from the original that he was not doing that, and
> looking up the _whole_ Message-ID.

yes

> There's no easy transition either - you'd never know if whom you were
> doing these queries actually implemented this stuff, and NXDOMAIN could
> mean either "BAD! BAD! discard!" or "I don't implement that feature".

same as SPF and DKIM. They are more or less good if all implement them !

> It's trying to make "SPF -all" survive forwarding, but not as well as
> DKIM would (absent message mangulation).

DKIM is good for forwarding but it does not solve phishing !

> He's suggesting asking _both_ A and B. =A0So both paypal.com and
> example.com would have to say "Yup, I know that Message-ID".

yes, that is the idea. Already answered in previous mail

> So, you'd have to control example.com and have one (presumably recent)
> sample Message-ID from paypal.com, and you could send as many as you
> want with any contents you want.
>
> [Few (if any) MTAs enforce unique Message-IDs on inbound email.]

well...a good point to investigate

> Neither SPF or DKIM are perfect, but it behooves us to not try to
> bandaid their defects with something like this. =A0Patching a hole in a
> submarine with window screening comes to mind as a suitable analogy ;-)

ok, not bandaid.....let=B4s reinvent SMTP with 3 way handshake ! that is
a more suitable analogy for my idea !

From steve@blighty.com  Thu Nov 17 14:29:45 2011
Return-Path: <steve@blighty.com>
X-Original-To: asrg@ietfa.amsl.com
Delivered-To: asrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 29AE91F0C63 for <asrg@ietfa.amsl.com>; Thu, 17 Nov 2011 14:29:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.359
X-Spam-Level: 
X-Spam-Status: No, score=-2.359 tagged_above=-999 required=5 tests=[AWL=0.240,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5iaqTX4Dxq+0 for <asrg@ietfa.amsl.com>; Thu, 17 Nov 2011 14:29:44 -0800 (PST)
Received: from m.wordtothewise.com (misc.wordtothewise.com [184.105.179.154]) by ietfa.amsl.com (Postfix) with ESMTP id 70B301F0C4C for <asrg@irtf.org>; Thu, 17 Nov 2011 14:29:44 -0800 (PST)
Received: from [192.168.80.43] (204.11.227.194.static.etheric.net [204.11.227.194]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: steve) by m.wordtothewise.com (Postfix) with ESMTPSA id 48E212EB40 for <asrg@irtf.org>; Thu, 17 Nov 2011 14:29:44 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1251.1)
From: Steve Atkins <steve@blighty.com>
In-Reply-To: <CAFdugamtPXjEHiwuJ3N2xyaXK+E0yCJfQi6vOey3jyff1UVvgw@mail.gmail.com>
Date: Thu, 17 Nov 2011 14:29:43 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <2A7B1043-D384-4593-9AD4-62A5B4CD739C@blighty.com>
References: <CAFdugamtPXjEHiwuJ3N2xyaXK+E0yCJfQi6vOey3jyff1UVvgw@mail.gmail.com>
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
X-Mailer: Apple Mail (2.1251.1)
Subject: Re: [Asrg] antiphishing idea
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.12
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/options/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: Thu, 17 Nov 2011 22:29:45 -0000

On Nov 17, 2011, at 10:30 AM, Christian Grunfeld wrote:

> Domains should have to publish in their DNSs the message-id (among any
> other thing) through a TXT or A record of any legit mail sent by them.
> The TTLs of those records can be adjusted to compensate for queued
> mails, etc.

The obvious flaw with a simple version of this proposal is replay
attacks. Once someone has sent me an email, I can send email "from"
them just by reusing the message-id.

One obvious fix to that is to allow each message-id to be used and
validated exactly once. The first MTA to see that message-id considers
the message to be valid, anyone after that doesn't. That's very similar
to the goodmail token approach.

Another obvious fix would be to include a timestamp and invalidate
messages that are "too old" - but the window in which you'd expect
to see legitimate delayed messages is longer than the time you'd expect
replay attacks to be attempted.

Another obvious fix is to tie the message-id to the content of the =
message
in some way, by including a hash of the message and a subset of the
headers. That would work quite well, but still leads to the operational
problem of requiring a tight binding between the sending MTA and the
DNS server for that domain, and the significant problem of it defeating
the caching that DNS provides, leading to both high traffic DNS queries
and a likelihood of DNS lookup failures (and hence delayed or lost =
email).

One way to work around that would be to look up not a unique token from
the message-id for a simple match, rather to look up a substring of the
message-id to retrieve a cryptographic key that could be used to =
validate
the rest of the message-id. That key entry would be cached well by
DNS and would work pretty well. Replace message-id with DKIM
headers and you have DKIM.

The less obvious flaw is that you're trying to combat phishing by =
"protecting"
the From: header by requiring it be authenticated, and requiring all
email using that From: domain be sent through a small number of
"trusted" MTAs.

That's exactly what ADSP attempts to do, and it's been shown to
cause fairly serious loss of legitimate email (because it's extremely
rare that you really know all legitimate email is sent from just the
servers youo think it is). And it's been shown not to work terribly
well against phishing, as there's not enough information in a
From: header to tell you if the mail is legitimate. If I register the
domain paypal-billing.com, send mail From: it, with valid-by-your-scheme
message-id headers then it's 100% legitimate email as far as
recipients are concerned. And it is legitimate - it's just not from
paypal.

Cheers,
  Steve


From mike@mtcc.com  Thu Nov 17 14:30:04 2011
Return-Path: <mike@mtcc.com>
X-Original-To: asrg@ietfa.amsl.com
Delivered-To: asrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 432591F0C4C for <asrg@ietfa.amsl.com>; Thu, 17 Nov 2011 14:30:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id M9DNMPC1Kexb for <asrg@ietfa.amsl.com>; Thu, 17 Nov 2011 14:30:03 -0800 (PST)
Received: from mtcc.com (mtcc.com [50.0.18.224]) by ietfa.amsl.com (Postfix) with ESMTP id A50291F0C4B for <asrg@irtf.org>; Thu, 17 Nov 2011 14:30:03 -0800 (PST)
Received: from takifugu.mtcc.com (takifugu.mtcc.com [50.0.18.224]) (authenticated bits=0) by mtcc.com (8.14.3/8.14.3) with ESMTP id pAHMU1YL009738 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Thu, 17 Nov 2011 14:30:01 -0800
Message-ID: <4EC58AE9.8050102@mtcc.com>
Date: Thu, 17 Nov 2011 14:30:01 -0800
From: Michael Thomas <mike@mtcc.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:1.8.1.22) Gecko/20090605 Thunderbird/2.0.0.22 Mnenhy/0.7.5.0
MIME-Version: 1.0
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
References: <CAFdugamtPXjEHiwuJ3N2xyaXK+E0yCJfQi6vOey3jyff1UVvgw@mail.gmail.com>	<20111117221346.27300.qmail@joyce.lan> <CAFduganLWiFQSRP9uG4auEr-bXsHcKSQV=2+C2pEF4AK3QGdKw@mail.gmail.com>
In-Reply-To: <CAFduganLWiFQSRP9uG4auEr-bXsHcKSQV=2+C2pEF4AK3QGdKw@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=998; t=1321569002; x=1322433002; c=relaxed/simple; s=thundersaddle.kirkwood; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=mtcc.com; i=mike@mtcc.com; z=From:=20Michael=20Thomas=20<mike@mtcc.com> |Subject:=20Re=3A=20[Asrg]=20antiphishing=20idea |Sender:=20 |To:=20Anti-Spam=20Research=20Group=20-=20IRTF=20<asrg@irtf .org> |Content-Type:=20text/plain=3B=20charset=3DISO-8859-1=3B=20 format=3Dflowed |Content-Transfer-Encoding:=207bit |MIME-Version:=201.0; bh=Cvu2unyoWdEAXDq+gTiOJsQygBagPkmulNHlRpGiB10=; b=mDXML7e5KLTVHudeL7q8M6chErnnZVbLvjhqPL7/u1S2a0dY9Xb6Bt6FSM zY6u5pXc0TBU9ls5lIdgV06ZfEOaeuBlGIQCTSzUtUb/HBVsvRVGA9W4uUzB yHrI0D4HmuZy40tmFzj/JMxp+/x3f2AbjSCOeYSqVaUcE8/5CgbME=;
Authentication-Results: ; v=0.1; dkim=pass header.i=mike@mtcc.com ( sig from mtcc.com/thundersaddle.kirkwood verified; );  dkim-asp=pass header.From=mike@mtcc.com
Subject: Re: [Asrg] antiphishing idea
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.12
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/options/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: Thu, 17 Nov 2011 22:30:04 -0000

On 11/17/2011 02:19 PM, Christian Grunfeld wrote:
> 2011/11/17 John Levine<johnl@taugh.com>:
>    
>>> Domains should have to publish in their DNSs the message-id (among any
>>> other thing) through a TXT or A record of any legit mail sent by them.
>>> The TTLs of those records can be adjusted to compensate for queued
>>> mails, etc.
>>>        
>> Maybe I'm missing something, but why would you want to do this rather
>> than a DKIM signature?  DKIM validates against the DNS, and protects
>> the whole message.
>>      
> because I can have a proper configured domain, I can properly sign my
> mails but I can send you an email with From: paypal.com header !
> DKIM does not protect you against this ! DKIM says that evil.com signs
> correctly the email and no alarms will trigger. The average user only
> see and "trust" the From: paypal.com mail header !
>    

Ask google if an improperly dkim-signed paypal.com mail sets off
alarms. I'll help you out: it does.

Mike

From sethb@panix.com  Thu Nov 17 15:28:05 2011
Return-Path: <sethb@panix.com>
X-Original-To: asrg@ietfa.amsl.com
Delivered-To: asrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DED2621F87FA for <asrg@ietfa.amsl.com>; Thu, 17 Nov 2011 15:28:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yVIWmoo8lfW4 for <asrg@ietfa.amsl.com>; Thu, 17 Nov 2011 15:28:00 -0800 (PST)
Received: from mailbackend.panix.com (mailbackend.panix.com [166.84.1.89]) by ietfa.amsl.com (Postfix) with ESMTP id 1DDF121F8770 for <asrg@irtf.org>; Thu, 17 Nov 2011 15:28:00 -0800 (PST)
Received: from panix5.panix.com (panix5.panix.com [166.84.1.5]) by mailbackend.panix.com (Postfix) with ESMTP id 8A54E28B53 for <asrg@irtf.org>; Thu, 17 Nov 2011 18:27:59 -0500 (EST)
Received: by panix5.panix.com (Postfix, from userid 756) id 7955124245; Thu, 17 Nov 2011 18:27:59 -0500 (EST)
From: Seth <sethb@panix.com>
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
In-reply-to: <CAFdugak9PqRtouPvm-BtnF1Vp00ZtzhBRcTRz2XFuC6+Tg_+_Q@mail.gmail.com> (message from Christian Grunfeld on Thu, 17 Nov 2011 19:04:40 -0300)
References: <CAFdugamtPXjEHiwuJ3N2xyaXK+E0yCJfQi6vOey3jyff1UVvgw@mail.gmail.com> <18B53BA2A483AD45962AAD1397BE1325382F75FA87@UK-EXCHMBX1.green.sophos> <CAFdugak9PqRtouPvm-BtnF1Vp00ZtzhBRcTRz2XFuC6+Tg_+_Q@mail.gmail.com>
Message-Id: <20111117232759.7955124245@panix5.panix.com>
Date: Thu, 17 Nov 2011 18:27:59 -0500 (EST)
Subject: Re: [Asrg] antiphishing idea
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.12
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/options/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: Thu, 17 Nov 2011 23:28:06 -0000

Christian Grunfeld <christian.grunfeld@gmail.com> wrote:

> sorry, I meant both of them ! you are obviously going to get the
> validation from the evil domail but you also need one from phished
> domain. The last one is only true if the mail was sent by paypal.com

No, it's true only if _any_ message was sent by paypal.com with that
Message-ID.  Copying a Message-ID isn't difficult, nor is getting
legitimate mail from paypal.

Seth

From clewis+ietf@mustelids.ca  Thu Nov 17 15:36:37 2011
Return-Path: <clewis+ietf@mustelids.ca>
X-Original-To: asrg@ietfa.amsl.com
Delivered-To: asrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 54EDB1F0C7F for <asrg@ietfa.amsl.com>; Thu, 17 Nov 2011 15:36:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.901
X-Spam-Level: 
X-Spam-Status: No, score=0.901 tagged_above=-999 required=5 tests=[AWL=-1.950,  BAYES_00=-2.599, FB_CIALIS_LEO3=3.899, FH_RELAY_NODNS=1.451, RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mDLFDji89GC3 for <asrg@ietfa.amsl.com>; Thu, 17 Nov 2011 15:36:32 -0800 (PST)
Received: from mail.mustelids.ca (unknown [174.35.130.2]) by ietfa.amsl.com (Postfix) with ESMTP id 1F38F1F0C67 for <asrg@irtf.org>; Thu, 17 Nov 2011 15:36:31 -0800 (PST)
Received: from [192.168.0.8] (otter.mustelids.ca [192.168.0.8]) (authenticated bits=0) by mail.mustelids.ca (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id pAHNaO3r028568 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <asrg@irtf.org>; Thu, 17 Nov 2011 18:36:24 -0500
Message-ID: <4EC59A78.6060704@mustelids.ca>
Date: Thu, 17 Nov 2011 18:36:24 -0500
From: Chris Lewis <clewis+ietf@mustelids.ca>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.8.1.23) Gecko/20090812 Thunderbird/2.0.0.23 Mnenhy/0.7.6.666
MIME-Version: 1.0
To: asrg@irtf.org
References: <CAFdugamtPXjEHiwuJ3N2xyaXK+E0yCJfQi6vOey3jyff1UVvgw@mail.gmail.com> <18B53BA2A483AD45962AAD1397BE1325382F75FA87@UK-EXCHMBX1.green.sophos> <4EC57EDD.30808@mustelids.ca> <CAFduga=LDU7tSPV-Tbjp8iSvhApx+8enmrCXd2E=9YYqoQuTNw@mail.gmail.com>
In-Reply-To: <CAFduga=LDU7tSPV-Tbjp8iSvhApx+8enmrCXd2E=9YYqoQuTNw@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [Asrg] antiphishing idea
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.12
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/options/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: Thu, 17 Nov 2011 23:36:37 -0000

On 11-11-17 05:25 PM, Christian Grunfeld wrote:

>> There's no easy transition either - you'd never know if whom you were
>> doing these queries actually implemented this stuff, and NXDOMAIN could
>> mean either "BAD! BAD! discard!" or "I don't implement that feature".
>
> same as SPF and DKIM. They are more or less good if all implement them !

Ah, sorry, no.  If the sender doesn't implement SPF or DKIM, you find 
out that it doesn't support it by not having an SPF or DKIM record, 
thus, you don't apply either.

In your proposal there is no way to tell whether a given server 
implements it, AND the result for "FAIL" is indistinguishable from the 
result for "NOT IMPLEMENTED".

In other words, you can only turn this feature on if everybody 
implements it.  At the same time.

That won't happen.

You have to add other transactions to be able to query if the server 
supports this feature.  If the forwarder doesn't (by mal or mis 
feasance), then it doesn't do anything useful.

>> It's trying to make "SPF -all" survive forwarding, but not as well as
>> DKIM would (absent message mangulation).
>
> DKIM is good for forwarding but it does not solve phishing !

Actually, it does, if the From is signed (which it usually is), and if 
the receiver knows (by some outside arrangement) to throw away anything 
that fails.

What it doesn't do is solve "froggery" (myriads of look-alike domains, 
which your proposal does not solve) nor does it solve the fact that most 
of the time the user doesn't even notice what's in the From: line (nor 
does your proposal).  Remember that many mail readers (outlook included) 
DO NOT SHOW YOU THE EMAIL ADDRESS in the From: line by default.

Sigh.

APWG just published a report that said that less than 20% of phishes had 
the correct phished-for domain in the From line...  Cutwail is pushing a 
lot of such things right now.

From christian.grunfeld@gmail.com  Thu Nov 17 16:18:20 2011
Return-Path: <christian.grunfeld@gmail.com>
X-Original-To: asrg@ietfa.amsl.com
Delivered-To: asrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4BD6B21F90F2 for <asrg@ietfa.amsl.com>; Thu, 17 Nov 2011 16:18:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.431
X-Spam-Level: 
X-Spam-Status: No, score=-3.431 tagged_above=-999 required=5 tests=[AWL=0.168,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TwyWIMzrTexv for <asrg@ietfa.amsl.com>; Thu, 17 Nov 2011 16:18:15 -0800 (PST)
Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by ietfa.amsl.com (Postfix) with ESMTP id E694E21F8C14 for <asrg@irtf.org>; Thu, 17 Nov 2011 16:18:14 -0800 (PST)
Received: by faap15 with SMTP id p15so3222593faa.13 for <asrg@irtf.org>; Thu, 17 Nov 2011 16:18:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=VRWnsTbohLA6T1NThOV2dR8dQJDoYds8t7VZxj5d7XM=; b=Uy4V8iGVwC0QdN8xsOPybTKctEMY8nTmPU35OLW07p9Im/tU6Cj9Syr2GxR8SPe6gO VKTJk439kImL41+L9OoWWIiZsZSvpC36W167lDno54WSgklVrd/c77Mpj6tdPkKSoMfo W+67LMjrIX6UXkfoywV9+MoghMwD+d3lRBhWI=
MIME-Version: 1.0
Received: by 10.182.222.99 with SMTP id ql3mr176013obc.67.1321575492508; Thu, 17 Nov 2011 16:18:12 -0800 (PST)
Received: by 10.182.47.103 with HTTP; Thu, 17 Nov 2011 16:18:12 -0800 (PST)
In-Reply-To: <4EC59A78.6060704@mustelids.ca>
References: <CAFdugamtPXjEHiwuJ3N2xyaXK+E0yCJfQi6vOey3jyff1UVvgw@mail.gmail.com> <18B53BA2A483AD45962AAD1397BE1325382F75FA87@UK-EXCHMBX1.green.sophos> <4EC57EDD.30808@mustelids.ca> <CAFduga=LDU7tSPV-Tbjp8iSvhApx+8enmrCXd2E=9YYqoQuTNw@mail.gmail.com> <4EC59A78.6060704@mustelids.ca>
Date: Thu, 17 Nov 2011 21:18:12 -0300
Message-ID: <CAFdugakuOV8rkZT7PyzqsKni1E5opU7TPC+by+NvLG5M_pn7iw@mail.gmail.com>
From: Christian Grunfeld <christian.grunfeld@gmail.com>
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: Re: [Asrg] antiphishing idea
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.12
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/options/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: Fri, 18 Nov 2011 00:18:20 -0000

> Ah, sorry, no. =A0If the sender doesn't implement SPF or DKIM, you find o=
ut
> that it doesn't support it by not having an SPF or DKIM record, thus, you
> don't apply either.
>
> In your proposal there is no way to tell whether a given server implement=
s
> it, AND the result for "FAIL" is indistinguishable from the result for "N=
OT
> IMPLEMENTED".

> In other words, you can only turn this feature on if everybody implements
> it. =A0At the same time.
>
> That won't happen.
>
> You have to add other transactions to be able to query if the server
> supports this feature. =A0If the forwarder doesn't (by mal or mis feasanc=
e),
> then it doesn't do anything useful.

ok, put a TXT RR in the DNS telling "I am using the proposal" as SPD and DK=
IM do


> Actually, it does, if the From is signed (which it usually is), and if th=
e
> receiver knows (by some outside arrangement) to throw away anything that
> fails.

anything that fails what? a signed email does not solve forgery of the
headers IN THE ORIGIN ! it solves forgery IN TRANSIT !
I can send an email to this list with my gmail account (wich goes
properly signed) claiming that is from you ! do you want me to try ?


> What it doesn't do is solve "froggery" (myriads of look-alike domains, wh=
ich
> your proposal does not solve) nor does it solve the fact that most of the
> time the user doesn't even notice what's in the From: line (nor does your
> proposal). =A0Remember that many mail readers (outlook included) DO NOT S=
HOW
> YOU THE EMAIL ADDRESS in the From: line by default.

my proposal does not need the user see the address...it checks
silently on behalf the user.

From johnl@iecc.com  Thu Nov 17 22:59:32 2011
Return-Path: <johnl@iecc.com>
X-Original-To: asrg@ietfa.amsl.com
Delivered-To: asrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 570401F0C7E for <asrg@ietfa.amsl.com>; Thu, 17 Nov 2011 22:59:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -111.055
X-Spam-Level: 
X-Spam-Status: No, score=-111.055 tagged_above=-999 required=5 tests=[AWL=0.144, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Pj4JmIFDsTtO for <asrg@ietfa.amsl.com>; Thu, 17 Nov 2011 22:59:31 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [64.57.183.53]) by ietfa.amsl.com (Postfix) with ESMTP id 65EDE1F0C60 for <asrg@irtf.org>; Thu, 17 Nov 2011 22:59:31 -0800 (PST)
Received: (qmail 63850 invoked from network); 18 Nov 2011 06:59:28 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 18 Nov 2011 06:59:28 -0000
Date: 18 Nov 2011 06:59:07 -0000
Message-ID: <20111118065907.21734.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: asrg@irtf.org
In-Reply-To: <CAFduganLWiFQSRP9uG4auEr-bXsHcKSQV=2+C2pEF4AK3QGdKw@mail.gmail.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
Subject: Re: [Asrg] antiphishing idea
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.12
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/options/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: Fri, 18 Nov 2011 06:59:32 -0000

>> Maybe I'm missing something, but why would you want to do this rather
>> than a DKIM signature?  DKIM validates against the DNS, and protects
>> the whole message.
>
>because I can have a proper configured domain, I can properly sign my
>mails but I can send you an email with From: paypal.com header !
>DKIM does not protect you against this !

I get the impression that you haven't read the very, very, very
extensive discussion on the DKIM list about how DKIM and/or ADSP do or
do not "protect" the address on the From: line, and what if anything
to do about it.  Please do so.  The archives are here:

http://mipassoc.org/pipermail/ietf-dkim/

It would also be worth taking a look at the archives of the earlier
MARID WG which also considered similar issues.  Its archives are here:

http://www.imc.org/ietf-mxcomp/mail-archive/

R's,
John


From prvs=0303DD298F=paul@pscs.co.uk  Fri Nov 18 02:30:26 2011
Return-Path: <prvs=0303DD298F=paul@pscs.co.uk>
X-Original-To: asrg@ietfa.amsl.com
Delivered-To: asrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2F57621F8A56 for <asrg@ietfa.amsl.com>; Fri, 18 Nov 2011 02:30:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.524
X-Spam-Level: 
X-Spam-Status: No, score=-2.524 tagged_above=-999 required=5 tests=[AWL=0.075,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JmYSwRtqVqQ5 for <asrg@ietfa.amsl.com>; Fri, 18 Nov 2011 02:30:25 -0800 (PST)
Received: from mail.pscs.co.uk (mail.pscs.co.uk [46.20.224.92]) by ietfa.amsl.com (Postfix) with ESMTP id 456D621F899D for <asrg@irtf.org>; Fri, 18 Nov 2011 02:30:23 -0800 (PST)
Received: from lmail.pscs.co.uk ([217.155.61.14]) by mail.pscs.co.uk ([46.20.224.92] running VPOP3) with ESMTP for <asrg@irtf.org>; Fri, 18 Nov 2011 10:30:04 -0000
Received: from [192.168.66.100] ([192.168.66.100]) by lmail.pscs.co.uk ([192.168.66.70] running VPOP3) with ESMTP for <asrg@irtf.org>; Fri, 18 Nov 2011 10:26:55 -0000
Message-ID: <4EC632EE.7020003@pscs.co.uk>
Date: Fri, 18 Nov 2011 10:26:54 +0000
From: Paul Smith <paul@pscs.co.uk>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
References: <CAFdugamtPXjEHiwuJ3N2xyaXK+E0yCJfQi6vOey3jyff1UVvgw@mail.gmail.com> <18B53BA2A483AD45962AAD1397BE1325382F75FA87@UK-EXCHMBX1.green.sophos> <CAFdugak9PqRtouPvm-BtnF1Vp00ZtzhBRcTRz2XFuC6+Tg_+_Q@mail.gmail.com> <20111117232759.7955124245@panix5.panix.com>
In-Reply-To: <20111117232759.7955124245@panix5.panix.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Authenticated-Sender: paul
X-Server: VPOP3 Enterprise V4.9 - Registered
X-Organisation: Paul Smith Computer Services
Subject: Re: [Asrg] antiphishing idea
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.12
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/options/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: Fri, 18 Nov 2011 10:30:26 -0000

On 17/11/2011 23:27, Seth wrote:
> Christian Grunfeld<christian.grunfeld@gmail.com>  wrote:
>
>> sorry, I meant both of them ! you are obviously going to get the
>> validation from the evil domail but you also need one from phished
>> domain. The last one is only true if the mail was sent by paypal.com
> No, it's true only if _any_ message was sent by paypal.com with that
> Message-ID.  Copying a Message-ID isn't difficult, nor is getting
> legitimate mail from paypal.
>

So, you put the message-id AND recipient in the source's database

If evil spammer/phisher gets Paypal to send him a message, then reuses 
that message-id in their own messages out, it would work with the 
original idea, but if you add the recipient to the data, you defeat that.




From prvs=0303DD298F=paul@pscs.co.uk  Fri Nov 18 02:30:30 2011
Return-Path: <prvs=0303DD298F=paul@pscs.co.uk>
X-Original-To: asrg@ietfa.amsl.com
Delivered-To: asrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 199AF21F8A58 for <asrg@ietfa.amsl.com>; Fri, 18 Nov 2011 02:30:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.539
X-Spam-Level: 
X-Spam-Status: No, score=-2.539 tagged_above=-999 required=5 tests=[AWL=0.060,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XlbQWw7Zj9hI for <asrg@ietfa.amsl.com>; Fri, 18 Nov 2011 02:30:25 -0800 (PST)
Received: from mail.pscs.co.uk (mail.pscs.co.uk [46.20.224.92]) by ietfa.amsl.com (Postfix) with ESMTP id 4579321F8A35 for <asrg@irtf.org>; Fri, 18 Nov 2011 02:30:23 -0800 (PST)
Received: from lmail.pscs.co.uk ([217.155.61.14]) by mail.pscs.co.uk ([46.20.224.92] running VPOP3) with ESMTP; Fri, 18 Nov 2011 10:30:06 -0000
Received: from [192.168.66.100] ([192.168.66.100]) by lmail.pscs.co.uk ([192.168.66.70] running VPOP3) with ESMTP; Fri, 18 Nov 2011 10:25:11 -0000
Message-ID: <4EC63287.5060108@pscs.co.uk>
Date: Fri, 18 Nov 2011 10:25:11 +0000
From: Paul Smith <paul@pscs.co.uk>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
References: <CAFdugamtPXjEHiwuJ3N2xyaXK+E0yCJfQi6vOey3jyff1UVvgw@mail.gmail.com> <18B53BA2A483AD45962AAD1397BE1325382F75FA87@UK-EXCHMBX1.green.sophos> <4EC57EDD.30808@mustelids.ca> <CAFduga=LDU7tSPV-Tbjp8iSvhApx+8enmrCXd2E=9YYqoQuTNw@mail.gmail.com> <4EC59A78.6060704@mustelids.ca> <CAFdugakuOV8rkZT7PyzqsKni1E5opU7TPC+by+NvLG5M_pn7iw@mail.gmail.com>
In-Reply-To: <CAFdugakuOV8rkZT7PyzqsKni1E5opU7TPC+by+NvLG5M_pn7iw@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Authenticated-Sender: paul
X-Server: VPOP3 Enterprise V4.9 - Registered
X-Organisation: Paul Smith Computer Services
Subject: Re: [Asrg] antiphishing idea
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.12
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/options/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: Fri, 18 Nov 2011 10:30:30 -0000

On 18/11/2011 00:18, Christian Grunfeld wrote:
>> What it doesn't do is solve "froggery" (myriads of look-alike domains, which
>> your proposal does not solve) nor does it solve the fact that most of the
>> time the user doesn't even notice what's in the From: line (nor does your
>> proposal).  Remember that many mail readers (outlook included) DO NOT SHOW
>> YOU THE EMAIL ADDRESS in the From: line by default.
> my proposal does not need the user see the address...it checks
> silently on behalf the user.
>

Unfortunately, all it will check is that the from address is OK-ish 
according to the sender's domain.

It doesn't check that that message that says 'your paypal account has 
been compromised, please enter your login details on 
http://badpeople.com/giveusyourmoney.php' is actually from Paypal. The 
'From' address, and the return path could be 'evilman@badpeople.com', 
and some people would still click on that link and enter their login 
details.

The biggest reason phishing works is that some (many?) people become 
very stupid as soon as you put a computer in front of them. Good luck 
with finding a solution for that... :) Ask them in the street for their 
password, and they'll tell you where to go, but send them an email with 
a 'keyword' in (eg 'Paypal', or their bank's name), and they'll tell you 
everything you want to know.


Actually, as an anti-forgery technique, which may help spam filters when 
determining reputation, I think your idea would help (I know others 
would disagree), but as a specifically anti-phishing technique, I think 
human stupidity will beat it.




From martijn.grooten@virusbtn.com  Fri Nov 18 06:32:25 2011
Return-Path: <martijn.grooten@virusbtn.com>
X-Original-To: asrg@ietfa.amsl.com
Delivered-To: asrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0D83821F8B3B for <asrg@ietfa.amsl.com>; Fri, 18 Nov 2011 06:32:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oTaC0PYdzG8y for <asrg@ietfa.amsl.com>; Fri, 18 Nov 2011 06:32:23 -0800 (PST)
Received: from mx4.sophos.com (mx4.sophos.com [216.47.234.213]) by ietfa.amsl.com (Postfix) with ESMTP id E142721F8B37 for <asrg@irtf.org>; Fri, 18 Nov 2011 06:32:21 -0800 (PST)
Received: from mx4.sophos.com (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id 317904E039B for <asrg@irtf.org>; Fri, 18 Nov 2011 14:32:20 +0000 (GMT)
Received: by mx4.sophos.com (Postfix, from userid 89) id 5A6644E04DA; Fri, 18 Nov 2011 13:29:40 +0000 (GMT)
Received: from uk-exch2.green.sophos (uk-exch2.green.sophos [10.100.199.17]) by mx4.sophos.com (Postfix) with ESMTPS id BEB684E3BA6 for <asrg@irtf.org>; Thu, 17 Nov 2011 22:24:09 +0000 (GMT)
Received: from UK-EXCHMBX1.green.sophos ([fe80:0000:0000:0000:e1bd:d3c1:23.222.229.221]) by uk-exch2.green.sophos ([10.100.199.17]) with mapi; Thu, 17 Nov 2011 22:24:08 +0000
From: Martijn Grooten <martijn.grooten@virusbtn.com>
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
Date: Thu, 17 Nov 2011 22:24:07 +0000
Thread-Topic: [Asrg] antiphishing idea
Thread-Index: AcyldPMs8ZSTv2wBQt6cJ6IhDL5ZewAAaOiP
Message-ID: <18B53BA2A483AD45962AAD1397BE1325382EF38BFE@UK-EXCHMBX1.green.sophos>
References: <CAFdugamtPXjEHiwuJ3N2xyaXK+E0yCJfQi6vOey3jyff1UVvgw@mail.gmail.com> <18B53BA2A483AD45962AAD1397BE1325382F75FA87@UK-EXCHMBX1.green.sophos>, <CAFdugak9PqRtouPvm-BtnF1Vp00ZtzhBRcTRz2XFuC6+Tg_+_Q@mail.gmail.com>
In-Reply-To: <CAFdugak9PqRtouPvm-BtnF1Vp00ZtzhBRcTRz2XFuC6+Tg_+_Q@mail.gmail.com>
Accept-Language: en-US, en-GB
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [Asrg] antiphishing idea
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.12
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/options/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: Fri, 18 Nov 2011 14:32:25 -0000

> SPF checks against envelope MAIL FROM: ...users dont know even that
> this thing exists ! they blindly trust on mail header From:
> How would be a relay attack? evils dont know every random message-id
> of a mail server legit mail. Are they going to query "every" random
> string? ....now you can query what you want on a DNS server...what is
> the difference?

Sorry, I meant rePlay attack. You get hold of one 'valid' messagge-id and u=
se that for all your phishing messages.

> sorry, I meant both of them ! you are obviously going to get the
> validation from the evil domail but you also need one from phished
> domain. The last one is only true if the mail was sent by paypal.com

So if I were to use Gmail to send mail on behalf of a example.com, a domain=
 which I hypothetically have an email address at (something which has worke=
d well for years), I'd have to validate the message ID of every email I wan=
t to send at example.com?

Martijn.

Virus Bulletin Ltd, The Pentagon, Abingdon, OX14 3YP, England.
Company Reg No: 2388295. VAT Reg No: GB 532 5598 33.

From martijn.grooten@virusbtn.com  Fri Nov 18 11:26:19 2011
Return-Path: <martijn.grooten@virusbtn.com>
X-Original-To: asrg@ietfa.amsl.com
Delivered-To: asrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 558E81F0C40 for <asrg@ietfa.amsl.com>; Fri, 18 Nov 2011 11:26:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.649
X-Spam-Level: 
X-Spam-Status: No, score=-4.649 tagged_above=-999 required=5 tests=[AWL=-1.949, BAYES_00=-2.599, FB_CIALIS_LEO3=3.899, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DXLJyuYikySV for <asrg@ietfa.amsl.com>; Fri, 18 Nov 2011 11:26:18 -0800 (PST)
Received: from mx4.sophos.com (mx4.sophos.com [216.47.234.213]) by ietfa.amsl.com (Postfix) with ESMTP id 46BB61F0C34 for <asrg@irtf.org>; Fri, 18 Nov 2011 11:26:09 -0800 (PST)
Received: from mx4.sophos.com (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id 8C81B4E0398 for <asrg@irtf.org>; Fri, 18 Nov 2011 19:26:08 +0000 (GMT)
Received: from uk-exch1.green.sophos (uk-exch1.green.sophos [10.100.199.16]) by mx4.sophos.com (Postfix) with ESMTPS id 349E34E01C5 for <asrg@irtf.org>; Fri, 18 Nov 2011 19:26:08 +0000 (GMT)
Received: from UK-EXCHMBX1.green.sophos ([fe80:0000:0000:0000:e1bd:d3c1:23.222.229.221]) by uk-exch1.green.sophos ([10.100.199.16]) with mapi; Fri, 18 Nov 2011 19:26:07 +0000
From: Martijn Grooten <martijn.grooten@virusbtn.com>
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
Date: Fri, 18 Nov 2011 19:26:05 +0000
Thread-Topic: [Asrg] antiphishing idea
Thread-Index: Acyl9Bvjd/azKOfrQOylADMPrqyTTwAMoZ+w
Message-ID: <18B53BA2A483AD45962AAD1397BE1325382F760216@UK-EXCHMBX1.green.sophos>
References: <CAFdugamtPXjEHiwuJ3N2xyaXK+E0yCJfQi6vOey3jyff1UVvgw@mail.gmail.com> <18B53BA2A483AD45962AAD1397BE1325382F75FA87@UK-EXCHMBX1.green.sophos> <4EC57EDD.30808@mustelids.ca> <CAFduga=LDU7tSPV-Tbjp8iSvhApx+8enmrCXd2E=9YYqoQuTNw@mail.gmail.com> <4EC59A78.6060704@mustelids.ca>
In-Reply-To: <4EC59A78.6060704@mustelids.ca>
Accept-Language: en-US, en-GB
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [Asrg] antiphishing idea
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.12
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/options/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: Fri, 18 Nov 2011 19:26:19 -0000

> What it doesn't do is solve "froggery" (myriads of look-alike domains,
> which your proposal does not solve) nor does it solve the fact that
> most
> of the time the user doesn't even notice what's in the From: line (nor
> does your proposal).  Remember that many mail readers (outlook
> included)
> DO NOT SHOW YOU THE EMAIL ADDRESS in the From: line by default.
>
> Sigh.
>
> APWG just published a report that said that less than 20% of phishes
> had
> the correct phished-for domain in the From line...  Cutwail is pushing
> a
> lot of such things right now.

Indeed. What the OP tries to solve is something that is only relevant to th=
ose phishing emails that:
- are not already blocked by spam filters;
- are not already thrown away as 'phishing' (or simply: as 'not my bank') b=
y the recipient;
- show the From: address in the victim's MUA;
- do use the phished-for domain (and not a subtle variant thereof) in the F=
rom:;
- have a victim that actually checked that From: line and concluded it was =
legitimate because of that.

How many emails are we talking about annually? And, putting the fact that i=
t may not work well or have unwanted side-effects aside, what would the cos=
t of these changes, extra lookups etc. be?

Martijn.



Virus Bulletin Ltd, The Pentagon, Abingdon, OX14 3YP, England.
Company Reg No: 2388295. VAT Reg No: GB 532 5598 33.

From clewis+ietf@mustelids.ca  Fri Nov 18 17:00:48 2011
Return-Path: <clewis+ietf@mustelids.ca>
X-Original-To: asrg@ietfa.amsl.com
Delivered-To: asrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A6DB01F0C45 for <asrg@ietfa.amsl.com>; Fri, 18 Nov 2011 17:00:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.831
X-Spam-Level: 
X-Spam-Status: No, score=-0.831 tagged_above=-999 required=5 tests=[AWL=0.217,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DIPwp0yXJZUr for <asrg@ietfa.amsl.com>; Fri, 18 Nov 2011 17:00:48 -0800 (PST)
Received: from mail.mustelids.ca (unknown [174.35.130.2]) by ietfa.amsl.com (Postfix) with ESMTP id F32441F0C40 for <asrg@irtf.org>; Fri, 18 Nov 2011 17:00:47 -0800 (PST)
Received: from [192.168.0.8] (otter.mustelids.ca [192.168.0.8]) (authenticated bits=0) by mail.mustelids.ca (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id pAJ10kRJ028473 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <asrg@irtf.org>; Fri, 18 Nov 2011 20:00:47 -0500
Message-ID: <4EC6FFBE.5090007@mustelids.ca>
Date: Fri, 18 Nov 2011 20:00:46 -0500
From: Chris Lewis <clewis+ietf@mustelids.ca>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.8.1.23) Gecko/20090812 Thunderbird/2.0.0.23 Mnenhy/0.7.6.666
MIME-Version: 1.0
To: asrg@irtf.org
References: <CAFdugamtPXjEHiwuJ3N2xyaXK+E0yCJfQi6vOey3jyff1UVvgw@mail.gmail.com> <18B53BA2A483AD45962AAD1397BE1325382F75FA87@UK-EXCHMBX1.green.sophos> <CAFdugak9PqRtouPvm-BtnF1Vp00ZtzhBRcTRz2XFuC6+Tg_+_Q@mail.gmail.com> <20111117232759.7955124245@panix5.panix.com> <4EC632EE.7020003@pscs.co.uk>
In-Reply-To: <4EC632EE.7020003@pscs.co.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [Asrg] antiphishing idea
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.12
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/options/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: Sat, 19 Nov 2011 01:00:48 -0000

On 11-11-18 05:26 AM, Paul Smith wrote:

> So, you put the message-id AND recipient in the source's database

I don't want to think about the privacy issues with that.

From asrg3@billmail.scconsult.com  Fri Nov 18 22:54:08 2011
Return-Path: <asrg3@billmail.scconsult.com>
X-Original-To: asrg@ietfa.amsl.com
Delivered-To: asrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 00F9B21F8B8A for <asrg@ietfa.amsl.com>; Fri, 18 Nov 2011 22:54:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UTVdN6SBY204 for <asrg@ietfa.amsl.com>; Fri, 18 Nov 2011 22:54:07 -0800 (PST)
Received: from toaster.scconsult.com (toaster.scconsult.com [66.73.230.185]) by ietfa.amsl.com (Postfix) with ESMTP id DCC0B21F8B89 for <asrg@irtf.org>; Fri, 18 Nov 2011 22:54:06 -0800 (PST)
Received: from deepfield.scconsult.com (deepfield.scconsult.com [192.168.254.22]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by toaster.scconsult.com (Postfix) with ESMTP id A133BEB70E0 for <asrg@irtf.org>; Sat, 19 Nov 2011 01:54:06 -0500 (EST)
Message-ID: <4EC7528C.4080603@billmail.scconsult.com>
Date: Sat, 19 Nov 2011 01:54:04 -0500
From: Bill Cole <asrg3@billmail.scconsult.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
References: <CAFdugamtPXjEHiwuJ3N2xyaXK+E0yCJfQi6vOey3jyff1UVvgw@mail.gmail.com> <20111117221346.27300.qmail@joyce.lan> <CAFduganLWiFQSRP9uG4auEr-bXsHcKSQV=2+C2pEF4AK3QGdKw@mail.gmail.com>
In-Reply-To: <CAFduganLWiFQSRP9uG4auEr-bXsHcKSQV=2+C2pEF4AK3QGdKw@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [Asrg] antiphishing idea
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: asrg@irtf.org
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/options/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: Sat, 19 Nov 2011 06:54:08 -0000

Christian Grunfeld wrote, On 11/17/11 5:19 PM:
> 2011/11/17 John Levine<johnl@taugh.com>:
>>> Domains should have to publish in their DNSs the message-id (among any
>>> other thing) through a TXT or A record of any legit mail sent by them.
>>> The TTLs of those records can be adjusted to compensate for queued
>>> mails, etc.
>>
>> Maybe I'm missing something, but why would you want to do this rather
>> than a DKIM signature?  DKIM validates against the DNS, and protects
>> the whole message.
>
> because I can have a proper configured domain, I can properly sign my
> mails but I can send you an email with From: paypal.com header !
> DKIM does not protect you against this ! DKIM says that evil.com signs
> correctly the email and no alarms will trigger. The average user only
> see and "trust" the From: paypal.com mail header !

The absurd idea of publishing valid MID's in DNS does nothing to stop this. 
The average user doesn't see MID's either, so a phish message can have an 
evil.com Message-ID and a paypal.com From header.

The reason the idea is absurd (beyond being utterly worthless as a practical 
matter) is that MID headers are frequently generated by MUA's that do not 
have any way to communicate the MID to the DNS authority for the domain part 
they use and frequently use domain parts that they really should not. For 
example, <4EC749E5.5040906@gmail.com> is a MID I recently used on a 
perfectly valid piece of email. Thunderbird generated it. A few seconds 
later I used another MUA to send an identical piece of mail with the MID 
<26F5BCB8-3977-452A-AA9B-6D64C9F90D69@gmail.com>. If I logged into GMail and 
sent another copy, it would be some very long local part @mail.gmail.com. I 
could legitimately send an identical message (except for the MID) with my 
GMail address as the From via another SMTP submission system and it would 
get a MID in the domain of the authentication identity I use with that 
sending system OR in gmail.com OR under the hostname of the submission host 
depending on which MUA I use. For many years I used a MUA which by default 
used an IP literal as the domain part of all of its MID's, which can be a 
reasonable tactic in some common circumstances.

At no point does any current MUA have to inject a new DNS record anywhere 
when it constructs a message. A MID is supposed to be globally unique, but 
it isn't really possible for any MUA to assure this perfectly since there is 
no strict standard for how a MID domain is selected or how a MID local-part 
is generated. There is no certainty that a MUA will submit mail through a 
system that will be related to the domain part of the MID.

The next problem is scale. It is not uncommon for a middling company to 
generate many thousands of messages daily with peak rates of multiple 
messages per second, while changing the externally visible DNS zone for the 
domain used in the MID and From on most messages very rarely, perhaps less 
than once in a year. Such an organization would need to make major 
infrastructural changes to deploy your idea, and might well see many (3? 5?) 
orders of magnitude more DNS query traffic on a domain they would now need 
to provision in a radically different way.

This is a concept that shares the fundamental flaws of SPF because it 
presumes that people will change how they send mail to adhere to an 
authentication protocol they know nothing about. It supplements that by 
requiring all MUA's to change and by requiring all domain owners whose users 
send mail to deploy new DNS infrastructure which will in many cases require 
new functionality (authenticated dynamic updates) which most domains do not 
currently use. All for a form of authentication that is inherently weak and 
does nothing that existing authentication mechanisms could do if it weren't 
so meaningless.

You will note that at no point have I suggested that you are crazy.


From schaefer@closedmail.com  Sat Nov 19 04:32:57 2011
Return-Path: <schaefer@closedmail.com>
X-Original-To: asrg@ietfa.amsl.com
Delivered-To: asrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B50F021F84CB for <asrg@ietfa.amsl.com>; Sat, 19 Nov 2011 04:32:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id z+TLPkefFequ for <asrg@ietfa.amsl.com>; Sat, 19 Nov 2011 04:32:52 -0800 (PST)
Received: from vms173017pub.verizon.net (vms173017pub.verizon.net [206.46.173.17]) by ietfa.amsl.com (Postfix) with ESMTP id B60ED21F84C3 for <asrg@irtf.org>; Sat, 19 Nov 2011 04:32:52 -0800 (PST)
Received: from torch.brasslantern.com ([unknown] [71.116.65.135]) by vms173017.mailsrvcs.net (Sun Java(tm) System Messaging Server 7u2-7.02 32bit (built Apr 16 2009)) with ESMTPA id <0LUW00J3QQTTTQH6@vms173017.mailsrvcs.net> for asrg@irtf.org; Sat, 19 Nov 2011 06:32:22 -0600 (CST)
Received: from torch.brasslantern.com (localhost.localdomain [127.0.0.1]) by torch.brasslantern.com (8.13.1/8.13.1) with ESMTP id pAJCWFsv022311	for <asrg@irtf.org>; Sat, 19 Nov 2011 04:32:16 -0800
Received: (from schaefer@localhost)	by torch.brasslantern.com (8.13.1/8.13.1/Submit) id pAJCWD29022310	for asrg@irtf.org; Sat, 19 Nov 2011 04:32:13 -0800
From: Bart Schaefer <schaefer@brasslantern.com>
Message-id: <111119043213.ZM22309@torch.brasslantern.com>
Date: Sat, 19 Nov 2011 04:32:13 -0800
In-reply-to: <4EC7528C.4080603@billmail.scconsult.com>
Comments: In reply to Bill Cole <asrg3@billmail.scconsult.com> "Re: [Asrg] antiphishing idea" (Nov 19,  1:54am)
References: <CAFdugamtPXjEHiwuJ3N2xyaXK+E0yCJfQi6vOey3jyff1UVvgw@mail.gmail.com> <20111117221346.27300.qmail@joyce.lan> <CAFduganLWiFQSRP9uG4auEr-bXsHcKSQV=2+C2pEF4AK3QGdKw@mail.gmail.com> <4EC7528C.4080603@billmail.scconsult.com>
X-Mailer: OpenZMail Classic (0.9.2 24April2005)
To: asrg@irtf.org
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
Subject: Re: [Asrg] antiphishing idea
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.12
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/options/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: Sat, 19 Nov 2011 12:32:57 -0000

On Nov 19,  1:54am, Bill Cole wrote:
}
} The reason the idea is absurd (beyond being utterly worthless as a    
} practical matter) is that MID headers are frequently generated by     
} MUA's that do not have any way to communicate the MID to the DNS      
} authority for the domain part                                         

Wouldn't it be the MTA that would be responsible for grabbing fields
out of the header during transmission and adding them to DNS?  This
would require that the MUA or MSA only talk to an MTA that has that
capability for the domains in both the MID and From, which is a whole
different kettle of fish.

It'd be possible for a 3rd-party service to provide both the database
and the DNS for this, but that's essentially re-inventing Goodmail,
which already failed in the attempt.

From christian.grunfeld@gmail.com  Sat Nov 19 06:55:33 2011
Return-Path: <christian.grunfeld@gmail.com>
X-Original-To: asrg@ietfa.amsl.com
Delivered-To: asrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5FCAA21F854D for <asrg@ietfa.amsl.com>; Sat, 19 Nov 2011 06:55:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.452
X-Spam-Level: 
X-Spam-Status: No, score=-3.452 tagged_above=-999 required=5 tests=[AWL=0.147,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ck5U7OcLiegQ for <asrg@ietfa.amsl.com>; Sat, 19 Nov 2011 06:55:32 -0800 (PST)
Received: from mail-gy0-f182.google.com (mail-gy0-f182.google.com [209.85.160.182]) by ietfa.amsl.com (Postfix) with ESMTP id 5209C21F84F8 for <asrg@irtf.org>; Sat, 19 Nov 2011 06:55:32 -0800 (PST)
Received: by ghbg20 with SMTP id g20so1945753ghb.13 for <asrg@irtf.org>; Sat, 19 Nov 2011 06:55:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=UQhjON7uBMkWDruU2gO19oNEqjvzw2Qj41zdGDD+I0I=; b=FPuWIlH76gCo0dI6KgN0u/e5+JdNprp9972CeO8jvQLJImCqiyJWVGqfRffHSFowMv Y2K52H8rNXERVcHMgRH+4RtQM4S9OpHYRx4gftX6BF7RjKpk/VMg+5L9wQJNbd/YmTnx FfHFyOzTnWcDbNIjaLR3d+jxYCc/KYGXIvq1Q=
MIME-Version: 1.0
Received: by 10.182.50.65 with SMTP id a1mr1648795obo.17.1321714530414; Sat, 19 Nov 2011 06:55:30 -0800 (PST)
Received: by 10.182.47.103 with HTTP; Sat, 19 Nov 2011 06:55:30 -0800 (PST)
In-Reply-To: <4EC7528C.4080603@billmail.scconsult.com>
References: <CAFdugamtPXjEHiwuJ3N2xyaXK+E0yCJfQi6vOey3jyff1UVvgw@mail.gmail.com> <20111117221346.27300.qmail@joyce.lan> <CAFduganLWiFQSRP9uG4auEr-bXsHcKSQV=2+C2pEF4AK3QGdKw@mail.gmail.com> <4EC7528C.4080603@billmail.scconsult.com>
Date: Sat, 19 Nov 2011 11:55:30 -0300
Message-ID: <CAFdugamO2GA5N7=JZt-XoUQo0Z1194hbxrOGsowHWF+fC1AvCw@mail.gmail.com>
From: Christian Grunfeld <christian.grunfeld@gmail.com>
To: asrg3@billmail.scconsult.com, asrg@irtf.org
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [Asrg] antiphishing idea
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.12
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/options/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: Sat, 19 Nov 2011 14:55:33 -0000

> The absurd idea of publishing valid MID's in DNS does nothing to stop this.
> The average user doesn't see MID's either, so a phish message can have an
> evil.com Message-ID and a paypal.com From header.
>
> The reason the idea is absurd (beyond being utterly worthless as a practical
> matter) is that MID headers are frequently generated by MUA's that do not
> have any way to communicate the MID to the DNS authority for the domain part
> they use and frequently use domain parts that they really should not. For
> example, <4EC749E5.5040906@gmail.com> is a MID I recently used on a
> perfectly valid piece of email. Thunderbird generated it. A few seconds
> later I used another MUA to send an identical piece of mail with the MID
> <26F5BCB8-3977-452A-AA9B-6D64C9F90D69@gmail.com>. If I logged into GMail and
> sent another copy, it would be some very long local part @mail.gmail.com. I
> could legitimately send an identical message (except for the MID) with my
> GMail address as the From via another SMTP submission system and it would
> get a MID in the domain of the authentication identity I use with that
> sending system OR in gmail.com OR under the hostname of the submission host
> depending on which MUA I use. For many years I used a MUA which by default
> used an IP literal as the domain part of all of its MID's, which can be a
> reasonable tactic in some common circumstances.
>
> At no point does any current MUA have to inject a new DNS record anywhere
> when it constructs a message. A MID is supposed to be globally unique, but
> it isn't really possible for any MUA to assure this perfectly since there is
> no strict standard for how a MID domain is selected or how a MID local-part
> is generated. There is no certainty that a MUA will submit mail through a
> system that will be related to the domain part of the MID.

I think you really dont know what is a MUA and a MTA ! MUAs SHOULD
submit emails to an MTA who is in charge of the transport for a
domain. Call them smarthosts or whatever you want.
MTAs for a domain should be close related to domain NS and could be
authorized to dinamically update records.

> The next problem is scale. It is not uncommon for a middling company to
> generate many thousands of messages daily with peak rates of multiple
> messages per second, while changing the externally visible DNS zone for the
> domain used in the MID and From on most messages very rarely, perhaps less
> than once in a year. Such an organization would need to make major
> infrastructural changes to deploy your idea, and might well see many (3? 5?)
> orders of magnitude more DNS query traffic on a domain they would now need
> to provision in a radically different way.

you really dont know ! nowdays for EVERY sent email there is a DNS
query...authoritatlvely or cached anywhere answered ! but there is ONE
!....SPF makes one more....DKIM makes one more...my idea makes one
more......how do you absurdely get 3 o 5 orders of magnitud more? do
you know what an order of magnitud is?

> This is a concept that shares the fundamental flaws of SPF because it
> presumes that people will change how they send mail to adhere to an
> authentication protocol they know nothing about. It supplements that by
> requiring all MUA's to change and by requiring all domain owners whose users
> send mail to deploy new DNS infrastructure which will in many cases require
> new functionality (authenticated dynamic updates) which most domains do not
> currently use. All for a form of authentication that is inherently weak and
> does nothing that existing authentication mechanisms could do if it weren't
> so meaningless.
>
> You will note that at no point have I suggested that you are crazy.

sorry but you are stup.....

From prvs=03048F4204=paul@pscs.co.uk  Sat Nov 19 08:40:08 2011
Return-Path: <prvs=03048F4204=paul@pscs.co.uk>
X-Original-To: asrg@ietfa.amsl.com
Delivered-To: asrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4158521F8713 for <asrg@ietfa.amsl.com>; Sat, 19 Nov 2011 08:40:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.549
X-Spam-Level: 
X-Spam-Status: No, score=-2.549 tagged_above=-999 required=5 tests=[AWL=0.050,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id f9pPNz9KFtpT for <asrg@ietfa.amsl.com>; Sat, 19 Nov 2011 08:40:07 -0800 (PST)
Received: from mail.pscs.co.uk (mail.pscs.co.uk [46.20.224.92]) by ietfa.amsl.com (Postfix) with ESMTP id 0CFA821F8512 for <asrg@irtf.org>; Sat, 19 Nov 2011 08:40:05 -0800 (PST)
Received: from lmail.pscs.co.uk ([217.155.61.14]) by mail.pscs.co.uk ([46.20.224.92] running VPOP3) with ESMTP; Sat, 19 Nov 2011 16:40:03 -0000
Received: from [192.168.57.100] ([192.168.57.100]) by lmail.pscs.co.uk ([192.168.66.70] running VPOP3) with ESMTP; Sat, 19 Nov 2011 16:31:42 -0000
Message-ID: <4EC7D9CA.7030900@pscs.co.uk>
Date: Sat, 19 Nov 2011 16:31:06 +0000
From: Paul Smith <paul@pscs.co.uk>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: asrg@irtf.org
References: <CAFdugamtPXjEHiwuJ3N2xyaXK+E0yCJfQi6vOey3jyff1UVvgw@mail.gmail.com> <20111117221346.27300.qmail@joyce.lan> <CAFduganLWiFQSRP9uG4auEr-bXsHcKSQV=2+C2pEF4AK3QGdKw@mail.gmail.com> <4EC7528C.4080603@billmail.scconsult.com>
In-Reply-To: <4EC7528C.4080603@billmail.scconsult.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Authenticated-Sender: paul
X-Server: VPOP3 Enterprise V4.9 - Registered
X-Organisation: Paul Smith Computer Services
Subject: Re: [Asrg] antiphishing idea
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.12
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/options/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: Sat, 19 Nov 2011 16:40:08 -0000

On 19/11/2011 06:54, Bill Cole wrote:
>> mails but I can send you an email with From: paypal.com header !
>> DKIM does not protect you against this ! DKIM says that evil.com signs
>> correctly the email and no alarms will trigger. The average user only
>> see and "trust" the From: paypal.com mail header !
> because I can have a proper configured domain, I can properly sign my
>
> The absurd idea of publishing valid MID's in DNS does nothing to stop 
> this. The average user doesn't see MID's either, so a phish message 
> can have an evil.com Message-ID and a paypal.com From header. 

You're missing the point here.

If you sent a message like:

Message-Id: <12345@gmail.com>
From: info@paypal.com

The receiving MTA would look for something like 
'12345-gmail.com._msgids.paypal.com'

It looks up the message ID in a zone related to the From address, NOT 
the zone related to the message id.

(I'm not saying there aren't other reasons against the original idea, 
but this isn't one of them)

Personally, I like the idea of a callback to validate that mail is what 
it says it is, but I'm not sure about using DNS as the callback mechanism.

> This is a concept that shares the fundamental flaws of SPF because it 
> presumes that people will change how they send mail to adhere to an 
> authentication protocol they know nothing about.
This is what I have problems with. Email at the moment is fundamentally 
flawed, because people send mail assuming totally lax authentication. 
10-15 years ago people used open relays and '% forwarding' all the time, 
but that changed, and people adapted. During the changeover period, lots 
of messages bounced, and people got frustrated (I had to deal with them 
all the time), but people quickly learned the 'right way' to do things 
(because they HAD to), and things improved.

  As long as the 'new authentication' method is implemented strongly, 
then people will adapt. IMV, the reason SPF doesn't work ATM is because 
even people who check it don't reject mail when they should. This lets 
badly configured systems 'sort of work' rather than failing totally. 
'sort of working' systems often stumble on with people getting 
frustrated, and maybe blaming the recipient rather than the sender. 
Failing totally would make the senders sort their stuff out.

Any new authentication method will have to make people change the way 
they work. The challenge is really finding one which will work 
effectively enough to make it worthwhile to need the changes. Rejecting 
solutions because they require changes to the way people work would have 
meant everyone would still be running open relays nowadays.




From asrg3@billmail.scconsult.com  Sat Nov 19 10:07:57 2011
Return-Path: <asrg3@billmail.scconsult.com>
X-Original-To: asrg@ietfa.amsl.com
Delivered-To: asrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D1FEB21F8480 for <asrg@ietfa.amsl.com>; Sat, 19 Nov 2011 10:07:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5FbOL+nRCYAm for <asrg@ietfa.amsl.com>; Sat, 19 Nov 2011 10:07:57 -0800 (PST)
Received: from toaster.scconsult.com (toaster.scconsult.com [66.73.230.185]) by ietfa.amsl.com (Postfix) with ESMTP id 1DE3E21F847B for <asrg@irtf.org>; Sat, 19 Nov 2011 10:07:57 -0800 (PST)
Received: from deepfield.scconsult.com (deepfield.scconsult.com [192.168.254.22]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by toaster.scconsult.com (Postfix) with ESMTP id 48A4BEB7940 for <asrg@irtf.org>; Sat, 19 Nov 2011 13:07:55 -0500 (EST)
Message-ID: <4EC7F07A.4090404@billmail.scconsult.com>
Date: Sat, 19 Nov 2011 13:07:54 -0500
From: Bill Cole <asrg3@billmail.scconsult.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
References: <CAFdugamtPXjEHiwuJ3N2xyaXK+E0yCJfQi6vOey3jyff1UVvgw@mail.gmail.com> <20111117221346.27300.qmail@joyce.lan> <CAFduganLWiFQSRP9uG4auEr-bXsHcKSQV=2+C2pEF4AK3QGdKw@mail.gmail.com> <4EC7528C.4080603@billmail.scconsult.com> <111119043213.ZM22309@torch.brasslantern.com>
In-Reply-To: <111119043213.ZM22309@torch.brasslantern.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [Asrg] antiphishing idea
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: asrg@irtf.org
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/options/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: Sat, 19 Nov 2011 18:07:57 -0000

Bart Schaefer wrote, On 11/19/11 7:32 AM:
> On Nov 19,  1:54am, Bill Cole wrote:
> }
> } The reason the idea is absurd (beyond being utterly worthless as a
> } practical matter) is that MID headers are frequently generated by
> } MUA's that do not have any way to communicate the MID to the DNS
> } authority for the domain part
>
> Wouldn't it be the MTA that would be responsible for grabbing fields
> out of the header during transmission and adding them to DNS?  This
> would require that the MUA or MSA only talk to an MTA that has that
> capability for the domains in both the MID and From, which is a whole
> different kettle of fish.

It would also be a radical narrowing in the definition of legitimate mail 
submission.

As it stands, it is a sound practice to use unrelated domains for the SMTP 
envelope sender and From/Sender/Reply-To/Message-ID headers. SPF was created 
with the hope that mail transport routing could be controlled enough to 
allow repudiation of mail at the transport layer, but that has proven to be 
a failure in general application. Only a small number of special-function 
domains can safely use "-all" in their SPF records.

Shorter: This mechanism would force some people to change how they submit 
mail. SPF has demonstrated that to be a crippling flaw.

> It'd be possible for a 3rd-party service to provide both the database
> and the DNS for this, but that's essentially re-inventing Goodmail,
> which already failed in the attempt.

We are at the point in mail authentication where there is very little space 
left for truly new mechanisms that aren't ultimately equivalent to existing 
limited successes like SPF and DKIM or past failures like Goodmail.

Anyone who wants trustworthy mail authentication and is willing to sacrifice 
the inherent functional and overhead costs of that ought to know where to 
find S/MIME and PGP. With SPF and DKIM broadly but not universally deployed 
it is hard to seriously consider proposals that buy slightly more 
authentication at the price of slightly constricting how people use email 
and requiring mail providers to set up substantial new infrastructure. From 
what I can see, there is very little space for concrete improvement from 
mail authentication without requiring smarter users and/or the end to 
accepting mail from random well-meaning strangers. The former is a pipe 
dream, the latter would be a tragedy.

From johnl@iecc.com  Sat Nov 19 11:05:37 2011
Return-Path: <johnl@iecc.com>
X-Original-To: asrg@ietfa.amsl.com
Delivered-To: asrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A87FD21F85BB for <asrg@ietfa.amsl.com>; Sat, 19 Nov 2011 11:05:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -111.069
X-Spam-Level: 
X-Spam-Status: No, score=-111.069 tagged_above=-999 required=5 tests=[AWL=0.130, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ydMoSvIqSdEj for <asrg@ietfa.amsl.com>; Sat, 19 Nov 2011 11:05:37 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [64.57.183.53]) by ietfa.amsl.com (Postfix) with ESMTP id F30C021F877F for <asrg@irtf.org>; Sat, 19 Nov 2011 11:05:36 -0800 (PST)
Received: (qmail 65953 invoked from network); 19 Nov 2011 19:05:35 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 19 Nov 2011 19:05:35 -0000
Date: 19 Nov 2011 19:05:13 -0000
Message-ID: <20111119190513.29824.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: asrg@irtf.org
In-Reply-To: <4EC7D9CA.7030900@pscs.co.uk>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
Subject: Re: [Asrg] per message databases, was antiphishing idea
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.12
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/options/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: Sat, 19 Nov 2011 19:05:37 -0000

>The receiving MTA would look for something like 
>'12345-gmail.com._msgids.paypal.com'
>
>It looks up the message ID in a zone related to the From address, NOT 
>the zone related to the message id.

I think we need a new category of FUSSP for anything that requires the
sender to maintain a public per-message database of all the messages
it's sent.  To put it mildly, this really REALLY doesn't scale.

R's,
John

PS: I'm not saying this is the only reason that looking up the message-id
isn't a good idea.

From steve@blighty.com  Sat Nov 19 11:44:39 2011
Return-Path: <steve@blighty.com>
X-Original-To: asrg@ietfa.amsl.com
Delivered-To: asrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B192321F85AA for <asrg@ietfa.amsl.com>; Sat, 19 Nov 2011 11:44:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.399
X-Spam-Level: 
X-Spam-Status: No, score=-2.399 tagged_above=-999 required=5 tests=[AWL=0.200,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id B+M27YlyHqR4 for <asrg@ietfa.amsl.com>; Sat, 19 Nov 2011 11:44:36 -0800 (PST)
Received: from m.wordtothewise.com (misc.wordtothewise.com [184.105.179.154]) by ietfa.amsl.com (Postfix) with ESMTP id 5346921F85A7 for <asrg@irtf.org>; Sat, 19 Nov 2011 11:44:36 -0800 (PST)
Received: from [192.168.80.43] (204.11.227.194.static.etheric.net [204.11.227.194]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: steve) by m.wordtothewise.com (Postfix) with ESMTPSA id D9EB12EB5A for <asrg@irtf.org>; Sat, 19 Nov 2011 11:44:28 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1251.1)
From: Steve Atkins <steve@blighty.com>
In-Reply-To: <20111119190513.29824.qmail@joyce.lan>
Date: Sat, 19 Nov 2011 11:44:28 -0800
Content-Transfer-Encoding: 7bit
Message-Id: <3EE701FD-7298-4D78-8571-63E6FC2EE945@blighty.com>
References: <20111119190513.29824.qmail@joyce.lan>
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
X-Mailer: Apple Mail (2.1251.1)
Subject: Re: [Asrg] per message databases, was antiphishing idea
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.12
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/options/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: Sat, 19 Nov 2011 19:44:39 -0000

On Nov 19, 2011, at 11:05 AM, John Levine wrote:

>> The receiving MTA would look for something like 
>> '12345-gmail.com._msgids.paypal.com'
>> 
>> It looks up the message ID in a zone related to the From address, NOT 
>> the zone related to the message id.
> 
> I think we need a new category of FUSSP for anything that requires the
> sender to maintain a public per-message database of all the messages
> it's sent.  To put it mildly, this really REALLY doesn't scale.


As a thought experiment, if every sender offered a POP3-esque service
rather than sending mail by SMTP, it would require about the same amount
of resources as the receivers are providing today to manage that same
traffic, and that's not unreasonable.

A database of just recent messages sent would require less resources than
that.

Cheers,
  Steve


From asrg3@billmail.scconsult.com  Sat Nov 19 11:47:58 2011
Return-Path: <asrg3@billmail.scconsult.com>
X-Original-To: asrg@ietfa.amsl.com
Delivered-To: asrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 90EDA21F84B6 for <asrg@ietfa.amsl.com>; Sat, 19 Nov 2011 11:47:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id H4pztVPv8lwK for <asrg@ietfa.amsl.com>; Sat, 19 Nov 2011 11:47:57 -0800 (PST)
Received: from toaster.scconsult.com (www.scconsult.com [66.73.230.185]) by ietfa.amsl.com (Postfix) with ESMTP id 2BA8221F84AB for <asrg@irtf.org>; Sat, 19 Nov 2011 11:47:57 -0800 (PST)
Received: from deepfield.scconsult.com (deepfield.scconsult.com [192.168.254.22]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by toaster.scconsult.com (Postfix) with ESMTP id 77F5DEB7AAD for <asrg@irtf.org>; Sat, 19 Nov 2011 14:47:56 -0500 (EST)
Message-ID: <4EC807EB.4010608@billmail.scconsult.com>
Date: Sat, 19 Nov 2011 14:47:55 -0500
From: Bill Cole <asrg3@billmail.scconsult.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
References: <CAFdugamtPXjEHiwuJ3N2xyaXK+E0yCJfQi6vOey3jyff1UVvgw@mail.gmail.com> <20111117221346.27300.qmail@joyce.lan> <CAFduganLWiFQSRP9uG4auEr-bXsHcKSQV=2+C2pEF4AK3QGdKw@mail.gmail.com> <4EC7528C.4080603@billmail.scconsult.com> <CAFdugamO2GA5N7=JZt-XoUQo0Z1194hbxrOGsowHWF+fC1AvCw@mail.gmail.com>
In-Reply-To: <CAFdugamO2GA5N7=JZt-XoUQo0Z1194hbxrOGsowHWF+fC1AvCw@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [Asrg] antiphishing idea
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: asrg@irtf.org
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/options/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: Sat, 19 Nov 2011 19:47:58 -0000

Please fix your MUA to respect Reply-To headers.

Christian Grunfeld wrote, On 11/19/11 9:55 AM:
>> The absurd idea of publishing valid MID's in DNS does nothing to stop this.
>> The average user doesn't see MID's either, so a phish message can have an
>> evil.com Message-ID and a paypal.com From header.
>>
>> The reason the idea is absurd (beyond being utterly worthless as a practical
>> matter) is that MID headers are frequently generated by MUA's that do not
>> have any way to communicate the MID to the DNS authority for the domain part
>> they use and frequently use domain parts that they really should not. For
>> example,<4EC749E5.5040906@gmail.com>  is a MID I recently used on a
>> perfectly valid piece of email. Thunderbird generated it. A few seconds
>> later I used another MUA to send an identical piece of mail with the MID
>> <26F5BCB8-3977-452A-AA9B-6D64C9F90D69@gmail.com>. If I logged into GMail and
>> sent another copy, it would be some very long local part @mail.gmail.com. I
>> could legitimately send an identical message (except for the MID) with my
>> GMail address as the From via another SMTP submission system and it would
>> get a MID in the domain of the authentication identity I use with that
>> sending system OR in gmail.com OR under the hostname of the submission host
>> depending on which MUA I use. For many years I used a MUA which by default
>> used an IP literal as the domain part of all of its MID's, which can be a
>> reasonable tactic in some common circumstances.
>>
>> At no point does any current MUA have to inject a new DNS record anywhere
>> when it constructs a message. A MID is supposed to be globally unique, but
>> it isn't really possible for any MUA to assure this perfectly since there is
>> no strict standard for how a MID domain is selected or how a MID local-part
>> is generated. There is no certainty that a MUA will submit mail through a
>> system that will be related to the domain part of the MID.
>
> I think you really dont know what is a MUA and a MTA !

I understand both fairly well, but I appreciate your concern for my 
understanding. It is unfortunate that there seems to be a language barrier 
preventing you from coherently explaining my ignorance to me.

> MUAs SHOULD
> submit emails to an MTA who is in charge of the transport for a
> domain.

That is something many people have been arguing about for many years. If you 
dig through the Google Groups archive you can find me going into the 
question at length in the late 1990's. I was wrong then because I thought 
that a mechanism equivalent to SPF would force people to use well-defined 
submission and transport paths tightly bound to the domains they use in 
their email addresses. SPF in widespread deployment has proven me wrong on 
that point. It is somewhat quaint to see someone still insisting on that 
sort of binding.

> Call them smarthosts or whatever you want.
> MTAs for a domain should be close related to domain NS and could be
> authorized to dinamically update records.

It would be useful for you to think about how you are using the words 
"should" and "could."

In a previous job I managed mail servers for the US subsidiary of a major 
global conglomerate headquartered in Germany. Due to control fetishists in 
Berlin and Frankfurt and some corporate asset shuffling between parent 
companies, some of the domains used by US employees had their authoritative 
DNS in very stable zones on machines in Germany. At one point a US IT 
manager insisted that we put SPF records in for one of those domains. That 
took 6 weeks, because no one in the US had been informed when 
responsibilities were shuffled in DE. Less than a year later when we were 
migrating our mail servers to a new set of machines with new IP's, it took 3 
weeks to get the SPF records changed because it was August (when apparently 
virtually everyone in Germany is on vacation.) In getting that change done, 
I learned that the authoritative DNS was running on hardware and software 
that had not been updated since 1997, almost a decade of stability. The 
person who told me this was very proud of it.

The point of that story: in the real world, there are generally functional 
email and DNS systems that do not work anything like the way you think they 
should now and really could not be adjusted to work as you want them without 
significant modifications to the software, hardware, and humans involved.


>> The next problem is scale. It is not uncommon for a middling company to
>> generate many thousands of messages daily with peak rates of multiple
>> messages per second, while changing the externally visible DNS zone for the
>> domain used in the MID and From on most messages very rarely, perhaps less
>> than once in a year. Such an organization would need to make major
>> infrastructural changes to deploy your idea, and might well see many (3? 5?)
>> orders of magnitude more DNS query traffic on a domain they would now need
>> to provision in a radically different way.
>
> you really dont know ! nowdays for EVERY sent email there is a DNS
> query...authoritatlvely or cached anywhere answered ! but there is ONE
> !....SPF makes one more....DKIM makes one more...my idea makes one
> more......how do you absurdely get 3 o 5 orders of magnitud more? do
> you know what an order of magnitud is?

Yes, or I would not have used the term. The above paragraph convinces me 
that we have a communication problem due to language.

It is not true today that every email message requires the creation of a new 
DNS record. This is not even true for domains that have deployed SPF and 
DKIM. It is quite possible for a domain to be stable for years with 
thousands of messages per day flowing from its users.

Query traffic for an authoritative DNS server due to mail can be trivial. 
Yes, there are queries as a result of each message sent, but today those are 
queries for records that can have TTL's of a day or longer. This means they 
are cacheable so that the authoritative server has query traffic that is a 
function of the diversity of recipients (i.e.how many DNS caches their MX 
hosts use in aggregate) rather than the number of unique messages. For large 
mail systems this can mean that the queries to their authoritative servers 
tops out in the low thousands per day that is attributable to mail. If there 
is to be a mechanism that requires a unique query per message by the MX host 
for a recipient, the authoritative server will get no help at all from the 
existence of DNS caches. I've worked with domains whose mail targets were 
focused enough that they got less than a thousand SPF queries per week for 
over a million messages sent, so 3 orders of magnitude boost in queries is 
definitely possible if there were to be a query per message. 5 OoM may be a 
stretch, but maybe not for a big bulk sender.

>> This is a concept that shares the fundamental flaws of SPF because it
>> presumes that people will change how they send mail to adhere to an
>> authentication protocol they know nothing about. It supplements that by
>> requiring all MUA's to change and by requiring all domain owners whose users
>> send mail to deploy new DNS infrastructure which will in many cases require
>> new functionality (authenticated dynamic updates) which most domains do not
>> currently use. All for a form of authentication that is inherently weak and
>> does nothing that existing authentication mechanisms could do if it weren't
>> so meaningless.
>>
>> You will note that at no point have I suggested that you are crazy.
>
> sorry but you are stup.....

OK, that's not a language issue. We're done here.

From schaefer@closedmail.com  Sat Nov 19 12:23:33 2011
Return-Path: <schaefer@closedmail.com>
X-Original-To: asrg@ietfa.amsl.com
Delivered-To: asrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CF4B121F84DD for <asrg@ietfa.amsl.com>; Sat, 19 Nov 2011 12:23:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GcuhGPn0ng9V for <asrg@ietfa.amsl.com>; Sat, 19 Nov 2011 12:23:33 -0800 (PST)
Received: from vms173005pub.verizon.net (vms173005pub.verizon.net [206.46.173.5]) by ietfa.amsl.com (Postfix) with ESMTP id EB82021F84DC for <asrg@irtf.org>; Sat, 19 Nov 2011 12:23:32 -0800 (PST)
Received: from torch.brasslantern.com ([unknown] [71.116.65.135]) by vms173005.mailsrvcs.net (Sun Java(tm) System Messaging Server 7u2-7.02 32bit (built Apr 16 2009)) with ESMTPA id <0LUX00M2SCMOHN50@vms173005.mailsrvcs.net> for asrg@irtf.org; Sat, 19 Nov 2011 14:23:18 -0600 (CST)
Received: from torch.brasslantern.com (localhost.localdomain [127.0.0.1]) by torch.brasslantern.com (8.13.1/8.13.1) with ESMTP id pAJKN9Tr022638	for <asrg@irtf.org>; Sat, 19 Nov 2011 12:23:11 -0800
Received: (from schaefer@localhost)	by torch.brasslantern.com (8.13.1/8.13.1/Submit) id pAJKN83L022637	for asrg@irtf.org; Sat, 19 Nov 2011 12:23:08 -0800
From: Bart Schaefer <schaefer@brasslantern.com>
Message-id: <111119122308.ZM22636@torch.brasslantern.com>
Date: Sat, 19 Nov 2011 12:23:08 -0800
In-reply-to: <3EE701FD-7298-4D78-8571-63E6FC2EE945@blighty.com>
Comments: In reply to Steve Atkins <steve@blighty.com> "Re: [Asrg] per message databases, was antiphishing idea" (Nov 19, 11:44am)
References: <20111119190513.29824.qmail@joyce.lan> <3EE701FD-7298-4D78-8571-63E6FC2EE945@blighty.com>
X-Mailer: OpenZMail Classic (0.9.2 24April2005)
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
Subject: Re: [Asrg] per message databases, was antiphishing idea
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.12
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/options/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: Sat, 19 Nov 2011 20:23:33 -0000

On Nov 19, 11:44am, Steve Atkins wrote:
}
} As a thought experiment, if every sender offered a POP3-esque service
} rather than sending mail by SMTP

How is that different from DJB's IM2000?

Cf. http://en.wikipedia.org/wiki/StubMail

From steve@blighty.com  Sat Nov 19 12:27:09 2011
Return-Path: <steve@blighty.com>
X-Original-To: asrg@ietfa.amsl.com
Delivered-To: asrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E9D3A21F869E for <asrg@ietfa.amsl.com>; Sat, 19 Nov 2011 12:27:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.428
X-Spam-Level: 
X-Spam-Status: No, score=-2.428 tagged_above=-999 required=5 tests=[AWL=0.171,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p6b6BDUtzKG2 for <asrg@ietfa.amsl.com>; Sat, 19 Nov 2011 12:27:09 -0800 (PST)
Received: from m.wordtothewise.com (misc.wordtothewise.com [184.105.179.154]) by ietfa.amsl.com (Postfix) with ESMTP id 6C64D21F85AA for <asrg@irtf.org>; Sat, 19 Nov 2011 12:27:09 -0800 (PST)
Received: from [192.168.80.43] (204.11.227.194.static.etheric.net [204.11.227.194]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: steve) by m.wordtothewise.com (Postfix) with ESMTPSA id 40E172EB3D for <asrg@irtf.org>; Sat, 19 Nov 2011 12:27:09 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1251.1)
From: Steve Atkins <steve@blighty.com>
In-Reply-To: <111119122308.ZM22636@torch.brasslantern.com>
Date: Sat, 19 Nov 2011 12:27:07 -0800
Content-Transfer-Encoding: 7bit
Message-Id: <A1ACBF5A-262A-428A-B0CB-399C86C1DF91@blighty.com>
References: <20111119190513.29824.qmail@joyce.lan> <3EE701FD-7298-4D78-8571-63E6FC2EE945@blighty.com> <111119122308.ZM22636@torch.brasslantern.com>
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
X-Mailer: Apple Mail (2.1251.1)
Subject: Re: [Asrg] per message databases, was antiphishing idea
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.12
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/options/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: Sat, 19 Nov 2011 20:27:10 -0000

On Nov 19, 2011, at 12:23 PM, Bart Schaefer wrote:

> On Nov 19, 11:44am, Steve Atkins wrote:
> }
> } As a thought experiment, if every sender offered a POP3-esque service
> } rather than sending mail by SMTP
> 
> How is that different from DJB's IM2000?
> 
> Cf. http://en.wikipedia.org/wiki/StubMail

One was put forward as a thought experiment, to help estimate
system resource usage, and will never be deployed.

The other will just never be deployed.

Cheers,
  Steve


From johnl@iecc.com  Sat Nov 19 12:31:42 2011
Return-Path: <johnl@iecc.com>
X-Original-To: asrg@ietfa.amsl.com
Delivered-To: asrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 37A2921F869E for <asrg@ietfa.amsl.com>; Sat, 19 Nov 2011 12:31:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -111.081
X-Spam-Level: 
X-Spam-Status: No, score=-111.081 tagged_above=-999 required=5 tests=[AWL=0.118, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id E-0fB2o4kRoK for <asrg@ietfa.amsl.com>; Sat, 19 Nov 2011 12:31:41 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [64.57.183.53]) by ietfa.amsl.com (Postfix) with ESMTP id 86BAD21F8669 for <asrg@irtf.org>; Sat, 19 Nov 2011 12:31:41 -0800 (PST)
Received: (qmail 98193 invoked from network); 19 Nov 2011 20:31:40 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 19 Nov 2011 20:31:40 -0000
Date: 19 Nov 2011 20:31:18 -0000
Message-ID: <20111119203118.33012.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: asrg@irtf.org
In-Reply-To: <111119122308.ZM22636@torch.brasslantern.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
Subject: Re: [Asrg] per message databases, was antiphishing idea
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.12
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/options/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: Sat, 19 Nov 2011 20:31:42 -0000

>} As a thought experiment, if every sender offered a POP3-esque service
>} rather than sending mail by SMTP
>
>How is that different from DJB's IM2000?

It's more like RSS.  But I take your point.

I think there's a difference due to the different update and query
patterns.  Anything that requires a high update rate and global
consistency is really hard and doesn't parallelize well.  That's why
ATM networks and airline reservations still use million dollar
mainframes rather than farms of PCs.

R's,
John

From clewis+ietf@mustelids.ca  Sat Nov 19 12:36:02 2011
Return-Path: <clewis+ietf@mustelids.ca>
X-Original-To: asrg@ietfa.amsl.com
Delivered-To: asrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DDD7D21F86D0 for <asrg@ietfa.amsl.com>; Sat, 19 Nov 2011 12:36:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.871
X-Spam-Level: 
X-Spam-Status: No, score=-0.871 tagged_above=-999 required=5 tests=[AWL=0.177,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BHptlSYiexT2 for <asrg@ietfa.amsl.com>; Sat, 19 Nov 2011 12:36:02 -0800 (PST)
Received: from mail.mustelids.ca (unknown [174.35.130.2]) by ietfa.amsl.com (Postfix) with ESMTP id 33F9321F86AA for <asrg@irtf.org>; Sat, 19 Nov 2011 12:36:02 -0800 (PST)
Received: from [192.168.0.8] (otter.mustelids.ca [192.168.0.8]) (authenticated bits=0) by mail.mustelids.ca (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id pAJKZke0025731 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <asrg@irtf.org>; Sat, 19 Nov 2011 15:35:47 -0500
Message-ID: <4EC81322.8060008@mustelids.ca>
Date: Sat, 19 Nov 2011 15:35:46 -0500
From: Chris Lewis <clewis+ietf@mustelids.ca>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.8.1.23) Gecko/20090812 Thunderbird/2.0.0.23 Mnenhy/0.7.6.666
MIME-Version: 1.0
To: asrg@irtf.org
References: <20111119190513.29824.qmail@joyce.lan> <3EE701FD-7298-4D78-8571-63E6FC2EE945@blighty.com>
In-Reply-To: <3EE701FD-7298-4D78-8571-63E6FC2EE945@blighty.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [Asrg] per message databases, was antiphishing idea
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.12
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/options/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: Sat, 19 Nov 2011 20:36:03 -0000

On 11-11-19 02:44 PM, Steve Atkins wrote:

> As a thought experiment, if every sender offered a POP3-esque service
> rather than sending mail by SMTP, it would require about the same amount
> of resources as the receivers are providing today to manage that same
> traffic, and that's not unreasonable.

It's called webmail, and I think it's true that you have to build out 
rather more infrastructure to support it than with a typical perimeter 
MTA/internal POP3-esque service.  The security implications are rather 
different as well.

Note also that per message database _traffic_ would scale with the total 
amount of email (around 80-95% spam), whereas POP and webmail 
infrastructure scales with the ham.

The per message database queries in DNS wouldn't be cacheable whereas 
about everything else in DNS is.  3-5 orders of magnitude increase in 
DNS traffic to the authoritatives isn't unreasonable in the least.

With large infrastructures doing messages to the tune of 100s or 1000s 
per second, usefully doing DNS updates at that frequency (and timely 
enough to be there when the receiver wants to query) seem entirely 
implausible to me.  Or you delay the email on the sending side to wait 
for the database to update... Ick.

A few thousand entries per second, with a hold-time of at least 4 days 
also seems a bit much for DNS to cope with - because _all_ your 
authoritatives would have to know them, and know them real fast, 
preferably before the email is sent.

From christian.grunfeld@gmail.com  Sat Nov 19 16:06:29 2011
Return-Path: <christian.grunfeld@gmail.com>
X-Original-To: asrg@ietfa.amsl.com
Delivered-To: asrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BA7A021F8500 for <asrg@ietfa.amsl.com>; Sat, 19 Nov 2011 16:06:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.468
X-Spam-Level: 
X-Spam-Status: No, score=-3.468 tagged_above=-999 required=5 tests=[AWL=0.131,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id C-WWKh0yOdF5 for <asrg@ietfa.amsl.com>; Sat, 19 Nov 2011 16:06:29 -0800 (PST)
Received: from mail-yw0-f54.google.com (mail-yw0-f54.google.com [209.85.213.54]) by ietfa.amsl.com (Postfix) with ESMTP id 0735121F84FD for <asrg@irtf.org>; Sat, 19 Nov 2011 16:06:28 -0800 (PST)
Received: by ywe9 with SMTP id 9so5336816ywe.13 for <asrg@irtf.org>; Sat, 19 Nov 2011 16:06:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=XxnyJGIp6har/e13HUJod7zsERiC+E1Lqamzl9dMStY=; b=RP/2JY9dXcuJ3dGxdLkxfPyKItYjSDGph/NQXYghbylHxe9A0LcEfPHQ56AEsNczPW jDk/SE/skJYxRZhzP1+S2E5VsudgzjxLWMM3S+9eYfgLazTntzksgLNUiQTlgPytypLx OnDWY1FnchUDPvYDDiLsoHw9LkE7Z8y9/2O4s=
MIME-Version: 1.0
Received: by 10.182.216.105 with SMTP id op9mr1873440obc.57.1321747588284; Sat, 19 Nov 2011 16:06:28 -0800 (PST)
Received: by 10.182.47.103 with HTTP; Sat, 19 Nov 2011 16:06:28 -0800 (PST)
In-Reply-To: <4EC807EB.4010608@billmail.scconsult.com>
References: <CAFdugamtPXjEHiwuJ3N2xyaXK+E0yCJfQi6vOey3jyff1UVvgw@mail.gmail.com> <20111117221346.27300.qmail@joyce.lan> <CAFduganLWiFQSRP9uG4auEr-bXsHcKSQV=2+C2pEF4AK3QGdKw@mail.gmail.com> <4EC7528C.4080603@billmail.scconsult.com> <CAFdugamO2GA5N7=JZt-XoUQo0Z1194hbxrOGsowHWF+fC1AvCw@mail.gmail.com> <4EC807EB.4010608@billmail.scconsult.com>
Date: Sat, 19 Nov 2011 21:06:28 -0300
Message-ID: <CAFdugan4Hg-5GYqCVp9U7+H0qRE6c_gHH+fE+b=JX+87JsmU1Q@mail.gmail.com>
From: Christian Grunfeld <christian.grunfeld@gmail.com>
To: asrg@irtf.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: Re: [Asrg] antiphishing idea
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.12
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/options/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: Sun, 20 Nov 2011 00:06:29 -0000

2011/11/19 Bill Cole <asrg3@billmail.scconsult.com>:

> I understand both fairly well, but I appreciate your concern for my
> understanding. It is unfortunate that there seems to be a language barrie=
r
> preventing you from coherently explaining my ignorance to me.

I do not need to explain coherently your ignorance to you since you're
doing pretty well job yourself.


> It would be useful for you to think about how you are using the words
> "should" and "could."

In my "bubble world" MUAs MUST submit emails to an MTA. Maybe not in
yours...that was why I=B4ve used "should".
SPF records tell the world which systems can send email for a
domain...so (as I said) MTAs are closely related to DNS servers for
that domain. With "closely related" I mean they must know each
other..then dynamic updates "could" be easily implemented !


> In a previous job I managed mail servers for the US subsidiary of a major
> global conglomerate headquartered in Germany. Due to control fetishists i=
n
> Berlin and Frankfurt and some corporate asset shuffling between parent
> companies, some of the domains used by US employees had their authoritati=
ve
> DNS in very stable zones on machines in Germany. At one point a US IT
> manager insisted that we put SPF records in for one of those domains. Tha=
t
> took 6 weeks, because no one in the US had been informed when
> responsibilities were shuffled in DE. Less than a year later when we were
> migrating our mail servers to a new set of machines with new IP's, it too=
k 3
> weeks to get the SPF records changed because it was August (when apparent=
ly
> virtually everyone in Germany is on vacation.) In getting that change don=
e,
> I learned that the authoritative DNS was running on hardware and software
> that had not been updated since 1997, almost a decade of stability. The
> person who told me this was very proud of it.

> The point of that story: in the real world, there are generally functiona=
l
> email and DNS systems that do not work anything like the way you think th=
ey
> should now and really could not be adjusted to work as you want them with=
out
> significant modifications to the software, hardware, and humans involved.

you 're talking about the Internet about 15 years ago. As someone
said...when using open relays was a "good" practice ! do not confuse
stability with no improvement !
No human intervention is needed to get dynamic updates to work. You
only need that NS trust you and accept your updates. And obviously if
those conditions are met you dont even need that NS are close to
you....they can stay in germany!


> It is not true today that every email message requires the creation of a =
new
> DNS record. This is not even true for domains that have deployed SPF and
> DKIM. It is quite possible for a domain to be stable for years with
> thousands of messages per day flowing from its users.

It is not true, right ! but I did not say that. I think you're
confusing a DNS query with a creation of a RR !
I said that today for every email there is at least one DNS query. If
your server checks for a fqdn HELO or a correct map between IP and
names you have a query. If your server checks SPF you have another. If
your server checks DKIM you have another. Its true that some of them
can be cached.

> .... I've worked with domains whose mail targets were
> focused enough that they got less than a thousand SPF queries per week fo=
r
> over a million messages sent, so 3 orders of magnitude boost in queries i=
s
> definitely possible if there were to be a query per message. 5 OoM may be=
 a
> stretch, but maybe not for a big bulk sender.

Well, you've worked in many places !  you got SPF queries in the
manner that others implement it or not. It is not an indicator of
query volumes !


>> sorry but you are stup.....
>
> OK, that's not a language issue. We're done here.

sorry about that

From prvs=0305DC4C8F=paul@pscs.co.uk  Sat Nov 19 16:10:29 2011
Return-Path: <prvs=0305DC4C8F=paul@pscs.co.uk>
X-Original-To: asrg@ietfa.amsl.com
Delivered-To: asrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E5E2321F8512 for <asrg@ietfa.amsl.com>; Sat, 19 Nov 2011 16:10:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.556
X-Spam-Level: 
X-Spam-Status: No, score=-2.556 tagged_above=-999 required=5 tests=[AWL=0.043,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0t9bxo5-JCbP for <asrg@ietfa.amsl.com>; Sat, 19 Nov 2011 16:10:28 -0800 (PST)
Received: from mail.pscs.co.uk (mail.pscs.co.uk [46.20.224.92]) by ietfa.amsl.com (Postfix) with ESMTP id 5F15921F8511 for <asrg@irtf.org>; Sat, 19 Nov 2011 16:10:28 -0800 (PST)
Received: from lmail.pscs.co.uk ([217.155.61.14]) by mail.pscs.co.uk ([46.20.224.92] running VPOP3) with ESMTP; Sun, 20 Nov 2011 00:10:09 -0000
Received: from [192.168.57.100] ([192.168.57.100]) by lmail.pscs.co.uk ([192.168.66.70] running VPOP3) with ESMTP; Sun, 20 Nov 2011 00:07:41 -0000
Message-ID: <4EC844A6.70609@pscs.co.uk>
Date: Sun, 20 Nov 2011 00:07:02 +0000
From: Paul Smith <paul@pscs.co.uk>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
References: <20111119190513.29824.qmail@joyce.lan> <3EE701FD-7298-4D78-8571-63E6FC2EE945@blighty.com> <4EC81322.8060008@mustelids.ca>
In-Reply-To: <4EC81322.8060008@mustelids.ca>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Authenticated-Sender: paul
X-Server: VPOP3 Enterprise V4.9 - Registered
X-Organisation: Paul Smith Computer Services
Subject: Re: [Asrg] per message databases, was antiphishing idea
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.12
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/options/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: Sun, 20 Nov 2011 00:10:30 -0000

On 19/11/2011 20:35, Chris Lewis wrote:
> Note also that per message database _traffic_ would scale with the 
> total amount of email (around 80-95% spam), whereas POP and webmail 
> infrastructure scales with the ham.
Yes, unless it has such a beneficial effect that spammers give up...  
:)  (or at least stop forging messages from those domains protected by 
this system)

Also, obviously, message IDs could easily be constructed to spread the 
load among DNS servers

> The per message database queries in DNS wouldn't be cacheable whereas 
> about everything else in DNS is.  3-5 orders of magnitude increase in 
> DNS traffic to the authoritatives isn't unreasonable in the least.
Only the last part of the DNS queries wouldn't be cacheable AFAICT.

So, if the message ID was '12345.bibble55@gmail.com', translating to a 
lookup of something like '12345.bibble55.gmail.com_msgids.gmail.com', 
only the '12345' bit isn't cacheable. The resolution down to the 
bibble55.gmail.com._msgids.gmail.com. would be cacheable AFAICS, and 
would allow partitioning of the data & queries to the 'bibble55' 
authoritative DNS server. So, root servers and Google's 'normal' DNS 
servers wouldn't have significantly more load than now (if any at all), 
it would just be the msgid DNS servers which would be loaded.

The message IDs can easily be generated so that a particular DNS server 
is not overloaded. Even so that the zones go out of use after a few 
days, so the higher level DNS server just returns a non-existent domain 
(with a big TTL) for the 'bibble55' zone when they have all "expired", 
rather than having that DNS server still handling checks on old message IDs.

In fact, using DNS would appear to enable scaling to massive levels 
quite well because of its built in delegation capabilities.

>
> With large infrastructures doing messages to the tune of 100s or 1000s 
> per second, usefully doing DNS updates at that frequency (and timely 
> enough to be there when the receiver wants to query) seem entirely 
> implausible to me.  Or you delay the email on the sending side to wait 
> for the database to update... Ick.
>
> A few thousand entries per second, with a hold-time of at least 4 days 
> also seems a bit much for DNS to cope with - because _all_ your 
> authoritatives would have to know them, and know them real fast, 
> preferably before the email is sent. 

I'm not sure how that would be such a big problem. The DNS server 
obviously wouldn't be a basic Bind setup (having to reload zone files 
etc), or with ddns updates, it would be a "custom" DNS server feeding 
off a backend database which knows about the message data at the same 
time as the sending MTA (or even when the messages are queued for sending)

It is also possible that the message IDs could be generated 
cryptographically, so the DNS server doesn't even need to have a 
database of message IDs, but can check, with a reasonable level of 
confidence, that the message ID is valid.

Also, given that 90% of the email we receive via Yahoo's servers is 
spam, if the spam is cut, then the large infrastructures should be 
sending a lot less spam out, so the problem will be smaller ;)

My big problem with this idea is that I'm not sure how it would really 
help more than other ideas. I don't see the use of DNS as being that big 
an issue, it's just a UDP callback check in essence. It's massively more 
efficient than a CBV check, at least as efficient as some SPF checks 
(using macros), and miniscule compared to the actual SMTP transaction.




From schaefer@closedmail.com  Sat Nov 19 16:43:45 2011
Return-Path: <schaefer@closedmail.com>
X-Original-To: asrg@ietfa.amsl.com
Delivered-To: asrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AF7DB21F8441 for <asrg@ietfa.amsl.com>; Sat, 19 Nov 2011 16:43:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id u5TBpxZ9aLSc for <asrg@ietfa.amsl.com>; Sat, 19 Nov 2011 16:43:45 -0800 (PST)
Received: from vms173005pub.verizon.net (vms173005pub.verizon.net [206.46.173.5]) by ietfa.amsl.com (Postfix) with ESMTP id 4300E21F8445 for <asrg@irtf.org>; Sat, 19 Nov 2011 16:43:45 -0800 (PST)
Received: from torch.brasslantern.com ([unknown] [71.116.65.135]) by vms173005.mailsrvcs.net (Sun Java(tm) System Messaging Server 7u2-7.02 32bit (built Apr 16 2009)) with ESMTPA id <0LUX00EHNOOJBX42@vms173005.mailsrvcs.net> for asrg@irtf.org; Sat, 19 Nov 2011 18:43:32 -0600 (CST)
Received: from torch.brasslantern.com (localhost.localdomain [127.0.0.1]) by torch.brasslantern.com (8.13.1/8.13.1) with ESMTP id pAK0hT2A022923	for <asrg@irtf.org>; Sat, 19 Nov 2011 16:43:31 -0800
Received: (from schaefer@localhost)	by torch.brasslantern.com (8.13.1/8.13.1/Submit) id pAK0hSb9022922	for asrg@irtf.org; Sat, 19 Nov 2011 16:43:28 -0800
From: Bart Schaefer <schaefer@brasslantern.com>
Message-id: <111119164328.ZM22921@torch.brasslantern.com>
Date: Sat, 19 Nov 2011 16:43:28 -0800
In-reply-to: <CAFdugan4Hg-5GYqCVp9U7+H0qRE6c_gHH+fE+b=JX+87JsmU1Q@mail.gmail.com>
Comments: In reply to Christian Grunfeld <christian.grunfeld@gmail.com> "Re: [Asrg] antiphishing idea" (Nov 19,  9:06pm)
References: <CAFdugamtPXjEHiwuJ3N2xyaXK+E0yCJfQi6vOey3jyff1UVvgw@mail.gmail.com> <20111117221346.27300.qmail@joyce.lan> <CAFduganLWiFQSRP9uG4auEr-bXsHcKSQV=2+C2pEF4AK3QGdKw@mail.gmail.com> <4EC7528C.4080603@billmail.scconsult.com> <CAFdugamO2GA5N7=JZt-XoUQo0Z1194hbxrOGsowHWF+fC1AvCw@mail.gmail.com> <4EC807EB.4010608@billmail.scconsult.com> <CAFdugan4Hg-5GYqCVp9U7+H0qRE6c_gHH+fE+b=JX+87JsmU1Q@mail.gmail.com>
X-Mailer: OpenZMail Classic (0.9.2 24April2005)
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
Subject: Re: [Asrg] antiphishing idea
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.12
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/options/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: Sun, 20 Nov 2011 00:43:45 -0000

On Nov 19,  9:06pm, Christian Grunfeld wrote:
} Subject: Re: [Asrg] antiphishing idea
}
} 2011/11/19 Bill Cole <asrg3@billmail.scconsult.com>:
} 
} > I learned that the authoritative DNS was running on hardware and software
} > that had not been updated since 1997, almost a decade of stability. The
} > person who told me this was very proud of it.
} 
} you 're talking about the Internet about 15 years ago.

No, he's talking about the internet 4 or 5 years ago.

"not since 1997" + "almost a decade" = approximately 2006.

} do not confuse stability with no improvement !

In fact that's *exactly* what he means.  Don't confuse "time has passed"
with "the situation has changed."

From clewis+ietf@mustelids.ca  Sat Nov 19 17:17:52 2011
Return-Path: <clewis+ietf@mustelids.ca>
X-Original-To: asrg@ietfa.amsl.com
Delivered-To: asrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6668421F8445 for <asrg@ietfa.amsl.com>; Sat, 19 Nov 2011 17:17:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.141
X-Spam-Level: 
X-Spam-Status: No, score=-0.141 tagged_above=-999 required=5 tests=[AWL=-0.582, BAYES_05=-1.11, FH_RELAY_NODNS=1.451, RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tAPreRBzCNAP for <asrg@ietfa.amsl.com>; Sat, 19 Nov 2011 17:17:52 -0800 (PST)
Received: from mail.mustelids.ca (unknown [174.35.130.2]) by ietfa.amsl.com (Postfix) with ESMTP id C0C7321F8441 for <asrg@irtf.org>; Sat, 19 Nov 2011 17:17:51 -0800 (PST)
Received: from [192.168.0.8] (otter.mustelids.ca [192.168.0.8]) (authenticated bits=0) by mail.mustelids.ca (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id pAK1H9tQ009849 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <asrg@irtf.org>; Sat, 19 Nov 2011 20:17:21 -0500
Message-ID: <4EC85515.8050904@mustelids.ca>
Date: Sat, 19 Nov 2011 20:17:09 -0500
From: Chris Lewis <clewis+ietf@mustelids.ca>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.8.1.23) Gecko/20090812 Thunderbird/2.0.0.23 Mnenhy/0.7.6.666
MIME-Version: 1.0
To: asrg@irtf.org
References: <CAFdugamtPXjEHiwuJ3N2xyaXK+E0yCJfQi6vOey3jyff1UVvgw@mail.gmail.com> <20111117221346.27300.qmail@joyce.lan> <CAFduganLWiFQSRP9uG4auEr-bXsHcKSQV=2+C2pEF4AK3QGdKw@mail.gmail.com> <4EC7528C.4080603@billmail.scconsult.com> <CAFdugamO2GA5N7=JZt-XoUQo0Z1194hbxrOGsowHWF+fC1AvCw@mail.gmail.com> <4EC807EB.4010608@billmail.scconsult.com> <CAFdugan4Hg-5GYqCVp9U7+H0qRE6c_gHH+fE+b=JX+87JsmU1Q@mail.gmail.com>
In-Reply-To: <CAFdugan4Hg-5GYqCVp9U7+H0qRE6c_gHH+fE+b=JX+87JsmU1Q@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [Asrg] antiphishing idea
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.12
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/options/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: Sun, 20 Nov 2011 01:17:52 -0000

On 11-11-19 07:06 PM, Christian Grunfeld wrote:
> 2011/11/19 Bill Cole<asrg3@billmail.scconsult.com>:
>
>> I understand both fairly well, but I appreciate your concern for my
>> understanding. It is unfortunate that there seems to be a language barrier
>> preventing you from coherently explaining my ignorance to me.
>
> I do not need to explain coherently your ignorance to you since you're
> doing pretty well job yourself.

Where's the C&C warning?

Bill can be somewhat abrasive, but ignorant in this area, he's most 
definitely not.

It's a bad idea to continue.




From johnl@iecc.com  Sat Nov 19 17:22:28 2011
Return-Path: <johnl@iecc.com>
X-Original-To: asrg@ietfa.amsl.com
Delivered-To: asrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 30A8A21F848A for <asrg@ietfa.amsl.com>; Sat, 19 Nov 2011 17:22:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -111.091
X-Spam-Level: 
X-Spam-Status: No, score=-111.091 tagged_above=-999 required=5 tests=[AWL=0.108, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S9ZgxZEh14iZ for <asrg@ietfa.amsl.com>; Sat, 19 Nov 2011 17:22:27 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [64.57.183.53]) by ietfa.amsl.com (Postfix) with ESMTP id A502221F8487 for <asrg@irtf.org>; Sat, 19 Nov 2011 17:22:26 -0800 (PST)
Received: (qmail 93707 invoked from network); 20 Nov 2011 01:22:25 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 20 Nov 2011 01:22:25 -0000
Date: 20 Nov 2011 01:22:03 -0000
Message-ID: <20111120012203.42747.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: asrg@irtf.org
In-Reply-To: <CAFdugan4Hg-5GYqCVp9U7+H0qRE6c_gHH+fE+b=JX+87JsmU1Q@mail.gmail.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
Subject: [Asrg] Please behave yourself on the ASRG list
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.12
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/options/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: Sun, 20 Nov 2011 01:22:28 -0000

>I do not need to explain coherently your ignorance to you since you're
>doing pretty well job yourself. ...

I have moderated future posts from this guy due to his repeated
personal attacks.

We welcome robust debate, but not personal invective.

Do keep in mind that this list has members who have been running email
systems for a very long time, and it is rarely a winning strategy to
impugn the competence of someone who may well have been running mail
systems before you could read.

R's,
John

From trelane@trelane.net  Sat Nov 19 17:27:09 2011
Return-Path: <trelane@trelane.net>
X-Original-To: asrg@ietfa.amsl.com
Delivered-To: asrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 06CA321F84A3 for <asrg@ietfa.amsl.com>; Sat, 19 Nov 2011 17:27:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.74
X-Spam-Level: 
X-Spam-Status: No, score=-0.74 tagged_above=-999 required=5 tests=[BAYES_20=-0.74]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6QgxiQGBEYx5 for <asrg@ietfa.amsl.com>; Sat, 19 Nov 2011 17:27:08 -0800 (PST)
Received: from mail.trelane.net (mail.trelane.net [66.93.203.104]) by ietfa.amsl.com (Postfix) with ESMTP id C12A51F0C44 for <asrg@irtf.org>; Sat, 19 Nov 2011 17:27:07 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by mail.trelane.net (Postfix) with ESMTP id 49C3E186544 for <asrg@irtf.org>; Sat, 19 Nov 2011 20:27:07 -0500 (EST)
X-Virus-Scanned: amavisd-new at trelane.net
Received: from mail.trelane.net ([127.0.0.1]) by localhost (master.trelane.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Yo4eHGdVO7J5 for <asrg@irtf.org>; Sat, 19 Nov 2011 20:27:05 -0500 (EST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by mail.trelane.net (Postfix) with ESMTP id 696161864FB for <asrg@irtf.org>; Sat, 19 Nov 2011 20:27:05 -0500 (EST)
Received: from [172.16.1.106] (router.trelane.net [66.93.203.152]) by mail.trelane.net (Postfix) with ESMTPA id 4A51818650E for <asrg@irtf.org>; Sat, 19 Nov 2011 20:27:03 -0500 (EST)
Message-ID: <4EC85766.6050809@trelane.net>
Date: Sat, 19 Nov 2011 20:27:02 -0500
From: Andrew Kirch <trelane@trelane.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: asrg@irtf.org
References: <20111120012203.42747.qmail@joyce.lan>
In-Reply-To: <20111120012203.42747.qmail@joyce.lan>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [Asrg] Please behave yourself on the ASRG list
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.12
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/options/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: Sun, 20 Nov 2011 01:27:09 -0000

Wow, for once it wasn't me!

Andrew

From clewis+ietf@mustelids.ca  Sat Nov 19 17:36:50 2011
Return-Path: <clewis+ietf@mustelids.ca>
X-Original-To: asrg@ietfa.amsl.com
Delivered-To: asrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9616B21F8507 for <asrg@ietfa.amsl.com>; Sat, 19 Nov 2011 17:36:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.841
X-Spam-Level: 
X-Spam-Status: No, score=-0.841 tagged_above=-999 required=5 tests=[AWL=0.207,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Cm7y+kQCmGgr for <asrg@ietfa.amsl.com>; Sat, 19 Nov 2011 17:36:50 -0800 (PST)
Received: from mail.mustelids.ca (unknown [174.35.130.2]) by ietfa.amsl.com (Postfix) with ESMTP id D53EC21F84FA for <asrg@irtf.org>; Sat, 19 Nov 2011 17:36:49 -0800 (PST)
Received: from [192.168.0.8] (otter.mustelids.ca [192.168.0.8]) (authenticated bits=0) by mail.mustelids.ca (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id pAK1amfe013281 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <asrg@irtf.org>; Sat, 19 Nov 2011 20:36:48 -0500
Message-ID: <4EC859B0.9020600@mustelids.ca>
Date: Sat, 19 Nov 2011 20:36:48 -0500
From: Chris Lewis <clewis+ietf@mustelids.ca>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.8.1.23) Gecko/20090812 Thunderbird/2.0.0.23 Mnenhy/0.7.6.666
MIME-Version: 1.0
To: asrg@irtf.org
References: <20111119190513.29824.qmail@joyce.lan> <3EE701FD-7298-4D78-8571-63E6FC2EE945@blighty.com> <4EC81322.8060008@mustelids.ca> <4EC844A6.70609@pscs.co.uk>
In-Reply-To: <4EC844A6.70609@pscs.co.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [Asrg] per message databases, was antiphishing idea
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.12
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/options/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: Sun, 20 Nov 2011 01:36:50 -0000

On 11-11-19 07:07 PM, Paul Smith wrote:
> On 19/11/2011 20:35, Chris Lewis wrote:
>> Note also that per message database _traffic_ would scale with the
>> total amount of email (around 80-95% spam), whereas POP and webmail
>> infrastructure scales with the ham.

> Yes, unless it has such a beneficial effect that spammers give up... :)

We wish ;-)

> (or at least stop forging messages from those domains protected by this
> system)

APWG's latest stats seem to indicate that only 20% of phishes currently 
use the "right" domain.  Having that 20% switch to what the other 80% 
already do doesn't gain much.  The ROI seems pretty low.

[I'm not sure I believe that it's really as low as 20%, but the point 
still holds.]

>> The per message database queries in DNS wouldn't be cacheable whereas
>> about everything else in DNS is. 3-5 orders of magnitude increase in
>> DNS traffic to the authoritatives isn't unreasonable in the least.
> Only the last part of the DNS queries wouldn't be cacheable AFAICT.

That's all it needs to swamp current authoritive loading guidelines... 
Every outbound email results in a single uncacheable query, whereas 
under normal circumstances, _none_ do.

> So, if the message ID was '12345.bibble55@gmail.com', translating to a
> lookup of something like '12345.bibble55.gmail.com_msgids.gmail.com',
> only the '12345' bit isn't cacheable. The resolution down to the
> bibble55.gmail.com._msgids.gmail.com. would be cacheable AFAICS, and
> would allow partitioning of the data & queries to the 'bibble55'
> authoritative DNS server. So, root servers and Google's 'normal' DNS
> servers wouldn't have significantly more load than now (if any at all),
> it would just be the msgid DNS servers which would be loaded.

Right.  You could conceivably provide a NS coresident with every 
outbound MTA.  You could even build the NS _into_ the MTA.  However, 
even then, once you start factoring in the operational considerations 
(crash/stop/restart, load balance, availability, sheer size of zone) it 
still remains more than a little daunting.

> My big problem with this idea is that I'm not sure how it would really
> help more than other ideas. I don't see the use of DNS as being that big
> an issue, it's just a UDP callback check in essence. It's massively more
> efficient than a CBV check, at least as efficient as some SPF checks
> (using macros), and miniscule compared to the actual SMTP transaction.

Right.  For the reasons I put up near the beginning, the ROI seems 
extremely low.  Forces a small number of phishers to switch to a 
technique that the rest of the phishers are already using.


