
From vesely@tana.it  Wed Aug 12 00:43:30 2009
Return-Path: <vesely@tana.it>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E4E4A3A6821 for <asrg@core3.amsl.com>; Wed, 12 Aug 2009 00:43:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.917
X-Spam-Level: 
X-Spam-Status: No, score=-3.917 tagged_above=-999 required=5 tests=[AWL=0.802,  BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CQC47A76roZJ for <asrg@core3.amsl.com>; Wed, 12 Aug 2009 00:43:30 -0700 (PDT)
Received: from wmail.tana.it (mail.tana.it [62.94.243.226]) by core3.amsl.com (Postfix) with ESMTP id C43B93A67C2 for <asrg@irtf.org>; Wed, 12 Aug 2009 00:43:29 -0700 (PDT)
Received: from [172.25.197.158] (pcale.tana [172.25.197.158]) (AUTH: CRAM-MD5 ale@tana.it, TLS: TLS1.0, 256bits, RSA_AES_256_CBC_SHA1) by wmail.tana.it with esmtp; Wed, 12 Aug 2009 09:29:05 +0200 id 00000000005DC036.000000004A826F41.000024F0
Message-ID: <4A826F42.3090903@tana.it>
Date: Wed, 12 Aug 2009 09:29:06 +0200
From: Alessandro Vesely <vesely@tana.it>
User-Agent: Thunderbird 2.0.0.22 (Windows/20090605)
MIME-Version: 1.0
To: AJ Jaghori <ciscoworkz@gmail.com>
References: <003d01c9dd01$bf3531d0$800c6f0a@china.huawei.com>	<3be421270905250718y5d62f6d5odb6f2bebecf418d0@mail.gmail.com>	<6684E747-55CB-4BB3-B838-9F4FE906AFE7@mail-abuse.org>	<200905251603.MAA16221@Sparkle.Rodents-Montreal.ORG>	<CCE0A3E1-4BCB-460C-AEA0-6548BB4AE8FE@mail-abuse.org>	<4A1D64C9.5060505@tana.it>	<47BC2197-472E-4615-97D2-F7E42B8F3B7D@mail-abuse.org>	<4A1E8BD3.8000103@tana.it> <20090528131509.GA13521@nic.fr>	<4A1E9CBF.4010703@tana.it> <be653210908112047x4f4075cfu70611559b99cbe08@mail.gmail.com>
In-Reply-To: <be653210908112047x4f4075cfu70611559b99cbe08@mail.gmail.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Cc: Anti-Spam Research Group - IRTF <asrg@irtf.org>, ietf@ietf.org
Subject: Re: [Asrg] DNS over SCTP
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Aug 2009 07:43:31 -0000

AJ Jaghori wrote:
> This is a common misconception.  DNS over SCTP will not solve 90% of the 
> problems!

Why?

Attackers are able to guess what DNS queries an SMTP server would put 
as a consequence of a client connection. Even after the Kaminsky fix, 
that leaves room for brute force attacks. If queries were run over 
TCP, the additional requirement to hijack a TCP connection would 
reduce the probabilities enough, even for today's botnets. Thus, using 
TCP would solve those security issues. (Is that 90%?) It would 
introduce some inefficiency, though. (More than DNSSEC?)

SCTP provides for several streams over a single connection, streams 
are asynchronous with one another like UDP packets, but are reliably 
connected and secured like TCP streams. With decent keep-alive 
directives, that would allow a client to be connected with a pool of 
relevant resolvers, thereby avoiding the inefficiencies that TCP would 
introduce.

> On Thu, May 28, 2009 at 10:16 AM, Alessandro Vesely <vesely@tana.it 
> <mailto:vesely@tana.it>> wrote:
> 
>     Stephane Bortzmeyer wrote:
> 
>        It seems that DNS over SCTP would solve 90% of the problems with 10%
>        of the efforts and resources required to implement DNSSEC. However,
>        I hear more often about the latter than the former. How come?
> 
> 
>    I've read this message via the IETF general mailing list and so I
>    missed the beginning. In what way can you compare DNSSEC (which
>    provides object security) and SCTP or TCP (which provide a better
>    channel security for DNS)?
> 
> 
> The discussion was about how to get rid of the threats illustrated,
> e.g., in Kaminsky, D.: "It’s the end of the cache as we know it."
> In: Black Hat conference (2008). Online at http://www.doxpara.com/DMK_BO2K8.ppt

From falk@bbn.com  Fri Aug 14 10:31:01 2009
Return-Path: <falk@bbn.com>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 63A713A6781 for <asrg@core3.amsl.com>; Fri, 14 Aug 2009 10:31:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.077
X-Spam-Level: 
X-Spam-Status: No, score=-2.077 tagged_above=-999 required=5 tests=[AWL=-0.277, BAYES_00=-2.599, SARE_SUB_RAND_LETTRS4=0.799]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id y98kK08zWTDq for <asrg@core3.amsl.com>; Fri, 14 Aug 2009 10:31:00 -0700 (PDT)
Received: from mx11.bbn.com (mx11.bbn.com [128.33.0.80]) by core3.amsl.com (Postfix) with ESMTP id 3F1173A6774 for <asrg@irtf.org>; Fri, 14 Aug 2009 10:31:00 -0700 (PDT)
Received: from dhcp89-081-142.bbn.com ([128.89.81.142]) by mx11.bbn.com with esmtp (Exim 4.60) (envelope-from <falk@bbn.com>) id 1MbzgA-0004Ry-FO for asrg@irtf.org; Fri, 14 Aug 2009 12:30:58 -0400
Message-ID: <4A859F54.7010909@bbn.com>
Date: Fri, 14 Aug 2009 13:31:00 -0400
From: Aaron Falk <falk@bbn.com>
User-Agent: Thunderbird 2.0.0.22 (Macintosh/20090605)
MIME-Version: 1.0
To: asrg@irtf.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: [Asrg] [Fwd: Copyrights and the IRTF and Independent Stream]
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Aug 2009 17:31:01 -0000

Forwarding to all active IRTF RG mail lists because this issue affects
the publication rights for IDs and RFCs developed within the IRTF. 
Information about IRTF RFCs can be found in
http://tools.ietf.org/html/draft-irtf-rfcs-03.  Please direct comments
to the RFC-interest list (coordinates below).

--aaron
  IRTF Chair

-------- Original Message --------
Subject: 	[rfc-i] Copyrights and the IRTF and Independent Stream
Date: 	Thu, 13 Aug 2009 18:59:42 +0200
From: 	Olaf Kolkman <olaf@NLnetLabs.nl>
To: 	RFC Interest <rfc-interest@rfc-editor.org>



Dear Colleagues,


This mail is about rights in RFCs and Internet drafts. The topic draws
context, and uses terminology from:
RFC 4844: The RFC Series and RFC Editor
RFC 4846: Independent Submissions to the RFC Editor
RFC 5378: Rights Contributors Provide to the IETF Trust
RFC 5377: Advice to the Trustees of the IETF Trust on Rights to Be
Granted in IETF Documents

First some administrational notes.

This mail serves as setting a baseline for a public discussion and is
based on a few (virtual and real-life) hallway discussions. The goal
of this discussion is to make sure all issues are brought to the table
and the stream maintainers and the Trust are aware of the communities
opinions. I see my role as an IAB member that is driving the
discussion, and mildly moderating it. In the end it is the role of the
IAB to see that an appropriate stream dependent process has been
followed and that the streams do not interact inapropriatly. So in
that sense this discussion informs the IAB too.

Although this mail is sent to multiple lists I would like to urge folk
to discuss the issues on the rfc-interest list:
   http://www.rfc-editor.org/mailman/listinfo/rfc-interest


Without further ado.

As you may know RFCs are published from different streams. With
respect to the incoming and outgoing rights only the rights of the
IETF stream documents are well defined. And currently the IAB has
chosen to have IAB documents fall under this regime too. The situation
is less clear for Independent and IRTF Stream documents: all existing
provisions are targeted specifically towards IETF Contributions (in
the narrow context defined by RFC5378). Besides, currently and in the
context of copyrights, Internet Drafts (I-Ds) are seen as IETF
contributions.

Maintainers of the Independent and IRTF stream would like to have
documents from their streams published with full rights to make
derivative works or make no derivative works whatsoever, and require
attribution in both cases.

There are two strategies to make this work:

1. Allow I-Ds and RFCs for the IAB, IRTF, and Independent stream to be
published with a Creative Commons license added.

A rough outline of one of the ideas that is floating around ist that
all contributions that are intended to become an RFC or are an IETF
contribution (in the sense of RFC 5378 definition) will continue to
have the 5378 license terms as defined by the trust. Since 5378 is
non-exclusive authors may add a creative commons license if they'd
like to. Care should be taken that those licenses would not be applied
to IETF contributions, as that could lead to 'spoofed standard-track
RFCs'

2. Have the trust manage the rights for the IAB, IRTF, and Independent
streams RFCs and I-Ds.

Both strategies may require that at the moment Internet Drafts is
published as an RFC it is clear on which stream they are intended to
be published, with which rights, and that the authors have appropriate
authority to grant/sublicense those rights.

In both cases we want to avoid that IETF contributions (I-Ds and
RFCs, although it is not clear whether this is a strong requirement
for I-Ds) are published with a license policy that would circumvent the
Trust's control over the outgoing rights.

A tactic/straw-man to implement (2) is as follows:

    i) Treat all I-Ds as or similar to IETF contributions (this way
       there is no doubt about the Trust having all necessary rights,
       see BCP78 section 5.3). There seem to be two paths to proceed:

        i.1) The stream controllers choose to apply the RFC5378 rules.
        	    This possibility is offered in section 4 of 5378 and the
  	    IAB stream chooses to apply the rules through its
	    declaration in section 11.

        i.2) The streams write a stream specific "Rights contributors
             provide to the IETF trust" document.


     ii) Have the stream controllers request  the IETF Trust to create
         license(s) for non IETF-Stream RFCs that grant for (full|no)
	derivative rights, attribution required. (document this
	request in an RFC).

    iii) Ask the trust to develop language that can be put on an I-D
         with which the author can request (full|no) derivative rights
         if/when the I-D is published on a specific non-IETF stream
	document. This sort of text would serve as an indication of
	consent with wide licensing and could be included as
	boilerplate material together with an indication of intended
	stream (as in draft-iab-streams-headers- boileplates).



There are some pros and cons to this scheme that we need to identify
in public discussion, hence this mail.

During the hallway discussion, I've seen the following arguments and
identified the following open questions. I don't claim completeness.

- The Trust is not well equiped to hold non-IETF documents. Mainly
   because it requires the interperetation that all documents are IETF
   Documents.

   Is this interpretation based on language in the Trust agreement or
   on the definition of IETF Documents in the context of BCP78?

   Or, is the trust well suited, and does implementation only need some
   boilerplate changes?


- IETF Stream RFCs need to be protected by limited derivative rights
   so that the IETF keeps ownership over its Standards and can maintain
   those.

   Suppose a I-D with full derivative rights is posted (either because
   the author has published it with Creative Commons, or because the
   Trust allows full derivative rights for stream specific I-Ds) would
   narrowing down the rights by publication as an IETF stream RFC cause
   any problems?



Feedback welcome,

--Olaf Kolkman




From ravisha22@gmail.com  Sun Aug 16 04:20:38 2009
Return-Path: <ravisha22@gmail.com>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9D0813A6CE3 for <asrg@core3.amsl.com>; Sun, 16 Aug 2009 04:20:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.091
X-Spam-Level: 
X-Spam-Status: No, score=-1.091 tagged_above=-999 required=5 tests=[AWL=-1.507, BAYES_40=-0.185, HTML_MESSAGE=0.001, J_CHICKENPOX_73=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X9HZl4lDpv6P for <asrg@core3.amsl.com>; Sun, 16 Aug 2009 04:20:37 -0700 (PDT)
Received: from qw-out-2122.google.com (qw-out-2122.google.com [74.125.92.24]) by core3.amsl.com (Postfix) with ESMTP id A72193A6894 for <asrg@irtf.org>; Sun, 16 Aug 2009 04:20:37 -0700 (PDT)
Received: by qw-out-2122.google.com with SMTP id 3so821445qwe.7 for <asrg@irtf.org>; Sun, 16 Aug 2009 04:20:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=4medDtOyfe0j3RCmAJ0UqZ4zI87z3t7s4PgF21PGBIE=; b=E69K5nB1fMX0bqxDGrhL6zejJw1C+dnarYDmLbcK+ZapuweoJj4GbazNwnciTYUj3I JP1BPQQgK+xGx0E/9YTfDYNN8cjNlceMxBv/t7QUXoc+QP6wrDgBrjoMD4eY5Dwyegow WfcBSmgz8FUfW7+9mueW5dhjr3V3yHf6u3D/A=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=Dxo8EKv1hGpOUpZEgdjCezL8o1D0Iwdmfle3EeNESkZE8KS9S6/W+VxF/nrFLB+fgT PINNBOzqbMenT0tHtaVvO/BhUD/B9gnRIPHJFthz3b1REBqgbl2OwARdyrUtHqwqtOji 3TynFxBykO2xCzYmnMZYNRo2KUcKc2PXZjUxY=
MIME-Version: 1.0
Received: by 10.224.17.75 with SMTP id r11mr3584024qaa.387.1250421639418; Sun,  16 Aug 2009 04:20:39 -0700 (PDT)
Date: Sun, 16 Aug 2009 16:50:39 +0530
Message-ID: <922a897b0908160420w4554837aj684e86eb586823af@mail.gmail.com>
From: Ravi shankar <ravisha22@gmail.com>
To: asrg@irtf.org
Content-Type: multipart/alternative; boundary=000feaed9d75a3161d04714079e3
Subject: [Asrg] SMTP pull anyone?
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Sun, 16 Aug 2009 11:20:38 -0000

--000feaed9d75a3161d04714079e3
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Hi,

Me and my buddy had a interesting discussion, which i thought could put
across the geeks here.

It goes something like this:

SMTP is currently a push protocol and is initiated by the the sender, no
controlling that fact.

But it is possible to overcome the relay problems, IP spoofing and domain
impersonation etc,

by making the servers pull the mails.

1. Sending server contacts the destination and proovides the Message ID and
sender details(and other details) and disconnects the session.

2. The receiving server queues it up and looks up the messages one by one
using DNS to determine their legitimacy.

3. If the IP that contacted is legitimate(can be verified by say SPF?), it
contacts the sender and provides the message ID with other details.

4. The sending server then hands over the message.

5. To overcome DDoS attacks, the receiving server can be made to request the
next 10 or so Message IDs that it will assign to messages,

so that if a attacker tries to give those details, it will know from the
next list of message IDs that it's fake connection.

6. May be by this collection of data, the IP addresses can be reported to a
RBL and blacklisted.

Please point the holes in this model, so that we might get a entirely new
insight.

Note: I have gone trough IM2000 and other similar discussions in the
archive. Just thought this version of C/R is worth getting discussed.

Regards,
Ravi

--000feaed9d75a3161d04714079e3
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div>Hi,</div>
<div>=A0</div>
<div>Me and my buddy had a interesting discussion, which i thought could pu=
t across the geeks here.</div>
<div>=A0</div>
<div>It goes something like this:</div>
<div>=A0</div>
<div>SMTP is currently a push protocol and is initiated by the the sender, =
no controlling that fact.</div>
<div>=A0</div>
<div>But it is possible to overcome the relay problems, IP spoofing and dom=
ain impersonation etc,</div>
<div>=A0</div>
<div>by making the servers pull the mails.</div>
<div>=A0</div>
<div>1. Sending server contacts the destination and proovides the Message I=
D and sender details(and other details)=A0and disconnects the session.</div=
>
<div>=A0</div>
<div>2. The receiving server queues it up and looks up the messages one by =
one using DNS to determine their legitimacy.</div>
<div>=A0</div>
<div>3. If the IP that contacted is legitimate(can be verified by say SPF?)=
, it contacts the sender and provides the message ID with other details.</d=
iv>
<div>=A0</div>
<div>4. The sending server then hands over the message.</div>
<div>=A0</div>
<div>5. To overcome DDoS attacks, the receiving server can be made to reque=
st the next 10 or so Message IDs that it will assign to messages,</div>
<div>=A0</div>
<div>so that if a attacker tries to give those details, it will know from t=
he next list of message IDs that it&#39;s fake connection.</div>
<div>=A0</div>
<div>6. May be by this collection of data, the IP addresses can be reported=
 to a RBL and blacklisted.</div>
<div>=A0</div>
<div>Please point the holes in this model, so that we might get a entirely =
new insight.</div>
<div>=A0</div>
<div>Note: I have gone trough IM2000 and other similar discussions in the a=
rchive. Just thought this version of C/R is worth getting discussed.</div>
<div>=A0</div>
<div>Regards,</div>
<div>Ravi</div>
<div>=A0</div>
<div>=A0</div>

--000feaed9d75a3161d04714079e3--

From asrg3@billmail.scconsult.com  Sun Aug 16 11:14:36 2009
Return-Path: <asrg3@billmail.scconsult.com>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 125DD3A69AB for <asrg@core3.amsl.com>; Sun, 16 Aug 2009 11:14:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.369
X-Spam-Level: 
X-Spam-Status: No, score=-1.369 tagged_above=-999 required=5 tests=[AWL=-1.230, BAYES_20=-0.74, J_CHICKENPOX_73=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id G98x+BM0U8HH for <asrg@core3.amsl.com>; Sun, 16 Aug 2009 11:14:35 -0700 (PDT)
Received: from toaster.scconsult.com (news.scconsult.com [66.73.230.190]) by core3.amsl.com (Postfix) with ESMTP id 5D09B3A6BD3 for <asrg@irtf.org>; Sun, 16 Aug 2009 11:14:01 -0700 (PDT)
Received: from bigsky.scconsult.com (bigsky.scconsult.com [192.168.2.102]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by toaster.scconsult.com (Postfix) with ESMTP id DBBBD93C4A0 for <asrg@irtf.org>; Sun, 16 Aug 2009 14:14:00 -0400 (EDT)
Message-ID: <4A884C68.7020301@billmail.scconsult.com>
Date: Sun, 16 Aug 2009 14:14:00 -0400
From: Bill Cole <asrg3@billmail.scconsult.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1b3pre) Gecko/20090408 Eudora/3.0b2
MIME-Version: 1.0
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
References: <922a897b0908160420w4554837aj684e86eb586823af@mail.gmail.com>
In-Reply-To: <922a897b0908160420w4554837aj684e86eb586823af@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [Asrg] SMTP pull anyone?
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: asrg@irtf.org
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Sun, 16 Aug 2009 18:14:36 -0000

Ravi shankar wrote, On 8/16/09 7:20 AM:
> Hi,
> Me and my buddy had a interesting discussion, which i thought could put
> across the geeks here.
> It goes something like this:
> SMTP is currently a push protocol and is initiated by the the sender, no
> controlling that fact.
> But it is possible to overcome the relay problems, IP spoofing and
> domain impersonation etc,
> by making the servers pull the mails.
> 1. Sending server contacts the destination and proovides the Message ID
> and sender details(and other details) and disconnects the session.
> 2. The receiving server queues it up and looks up the messages one by
> one using DNS to determine their legitimacy.

DNS itself provides no mechanism for determining the legitimacy of email.

DNS is used *as a medium* for various applications that are used to identify 
mail as legitimate or illegitimate by various standards of legitimacy, and a 
major reason for its use in those applications is to make it feasible for 
mail systems to do the validation synchronously during the SMTP session. By 
using a lightweight, distributed, cached database, mail systems are spared 
from deferring a message, queuing its validation, remembering the results, 
and waiting for the sender to offer it in an identical way again. You are 
suggesting that receivers should take on all the heavyweight management but 
retain using DNS for something unspecified. It makes no sense.

> 3. If the IP that contacted is legitimate(can be verified by say SPF?),
> it contacts the sender and provides the message ID with other details.

The *most* that SPF can provide towards showing "legitimacy" is to confirm 
that the envelope sender address of a message is not forged. It is very rare 
for large senders of any sort to deploy records that can do that strongly. 
There is nothing about SPF that directly attacks spamming. It could in 
theory be used to attack sender forgery, but the collateral damage has 
proven to be too great for either sending or receiving systems to actually 
apply it strongly to that end. Meanwhile, a lot of spammers are sending a 
lot of spam with senders that are validated to the degree that SPF can 
validate anything.


> 4. The sending server then hands over the message.
> 5. To overcome DDoS attacks, the receiving server can be made to request
> the next 10 or so Message IDs that it will assign to messages,
> so that if a attacker tries to give those details, it will know from the
> next list of message IDs that it's fake connection.

That sentence makes no sense. What did you mean to say?

> 6. May be by this collection of data, the IP addresses can be reported
> to a RBL and blacklisted.
> Please point the holes in this model, so that we might get a entirely
> new insight.

Nothing you have described would add to spam control as it is currently 
being done, as far as I can see. The 'model' is too vague to critique inn 
detail because you aren't really providing any meaningful details.

In order to bring anything truly new and useful to controlling email spam, a 
new idea has to either attack spam in a way that existing tactics don't, do 
a demonstrably better job than existing tactics, or overcome the negative 
aspects of existing tactics. You have identified none of those in your new 
idea.

> Note: I have gone trough IM2000 and other similar discussions in the
> archive. Just thought this version of C/R is worth getting discussed.

As described, there's not much to discuss. It looks like it might be a 
little like IM2000 (which has been a complete failure) if fleshed out, but 
you haven't explained how this would differ from it, how it would integrate 
with existing SMTP, or how it would offer anything significantly better than 
existing mechanisms.

Right now, receivers can choose to validate the sender against SPF records 
after receiving the MAIL command and reject non-validating messages at that 
point, or they can wait until RCPT if they want their rejections to be more 
broadly respected, or they can wait until the second phase of DATA if they 
want to weight SPF results along with other filters that rely on message 
data. Many sites already explicitly reject the vast majority of offered 
messages in response to RCPT or earlier without requiring legitimate senders 
to sit on a pile of pending offered messages that may or may not be asked 
for later. You have not identified any benefits for receiving systems or 
legitimate senders, so it is hard to agree that it is "worth getting 
discussed" or indeed worth anything at all. Where is the added value?

From meta404@gmail.com  Sun Aug 16 11:38:10 2009
Return-Path: <meta404@gmail.com>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 102A83A6C7A for <asrg@core3.amsl.com>; Sun, 16 Aug 2009 11:38:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level: 
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id s3xfjiJ1GbP0 for <asrg@core3.amsl.com>; Sun, 16 Aug 2009 11:38:09 -0700 (PDT)
Received: from mail-bw0-f222.google.com (mail-bw0-f222.google.com [209.85.218.222]) by core3.amsl.com (Postfix) with ESMTP id 074D23A6A49 for <asrg@irtf.org>; Sun, 16 Aug 2009 11:38:08 -0700 (PDT)
Received: by bwz22 with SMTP id 22so1947874bwz.18 for <asrg@irtf.org>; Sun, 16 Aug 2009 11:38:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to :content-type:content-transfer-encoding; bh=4qX1hwPY/YTbqen71VDJ4iz0IUhkTpWg2z94CE4dgtY=; b=sA5jtCSwrhD82n2yQLuc144X8BtJQrHdKafsz51NnbPFZDbT632pl6EO00lbcTiLEv 0Fhn0ZVfAr0nOdiGELXCxGeyLvRZaVhpEpeyzIyiJ8OR1UoWPSVGnqAY3/iLCmUk8f8j B60ttHagAxA6M6b3HyEtpNeCeeubT5+sOz84c=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type :content-transfer-encoding; b=BzOOYw2tukGvPVdaeY6xxaBeIGW4YI5O3DF0VsgqZ6/782NHUGN5/G1NpzO0l9mQ5V xI5+n75mPJ5DqHopLfY/+PZ9jgDJLZCqYIaIZcJEOVSQPVartoO0ozAX0AlAm9aD7TVA /pP8Ly8Cx4FGCaI69mr+LvUqZsDhgrb34ORJ4=
MIME-Version: 1.0
Sender: meta404@gmail.com
Received: by 10.223.1.137 with SMTP id 9mr757439faf.93.1250447892901; Sun, 16  Aug 2009 11:38:12 -0700 (PDT)
In-Reply-To: <922a897b0908160420w4554837aj684e86eb586823af@mail.gmail.com>
References: <922a897b0908160420w4554837aj684e86eb586823af@mail.gmail.com>
Date: Sun, 16 Aug 2009 13:38:12 -0500
X-Google-Sender-Auth: ff3e14fe217e5aa9
Message-ID: <7eeceb440908161138y6dc9563fgf464f4b8f09bf09e@mail.gmail.com>
From: mathew <meta@pobox.com>
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [Asrg] SMTP pull anyone?
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Sun, 16 Aug 2009 18:38:10 -0000

On Sun, Aug 16, 2009 at 06:20, Ravi shankar<ravisha22@gmail.com> wrote:
> Me and my buddy had a interesting discussion, which i thought could
> put across the geeks here.
[... pull e-mail description...]

I wrote up something very similar, and as noted, there was IM2000.

At this point, the consensus on this list as far as I can determine is
"Nothing will work, and if you think otherwise go implement it and
prove us wrong". So I'd suggest digging out an ANSI C compiler as your
only productive next step.


mathew
-- 
<URL:http://www.pobox.com/~meta/>

From dhc@dcrocker.net  Sun Aug 16 11:46:08 2009
Return-Path: <dhc@dcrocker.net>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7A7643A693F for <asrg@core3.amsl.com>; Sun, 16 Aug 2009 11:46:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.771
X-Spam-Level: 
X-Spam-Status: No, score=-2.771 tagged_above=-999 required=5 tests=[AWL=-0.172, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5Izam4QDwEpO for <asrg@core3.amsl.com>; Sun, 16 Aug 2009 11:46:07 -0700 (PDT)
Received: from sbh17.songbird.com (unknown [IPv6:2001:470:1:76:0:ffff:4834:7148]) by core3.amsl.com (Postfix) with ESMTP id 394BA3A6929 for <asrg@irtf.org>; Sun, 16 Aug 2009 11:46:07 -0700 (PDT)
Received: from [127.0.0.1] (ppp-68-120-198-98.dsl.pltn13.pacbell.net [68.120.198.98]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id n7GIk56l024268 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <asrg@irtf.org>; Sun, 16 Aug 2009 11:46:10 -0700
Message-ID: <4A8853DE.4050402@dcrocker.net>
Date: Sun, 16 Aug 2009 11:45:50 -0700
From: Dave CROCKER <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Thunderbird 2.0.0.22 (Windows/20090605)
MIME-Version: 1.0
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
References: <922a897b0908160420w4554837aj684e86eb586823af@mail.gmail.com>
In-Reply-To: <922a897b0908160420w4554837aj684e86eb586823af@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Sun, 16 Aug 2009 11:46:10 -0700 (PDT)
Subject: Re: [Asrg] SMTP pull anyone?
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: dcrocker@bbiw.net, Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Sun, 16 Aug 2009 18:46:08 -0000

Ravi shankar wrote:
> SMTP is currently a push protocol and is initiated by the the sender, no 
> controlling that fact.
>  
> But it is possible to overcome the relay problems, IP spoofing and 
> domain impersonation etc,
>  
> by making the servers pull the mails.


<http://v3.espacenet.com/textdoc?DB=EPODOC&IDX=US6192407>

-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From johnl@iecc.com  Sun Aug 16 15:29:43 2009
Return-Path: <johnl@iecc.com>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8516E3A6EBE for <asrg@core3.amsl.com>; Sun, 16 Aug 2009 15:29:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -16.785
X-Spam-Level: 
X-Spam-Status: No, score=-16.785 tagged_above=-999 required=5 tests=[BAYES_40=-0.185, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QQEbMLM+Wc3K for <asrg@core3.amsl.com>; Sun, 16 Aug 2009 15:29:42 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [208.31.42.53]) by core3.amsl.com (Postfix) with ESMTP id 54EB53A6CAE for <asrg@irtf.org>; Sun, 16 Aug 2009 15:29:42 -0700 (PDT)
Received: (qmail 61335 invoked from network); 16 Aug 2009 22:29:44 -0000
Received: from mail1.iecc.com (208.31.42.56) by mail1.iecc.com with QMQP; 16 Aug 2009 22:29:44 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:in-reply-to:cc:mime-version:content-type:content-transfer-encoding; s=k0908; olt=johnl@user.iecc.com; bh=W1vcKhlCasJQaitCQVqsVv4lW0BhAE8RBCA/JPcE4CU=; b=lr9Jt+MY2jiSfENZ7EzsdcTZMA5a4kXyk6f/O4Bq5BFXfaEHUcvpaM5BBwAC0XLc4OJtbeZ1M1L2LLrpQz8zrE+zxjpG7YLqEnlM0llBnmuRtvAa0OuRfdUebO0XJ2IksdKlN9ZNzg7kvVe2tig/AMISyrT0dPTM5xEQGuEuJMc=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:subject:in-reply-to:cc:mime-version:content-type:content-transfer-encoding; s=k0908; bh=W1vcKhlCasJQaitCQVqsVv4lW0BhAE8RBCA/JPcE4CU=; b=OdpI5kfx/Yr4damW66k9VJGmezA7BuFVfTnm0Jt1xkj5WaKkS/+VUI7XTBJyZvstVs4/XEc316kgCaYpMT/etcBwWJwL1XOXqWxjb5tHQN3n9CeGsNyom7UzAsuZwj+aCEnA/zT22xVDcODGghxlI/EeQojUvM3S6nPXmH3lXs0=
Date: 16 Aug 2009 22:29:44 -0000
Message-ID: <20090816222944.96264.qmail@simone.iecc.com>
From: John Levine <johnl@taugh.com>
To: asrg@irtf.org
In-Reply-To: <4A8853DE.4050402@dcrocker.net>
Organization: 
Cc: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7bit
Subject: Re: [Asrg] SMTP pull anyone?
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Sun, 16 Aug 2009 22:29:43 -0000

>> SMTP is currently a push protocol and is initiated by the the
>> sender, no controlling that fact.
  
>> But it is possible to overcome the relay problems, IP spoofing and
>> domain impersonation etc,
  
>> by making the servers pull the mails.

> US6192407

Ah, right, the famous Tumbleweed patent.  Here's a better link
with a readable version.

http://www.google.com/patents?vid=USPAT6192407

This patent covers the idea of putting a message on a web server and
sending the recipient a URL to retrieve the message.  Tumbleweed
enforces it very aggressively.  See the list of suits in their
Wikipedia page.

Were it not for the patent, I expect we'd have a lot of institutions
setting up per-user password protected RSS or Atom feeds with
statements and other messages, and sending you mail telling you to
check your feed when there's something new.

R's,
John

From ravisha22@gmail.com  Mon Aug 17 02:53:39 2009
Return-Path: <ravisha22@gmail.com>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 27D3728C295 for <asrg@core3.amsl.com>; Mon, 17 Aug 2009 02:53:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.412
X-Spam-Level: 
X-Spam-Status: No, score=-2.412 tagged_above=-999 required=5 tests=[AWL=0.186,  BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JDQKb5S1W+RR for <asrg@core3.amsl.com>; Mon, 17 Aug 2009 02:53:32 -0700 (PDT)
Received: from mail-qy0-f194.google.com (mail-qy0-f194.google.com [209.85.221.194]) by core3.amsl.com (Postfix) with ESMTP id 7E89628C294 for <asrg@irtf.org>; Mon, 17 Aug 2009 02:53:32 -0700 (PDT)
Received: by qyk32 with SMTP id 32so2002905qyk.15 for <asrg@irtf.org>; Mon, 17 Aug 2009 02:53:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=7AQejJ33Nk8NYjSxxxpbGM5ZXXOAH4XNEMvZD8sD9dw=; b=YWQMPy6vnWXviEKGvbTB+S46KMVKOi/upyltSCPNHVjfNrkvhDYo7o2e0fe0zuJiKJ 2OtpuVw0xlh2fsVuS6v/S8+zI3nFlPhMPXdh03yegWefoGmN0GeQIqPv2H6pNcHcNq8t RH3GtfFgpMQYLxeuc3L77ZIoo69CWi5oVHFrs=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=cID+nHo+dNFJG6josObO1tMv5YoTdU28+3y8f6pgx6BT9QdAdwl9SPlKXPq1v1s3ky 5rFDoEE45Nu8OcQWTbz59AdEUnW1B82skX2fjXISl2UGZGoX5y/9nfRuYMTus7GjCxY0 l0g2vbQ5sT/iEQRC+3NHHVzXkkC6DRWx+owWA=
MIME-Version: 1.0
Received: by 10.224.103.12 with SMTP id i12mr4044430qao.120.1250502816117;  Mon, 17 Aug 2009 02:53:36 -0700 (PDT)
Date: Mon, 17 Aug 2009 15:23:36 +0530
Message-ID: <922a897b0908170253k60c0d57dh5e593c78f9137fab@mail.gmail.com>
From: Ravi shankar <ravisha22@gmail.com>
To: asrg@irtf.org
Content-Type: multipart/alternative; boundary=000feaf1dbdd2538310471536035
Subject: [Asrg] [ASRG] SMTP pull anyone?
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Aug 2009 09:53:39 -0000

--000feaf1dbdd2538310471536035
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

>DNS is used *as a medium* for various applications that are used to
identify

>mail as legitimate or illegitimate by various standards of legitimacy, and
a

>major reason for its use in those applications is to make it feasible for

>mail systems to do the validation synchronously during the SMTP session. By

>using a lightweight, distributed, cached database, mail systems are spared

>from deferring a message, queuing its validation, remembering the results,

>and waiting for the sender to offer it in an identical way again. You are

>suggesting that receivers should take on all the heavyweight management but

>retain using DNS for something unspecified. It makes no sense.

Bill,

Today's model is no different from what i have suggested in that they deploy
costly anti-spam

solutions, which utilise probably 10 fold resource than what this solution
will use. By allowing the system to cut most of the spam through a simple
pull mechanism, compares very well against today's anti-spam software model,
which not all can afford.

>The *most* that SPF can provide towards showing "legitimacy" is to confirm

>that the envelope sender address of a message is not forged. It is very
rare

>for large senders of any sort to deploy records that can do that strongly.

>There is nothing about SPF that directly attacks spamming. It could in

>theory be used to attack sender forgery, but the collateral damage has

>proven to be too great for either sending or receiving systems to actually

>apply it strongly to that end. Meanwhile, a lot of spammers are sending a

>lot of spam with senders that are validated to the degree that SPF can

>validate anything.

Actually SPF only validate the legitimacy of the sender IP and domain
relation and i mentioned SPF as just a example. And if the large senders
cannot implement something as simple as a TXT record for SPF (leave alone
DKIM), then probably they do no care about spam. SPF or DKIM are only
effective when deployed by all the domains that send mails.

> 4. The sending server then hands over the message.

> 5. To overcome DDoS attacks, the receiving server can be made to request

> the next 10 or so Message IDs that it will assign to messages,

> so that if a attacker tries to give those details, it will know from the

> next list of message IDs that it's fake connection.

>>>That sentence makes no sense. What did you mean to say?

What i mean is in order to prevent a system from getting overwhelmed, by
anonymous submission, if for say domain1.com server knows the next 10
message ID that will be sent by domain2.com, then it can confidently reject
those message submission attempts that does not have any mails in this range
(ofcourse this logic holds only if domain2.com is going to send those 10
message IDs domain1.com only)

>Nothing you have described would add to spam control as it is currently

>being done, as far as I can see. The 'model' is too vague to critique inn

>detail because you aren't really providing any meaningful details.

>In order to bring anything truly new and useful to controlling email spam,
a

>new idea has to either attack spam in a way that existing tactics don't, do

>a demonstrably better job than existing tactics, or overcome the negative

>aspects of existing tactics. You have identified none of those in your new

>idea.

I guess we are expecting a magic solution that will stop all the spam in a
single go and would not require us from changing our system continuosly. But
unfortunately, every system has flaws and has to be corrected one step at a
time, this i believe is the evolution.
I have done my best to detail how this system applies in various steps of a
mail communication, may be i can work on a pictorial representation, if
someone else requires it as well.


Regards,
Ravi

--000feaf1dbdd2538310471536035
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<font size=3D"2">
<p>&gt;DNS is used *as a medium* for various applications that are used to =
identify</p>
<p>&gt;mail as legitimate or illegitimate by various standards of legitimac=
y, and a</p>
<p>&gt;major reason for its use in those applications is to make it feasibl=
e for</p>
<p>&gt;mail systems to do the validation synchronously during the SMTP sess=
ion. By</p>
<p>&gt;using a lightweight, distributed, cached database, mail systems are =
spared</p>
<p>&gt;from deferring a message, queuing its validation, remembering the re=
sults,</p>
<p>&gt;and waiting for the sender to offer it in an identical way again. Yo=
u are</p>
<p>&gt;suggesting that receivers should take on all the heavyweight managem=
ent but</p>
<p>&gt;retain using DNS for something unspecified. It makes no sense.</p>
<p>Bill,</p>
<p>Today&#39;s model is no different from what i have suggested in that the=
y deploy costly anti-spam</p>
<p>solutions, which utilise probably 10 fold resource than what this soluti=
on will use. By allowing the system to cut most of the spam through a simpl=
e pull mechanism, compares very well against today&#39;s anti-spam software=
 model, which not all can afford.</p>

<p>&gt;The *most* that SPF can provide towards showing &quot;legitimacy&quo=
t; is to confirm</p>
<p>&gt;that the envelope sender address of a message is not forged. It is v=
ery rare</p>
<p>&gt;for large senders of any sort to deploy records that can do that str=
ongly.</p>
<p>&gt;There is nothing about SPF that directly attacks spamming. It could =
in</p>
<p>&gt;theory be used to attack sender forgery, but the collateral damage h=
as</p>
<p>&gt;proven to be too great for either sending or receiving systems to ac=
tually</p>
<p>&gt;apply it strongly to that end. Meanwhile, a lot of spammers are send=
ing a</p>
<p>&gt;lot of spam with senders that are validated to the degree that SPF c=
an</p>
<p>&gt;validate anything.</p>
<p>Actually SPF only validate the legitimacy of the sender IP and domain re=
lation and i mentioned SPF as just a example. And if the large senders cann=
ot implement something as simple as a TXT record for SPF (leave alone DKIM)=
, then probably they do no care about spam. SPF or DKIM are only effective =
when deployed by all the domains that send mails.</p>

<p>&gt; 4. The sending server then hands over the message.</p>
<p>&gt; 5. To overcome DDoS attacks, the receiving server can be made to re=
quest</p>
<p>&gt; the next 10 or so Message IDs that it will assign to messages,</p>
<p>&gt; so that if a attacker tries to give those details, it will know fro=
m the</p>
<p>&gt; next list of message IDs that it&#39;s fake connection.</p>
<p>&gt;&gt;&gt;That sentence makes no sense. What did you mean to say?</p>
<p>What i mean is in order to prevent a system from getting overwhelmed, by=
 anonymous submission, if for say <a href=3D"http://domain1.com">domain1.co=
m</a> server knows the next 10 message ID that will be sent by <a href=3D"h=
ttp://domain2.com">domain2.com</a>, then it can confidently reject those me=
ssage submission attempts that does not have any mails in this range (ofcou=
rse this logic holds only if <a href=3D"http://domain2.com">domain2.com</a>=
 is going to send those 10 message IDs <a href=3D"http://domain1.com">domai=
n1.com</a> only)</p>

<p>&gt;Nothing you have described would add to spam control as it is curren=
tly</p>
<p>&gt;being done, as far as I can see. The &#39;model&#39; is too vague to=
 critique inn</p>
<p>&gt;detail because you aren&#39;t really providing any meaningful detail=
s.</p>
<p>&gt;In order to bring anything truly new and useful to controlling email=
 spam, a</p>
<p>&gt;new idea has to either attack spam in a way that existing tactics do=
n&#39;t, do</p>
<p>&gt;a demonstrably better job than existing tactics, or overcome the neg=
ative</p>
<p>&gt;aspects of existing tactics. You have identified none of those in yo=
ur new</p>
<p>&gt;idea.</p>
<p>I guess we are expecting a magic solution that will stop all the spam in=
 a single go and would not require us from changing our system continuosly.=
 But unfortunately, every system has flaws and has to be corrected one step=
 at a time, this i believe is the evolution. </p>

<div>I have done my best to detail how this system applies in various steps=
 of a mail communication, may be i can work on a pictorial representation, =
if someone else requires it as well.</div>
<div>=A0</div>
<div>=A0</div>
<div>Regards,</div>
<div>Ravi</div></font>

--000feaf1dbdd2538310471536035--

From iane@sussex.ac.uk  Mon Aug 17 03:05:47 2009
Return-Path: <iane@sussex.ac.uk>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E63773A681A for <asrg@core3.amsl.com>; Mon, 17 Aug 2009 03:05:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.392
X-Spam-Level: 
X-Spam-Status: No, score=-1.392 tagged_above=-999 required=5 tests=[AWL=-1.207, BAYES_40=-0.185]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id decDNs0HU9K0 for <asrg@core3.amsl.com>; Mon, 17 Aug 2009 03:05:47 -0700 (PDT)
Received: from sivits.uscs.susx.ac.uk (sivits.uscs.susx.ac.uk [139.184.14.88]) by core3.amsl.com (Postfix) with ESMTP id D80233A672E for <asrg@irtf.org>; Mon, 17 Aug 2009 03:05:46 -0700 (PDT)
Received: from lewes.staff.uscs.susx.ac.uk ([139.184.134.43]:49541) by sivits.uscs.susx.ac.uk with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.64) (envelope-from <iane@sussex.ac.uk>) id KOIMPK-0008UF-HX for asrg@irtf.org; Mon, 17 Aug 2009 11:05:44 +0100
Date: Mon, 17 Aug 2009 11:05:44 +0100
From: Ian Eiloart <iane@sussex.ac.uk>
Sender: iane@sussex.ac.uk
To: asrg@irtf.org
Message-ID: <2E9DB38172DCD7955B90C74C@lewes.staff.uscs.susx.ac.uk>
In-Reply-To: <4A884C68.7020301@billmail.scconsult.com>
References: <922a897b0908160420w4554837aj684e86eb586823af@mail.gmail.com> <4A884C68.7020301@billmail.scconsult.com>
Originator-Info: login-token=Mulberry:01fHD1aeXRY8693UnL6Jbv5Wjc4ugWw9+W8ds=;  token_authority=support@its.sussex.ac.uk
X-Mailer: Mulberry/4.0.8 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Sussex: true 
X-Sussex-transport: remote_smtp 
Subject: Re: [Asrg] SMTP pull anyone?
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Aug 2009 10:05:48 -0000

--On 16 August 2009 14:14:00 -0400 Bill Cole <asrg3@billmail.scconsult.com> 
wrote:

>
>> 3. If the IP that contacted is legitimate(can be verified by say SPF?),
>> it contacts the sender and provides the message ID with other details.
>
> The *most* that SPF can provide towards showing "legitimacy" is to
> confirm that the envelope sender address of a message is not forged. It
> is very rare for large senders of any sort to deploy records that can do
> that strongly. There is nothing about SPF that directly attacks spamming.
> It could in theory be used to attack sender forgery, but the collateral
> damage has proven to be too great for either sending or receiving systems
> to actually apply it strongly to that end. Meanwhile, a lot of spammers
> are sending a lot of spam with senders that are validated to the degree
> that SPF can validate anything.

SPF deployment has grown rapidly from 5% of 2,000,000 sampled domains to 
17% over the past three years, apparently including most USA banks. About 
half of spf publishing domains, including some large senders like facebook, 
use "-all" records. Apart from anything else "-all" on its own is a good 
way of saying "this isn't an email domain", and it's probably a good idea 
to publish it for every A record that doesn't point to a mail server.

Furthermore, some large recipients like gmail use these records to help 
assign reputation to senders. Forwarded email is likely already suffering 
from deliverability problems when the sender address is not rewritten (at 
least in cases like forwarding facebook mail to gmail, for example), and 
these problems will continue to get worse, not better as SPF deployment 
increases, and as records are increasingly respected.

People who want to offer a reliable forwarding service to their users 
already need to be thinking about rewriting sender addresses.

It might take a few years, but I'm convinced that we'll look back on SPF 
deployment in the same was that we look back on the campaign against open 
relays some years ago.

-- 
Ian Eiloart
IT Services, University of Sussex
01273-873148 x3148
For new support requests, see http://www.sussex.ac.uk/its/help/

From johnl@iecc.com  Mon Aug 17 06:04:27 2009
Return-Path: <johnl@iecc.com>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5ADD63A6ED7 for <asrg@core3.amsl.com>; Mon, 17 Aug 2009 06:04:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -18.596
X-Spam-Level: 
X-Spam-Status: No, score=-18.596 tagged_above=-999 required=5 tests=[AWL=0.604, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id awRzW+4Ntgz5 for <asrg@core3.amsl.com>; Mon, 17 Aug 2009 06:04:26 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [208.31.42.53]) by core3.amsl.com (Postfix) with ESMTP id 73A6A3A6EFB for <asrg@irtf.org>; Mon, 17 Aug 2009 06:03:59 -0700 (PDT)
Received: (qmail 15340 invoked from network); 17 Aug 2009 13:03:57 -0000
Received: from mail1.iecc.com (208.31.42.56) by mail1.iecc.com with QMQP; 17 Aug 2009 13:03:57 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:in-reply-to:cc:mime-version:content-type:content-transfer-encoding; s=k0908; olt=johnl@user.iecc.com; bh=nyTAPL0kA2LBIAtEgS9qQOdlwtfHoVMfq5AABWMMQoY=; b=dhDVUaGriRiO7OMOMZafAPTGbR4JaIBlNN2sG5zGcnnYNQ6munzm8eRthp4TD4M3cuVT5cX2UdE0mPgn06hVIQv6YogkZtg/+xcZSAgmvubzslVplrQp6sx6olFMAjuTp4dadP2niiBMU1C4YvEhk3lPQciqG1uYfBADPFx+Fhs=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:subject:in-reply-to:cc:mime-version:content-type:content-transfer-encoding; s=k0908; bh=nyTAPL0kA2LBIAtEgS9qQOdlwtfHoVMfq5AABWMMQoY=; b=PhNelazJ0WViaFRaiTQ8H3pMs6ZgK4GsPXNRaiOMOAQlwTmebv11fnNl+fj73z9G+rcQGJ+aZbG37KHbSHRngdKJY/7VocNZpkf2tsYN7cF2CK8f6ZNQ2I85Obn2UHxUH5lB31oUTOS/UG0Bi1fW7bBqEPNREe5C84DVNwPRXmw=
Date: 17 Aug 2009 13:03:57 -0000
Message-ID: <20090817130357.18416.qmail@simone.iecc.com>
From: John Levine <johnl@taugh.com>
To: asrg@irtf.org
In-Reply-To: <922a897b0908170253k60c0d57dh5e593c78f9137fab@mail.gmail.com>
Organization: 
Cc: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7bit
Subject: Re: [Asrg] [ASRG] SMTP pull anyone?
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Aug 2009 13:04:27 -0000

> By allowing the system to cut most of the spam through a simple pull
> mechanism, compares very well against today's anti-spam software
> model, which not all can afford.

I gather that you are proposing a system in which mail from a particular
domain can only be offered from servers that are somehow authorized by
or related to that domain.  If so, that is a huge change to the SMTP
store-and-forward model.

The predecessor to SMTP was a hack layered on FTP which only worked if
the sender and recipient systems were both online at the same time
and could talk directly to each other.  SMTP store-and-forward
was a big advance over that a lot of real useful mail systems depend
on being able to deliver mail in multiple stages.

If your idea is that mail from foo.com can only come from a foo.com
server or something like that, you might want to explain how your
proposal differs from RSS, and particularly from the model in the
Tumbleweed patent.

R's,
John

PS:

>I guess we are expecting a magic solution that will stop all the spam in a
>single go and would not require us from changing our system continuosly.

No we are not, and I have to say that's not a very useful line of argument.

From rsk@gsp.org  Mon Aug 17 07:44:57 2009
Return-Path: <rsk@gsp.org>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 61B483A6951 for <asrg@core3.amsl.com>; Mon, 17 Aug 2009 07:44:57 -0700 (PDT)
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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AFFlOgg93bfa for <asrg@core3.amsl.com>; Mon, 17 Aug 2009 07:44:56 -0700 (PDT)
Received: from taos.firemountain.net (taos.firemountain.net [207.114.3.54]) by core3.amsl.com (Postfix) with ESMTP id 331743A699F for <asrg@irtf.org>; Mon, 17 Aug 2009 07:44:54 -0700 (PDT)
Received: from squonk.gsp.org (bltmd-207.114.25.206.dsl.charm.net [207.114.25.206]) by taos.firemountain.net (8.14.1/8.14.1) with ESMTP id n7HEiuuD007917 for <asrg@irtf.org>; Mon, 17 Aug 2009 10:44:57 -0400 (EDT)
Received: from avatar.gsp.org (avatar.gsp.org [192.168.0.11]) by squonk.gsp.org (8.14.1/8.14.1) with ESMTP id n7HEbMQp004789 for <asrg@irtf.org>; Mon, 17 Aug 2009 10:37:23 -0400 (EDT)
Received: from avatar.gsp.org (localhost [127.0.0.1]) by avatar.gsp.org (8.14.3/8.14.3/Debian-4) with ESMTP id n7HEiouF025789 for <asrg@irtf.org>; Mon, 17 Aug 2009 10:44:50 -0400
Received: (from rsk@localhost) by avatar.gsp.org (8.14.3/8.14.3/Submit) id n7HEiooW025788 for asrg@irtf.org; Mon, 17 Aug 2009 10:44:50 -0400
Date: Mon, 17 Aug 2009 10:44:50 -0400
From: Rich Kulawiec <rsk@gsp.org>
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
Message-ID: <20090817144450.GA22048@gsp.org>
References: <922a897b0908170253k60c0d57dh5e593c78f9137fab@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <922a897b0908170253k60c0d57dh5e593c78f9137fab@mail.gmail.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
Subject: Re: [Asrg] [ASRG] SMTP pull anyone?
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Aug 2009 14:44:57 -0000

On Mon, Aug 17, 2009 at 03:23:36PM +0530, Ravi shankar wrote:
> Today's model is no different from what i have suggested in that they deploy
> costly anti-spam solutions, which utilise probably 10 fold resource
> than what this solution will use.

If they are costly, and if they use so many resources, then they're not
very good solutions.  It's not difficult at all to construct very cheap,
very efficient anti-spam solutions which exhibit good performance
characteristics (that is: low FP, low FN, no backscatter, no spamming,
no special MUA/MTA software needed, etc.)

The fact that some (many?) people choose not to avail themselves of these
methods is unfortunate, but doesn't invalidate the methods.

---Rsk



From dotis@mail-abuse.org  Mon Aug 17 09:24:47 2009
Return-Path: <dotis@mail-abuse.org>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4FB2F3A67E2 for <asrg@core3.amsl.com>; Mon, 17 Aug 2009 09:24:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.423
X-Spam-Level: 
X-Spam-Status: No, score=-5.423 tagged_above=-999 required=5 tests=[AWL=1.176,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8WnkGv0MrSf7 for <asrg@core3.amsl.com>; Mon, 17 Aug 2009 09:24:46 -0700 (PDT)
Received: from harry.mail-abuse.org (harry.mail-abuse.org [168.61.5.27]) by core3.amsl.com (Postfix) with ESMTP id 3DA0E3A677C for <asrg@irtf.org>; Mon, 17 Aug 2009 09:24:32 -0700 (PDT)
Received: from SJC-Office-NAT-214.mail-abuse.org (gateway1.sjc.mail-abuse.org [168.61.5.81]) by harry.mail-abuse.org (Postfix) with ESMTP id CD75FA9443A for <asrg@irtf.org>; Mon, 17 Aug 2009 16:24:32 +0000 (UTC)
Message-ID: <4A898440.6080006@mail-abuse.org>
Date: Mon, 17 Aug 2009 09:24:32 -0700
From: Douglas Otis <dotis@mail-abuse.org>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1.1) Gecko/20090715 Thunderbird/3.0b3
MIME-Version: 1.0
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
References: <922a897b0908170253k60c0d57dh5e593c78f9137fab@mail.gmail.com> <20090817144450.GA22048@gsp.org>
In-Reply-To: <20090817144450.GA22048@gsp.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [Asrg] [ASRG] SMTP pull anyone?
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Aug 2009 16:24:47 -0000

On 8/17/09 7:44 AM, Rich Kulawiec wrote:
> On Mon, Aug 17, 2009 at 03:23:36PM +0530, Ravi shankar wrote:
>> Today's model is no different from what i have suggested in that they deploy
>> costly anti-spam solutions, which utilise probably 10 fold resource
>> than what this solution will use.
>
> If they are costly, and if they use so many resources, then they're not
> very good solutions.  It's not difficult at all to construct very cheap,
> very efficient anti-spam solutions which exhibit good performance
> characteristics (that is: low FP, low FN, no backscatter, no spamming,
> no special MUA/MTA software needed, etc.)
>
> The fact that some (many?) people choose not to avail themselves of these
> methods is unfortunate, but doesn't invalidate the methods.

Rich,

Could you provide a brief outline regarding what constitutes an 
efficient anti-spam solution?

-Doug

From mike@mtcc.com  Mon Aug 17 09:35:06 2009
Return-Path: <mike@mtcc.com>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 610CB28C26E for <asrg@core3.amsl.com>; Mon, 17 Aug 2009 09:35:06 -0700 (PDT)
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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qRVpizv5O6sQ for <asrg@core3.amsl.com>; Mon, 17 Aug 2009 09:35:05 -0700 (PDT)
Received: from mtcc11.mtcc.com (mtcc11.mtcc.com [64.142.29.211]) by core3.amsl.com (Postfix) with ESMTP id 1B4463A69F6 for <asrg@irtf.org>; Mon, 17 Aug 2009 09:34:28 -0700 (PDT)
Received: from mtcc11.mtcc.com (mtcc11.mtcc.com [64.142.29.211]) (authenticated bits=0) by mtcc11.mtcc.com (8.14.3/8.14.3) with ESMTP id n7HGYRBI013452 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <asrg@irtf.org>; Mon, 17 Aug 2009 09:34:27 -0700
Message-ID: <4A898693.7030609@mtcc.com>
Date: Mon, 17 Aug 2009 09:34:27 -0700
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: <20090816222944.96264.qmail@simone.iecc.com>
In-Reply-To: <20090816222944.96264.qmail@simone.iecc.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [Asrg] SMTP pull anyone?
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Aug 2009 16:35:06 -0000

I don't see how push or pull fundamentally changes the spam
equation in any case. The problem wrt spam is the any-any nature
of who you receive communication from, not who initiates the
connection.

I can create a walled garden trivially with smtp just be rejecting
connections from people not on my whitelist. Likewise, anything that
is promiscuous with who it receives from better be prepared for
mail-transmitted diseases (MTD's). That's just the nature of opening
up. So SMTP itself isn't the problem, or more specifically fretting
about SMTP is nipping around the edges of 20 with the 80-20 rule.

Mike

On 08/16/2009 03:29 PM, John Levine wrote:
>>> SMTP is currently a push protocol and is initiated by the the
>>> sender, no controlling that fact.
>
>>> But it is possible to overcome the relay problems, IP spoofing and
>>> domain impersonation etc,
>
>>> by making the servers pull the mails.
>
>> US6192407
>
> Ah, right, the famous Tumbleweed patent.  Here's a better link
> with a readable version.
>
> http://www.google.com/patents?vid=USPAT6192407
>
> This patent covers the idea of putting a message on a web server and
> sending the recipient a URL to retrieve the message.  Tumbleweed
> enforces it very aggressively.  See the list of suits in their
> Wikipedia page.
>
> Were it not for the patent, I expect we'd have a lot of institutions
> setting up per-user password protected RSS or Atom feeds with
> statements and other messages, and sending you mail telling you to
> check your feed when there's something new.
>
> R's,
> John
> _______________________________________________
> Asrg mailing list
> Asrg@irtf.org
> http://www.irtf.org/mailman/listinfo/asrg


From dotis@mail-abuse.org  Mon Aug 17 10:15:04 2009
Return-Path: <dotis@mail-abuse.org>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6801B3A6853 for <asrg@core3.amsl.com>; Mon, 17 Aug 2009 10:15:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.521
X-Spam-Level: 
X-Spam-Status: No, score=-5.521 tagged_above=-999 required=5 tests=[AWL=1.078,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vwJ0i5G9XmBo for <asrg@core3.amsl.com>; Mon, 17 Aug 2009 10:15:03 -0700 (PDT)
Received: from harry.mail-abuse.org (harry.mail-abuse.org [168.61.5.27]) by core3.amsl.com (Postfix) with ESMTP id AF11A3A684A for <asrg@irtf.org>; Mon, 17 Aug 2009 10:15:03 -0700 (PDT)
Received: from SJC-Office-NAT-214.mail-abuse.org (gateway1.sjc.mail-abuse.org [168.61.5.81]) by harry.mail-abuse.org (Postfix) with ESMTP id 6E2BCA9443A for <asrg@irtf.org>; Mon, 17 Aug 2009 17:14:44 +0000 (UTC)
Message-ID: <4A899004.2090000@mail-abuse.org>
Date: Mon, 17 Aug 2009 10:14:44 -0700
From: Douglas Otis <dotis@mail-abuse.org>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1.1) Gecko/20090715 Thunderbird/3.0b3
MIME-Version: 1.0
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
References: <20090816222944.96264.qmail@simone.iecc.com> <4A898693.7030609@mtcc.com>
In-Reply-To: <4A898693.7030609@mtcc.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [Asrg] SMTP pull anyone?
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Aug 2009 17:15:04 -0000

On 8/17/09 9:34 AM, Michael Thomas wrote:
> I don't see how push or pull fundamentally changes the spam
> equation in any case. The problem wrt spam is the any-any nature
> of who you receive communication from, not who initiates the
> connection.

The pull concept is fairly simple.  When creating a white-list, it 
becomes important to identify the source of the message.  Since email 
uses store and forwarding, originating sources of messages can be 
difficult to determine, based upon the message alone.  Of course DKIM 
helps with that, but it would be more ideal to shift a greater portion 
of the burden toward the sender for email to continue to scale.

By exchanging only references to messages that are held on-line, the 
message itself does not need to be initially exchanged.  When contacted 
by a specific source that has been white-listed, your MUA could fetch 
the desired message from the on-line server at the same time references 
have been retrieved.

When a reference has been falsified, no message can be fetched.  This 
would not demand cryptographic efforts by the sender, or expect receipt 
of an exponentially increasing volume of junk, or tens or hundreds of 
DNS transactions per domain to resolve server authorizations.

One wonders whether IMAP might be tweaked to provide an online function 
rather than using traditional URIs.  The problem should not be viewed as 
the 80-20 rule where 80% of the problems are caused by 20% of the 
sources.  This should be viewed as the 99-99 rule, in today's email 
environment.

-Doug

From ravisha22@gmail.com  Mon Aug 17 12:22:58 2009
Return-Path: <ravisha22@gmail.com>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1F0F328C2F1 for <asrg@core3.amsl.com>; Mon, 17 Aug 2009 12:22:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.474
X-Spam-Level: 
X-Spam-Status: No, score=-2.474 tagged_above=-999 required=5 tests=[AWL=0.124,  BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DQEXNPNXMV66 for <asrg@core3.amsl.com>; Mon, 17 Aug 2009 12:22:57 -0700 (PDT)
Received: from mail-qy0-f194.google.com (mail-qy0-f194.google.com [209.85.221.194]) by core3.amsl.com (Postfix) with ESMTP id 4817928C2EE for <asrg@irtf.org>; Mon, 17 Aug 2009 12:22:57 -0700 (PDT)
Received: by qyk32 with SMTP id 32so2247217qyk.15 for <asrg@irtf.org>; Mon, 17 Aug 2009 12:23:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=jVIQN07ElYibT8OMyI+M8sfmnEfUUFlK0m7WoTVxIU0=; b=PQ9JmljC1keiqTnkMQfnkJSi1jGKTO9S2sfbvPrnsaD10Qc5aQV/YO3d0iId+iqHHd uaPT6NX4qPrmG15FDccRI3bi2zS+tBrfGY0qTeRo7+F9RiVneZ9ohvH1QzjP+++0YiYI rEAHhcFmWb/9QCLdK3Ul3H9BgC1X9I8eFbDLc=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=YeJ2YgqXmLjJDO1H4+szKGqD5OCwpu2VKCml+XhyhCCCpXBkaAfsiVAn9QWqKEduUb 4DiqDZwv5pDHNoBK9AKxh6HidQzSHt+Gbi5/MCKY0Q0QJfqQpBIbFyW7aUv2bhF65iiq t83WZDhNawTdeGT37gY0L5jagPNXfjfQyue7k=
MIME-Version: 1.0
Received: by 10.224.116.212 with SMTP id n20mr4616627qaq.172.1250536978278;  Mon, 17 Aug 2009 12:22:58 -0700 (PDT)
Date: Tue, 18 Aug 2009 00:52:58 +0530
Message-ID: <922a897b0908171222y30c07483x829e0f1491ab40f@mail.gmail.com>
From: Ravi shankar <ravisha22@gmail.com>
To: asrg@irtf.org
Content-Type: multipart/alternative; boundary=00c09f9720085f06ab04715b5422
Subject: Re: [Asrg] [ASRG] SMTP pull anyone?
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Aug 2009 19:22:58 -0000

--00c09f9720085f06ab04715b5422
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

@John Levine,

The model is like a simple C/R involving Message ID of a mail. The sending
domain provides the Message ID and allows computational time for the
receiving domain and then query the sending domain to send the message.

Apparently i was not aware of the tumbleweed patent, in which case,
Tumbleweed, can claim this model if implemented as a infringement or
complete violation.

Regards,
Ravi

--00c09f9720085f06ab04715b5422
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div>@John Levine,</div>
<div>=A0</div>
<div>The model is like a simple C/R involving Message ID of a mail. The sen=
ding domain provides the Message ID and allows computational time for the r=
eceiving domain and then query the sending domain to send the message.</div=
>

<div>=A0</div>
<div>Apparently i was not aware of the tumbleweed patent, in which case, Tu=
mbleweed, can claim this model if implemented as a infringement or complete=
 violation.</div>
<div>=A0</div>
<div>Regards,</div>
<div>Ravi</div>

--00c09f9720085f06ab04715b5422--

From rsk@gsp.org  Mon Aug 17 19:09:57 2009
Return-Path: <rsk@gsp.org>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6605B3A697E for <asrg@core3.amsl.com>; Mon, 17 Aug 2009 19:09:57 -0700 (PDT)
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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id D19-vrIcwqmh for <asrg@core3.amsl.com>; Mon, 17 Aug 2009 19:09:56 -0700 (PDT)
Received: from taos.firemountain.net (taos.firemountain.net [207.114.3.54]) by core3.amsl.com (Postfix) with ESMTP id 5202D28C1A0 for <asrg@irtf.org>; Mon, 17 Aug 2009 19:09:55 -0700 (PDT)
Received: from squonk.gsp.org (bltmd-207.114.25.206.dsl.charm.net [207.114.25.206]) by taos.firemountain.net (8.14.1/8.14.1) with ESMTP id n7I29vqr020318 for <asrg@irtf.org>; Mon, 17 Aug 2009 22:09:59 -0400 (EDT)
Received: from avatar.gsp.org (avatar.gsp.org [192.168.0.11]) by squonk.gsp.org (8.14.1/8.14.1) with ESMTP id n7I22N1l023007 for <asrg@irtf.org>; Mon, 17 Aug 2009 22:02:23 -0400 (EDT)
Received: from avatar.gsp.org (localhost [127.0.0.1]) by avatar.gsp.org (8.14.3/8.14.3/Debian-4) with ESMTP id n7I29qrq031118 for <asrg@irtf.org>; Mon, 17 Aug 2009 22:09:52 -0400
Received: (from rsk@localhost) by avatar.gsp.org (8.14.3/8.14.3/Submit) id n7I29qQK031117 for asrg@irtf.org; Mon, 17 Aug 2009 22:09:52 -0400
Date: Mon, 17 Aug 2009 22:09:52 -0400
From: Rich Kulawiec <rsk@gsp.org>
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
Message-ID: <20090818020952.GA30677@gsp.org>
References: <922a897b0908170253k60c0d57dh5e593c78f9137fab@mail.gmail.com> <20090817144450.GA22048@gsp.org> <4A898440.6080006@mail-abuse.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4A898440.6080006@mail-abuse.org>
User-Agent: Mutt/1.5.18 (2008-05-17)
Subject: Re: [Asrg] [ASRG] SMTP pull anyone?
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Aug 2009 02:09:57 -0000

On Mon, Aug 17, 2009 at 09:24:32AM -0700, Douglas Otis wrote:
> Could you provide a brief outline regarding what constitutes an  
> efficient anti-spam solution?

Sure.  In brief (really brief!) and in (rough) order of application
	and increasing resource cost:

Spamhaus DROP list on perimeter routers/firewalls
Consider IDP list on perimeter routers/firewalls
Use firewall rulesets per-country, see ipdeny.com *or* if possible,
	use default-deny and grant access per-country
Use multiline SMTP greeting (defeats some zombies)
Use "greetpause" or equivalent (defeats some zombies)
Enforce DNS/rDNS existence/consistency checks on
	hostname, MX records and HELO parameter;
	defer/reject as appropriate
Blacklist known virus/ratware senders, e.g. "big@boss.com".  Faster
	than running through an AV check
Permanently blacklist known phisher domains.  Even if acquired by legit
	companies will never be used.
Consider blacklisting spammer-infested/useless TLDs (e.g., .info, .mobi)
	with whitelisting as needed, if needed
Permanently blacklist known spammer domains (e.g. Joe Wein's list)
Permanently blacklist any "snowshoe" domain/domain group on sight
Blacklist any "snowshoe" network range on sight
Use enemieslist or other similar rDNS-based blocks on end-user/dynamic names
Use Spamhaus Zen DNSBL
Use other DNSBLs/RHSBLs as appropriate
Throttle connections with excessive attempts/deliveries
	to nonexistent users/etc.

Obviously, the choice of which ones, in which order, with which
configuration, depends on mail system administrator knowledge of local
mail patterns.  Everyone should analyze their own logs to gain that
knowledge.  And some of these are no-brainers no matter what those
patterns are, e.g., DROP list, DNS/rDNS checks, Spamhaus Zen, etc.
And I've probably omitted some by doing this off the top of my head.
On a Monday. ;-)

---Rsk

From johnl@iecc.com  Mon Aug 17 20:38:01 2009
Return-Path: <johnl@iecc.com>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 752C13A6D2D for <asrg@core3.amsl.com>; Mon, 17 Aug 2009 20:38:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -18.797
X-Spam-Level: 
X-Spam-Status: No, score=-18.797 tagged_above=-999 required=5 tests=[AWL=0.402, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FS7eMyxJqhOm for <asrg@core3.amsl.com>; Mon, 17 Aug 2009 20:38:00 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [208.31.42.53]) by core3.amsl.com (Postfix) with ESMTP id 2EA4D3A6A70 for <asrg@irtf.org>; Mon, 17 Aug 2009 20:37:59 -0700 (PDT)
Received: (qmail 6601 invoked from network); 18 Aug 2009 03:38:01 -0000
Received: from mail1.iecc.com (208.31.42.56) by mail1.iecc.com with QMQP; 18 Aug 2009 03:38:01 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:in-reply-to:cc:mime-version:content-type:content-transfer-encoding; s=k0908; olt=johnl@user.iecc.com; bh=ClLMvIujq22NbF5hDWF1iceQi+lrToU97vqL9ioRbK8=; b=imMI1gvWclJfkSpSBVvDZI7kEyLiyd3FHQN7lg78doGlNb0zs/mO/GXDJPjklNYUpHNQP8K0RFRvPbQOXanBo+Aa3kZWMvb2mS11ph9rOn/9eM5VM6XlBodSiujOE8ETz/UbaF3T2kJ/CREk7zvdJju3Jl5qObU2htZ3apYFgAA=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:subject:in-reply-to:cc:mime-version:content-type:content-transfer-encoding; s=k0908; bh=ClLMvIujq22NbF5hDWF1iceQi+lrToU97vqL9ioRbK8=; b=i2Pnjkf1LzKtF7CXaTdqSO9GBL7a6Dv4LaAFjd/xux6SKbjiqwEU5wdHXxUIcQtw+PlVy/BBuN9ILP15IX5KfawOfUESedB/o1y5h7w3QrRrqe6mg7d3GF8JlPUk35nuaNEzPhirbRO4YuOq0I5XkMJvkjD8xQyr5Hh+GShU8vU=
Date: 18 Aug 2009 03:38:01 -0000
Message-ID: <20090818033801.4352.qmail@simone.iecc.com>
From: John Levine <johnl@taugh.com>
To: asrg@irtf.org
In-Reply-To: <922a897b0908171222y30c07483x829e0f1491ab40f@mail.gmail.com>
Organization: 
Cc: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7bit
Subject: Re: [Asrg] [ASRG] SMTP pull anyone?
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Aug 2009 03:38:01 -0000

>The model is like a simple C/R involving Message ID of a mail. The
>sending domain provides the Message ID and allows computational time
>for the receiving domain and then query the sending domain to send
>the message.

This model has been proposed many, many, times before.  I suppose we should
make a page for it in the ASRG wiki of anti-spam techniques even though it's
more of a mail system redesign than an anti-spam measure.

R's,
John

From steve@blighty.com  Mon Aug 17 20:43:16 2009
Return-Path: <steve@blighty.com>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2284B3A6DE5 for <asrg@core3.amsl.com>; Mon, 17 Aug 2009 20:43:16 -0700 (PDT)
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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FdSUvSv6aOiG for <asrg@core3.amsl.com>; Mon, 17 Aug 2009 20:43:15 -0700 (PDT)
Received: from m.wordtothewise.com (fruitbat.wordtothewise.com [208.187.80.135]) by core3.amsl.com (Postfix) with ESMTP id 5FB6428C1BB for <asrg@irtf.org>; Mon, 17 Aug 2009 20:43:15 -0700 (PDT)
Received: from [192.168.80.34] (184.wordtothewise.com [208.187.80.184]) by m.wordtothewise.com (Postfix) with ESMTP id 9D49F807C7 for <asrg@irtf.org>; Mon, 17 Aug 2009 20:42:56 -0700 (PDT)
Message-Id: <D30442DC-16E5-4827-864F-502FFF590BE4@blighty.com>
From: Steve Atkins <steve@blighty.com>
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
In-Reply-To: <20090818033801.4352.qmail@simone.iecc.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v936)
Date: Mon, 17 Aug 2009 20:43:13 -0700
References: <20090818033801.4352.qmail@simone.iecc.com>
X-Mailer: Apple Mail (2.936)
Subject: Re: [Asrg] [ASRG] SMTP pull anyone?
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Aug 2009 03:43:16 -0000

On Aug 17, 2009, at 8:38 PM, John Levine wrote:

>> The model is like a simple C/R involving Message ID of a mail. The
>> sending domain provides the Message ID and allows computational time
>> for the receiving domain and then query the sending domain to send
>> the message.
>
> This model has been proposed many, many, times before.  I suppose we  
> should
> make a page for it in the ASRG wiki of anti-spam techniques even  
> though it's
> more of a mail system redesign than an anti-spam measure.

If you do, mention RFC 2017.

Cheers,
   Steve


From johnl@iecc.com  Mon Aug 17 20:47:32 2009
Return-Path: <johnl@iecc.com>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D1F573A6DAC for <asrg@core3.amsl.com>; Mon, 17 Aug 2009 20:47:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -18.897
X-Spam-Level: 
X-Spam-Status: No, score=-18.897 tagged_above=-999 required=5 tests=[AWL=0.302, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dOz15AvZwC3C for <asrg@core3.amsl.com>; Mon, 17 Aug 2009 20:47:32 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [208.31.42.53]) by core3.amsl.com (Postfix) with ESMTP id D094C3A68BA for <asrg@irtf.org>; Mon, 17 Aug 2009 20:47:31 -0700 (PDT)
Received: (qmail 11176 invoked from network); 18 Aug 2009 03:47:36 -0000
Received: from mail1.iecc.com (208.31.42.56) by mail1.iecc.com with QMQP; 18 Aug 2009 03:47:36 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:in-reply-to:cc:mime-version:content-type:content-transfer-encoding; s=k0908; olt=johnl@user.iecc.com; bh=1IcYxwDfLP6f+oIV9LCpZNIFFtJYB4JrpkPfXyOhteU=; b=L8NAnixeUWceHQNyVliQrJAi5c8QFDrm11NzzZYnGMii9u4VuYdekZjzSwzoBBwZQmq3e3LT9myKIlJC29LM9iyHP6PWNp+qgJhWnrbrl4wlqhu4frdNFhUVOgvZNchLq9PzKrGreNyIe8/Vi0TA/5GtFk4vV7GOzMwObvfMSVE=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:subject:in-reply-to:cc:mime-version:content-type:content-transfer-encoding; s=k0908; bh=1IcYxwDfLP6f+oIV9LCpZNIFFtJYB4JrpkPfXyOhteU=; b=QYwAM96iyjKc2f5OtobhS9yilsrW5GLbV0u/ntFxi1OxGtZBayHuz/RTY9GwtV9Jd0czb1oC47/MKPnOdYioT7z2vykR0aTCYlEhPzdilRsqTp0YCeFBtyWGjpx9Vu0MZo7P8ZVwMmgdznx5ZUTIdB1oHI1vH2r7Kd+P2rS79NE=
Date: 18 Aug 2009 03:47:36 -0000
Message-ID: <20090818034736.4642.qmail@simone.iecc.com>
From: John Levine <johnl@taugh.com>
To: asrg@irtf.org
In-Reply-To: <4A898693.7030609@mtcc.com>
Organization: 
Cc: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7bit
Subject: Re: [Asrg] SMTP pull anyone?
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Aug 2009 03:47:32 -0000

>I don't see how push or pull fundamentally changes the spam equation
>in any case. The problem wrt spam is the any-any nature of who you
>receive communication from, not who initiates the connection.

I agree.  The main advantage I see to pull is bandwidth management,
since recipients can decide when and whether to retrieve mail for
users, rather than having to accept it all just in case someone wants
to read it.

The disadvantage is that it requires that senders and receivers all be
connected to the same network all the time, which is a lot closer to
true now than it was in the 1980s, but still a long way from
universally true.

R's,
John


From vesely@tana.it  Tue Aug 18 05:51:22 2009
Return-Path: <vesely@tana.it>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2780F3A680F for <asrg@core3.amsl.com>; Tue, 18 Aug 2009 05:51:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.569
X-Spam-Level: 
X-Spam-Status: No, score=-3.569 tagged_above=-999 required=5 tests=[AWL=-1.150, BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, MANGLED_SPAM=2.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yJuqvv1tBKGe for <asrg@core3.amsl.com>; Tue, 18 Aug 2009 05:51:21 -0700 (PDT)
Received: from wmail.tana.it (mail.tana.it [62.94.243.226]) by core3.amsl.com (Postfix) with ESMTP id 0D52A3A63EC for <asrg@irtf.org>; Tue, 18 Aug 2009 05:51:20 -0700 (PDT)
Received: from [192.168.15.114] (wf-salyut.imt.ru [212.16.1.106]) (AUTH: CRAM-MD5 ale@tana.it, TLS: TLS1.0, 256bits, RSA_AES_256_CBC_SHA1) by wmail.tana.it with esmtp; Tue, 18 Aug 2009 14:48:58 +0200 id 00000000005DC02F.000000004A8AA33A.00000F42
Message-ID: <4A8AA40B.5060801@tana.it>
Date: Tue, 18 Aug 2009 16:52:27 +0400
From: Alessandro Vesely <vesely@tana.it>
User-Agent: Thunderbird 2.0.0.22 (Windows/20090605)
MIME-Version: 1.0
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
References: <20090818033801.4352.qmail@simone.iecc.com> <D30442DC-16E5-4827-864F-502FFF590BE4@blighty.com>
In-Reply-To: <D30442DC-16E5-4827-864F-502FFF590BE4@blighty.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [Asrg] [ASRG] SMTP pull anyone?
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Aug 2009 12:51:22 -0000

Steve Atkins wrote:
> On Aug 17, 2009, at 8:38 PM, John Levine wrote:
> 
>>> The model is like a simple C/R involving Message ID of a mail. The 
>>> sending domain provides the Message ID and allows computational time 
>>> for the receiving domain and then query the sending domain to send 
>>> the message.
>>
>> This model has been proposed many, many, times before.  I suppose we should
>> make a page for it in the ASRG wiki of anti-spam techniques even though it's
>> more of a mail system redesign than an anti-spam measure.

Agreed; however, I'm out of office this week, and will consider 
doing this only when I'll be back. (As a new entry in 
http://wiki.asrg.sp.am/wiki/Taxonomy_of_anti-spam_techniques#SMTP_techniques 
I suppose).

IMHO, this model --this instance of it-- stems from the common 
qui pro quo generated by speaking of clients (or servers) as if 
they were hosts, rather than processes: Most spam comes from 
clients, I want to eliminate it, hence I will only pull mail 
from servers.

> If you do, mention RFC 2017.

Good point. External-Body resembles "SMTP pull", except for 
implying that the content should be retrieved by the MUA.

RFC 2111's mid URLs could be used to retrieve a message sent by 
SMTP (or stored via IMAP) if access by Message-ID were provided.

In order to infringe the Tumbleweed patent, AFAICS, one 
additionally has to automate checking the log file, as an 
alternative to positive DSNs for the externally stored content.

From vesely@tana.it  Tue Aug 18 06:37:07 2009
Return-Path: <vesely@tana.it>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 499753A67A3 for <asrg@core3.amsl.com>; Tue, 18 Aug 2009 06:37:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.591
X-Spam-Level: 
X-Spam-Status: No, score=-3.591 tagged_above=-999 required=5 tests=[AWL=-0.361, BAYES_05=-1.11, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245,  RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SUiA2M+YZ7kb for <asrg@core3.amsl.com>; Tue, 18 Aug 2009 06:37:06 -0700 (PDT)
Received: from wmail.tana.it (wmail.tana.it [62.94.243.226]) by core3.amsl.com (Postfix) with ESMTP id 63D2D3A695F for <asrg@irtf.org>; Tue, 18 Aug 2009 06:37:06 -0700 (PDT)
Received: from [192.168.15.114] (wf-salyut.imt.ru [212.16.1.106]) (AUTH: CRAM-MD5 ale@tana.it, TLS: TLS1.0, 256bits, RSA_AES_256_CBC_SHA1) by wmail.tana.it with esmtp; Tue, 18 Aug 2009 15:36:50 +0200 id 00000000005DC031.000000004A8AAE72.00006B59
Message-ID: <4A8AAF44.5020604@tana.it>
Date: Tue, 18 Aug 2009 17:40:20 +0400
From: Alessandro Vesely <vesely@tana.it>
User-Agent: Thunderbird 2.0.0.22 (Windows/20090605)
MIME-Version: 1.0
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
References: <20090816222944.96264.qmail@simone.iecc.com> <4A898693.7030609@mtcc.com>
In-Reply-To: <4A898693.7030609@mtcc.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [Asrg] SMTP pull anyone?
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Aug 2009 13:37:07 -0000

Michael Thomas wrote:
> I can create a walled garden trivially with smtp just be rejecting 
> connections from people not on my whitelist. Likewise, anything that 
> is promiscuous with who it receives from better be prepared for 
> mail-transmitted diseases (MTD's). That's just the nature of opening 
> up. So SMTP itself isn't the problem, or more specifically fretting 
> about SMTP is nipping around the edges of 20 with the 80-20 rule.

I don't think "opening up" is bound to have a unique nature. A 
protocol might provide for ways to open up _and_ allow 
traceability, responsibility, and accountability. Such features 
are implicit in walled gardens. Explicating them requires a more 
thorough analysis of the relevant conventions and rules, at an 
abstraction level such that its outcome can be globally 
accepted. Much of the required "political" work is already 
available as privacy recommendations --later than SMTP. It is 
possible to tweak SMTP so as to comply with that. While that 
would not "eliminate spam", it would permit to manage it 
cleanly, properly, and without sacrificing reliability.

From dhc@dcrocker.net  Tue Aug 18 07:24:55 2009
Return-Path: <dhc@dcrocker.net>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E2BA23A6D90 for <asrg@core3.amsl.com>; Tue, 18 Aug 2009 07:24:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.733
X-Spam-Level: 
X-Spam-Status: No, score=-2.733 tagged_above=-999 required=5 tests=[AWL=-0.134, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VTGeNB5sIk1G for <asrg@core3.amsl.com>; Tue, 18 Aug 2009 07:24:55 -0700 (PDT)
Received: from sbh17.songbird.com (unknown [IPv6:2001:470:1:76:0:ffff:4834:7148]) by core3.amsl.com (Postfix) with ESMTP id 4920D3A69DB for <asrg@irtf.org>; Tue, 18 Aug 2009 07:24:28 -0700 (PDT)
Received: from [127.0.0.1] (ppp-68-120-198-98.dsl.pltn13.pacbell.net [68.120.198.98]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id n7IEOPHR011165 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <asrg@irtf.org>; Tue, 18 Aug 2009 07:24:31 -0700
Message-ID: <4A8AB999.1010103@dcrocker.net>
Date: Tue, 18 Aug 2009 07:24:25 -0700
From: Dave CROCKER <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Thunderbird 2.0.0.22 (Windows/20090605)
MIME-Version: 1.0
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
References: <20090818034736.4642.qmail@simone.iecc.com>
In-Reply-To: <20090818034736.4642.qmail@simone.iecc.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Tue, 18 Aug 2009 07:24:31 -0700 (PDT)
Subject: Re: [Asrg] SMTP pull anyone?
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: dcrocker@bbiw.net, Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Aug 2009 14:24:56 -0000

John Levine wrote:
> I agree.  The main advantage I see to pull is bandwidth management,
...
> The disadvantage is that it requires that senders and receivers all be
> connected to the same network all the time, 


The disadvantages are more substantial.  This is a very high overhead model, in 
terms of hassling the recipient and in terms of transactions costs.

d/

-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From asrg3@billmail.scconsult.com  Tue Aug 18 09:49:51 2009
Return-Path: <asrg3@billmail.scconsult.com>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C9A2D3A6AE0 for <asrg@core3.amsl.com>; Tue, 18 Aug 2009 09:49:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.827
X-Spam-Level: 
X-Spam-Status: No, score=-1.827 tagged_above=-999 required=5 tests=[AWL=0.457,  BAYES_00=-2.599, SARE_MILLIONSOF=0.315]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CaNaV0IIAziT for <asrg@core3.amsl.com>; Tue, 18 Aug 2009 09:49:44 -0700 (PDT)
Received: from toaster.scconsult.com (ns.scconsult.com [66.73.230.190]) by core3.amsl.com (Postfix) with ESMTP id 6D7A93A6BB2 for <asrg@irtf.org>; Tue, 18 Aug 2009 09:49:29 -0700 (PDT)
Received: from bigsky.scconsult.com (bigsky.scconsult.com [192.168.2.102]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by toaster.scconsult.com (Postfix) with ESMTP id 1453193E4EB for <asrg@irtf.org>; Tue, 18 Aug 2009 12:49:34 -0400 (EDT)
Message-ID: <4A8ADB9D.5080004@billmail.scconsult.com>
Date: Tue, 18 Aug 2009 12:49:33 -0400
From: Bill Cole <asrg3@billmail.scconsult.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1b3pre) Gecko/20090408 Eudora/3.0b2
MIME-Version: 1.0
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
References: <922a897b0908170253k60c0d57dh5e593c78f9137fab@mail.gmail.com>
In-Reply-To: <922a897b0908170253k60c0d57dh5e593c78f9137fab@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [Asrg] [ASRG] SMTP pull anyone?
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: asrg@irtf.org
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Aug 2009 16:49:51 -0000

Ravi shankar wrote, On 8/17/09 5:53 AM:
>
>
>  >DNS is used *as a medium* for various applications that are used to
> identify
>
>  >mail as legitimate or illegitimate by various standards of legitimacy,
> and a
>
>  >major reason for its use in those applications is to make it feasible for
>
>  >mail systems to do the validation synchronously during the SMTP
> session. By
>
>  >using a lightweight, distributed, cached database, mail systems are spared
>
>  >from deferring a message, queuing its validation, remembering the results,
>
>  >and waiting for the sender to offer it in an identical way again. You are
>
>  >suggesting that receivers should take on all the heavyweight
> management but
>
>  >retain using DNS for something unspecified. It makes no sense.
>
> Bill,
>
> Today's model is no different from what i have suggested in that they
> deploy costly anti-spam
>
> solutions, which utilise probably 10 fold resource than what this
> solution will use. By allowing the system to cut most of the spam
> through a simple pull mechanism, compares very well against today's
> anti-spam software model, which not all can afford.

I don't see how this reduces the effort required on the receiving side in 
comparison to currently common practices. I do see how it increases 
receiving system effort compared to currently common practices. I suspect 
that you don't understand those practices, so I'll explain at length...

It is very common for mail servers to apply multiple threshold criteria 
(often utilizing DNS) before the DATA command in a SMTP session to decide 
how to respond to the earlier commands, often making rejection decisions 
very early. SPF and the most common type of DNSBL can be checked that way 
and often are, along with rules like requiring the sender domain to have a 
valid MX or A record, shunning clients that use idiosyncratically invalid 
HELO names, etc. This does not require message data analysis, as it is done 
before the message data is offered. After receiving a RCPT command, the 
receiver knows the IP address of the sending client, the name it used for 
itself in the HELO or EHLO command, the envelope sender address, one or more 
recipient addresses, and the reject/accept results for any previously named 
recipients. In some cases where extensions to SMTP are used, it may also 
know some message and authentication metadata. It is quite normal for a mail 
server to use those facts and derivative facts (like the existence and 
content of DNS records related to them) to decide how to respond to that 
RCPT command.

For many mail systems, anti-spam measures done before the DATA command using 
metadata safely reject a large majority of spam (often a large majority of 
all email) and whitelist a smaller stream of messages. This sidesteps 
high-cost approaches that parse message data. For example, from the last 
10,000 connections to my own very small mail server, only 873 messages were 
passed to the part of my spam control system that examines the message data 
and 35 messages were cleared around that filtering. Obviously I can't get a 
perfect measurement for accuracy since I can't be sure that every error will 
be noticed and brought to my attention, but it has been many months and 
millions of messages since the last time I know that system to have rejected 
a legitimate message ahead of the data filters and it hasn't protected any 
spam from data filtering in the 5 years that I've been doing it. That 
performance is similar to what I've seen in the larger mail systems that 
I've managed for others.

The use of metadata rules (i.e. using envelope and session parameters and 
their derivatives) to reduce the flow of mail into message data filters is 
not a new or rare strategy, but rather is an evolutionary remnant of the 
earliest spam control tactics. For many years, spam exclusion was almost 
exclusively done before the DATA phase of SMTP because it worked well enough 
and because filtering based on message data was more resource-intensive than 
it could justify with results. To this day, well-run mail systems whose 
operators are concerned about the resource demands of spam control use the 
information available early in the SMTP transaction to decide whether to 
allow the sender to 'push' the message itself.

The 'pull' model you have described does not specify any way in which it can 
improve on the pre-data filtering that is already being done, but it does 
add a burden to both sides of legitimate transactions: keeping track of 
message offers that are pending a decision to pull and an actual pull 
attempt. In order to justify that added burden (in addition to the huge 
development and deployment costs) you would need to explain how your pull 
model facilitates better filtering than what sites do now. Sparing systems 
from message data filtering isn't enough, unless you have some case for your 
model doing that consistently and sustainably better than current tactics 
that operate during the SMTP session.


>  >The *most* that SPF can provide towards showing "legitimacy" is to confirm
>
>  >that the envelope sender address of a message is not forged. It is
> very rare
>
>  >for large senders of any sort to deploy records that can do that strongly.
>
>  >There is nothing about SPF that directly attacks spamming. It could in
>
>  >theory be used to attack sender forgery, but the collateral damage has
>
>  >proven to be too great for either sending or receiving systems to actually
>
>  >apply it strongly to that end. Meanwhile, a lot of spammers are sending a
>
>  >lot of spam with senders that are validated to the degree that SPF can
>
>  >validate anything.
>
> Actually SPF only validate the legitimacy of the sender IP and domain
> relation and i mentioned SPF as just a example.

SPF is specified as applying to the whole envelope sender. Explicit records 
using the %l macro are rare, but many domains assure that the hosts they 
affirm in SPF are using correct local parts in sender addresses. That is 
what would be expected with normal MTA software and configurations that 
could be affirmed in SPF.

> And if the large senders
> cannot implement something as simple as a TXT record for SPF (leave
> alone DKIM), then probably they do no care about spam.

I understand that it is easy and tempting to be dismissive about the lack of 
care among large senders, but it is self-defeating when trying to devise and 
evangelize a new spam control mechanism.

It is worth noting that Microsoft (as Hotmail) has been the most important 
actor in getting SPF records deployed by others, even though Hotmail systems 
are chronic spam sources and their inbound mail systems do not use SPF 
records in anything like a normal way.

 > SPF or DKIM are
> only effective when deployed by all the domains that send mails.

That is a ridiculously false statement. I have to assume that we are having 
a problem of differing idioms of English, or else I would think you a fool.


>  > 4. The sending server then hands over the message.
>
>  > 5. To overcome DDoS attacks, the receiving server can be made to request
>
>  > the next 10 or so Message IDs that it will assign to messages,
>
>  > so that if a attacker tries to give those details, it will know from the
>
>  > next list of message IDs that it's fake connection.
>
>  >>>That sentence makes no sense. What did you mean to say?
>

> What i mean is in order to prevent a system from getting overwhelmed, by
> anonymous submission, if for say domain1.com server knows the next 10
> message ID that will be sent by domain2.com, then it can confidently
> reject those message submission attempts that does not have any mails in
> this range (ofcourse this logic holds only if domain2.com is going to
> send those 10 message IDs domain1.com only)

Okay, so you are redefining "Message ID" as a new identifier defined by each 
MTA for each message that it handles, rather than as something related to 
the Message-ID mail header.

That concept is interesting, but it is not consistent with how mail systems 
work today. It brings into question whether you have a useful understanding 
of the range of ways that people use email and the range of ways that mail 
servers handle mail. The practices that would have to end in order to enable 
this facet of your idea include those which forced SPF into its arcane 
complexity and those which constrain its strength and deployability today.


>  >Nothing you have described would add to spam control as it is currently
>
>  >being done, as far as I can see. The 'model' is too vague to critique inn
>
>  >detail because you aren't really providing any meaningful details.
>
>  >In order to bring anything truly new and useful to controlling email
> spam, a
>
>  >new idea has to either attack spam in a way that existing tactics
> don't, do
>
>  >a demonstrably better job than existing tactics, or overcome the negative
>
>  >aspects of existing tactics. You have identified none of those in your new
>
>  >idea.
>
> I guess we are expecting a magic solution that will stop all the spam in
> a single go and would not require us from changing our system
> continuosly.

Not at all, and that is part of why I am skeptical about your suggestion. It 
would be a radically new way of handling email, to a degree that it would 
not really make sense to define it as an extension to SMTP.

> But unfortunately, every system has flaws and has to be
> corrected one step at a time, this i believe is the evolution.

Gradual evolutionary steps have to provide a real hope of some incremental 
benefit to early adopters without doing them immediate harm. Even if you had 
a fully detailed model for how this would work and had a deployable way to 
integrate it today into existing mail systems, you would need to assure that 
it would be harmless to offer now (i.e. no rejection of legitimate mail from 
non-users of the new system) and that it could provide some benefit for both 
senders and receivers who adopt it before it becomes widely deployed. As 
described, it increases the difficulty of handling mail for both sides and 
offers neither side any concrete benefits.


> I have done my best to detail how this system applies in various steps
> of a mail communication, may be i can work on a pictorial
> representation, if someone else requires it as well.

If this is what you consider "detail" then you have a major obstacle to 
being taken seriously. Drawing pictures wouldn't be a step forward. Defining 
a transaction protocol would be, but I wouldn't suggest you do that until 
you identify concrete ways that your model offers benefits that existing 
common practices cannot offer.

From schaefer@closedmail.com  Tue Aug 18 10:04:38 2009
Return-Path: <schaefer@closedmail.com>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B2BFF3A6B3A for <asrg@core3.amsl.com>; Tue, 18 Aug 2009 10:04:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.11
X-Spam-Level: 
X-Spam-Status: No, score=-1.11 tagged_above=-999 required=5 tests=[BAYES_05=-1.11]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EUWorfKFa33D for <asrg@core3.amsl.com>; Tue, 18 Aug 2009 10:04:38 -0700 (PDT)
Received: from vms173003pub.verizon.net (vms173003pub.verizon.net [206.46.173.3]) by core3.amsl.com (Postfix) with ESMTP id 7C17828C2E2 for <asrg@irtf.org>; Tue, 18 Aug 2009 10:03:59 -0700 (PDT)
Received: from torch.brasslantern.com ([96.238.220.32]) by vms173003.mailsrvcs.net (Sun Java(tm) System Messaging Server 6.3-7.04 (built Sep 26 2008; 32bit)) with ESMTPA id <0KOK00LN1BMP9YO5@vms173003.mailsrvcs.net> for asrg@irtf.org; Tue, 18 Aug 2009 03:01:42 -0500 (CDT)
Received: from torch.brasslantern.com (localhost.localdomain [127.0.0.1]) by torch.brasslantern.com (8.13.1/8.13.1) with ESMTP id n7I81aq8029372	for <asrg@irtf.org>; Tue, 18 Aug 2009 01:01:36 -0700
Received: (from schaefer@localhost)	by torch.brasslantern.com (8.13.1/8.13.1/Submit) id n7I81aLB029371	for asrg@irtf.org; Tue, 18 Aug 2009 01:01:36 -0700
From: Bart Schaefer <schaefer@brasslantern.com>
Message-id: <090818010136.ZM29370@torch.brasslantern.com>
Date: Tue, 18 Aug 2009 01:01:36 -0700
In-reply-to: <20090818034736.4642.qmail@simone.iecc.com>
Comments: In reply to John Levine <johnl@taugh.com> "Re: [Asrg] SMTP pull anyone?" (Aug 18,  3:47am)
References: <20090818034736.4642.qmail@simone.iecc.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] SMTP pull anyone?
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Aug 2009 17:04:38 -0000

On Aug 18,  3:47am, John Levine wrote:
>
> The disadvantage is that it requires that senders and receivers all
> be connected to the same network all the time, which is a lot closer
> to true now than it was in the 1980s, but still a long way from
> universally true.

I'm not a proponent of the pull model, but it seems to me this could
be overcome if each receiver in a store-and-forward sequence were
able to inform its immediate upstream when it is not able to perform
the pull.

E.g., transmit the "pull handle" as far as possible, then have the
last relay that is capable of doing so, issue the pull request.

This could probably even be done with one new SMTP verb plus ETRN.
E.g. DATA FROM:<message-id> where the domain part of the message-id
must resolve to the host that will cough up the message.  If the
receiver responds 50z or 455, the sender must do the pull.  If the
receiver responds 354, sender sends dot, and eventually some receiver
connects to <message-id-domain> and issues ETRN #<message-id-local>.

All sorts of security implications to be worked out, Tumbleweed
problems aside.

From dotis@mail-abuse.org  Tue Aug 18 10:10:22 2009
Return-Path: <dotis@mail-abuse.org>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 15BE228C2ED for <asrg@core3.amsl.com>; Tue, 18 Aug 2009 10:10:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.604
X-Spam-Level: 
X-Spam-Status: No, score=-5.604 tagged_above=-999 required=5 tests=[AWL=0.995,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ky2BsZUH8x14 for <asrg@core3.amsl.com>; Tue, 18 Aug 2009 10:10:20 -0700 (PDT)
Received: from harry.mail-abuse.org (harry.mail-abuse.org [168.61.5.27]) by core3.amsl.com (Postfix) with ESMTP id 9F86028C26F for <asrg@irtf.org>; Tue, 18 Aug 2009 10:10:20 -0700 (PDT)
Received: from SJC-Office-NAT-214.mail-abuse.org (gateway1.sjc.mail-abuse.org [168.61.5.81]) by harry.mail-abuse.org (Postfix) with ESMTP id 52708A9443E for <asrg@irtf.org>; Tue, 18 Aug 2009 17:10:23 +0000 (UTC)
Message-ID: <4A8AE07F.3010305@mail-abuse.org>
Date: Tue, 18 Aug 2009 10:10:23 -0700
From: Douglas Otis <dotis@mail-abuse.org>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1.1) Gecko/20090715 Thunderbird/3.0b3
MIME-Version: 1.0
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
References: <20090818033801.4352.qmail@simone.iecc.com> <D30442DC-16E5-4827-864F-502FFF590BE4@blighty.com>
In-Reply-To: <D30442DC-16E5-4827-864F-502FFF590BE4@blighty.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [Asrg] [ASRG] SMTP pull anyone?
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Aug 2009 17:10:22 -0000

On 8/17/09 8:43 PM, Steve Atkins wrote:
>
> On Aug 17, 2009, at 8:38 PM, John Levine wrote:
>
>>> The model is like a simple C/R involving Message ID of a mail.
>>> The sending domain provides the Message ID and allows
>>> computational time for the receiving domain and then query the
>>> sending domain to send the message.
>>
>> This model has been proposed many, many, times before. I suppose we
>> should make a page for it in the ASRG wiki of anti-spam techniques
>> even though it's more of a mail system redesign than an anti-spam
>> measure.
>
> If you do, mention RFC 2017.

Good point since this RFC was adopted in October 1996 and patent 
5,790,790 was filed October 24, 1996 by Jeffry C. Smith of Menlo Park, 
and Jean-Christophe Bandini, of Cupertino. But patent 6,192,407 
describes "private URLS" or PURLS and was filed April 1997.


XAM offers an 80 byte reference that can be made "public" while still 
offer security that does not involve the moving parts found in the '97 
patent.

-Doug

From CLEWIS@nortel.com  Tue Aug 18 10:17:39 2009
Return-Path: <CLEWIS@nortel.com>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D263928C31B for <asrg@core3.amsl.com>; Tue, 18 Aug 2009 10:17:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.11
X-Spam-Level: 
X-Spam-Status: No, score=-5.11 tagged_above=-999 required=5 tests=[BAYES_05=-1.11, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qJjLqnf9nqzR for <asrg@core3.amsl.com>; Tue, 18 Aug 2009 10:17:39 -0700 (PDT)
Received: from zcars04e.nortel.com (zcars04e.nortel.com [47.129.242.56]) by core3.amsl.com (Postfix) with ESMTP id DDB933A6B5A for <asrg@irtf.org>; Tue, 18 Aug 2009 10:17:38 -0700 (PDT)
Received: from zrtphxs1.corp.nortel.com (zrtphxs1.corp.nortel.com [47.140.202.46]) by zcars04e.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id n7IHFWQ05065 for <asrg@irtf.org>; Tue, 18 Aug 2009 17:15:33 GMT
Received: from zrtphx5h0.corp.nortel.com ([47.140.202.65]) by zrtphxs1.corp.nortel.com with Microsoft SMTPSVC(6.0.3790.3959);  Tue, 18 Aug 2009 13:17:33 -0400
Received: from [47.9.16.79] (47.9.16.79) by zrtphx5h0.corp.nortel.com (47.140.202.65) with Microsoft SMTP Server (TLS) id 8.1.340.0; Tue, 18 Aug 2009 13:17:32 -0400
Message-ID: <4A8AE22C.7030300@nortel.com>
Date: Tue, 18 Aug 2009 11:17:32 -0600
From: "Chris Lewis" <clewis@nortel.com>
Organization: Nortel
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.22) Gecko/20090605 Lightning/0.9 Thunderbird/2.0.0.22 Mnenhy/0.7.6.666
MIME-Version: 1.0
To: "asrg@irtf.org" <asrg@irtf.org>
References: <922a897b0908170253k60c0d57dh5e593c78f9137fab@mail.gmail.com> <4A8ADB9D.5080004@billmail.scconsult.com>
In-Reply-To: <4A8ADB9D.5080004@billmail.scconsult.com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 18 Aug 2009 17:17:33.0889 (UTC) FILETIME=[C6759B10:01CA2027]
Subject: Re: [Asrg] [ASRG] SMTP pull anyone?
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Aug 2009 17:17:39 -0000

Bill Cole wrote:

> I don't see how this reduces the effort required on the receiving side in
> comparison to currently common practices.

Precisely - in fact, it increases the work the receiver has to do, 
probably substantially.

Consider: the offer/callback approach is identical to SMTP up to the 
DATA keyword.

The "offer" would have to have more-or-less the same information as the 
pre-DATA SMTP information in normal SMTP.  A SMTP server can just as 
easily reject on that data pre-DATA, as to "choose not to do" the call 
back.  So, up to this point, the offer/callback approach doesn't do any 
less work than normal SMTP.

Then offer/callback actually has to call back and retrieve the message. 
  You also have to build in mechanisms to make sure that someone _else_ 
isn't doing the retrieval.

Then, if you do any DATA filtering, _both_ approaches have to do similar 
levels of work.

In other words, the offer/callback approach only causes you to expend 
more work actually implementing the callback _itself_, plus checking it 
for validity.

From dhc@dcrocker.net  Tue Aug 18 11:00:39 2009
Return-Path: <dhc@dcrocker.net>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E43A63A6B7B for <asrg@core3.amsl.com>; Tue, 18 Aug 2009 11:00:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.719
X-Spam-Level: 
X-Spam-Status: No, score=-2.719 tagged_above=-999 required=5 tests=[AWL=-0.120, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BuudKgxU-q9G for <asrg@core3.amsl.com>; Tue, 18 Aug 2009 11:00:39 -0700 (PDT)
Received: from sbh17.songbird.com (unknown [IPv6:2001:470:1:76:0:ffff:4834:7148]) by core3.amsl.com (Postfix) with ESMTP id 90E893A697D for <asrg@irtf.org>; Tue, 18 Aug 2009 11:00:38 -0700 (PDT)
Received: from [127.0.0.1] (ppp-68-120-198-98.dsl.pltn13.pacbell.net [68.120.198.98]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id n7II0aBQ020596 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <asrg@irtf.org>; Tue, 18 Aug 2009 11:00:42 -0700
Message-ID: <4A8AEC44.6010706@dcrocker.net>
Date: Tue, 18 Aug 2009 11:00:36 -0700
From: Dave CROCKER <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Thunderbird 2.0.0.22 (Windows/20090605)
MIME-Version: 1.0
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
References: <922a897b0908170253k60c0d57dh5e593c78f9137fab@mail.gmail.com>	<4A8ADB9D.5080004@billmail.scconsult.com> <4A8AE22C.7030300@nortel.com>
In-Reply-To: <4A8AE22C.7030300@nortel.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Tue, 18 Aug 2009 11:00:42 -0700 (PDT)
Subject: Re: [Asrg] [ASRG] SMTP pull anyone?
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: dcrocker@bbiw.net, Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Aug 2009 18:00:40 -0000

Chris Lewis wrote:
> Bill Cole wrote:
> 
>> I don't see how this reduces the effort required on the receiving side in
>> comparison to currently common practices.
> 
> Precisely - in fact, it increases the work the receiver has to do, 
> probably substantially.


+1.

When discussing different protocol models, folks should be required to explain a 
collection of relatively obvious cost/benefit differences, such as:

1. Latency/Delay

2. Transaction (Round-trip) exchange count

3. Robustness/fragility

4. Administration

5. Privacy

6. Authenticity/Spoofing

...


For the SMTP push model (and ignoring the possible pull last-hop):

1. Low latency
2. A bit too chatty, but pipelining largely fixed this
3. History demonstrates high robustness
4. Low administration (only DNS MX)
5. Privacy is theoretically non-existent
6. Authenticity is demonstrably horrible

d/

d/
-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From dotis@mail-abuse.org  Tue Aug 18 13:45:56 2009
Return-Path: <dotis@mail-abuse.org>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B2FD628C356 for <asrg@core3.amsl.com>; Tue, 18 Aug 2009 13:45:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.675
X-Spam-Level: 
X-Spam-Status: No, score=-5.675 tagged_above=-999 required=5 tests=[AWL=0.924,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2VB-MJDFo9BU for <asrg@core3.amsl.com>; Tue, 18 Aug 2009 13:45:56 -0700 (PDT)
Received: from harry.mail-abuse.org (harry.mail-abuse.org [168.61.5.27]) by core3.amsl.com (Postfix) with ESMTP id 5FDA128C36C for <asrg@irtf.org>; Tue, 18 Aug 2009 13:45:55 -0700 (PDT)
Received: from SJC-Office-NAT-214.mail-abuse.org (gateway1.sjc.mail-abuse.org [168.61.5.81]) by harry.mail-abuse.org (Postfix) with ESMTP id 6C8E8A9443A for <asrg@irtf.org>; Tue, 18 Aug 2009 20:45:46 +0000 (UTC)
Message-ID: <4A8B12FA.6090203@mail-abuse.org>
Date: Tue, 18 Aug 2009 13:45:46 -0700
From: Douglas Otis <dotis@mail-abuse.org>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1.1) Gecko/20090715 Thunderbird/3.0b3
MIME-Version: 1.0
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
References: <922a897b0908170253k60c0d57dh5e593c78f9137fab@mail.gmail.com>	<4A8ADB9D.5080004@billmail.scconsult.com> <4A8AE22C.7030300@nortel.com>
In-Reply-To: <4A8AE22C.7030300@nortel.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [Asrg] [ASRG] SMTP pull anyone?
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Aug 2009 20:45:56 -0000

On 8/18/09 10:17 AM, Chris Lewis wrote:
> Bill Cole wrote:
>
>> I don't see how this reduces the effort required on the receiving side in
>> comparison to currently common practices.
>
> Precisely - in fact, it increases the work the receiver has to do,
> probably substantially.

As accepted IP addresses are reduced, there will be increased abuse of 
existing services, that were likely exposed through information gleaned 
from compromised computers.  This will eventually move the problem to 
the point where the IP address of the client offers fewer clues about a 
message source.  Without some simply means to identify undesired 
messages, the sheer volume of undesired email will provide a growing 
burden.  Especially when content filtering must be deployed.  It is hard 
to imagine a more resource intensive strategy.

> Consider: the offer/callback approach is identical to SMTP up to the
> DATA keyword.

Not if MUA or specialized MDAs gather the messages marked as desired. A 
selection based upon the offers should reduce the overhead considerably.

> The "offer" would have to have more-or-less the same information as the
> pre-DATA SMTP information in normal SMTP.

No. Unlike that of an SMTP exchange, when reference information is not 
valid, the reference does not work.  This removes the validation steps.

-Doug

From CLEWIS@nortel.com  Tue Aug 18 23:53:20 2009
Return-Path: <CLEWIS@nortel.com>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B4EDC3A6C3C for <asrg@core3.amsl.com>; Tue, 18 Aug 2009 23:53:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.854
X-Spam-Level: 
X-Spam-Status: No, score=-5.854 tagged_above=-999 required=5 tests=[AWL=0.744,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oTblPh2lkjTk for <asrg@core3.amsl.com>; Tue, 18 Aug 2009 23:53:20 -0700 (PDT)
Received: from zrtps0kp.nortel.com (zrtps0kp.nortel.com [47.140.192.56]) by core3.amsl.com (Postfix) with ESMTP id BAAE33A6BB9 for <asrg@irtf.org>; Tue, 18 Aug 2009 23:53:19 -0700 (PDT)
Received: from zrtphxs1.corp.nortel.com (casmtp.ca.nortel.com [47.140.202.46]) by zrtps0kp.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id n7J6G8123953 for <asrg@irtf.org>; Wed, 19 Aug 2009 06:16:08 GMT
Received: from zrtphx5h0.corp.nortel.com ([47.140.202.65]) by zrtphxs1.corp.nortel.com with Microsoft SMTPSVC(6.0.3790.3959);  Wed, 19 Aug 2009 02:16:07 -0400
Received: from [47.9.16.27] (47.9.16.27) by zrtphx5h0.corp.nortel.com (47.140.202.65) with Microsoft SMTP Server (TLS) id 8.1.340.0; Wed, 19 Aug 2009 02:16:06 -0400
Message-ID: <4A8B98A5.5020506@nortel.com>
Date: Wed, 19 Aug 2009 00:16:05 -0600
From: "Chris Lewis" <clewis@nortel.com>
Organization: Nortel
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.22) Gecko/20090605 Lightning/0.9 Thunderbird/2.0.0.22 Mnenhy/0.7.6.666
MIME-Version: 1.0
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
References: <922a897b0908170253k60c0d57dh5e593c78f9137fab@mail.gmail.com>	<4A8ADB9D.5080004@billmail.scconsult.com>	<4A8AE22C.7030300@nortel.com> <4A8B12FA.6090203@mail-abuse.org>
In-Reply-To: <4A8B12FA.6090203@mail-abuse.org>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 19 Aug 2009 06:16:07.0268 (UTC) FILETIME=[89CD9240:01CA2094]
Subject: Re: [Asrg] [ASRG] SMTP pull anyone?
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Aug 2009 06:53:20 -0000

Douglas Otis wrote:
> On 8/18/09 10:17 AM, Chris Lewis wrote:
>> Bill Cole wrote:
>>
>>> I don't see how this reduces the effort required on the receiving side in
>>> comparison to currently common practices.
>> Precisely - in fact, it increases the work the receiver has to do,
>> probably substantially.

>> Consider: the offer/callback approach is identical to SMTP up to the
>> DATA keyword.

> Not if MUA or specialized MDAs gather the messages marked as desired. A 
> selection based upon the offers should reduce the overhead considerably.

This does not provide any new mechanisms for deciding what is, in fact, 
wanted.

Step back.  The "hard part" of this proposal is deciding what email is 
desired.  The proposal makes no suggestions on something "new" that 
could be used to do this.  As it stands, it's simply a more convoluted 
and expensive version of SMTP.

What does "pull" provide that existing "push" does not in terms of 
improved filtering?  Until and unless you can answer that, it's moot.

Does it provide a innovative way of deciding what email is desired?  No.

That you don't transfer the DATA if the email is undesired?  Given that 
the vast majority of spam is well under 10K in size, this pales in 
comparison to the complexity and network loading of actually performing 
the pull.

Certainly, you can extend the push to include additional stuff.  Like 
DKIM or something different.  But that's just as easily done/possible in 
push, and already is.

Letting the MUA fill up with offers, and forcing the user to to decide 
what's wanted has the same problems as junk folders.  The legit email 
gets lost in the noise.

In fact, junk folders are "pull".  How well do they work?  Not well.

From macfisherman@gmail.com  Wed Aug 26 09:09:22 2009
Return-Path: <macfisherman@gmail.com>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 07E6E3A70A0 for <asrg@core3.amsl.com>; Wed, 26 Aug 2009 09:09:22 -0700 (PDT)
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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PFRnKg5qY4mm for <asrg@core3.amsl.com>; Wed, 26 Aug 2009 09:09:21 -0700 (PDT)
Received: from mail-ew0-f206.google.com (mail-ew0-f206.google.com [209.85.219.206]) by core3.amsl.com (Postfix) with ESMTP id E264128C2D7 for <asrg@irtf.org>; Wed, 26 Aug 2009 09:09:20 -0700 (PDT)
Received: by ewy2 with SMTP id 2so311637ewy.17 for <asrg@irtf.org>; Wed, 26 Aug 2009 09:09:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=S7LlVaAduFMAFHe4G0wwLoRKKRTrGZBHZlBjRyJanjY=; b=kHqgkWwqoZcd0JzgmOfrSSptlcQh/hXPo8cOB00ALnT/OjA3RyiqPXwQUSZRq38jhb QXaoMbZma6JYCKGgBjCNFS60obpnsVSJkx2gTdas6id6J15EyBHJ49GZLv3/FGMlGKUB xolP+fO3V6mjqjqPv9628rdVrg0LmWXnbxRuc=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=HUct62jjCzBKiGrPIXMdhBDEBkui6pI8ekW5Yc5j5JUW0kbiC76sauOHQXuV+bJB7F sJgBuQp9CEBnqrQaJ/GzaashJgqhkHGJrN276+EmSATQmdBpSIX2EFov5PgnFlafWZNF Zk0q8YfoJzgiw2RgstzQ2KYsWyGvB9KpqXNXw=
MIME-Version: 1.0
Received: by 10.210.27.20 with SMTP id a20mr4128501eba.28.1251302818783; Wed,  26 Aug 2009 09:06:58 -0700 (PDT)
In-Reply-To: <20090818020952.GA30677@gsp.org>
References: <922a897b0908170253k60c0d57dh5e593c78f9137fab@mail.gmail.com> <20090817144450.GA22048@gsp.org> <4A898440.6080006@mail-abuse.org> <20090818020952.GA30677@gsp.org>
Date: Wed, 26 Aug 2009 12:06:58 -0400
Message-ID: <45ae90370908260906t223ea020g1e964670fad7ef0d@mail.gmail.com>
From: Jeff Macdonald <macfisherman@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] [ASRG] SMTP pull anyone?
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Aug 2009 16:09:22 -0000

On Mon, Aug 17, 2009 at 10:09 PM, Rich Kulawiec<rsk@gsp.org> wrote:
> On Mon, Aug 17, 2009 at 09:24:32AM -0700, Douglas Otis wrote:
>> Could you provide a brief outline regarding what constitutes an
>> efficient anti-spam solution?
>
> Sure. =A0In brief (really brief!) and in (rough) order of application
> =A0 =A0 =A0 =A0and increasing resource cost:

<snip very detailed list>

Rich, does ipv6 change any of this?


--=20
Jeff Macdonald
Ayer, MA

From johnl@iecc.com  Wed Aug 26 11:06:00 2009
Return-Path: <johnl@iecc.com>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4FCDD3A6CB5 for <asrg@core3.amsl.com>; Wed, 26 Aug 2009 11:06:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -18.028
X-Spam-Level: 
X-Spam-Status: No, score=-18.028 tagged_above=-999 required=5 tests=[AWL=-0.688, BAYES_20=-0.74, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id y9rqSpAfoCoc for <asrg@core3.amsl.com>; Wed, 26 Aug 2009 11:05:59 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [208.31.42.53]) by core3.amsl.com (Postfix) with ESMTP id 255C03A6AA6 for <asrg@irtf.org>; Wed, 26 Aug 2009 11:05:59 -0700 (PDT)
Received: (qmail 49772 invoked from network); 26 Aug 2009 18:06:02 -0000
Received: from mail1.iecc.com (208.31.42.56) by mail1.iecc.com with QMQP; 26 Aug 2009 18:06:02 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:in-reply-to:cc:mime-version:content-type:content-transfer-encoding; s=k0908; olt=johnl@user.iecc.com; bh=BMEIuRuB+nSKmOhTSqb7Mm0MoGdd7ha9GDj408TecYY=; b=nuSEWlMrFTHUOYhvEz7BFj7+MXW4Q31HReio1ngSa5vHmat378U01KWbURma6Gik+2C/3lwepxCwz99ZDvbdQ/JbGX+59sGTnlRbLA2a+pv+C7JyPz2UfGbzmuUViDGAB1UAVCkDWATjVHUeHXZQgfi0nWehL644tNOGtWg18+U=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:subject:in-reply-to:cc:mime-version:content-type:content-transfer-encoding; s=k0908; bh=BMEIuRuB+nSKmOhTSqb7Mm0MoGdd7ha9GDj408TecYY=; b=KfBo3StTP2MPNHuHSaTMQfHBxwFArlgROLL/RAVrVQu9toYUA4+/yI58tBjMDqS4bMASGudhHjkpoTN+HNR9fQtZ6Y3xZWwKYH70mldZTRBWSVtiBdDz/wbJdTsQN6W6/KR46a5zNXhonjpcWxgVGJ3s6xd3jnhtM2wm+qXa0xM=
Date: 26 Aug 2009 18:06:01 -0000
Message-ID: <20090826180601.79333.qmail@simone.iecc.com>
From: John Levine <johnl@taugh.com>
To: asrg@irtf.org
In-Reply-To: <45ae90370908260906t223ea020g1e964670fad7ef0d@mail.gmail.com>
Organization: 
Cc: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7bit
Subject: Re: [Asrg] [ASRG] SMTP pull anyone?
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Aug 2009 18:06:00 -0000

>Rich, does ipv6 change any of this?

I'm not Rich, but the open question at this point is how effective
DNSBLs will be on IPv6.

A DNSBL that blocks a single IP at a time, like the CBL and XBL, would
be unworkable.  A typical v6 setup allocates a /64 to each host which
allows various sorts of clever self-configuration, but also means the
host can easily use a different IP address for every connection it
ever makes. (At one address per millisecond, it would take 500 million
years to run through a /64.)  DNSBLs can and do list ranges, and an
obvious change would be to make the finest listed granularity be a
/64, but we really have no idea how the vast number of v6 addresses
will be handed out, and whether it will be practical to create
listings that cover all of the available addresses for a particular
host without also listing a lot of its neighbors.

This suggests that whitelisting techniques (most likely based on DKIM)
will become much more important to recognize mail from people you know
are credible.

R's,
John

From dotis@mail-abuse.org  Wed Aug 26 12:30:33 2009
Return-Path: <dotis@mail-abuse.org>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CF74D3A6C57 for <asrg@core3.amsl.com>; Wed, 26 Aug 2009 12:30:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.674
X-Spam-Level: 
X-Spam-Status: No, score=-5.674 tagged_above=-999 required=5 tests=[AWL=0.925,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id l4JECs8iFK9w for <asrg@core3.amsl.com>; Wed, 26 Aug 2009 12:30:33 -0700 (PDT)
Received: from harry.mail-abuse.org (harry.mail-abuse.org [168.61.5.27]) by core3.amsl.com (Postfix) with ESMTP id 3C43D3A6AD9 for <asrg@irtf.org>; Wed, 26 Aug 2009 12:30:33 -0700 (PDT)
Received: from SJC-Office-NAT-214.mail-abuse.org (gateway1.sjc.mail-abuse.org [168.61.5.81]) by harry.mail-abuse.org (Postfix) with ESMTP id C28EDA94447 for <asrg@irtf.org>; Wed, 26 Aug 2009 19:29:54 +0000 (UTC)
Message-ID: <4A958D32.20808@mail-abuse.org>
Date: Wed, 26 Aug 2009 12:29:54 -0700
From: Douglas Otis <dotis@mail-abuse.org>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1.1) Gecko/20090715 Thunderbird/3.0b3
MIME-Version: 1.0
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
References: <20090826180601.79333.qmail@simone.iecc.com>
In-Reply-To: <20090826180601.79333.qmail@simone.iecc.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [Asrg] [ASRG] SMTP pull anyone?
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Aug 2009 19:30:33 -0000

On 8/26/09 11:06 AM, John Levine wrote:
>> Rich, does ipv6 change any of this?
[]
> This suggests that whitelisting techniques (most likely based on DKIM)
> will become much more important to recognize mail from people you know
> are credible.

Agreed. The transition will be from blocking bad, to accepting known 
good.  One might expect efforts being made to vet new domains or IP 
addresses.

-Doug

From feenberg@nber.org  Wed Aug 26 14:30:22 2009
Return-Path: <feenberg@nber.org>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4BC5B3A6CF5 for <asrg@core3.amsl.com>; Wed, 26 Aug 2009 14:30:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IJN72226zdA0 for <asrg@core3.amsl.com>; Wed, 26 Aug 2009 14:30:21 -0700 (PDT)
Received: from mail2.nber.org (mail2.nber.org [66.251.72.79]) by core3.amsl.com (Postfix) with ESMTP id 40A273A672F for <asrg@irtf.org>; Wed, 26 Aug 2009 14:30:20 -0700 (PDT)
Received: from nber5.nber.org (nber5.nber.org [66.251.72.75]) by mail2.nber.org (8.14.1/8.13.8) with ESMTP id n7QLUPBu065727 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT) for <asrg@irtf.org>; Wed, 26 Aug 2009 17:30:26 -0400 (EDT) (envelope-from feenberg@nber.org)
Received: from nber5.nber.org (localhost [127.0.0.1]) by nber5.nber.org (8.13.8+Sun/8.13.8) with ESMTP id n7QLMchZ020981; Wed, 26 Aug 2009 17:22:38 -0400 (EDT)
Received: from localhost (Unknown UID 1079@localhost) by nber5.nber.org (8.13.8+Sun/8.13.8/Submit) with ESMTP id n7QLMaon020978; Wed, 26 Aug 2009 17:22:38 -0400 (EDT)
X-Authentication-Warning: nber5.nber.org: Unknown UID 1079 owned process doing -bs
Date: Wed, 26 Aug 2009 17:22:35 -0400 (EDT)
From: Daniel Feenberg <feenberg@nber.org>
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
In-Reply-To: <20090826180601.79333.qmail@simone.iecc.com>
Message-ID: <Pine.GSO.4.64.0908261605410.13418@nber5.nber.org>
References: <20090826180601.79333.qmail@simone.iecc.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Anti-Virus: Kaspersky Anti-Virus for Sendmail with Milter API 5.6.20, bases: 20090826 #2444719, check: 20090826 clean
Subject: Re: [Asrg] [ASRG] SMTP pull anyone?
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Aug 2009 21:30:22 -0000

On Wed, 26 Aug 2009, John Levine wrote:

>> Rich, does ipv6 change any of this?
>
> I'm not Rich, but the open question at this point is how effective
> DNSBLs will be on IPv6.

I think it unlikely that an IPv6 only MTA will ever have acceptance even 
as wide as, for instance, MTAs with "pool" or "dial-up" in their RDNS. 
IPv6 only MTAs will be refused by many MTAs. There are simply too many 
IPv6 addresses to blacklist bad hats, and blacklisting /48s would be a 
very broad brush. The advantage of IPv4 is that the number of addresses is 
finite, and legitimate holders of addresses are loath to waste them.

I understand that many IPv6 capable MTAs exist, but I expect they do all 
or nearly all of their external traffic via IPv4. I don't mean a general 
condemdantion of IPv6, I am only saying that SMTP traffic from strangers 
on IPv6 is not likely to be worthwhile.

Daniel Feenberg


>
> A DNSBL that blocks a single IP at a time, like the CBL and XBL, would
> be unworkable.  A typical v6 setup allocates a /64 to each host which
> allows various sorts of clever self-configuration, but also means the
> host can easily use a different IP address for every connection it
> ever makes. (At one address per millisecond, it would take 500 million
> years to run through a /64.)  DNSBLs can and do list ranges, and an
> obvious change would be to make the finest listed granularity be a
> /64, but we really have no idea how the vast number of v6 addresses
> will be handed out, and whether it will be practical to create
> listings that cover all of the available addresses for a particular
> host without also listing a lot of its neighbors.
>
> This suggests that whitelisting techniques (most likely based on DKIM)
> will become much more important to recognize mail from people you know
> are credible.
>
> R's,
> John
> _______________________________________________
> Asrg mailing list
> Asrg@irtf.org
> http://www.irtf.org/mailman/listinfo/asrg
>

From graeme@graemef.net  Wed Aug 26 15:17:19 2009
Return-Path: <graeme@graemef.net>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 810833A70E7 for <asrg@core3.amsl.com>; Wed, 26 Aug 2009 15:17:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.001
X-Spam-Level: 
X-Spam-Status: No, score=0.001 tagged_above=-999 required=5 tests=[BAYES_50=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ToXyU8nt2nfr for <asrg@core3.amsl.com>; Wed, 26 Aug 2009 15:17:18 -0700 (PDT)
Received: from boom.graemef.net (boom.graemef.net [82.113.154.29]) by core3.amsl.com (Postfix) with ESMTP id A86703A67A6 for <asrg@irtf.org>; Wed, 26 Aug 2009 15:17:18 -0700 (PDT)
Received: from cpc1-shep3-0-0-cust909.lei3.cable.ntl.com ([82.5.39.142]) by boom.graemef.net with esmtpa (Exim 4.69) (envelope-from <graeme@graemef.net>) id 1MgQny-0000Ss-PR for asrg@irtf.org; Wed, 26 Aug 2009 23:17:23 +0100
From: Graeme Fowler <graeme@graemef.net>
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
In-Reply-To: <Pine.GSO.4.64.0908261605410.13418@nber5.nber.org>
References: <20090826180601.79333.qmail@simone.iecc.com> <Pine.GSO.4.64.0908261605410.13418@nber5.nber.org>
Content-Type: text/plain
Date: Wed, 26 Aug 2009 23:17:19 +0100
Message-Id: <1251325039.6778.46.camel@ernie.internal.graemef.net>
Mime-Version: 1.0
X-Mailer: Evolution 2.24.5 (2.24.5-2.fc10) 
Content-Transfer-Encoding: 7bit
Subject: Re: [Asrg] [ASRG] SMTP pull anyone?
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Aug 2009 22:17:19 -0000

Apologies if this comes over in an inflammatory or tediously weak way,
but...

On Wed, 2009-08-26 at 17:22 -0400, Daniel Feenberg wrote:
> I understand that many IPv6 capable MTAs exist, but I expect they do all 
> or nearly all of their external traffic via IPv4. I don't mean a general 
> condemdantion of IPv6, I am only saying that SMTP traffic from strangers 
> on IPv6 is not likely to be worthwhile.

This is different from IPv4 SMTP traffic from strangers how, exactly?
The vast majority of previously unseen connections handled by MTAs under
my direct control right now using v4 only are "not likely to be
worthwhile". The fact that there are several powers of 2 (well, many)
more hosts in the v6 world makes no difference apart from a scaling
factor.

Imagine if I ran a hypothetical organisation which used network
intelligence gathered from previous SMTP sessions to determine how to
handle a connection from a previously unseen host - it wouldn't matter a
jot if those connections came from a v4 or a v6 host. The only common
factor is that they were previously unseen (ie a "stranger").

Well run organisations will fix the address (as they do now) of their
outbound MTAs, and therefore allow intelligence to build up over time
about their usage and "goodness quotient". If anyone's crazy enough to
float the outbound IP around, even inside a v4 /24, then they should
expect their reputation to stay on the side of "low". If they do it
inside a v6 /64, they're really crazy.

Graeme


From rsk@gsp.org  Wed Aug 26 15:21:11 2009
Return-Path: <rsk@gsp.org>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0E8453A6AB3 for <asrg@core3.amsl.com>; Wed, 26 Aug 2009 15:21:11 -0700 (PDT)
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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CO+FeINI+7qt for <asrg@core3.amsl.com>; Wed, 26 Aug 2009 15:21:06 -0700 (PDT)
Received: from taos.firemountain.net (taos.firemountain.net [207.114.3.54]) by core3.amsl.com (Postfix) with ESMTP id 777DD3A70EF for <asrg@irtf.org>; Wed, 26 Aug 2009 15:21:06 -0700 (PDT)
Received: from squonk.gsp.org (bltmd-207.114.25.206.dsl.charm.net [207.114.25.206]) by taos.firemountain.net (8.14.1/8.14.1) with ESMTP id n7QMLBpu012679 for <asrg@irtf.org>; Wed, 26 Aug 2009 18:21:12 -0400 (EDT)
Received: from avatar.gsp.org (avatar.gsp.org [192.168.0.11]) by squonk.gsp.org (8.14.1/8.14.1) with ESMTP id n7QMD7Am001415 for <asrg@irtf.org>; Wed, 26 Aug 2009 18:13:07 -0400 (EDT)
Received: from avatar.gsp.org (localhost [127.0.0.1]) by avatar.gsp.org (8.14.3/8.14.3/Debian-4) with ESMTP id n7QML5Gd029344 for <asrg@irtf.org>; Wed, 26 Aug 2009 18:21:06 -0400
Received: (from rsk@localhost) by avatar.gsp.org (8.14.3/8.14.3/Submit) id n7QML57E029334 for asrg@irtf.org; Wed, 26 Aug 2009 18:21:05 -0400
Date: Wed, 26 Aug 2009 18:21:05 -0400
From: Rich Kulawiec <rsk@gsp.org>
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
Message-ID: <20090826222105.GA24507@gsp.org>
References: <45ae90370908260906t223ea020g1e964670fad7ef0d@mail.gmail.com> <20090826180601.79333.qmail@simone.iecc.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20090826180601.79333.qmail@simone.iecc.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
Subject: Re: [Asrg] [ASRG] SMTP pull anyone?
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Aug 2009 22:21:11 -0000

On Wed, Aug 26, 2009 at 06:06:01PM -0000, John Levine wrote:
> >Rich, does ipv6 change any of this?
> 
> I'm not Rich, but the open question at this point is how effective
> DNSBLs will be on IPv6.

What John said.

Point blocks already have their issues, for example (a) hosts using
dynamic addressing can hop around within a network allocation and
(b) spammers can try to use snowshoe techniques to tread lightly
enough to evade them.  And they can be unwieldly.  I think all of
this is likely to get worse with IPv6.  I rather suspect that this
will lead to mechanisms using entire network blocks -- some of which
we already have.  (For example, we have MTAs that understand blacklists
in CIDR format.)

At least some of the other measures should continue working, though,
as they're independent of IPv4-IPv6.  But I think while they may be
helpful, they're not going to be enough.

I don't see much help coming from SPF or DKIM or whatever: most of the
spam that makes it past my setup is correctly marked with one of these.
(<cough> Hotmail, Yahoo)  I expect this will get much worse as spammers
begin to leverage the full power of the botnets they're operating.

---Rsk

From macfisherman@gmail.com  Wed Aug 26 20:17:23 2009
Return-Path: <macfisherman@gmail.com>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CA9C13A690B for <asrg@core3.amsl.com>; Wed, 26 Aug 2009 20:17:23 -0700 (PDT)
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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YrDENGe723CL for <asrg@core3.amsl.com>; Wed, 26 Aug 2009 20:17:23 -0700 (PDT)
Received: from ey-out-2122.google.com (ey-out-2122.google.com [74.125.78.26]) by core3.amsl.com (Postfix) with ESMTP id D6EF83A6814 for <asrg@irtf.org>; Wed, 26 Aug 2009 20:17:22 -0700 (PDT)
Received: by ey-out-2122.google.com with SMTP id 25so160662eya.27 for <asrg@irtf.org>; Wed, 26 Aug 2009 20:17:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=HhsfBfcCEIa+2Wjy7xJ9S5ONpfEv46zI7MiEgkptwyA=; b=bNu+DQzcLe+NJKdu+Qdt4IW/wM49mqmNtKdAptICWU8XFArQQVjySYiWr3Xy06zDO5 pTWRYd3bzcDnTppR9mDztB8aAcF2S/jSZJgI2icPC9o+hcHMyq2bdylEW/PaAKNyqFIX bXAn7oQXwUmDi3M5gsYoL65gGSYVMZW9LvR3k=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=NHAGsU1BWRS1Fa54amwFKiHMW2MUXzFWPOBsdqAK5GqmqFIQK2oh8YvddLJLjPMEWe ilDIDcSb+1lMne+eyIJQZMzwl09UEYYxFhdwORMF5c7fVSyTZjVV0BiOWc40qXMWVy8W qSBpK47JnyEFEfEEGBMg/4/ozekAkZcBQrtaU=
MIME-Version: 1.0
Received: by 10.210.135.1 with SMTP id i1mr9165337ebd.48.1251343048051; Wed,  26 Aug 2009 20:17:28 -0700 (PDT)
In-Reply-To: <20090826222105.GA24507@gsp.org>
References: <45ae90370908260906t223ea020g1e964670fad7ef0d@mail.gmail.com> <20090826180601.79333.qmail@simone.iecc.com> <20090826222105.GA24507@gsp.org>
Date: Wed, 26 Aug 2009 23:17:28 -0400
Message-ID: <45ae90370908262017n455c0d0dg605ae81278792c80@mail.gmail.com>
From: Jeff Macdonald <macfisherman@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] [ASRG] SMTP pull anyone?
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Aug 2009 03:17:23 -0000

On Wed, Aug 26, 2009 at 6:21 PM, Rich Kulawiec<rsk@gsp.org> wrote:
> On Wed, Aug 26, 2009 at 06:06:01PM -0000, John Levine wrote:
>> >Rich, does ipv6 change any of this?
>>
>> I'm not Rich, but the open question at this point is how effective
>> DNSBLs will be on IPv6.
>
> What John said.
>
> Point blocks already have their issues, for example (a) hosts using
> dynamic addressing can hop around within a network allocation and
> (b) spammers can try to use snowshoe techniques to tread lightly
> enough to evade them. =A0And they can be unwieldly. =A0I think all of
> this is likely to get worse with IPv6. =A0I rather suspect that this
> will lead to mechanisms using entire network blocks -- some of which
> we already have. =A0(For example, we have MTAs that understand blacklists
> in CIDR format.)
>
> At least some of the other measures should continue working, though,
> as they're independent of IPv4-IPv6. =A0But I think while they may be
> helpful, they're not going to be enough.
>
> I don't see much help coming from SPF or DKIM or whatever: most of the
> spam that makes it past my setup is correctly marked with one of these.
> (<cough> Hotmail, Yahoo) =A0I expect this will get much worse as spammers
> begin to leverage the full power of the botnets they're operating.

So, if one were willing to accept that there will be valid IPv6 MTA
based connections, and the practicality of using IPv4 methods is no
longer feasible, then your list would be composed of only SMTP
envelope and body checks?


--=20
Jeff Macdonald
Ayer, MA

From steve@blighty.com  Wed Aug 26 20:30:16 2009
Return-Path: <steve@blighty.com>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9CF2F3A6D50 for <asrg@core3.amsl.com>; Wed, 26 Aug 2009 20:30:16 -0700 (PDT)
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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1nRBJDj2FHGS for <asrg@core3.amsl.com>; Wed, 26 Aug 2009 20:30:15 -0700 (PDT)
Received: from m.wordtothewise.com (fruitbat.wordtothewise.com [208.187.80.135]) by core3.amsl.com (Postfix) with ESMTP id E91233A6CEF for <asrg@irtf.org>; Wed, 26 Aug 2009 20:30:15 -0700 (PDT)
Received: from [192.168.80.34] (184.wordtothewise.com [208.187.80.184]) by m.wordtothewise.com (Postfix) with ESMTP id 83B9B80792 for <asrg@irtf.org>; Wed, 26 Aug 2009 20:30:02 -0700 (PDT)
Message-Id: <F32F76CE-829D-4C8C-A3B8-E5C344C14292@blighty.com>
From: Steve Atkins <steve@blighty.com>
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
In-Reply-To: <Pine.GSO.4.64.0908261605410.13418@nber5.nber.org>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v936)
Date: Wed, 26 Aug 2009 20:30:17 -0700
References: <20090826180601.79333.qmail@simone.iecc.com> <Pine.GSO.4.64.0908261605410.13418@nber5.nber.org>
X-Mailer: Apple Mail (2.936)
Subject: Re: [Asrg] [ASRG] SMTP pull anyone?
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Aug 2009 03:30:16 -0000

On Aug 26, 2009, at 2:22 PM, Daniel Feenberg wrote:

>
>
> On Wed, 26 Aug 2009, John Levine wrote:
>
>>> Rich, does ipv6 change any of this?
>>
>> I'm not Rich, but the open question at this point is how effective
>> DNSBLs will be on IPv6.
>
> I think it unlikely that an IPv6 only MTA will ever have acceptance  
> even as wide as, for instance, MTAs with "pool" or "dial-up" in  
> their RDNS. IPv6 only MTAs will be refused by many MTAs. There are  
> simply too many IPv6 addresses to blacklist bad hats, and  
> blacklisting /48s would be a very broad brush. The advantage of IPv4  
> is that the number of addresses is finite, and legitimate holders of  
> addresses are loath to waste them.

I see this asserted a lot, but I don't really see much in the way of  
plausible arguments to back it up.

If anything, some blacklist techniques are likely to be easier and  
more effective on IPv6 than v4 for the obvious NAT / dynamic  
assignment reasons.

Cheers,
   Steve


From CLEWIS@nortel.com  Wed Aug 26 20:48:46 2009
Return-Path: <CLEWIS@nortel.com>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E48D73A659A for <asrg@core3.amsl.com>; Wed, 26 Aug 2009 20:48:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.11
X-Spam-Level: 
X-Spam-Status: No, score=-5.11 tagged_above=-999 required=5 tests=[BAYES_05=-1.11, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oUUYhdaZSgXc for <asrg@core3.amsl.com>; Wed, 26 Aug 2009 20:48:46 -0700 (PDT)
Received: from zrtps0kp.nortel.com (zrtps0kp.nortel.com [47.140.192.56]) by core3.amsl.com (Postfix) with ESMTP id 2007B3A6A87 for <asrg@irtf.org>; Wed, 26 Aug 2009 20:48:28 -0700 (PDT)
Received: from zrtphxs1.corp.nortel.com (zrtphxs1.corp.nortel.com [47.140.202.46]) by zrtps0kp.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id n7R3mTK17186 for <asrg@irtf.org>; Thu, 27 Aug 2009 03:48:29 GMT
Received: from zrtphx5h0.corp.nortel.com ([47.140.202.65]) by zrtphxs1.corp.nortel.com with Microsoft SMTPSVC(6.0.3790.3959);  Wed, 26 Aug 2009 23:48:14 -0400
Received: from [47.130.64.174] (47.130.64.174) by zrtphx5h0.corp.nortel.com (47.140.202.65) with Microsoft SMTP Server (TLS) id 8.1.340.0; Wed, 26 Aug 2009 23:48:13 -0400
Message-ID: <4A9601FC.1090607@nortel.com>
Date: Wed, 26 Aug 2009 23:48:12 -0400
From: "Chris Lewis" <clewis@nortel.com>
Organization: Nortel
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.23) Gecko/20090812 Lightning/0.9 Thunderbird/2.0.0.23 Mnenhy/0.7.6.666
MIME-Version: 1.0
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
References: <20090826180601.79333.qmail@simone.iecc.com>	<Pine.GSO.4.64.0908261605410.13418@nber5.nber.org> <F32F76CE-829D-4C8C-A3B8-E5C344C14292@blighty.com>
In-Reply-To: <F32F76CE-829D-4C8C-A3B8-E5C344C14292@blighty.com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 27 Aug 2009 03:48:14.0096 (UTC) FILETIME=[3448F900:01CA26C9]
Subject: Re: [Asrg] [ASRG] SMTP pull anyone?
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Aug 2009 03:48:47 -0000

Steve Atkins wrote:

> I see this asserted a lot, but I don't really see much in the way of  
> plausible arguments to back it up.
> 
> If anything, some blacklist techniques are likely to be easier and  
> more effective on IPv6 than v4 for the obvious NAT / dynamic  
> assignment reasons.

Frankly, I don't think anything that earth shattering will occur, even 
if ipv6 takes over completely.

Undoubtably some techniques will work better, some about the same, and 
some won't work worth squat - they'll either evolve to work better, fade 
into meaninglessness, or just outright die.

It's not as if it hasn't happened before.  See much use of open relay 
DNSBLs anymore?  Thought not.

From vesely@tana.it  Thu Aug 27 01:50:43 2009
Return-Path: <vesely@tana.it>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0DFAF3A6D57 for <asrg@core3.amsl.com>; Thu, 27 Aug 2009 01:50:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.719
X-Spam-Level: 
X-Spam-Status: No, score=-4.719 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tMEIcRkGWZ4G for <asrg@core3.amsl.com>; Thu, 27 Aug 2009 01:50:42 -0700 (PDT)
Received: from wmail.tana.it (wmail.tana.it [62.94.243.226]) by core3.amsl.com (Postfix) with ESMTP id 2F8F23A67F3 for <asrg@irtf.org>; Thu, 27 Aug 2009 01:50:42 -0700 (PDT)
Received: from [217.203.154.28] ([217.203.154.28]) (AUTH: CRAM-MD5 ale@tana.it, TLS: TLS1.0, 256bits, RSA_AES_256_CBC_SHA1) by wmail.tana.it with esmtp; Thu, 27 Aug 2009 10:50:39 +0200 id 00000000005DC02F.000000004A9648E0.000031B1
Message-ID: <4A9648E4.7020507@tana.it>
Date: Thu, 27 Aug 2009 12:50:44 +0400
From: Alessandro Vesely <vesely@tana.it>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
References: <20090826180601.79333.qmail@simone.iecc.com>
In-Reply-To: <20090826180601.79333.qmail@simone.iecc.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [Asrg] [ASRG] SMTP pull anyone?
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Aug 2009 08:50:43 -0000

John Levine wrote:
> A DNSBL that blocks a single IP at a time, like the CBL and XBL, would
> be unworkable.  A typical v6 setup allocates a /64 to each host which
> allows various sorts of clever self-configuration, but also means the
> host can easily use a different IP address for every connection it
> ever makes. (At one address per millisecond, it would take 500 million
> years to run through a /64.)

Very well stated! I think we may say that, for any practical 
concern, tracking IP addresses won't have clear advantages over 
tracking registered domain names.

Rick's very detailed list provides many good hints. However, 
sooner or later somebody should state some clear instructions 
for running an MTA. I mean something that a company, an 
association, or even a household can easily set up and maintain, 
rather than an art/craft requiring arcane esoteric skills. In 
particular, tracking registered domain names allows to keep 
non-DNS settings unchanged through a change of connection 
provider(s), which seems to me a worthwhile simplification.

From tjc@ecs.soton.ac.uk  Thu Aug 27 02:26:41 2009
Return-Path: <tjc@ecs.soton.ac.uk>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B96B33A6DC8 for <asrg@core3.amsl.com>; Thu, 27 Aug 2009 02:26:41 -0700 (PDT)
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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id N9AYlhDl9VDR for <asrg@core3.amsl.com>; Thu, 27 Aug 2009 02:26:40 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) by core3.amsl.com (Postfix) with ESMTP id E72413A6B1C for <asrg@irtf.org>; Thu, 27 Aug 2009 02:26:39 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (localhost.ecs.soton.ac.uk [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id n7R9Qhdh022867 for <asrg@irtf.org>; Thu, 27 Aug 2009 10:26:43 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk n7R9Qhdh022867
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=200903; t=1251365203; bh=vx8B81Kw1ZUCut57u2eOxhVHfpQ=; h=Date:From:To:Subject:References:Mime-Version:In-Reply-To; b=23dzXVQuoML9IP5vfIa27DgE/b1zxrL7BjStZiUOK9A+Ikj3GtpDAizVXN3ZaW61U SKWg7Eya/jfVMtYn1uffJ5ZbzDksZDhHmoDuw/oOm14qy5eWHUWanPOpewug/ocVJU kg5Tp2Y/BCRKp05mjatpJjEG/9nWwICBbMpYbeGg=
Received: from gander.ecs.soton.ac.uk ([2001:630:d0:f102:21d:9ff:fe22:9fc]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102:21e:c9ff:fe2e:e915]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP id l7QAQh0427703426cp ret-id none; Thu, 27 Aug 2009 10:26:43 +0100
Received: from login.ecs.soton.ac.uk (login.ecs.soton.ac.uk [IPv6:2001:630:d0:f102:230:48ff:fe59:5f12]) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id n7R9QYVG021982 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <asrg@irtf.org>; Thu, 27 Aug 2009 10:26:34 +0100
Received: from login.ecs.soton.ac.uk (localhost.localdomain [127.0.0.1]) by login.ecs.soton.ac.uk (8.13.8/8.11.6) with ESMTP id n7R9QXfH007305 for <asrg@irtf.org>; Thu, 27 Aug 2009 10:26:33 +0100
Received: (from tjc@localhost) by login.ecs.soton.ac.uk (8.13.8/8.13.8/Submit) id n7R9QXUM007304 for asrg@irtf.org; Thu, 27 Aug 2009 10:26:33 +0100
Date: Thu, 27 Aug 2009 10:26:33 +0100
From: Tim Chown <tjc@ecs.soton.ac.uk>
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
Message-ID: <EMEW3|58a020d42973ba230015fc29c44e0564l7QAQh03tjc|ecs.soton.ac.uk|2633.GB4842@login.ecs.soton.ac.uk>
References: <20090826180601.79333.qmail@simone.iecc.com> <Pine.GSO.4.64.0908261605410.13418@nber5.nber.org> <20090827092633.GB4842@login.ecs.soton.ac.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.GSO.4.64.0908261605410.13418@nber5.nber.org>
User-Agent: Mutt/1.4.2.2i
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: client=relay,forged,no_ptr,ipv6; mail=; rcpt=
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: n7R9Qhdh022867
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Subject: Re: [Asrg] [ASRG] SMTP pull anyone?
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Aug 2009 09:26:41 -0000

On Wed, Aug 26, 2009 at 05:22:35PM -0400, Daniel Feenberg wrote:
> 
> I think it unlikely that an IPv6 only MTA will ever have acceptance even 
> as wide as, for instance, MTAs with "pool" or "dial-up" in their RDNS. 
> IPv6 only MTAs will be refused by many MTAs. There are simply too many 
> IPv6 addresses to blacklist bad hats, and blacklisting /48s would be a 
> very broad brush. The advantage of IPv4 is that the number of addresses is 
> finite, and legitimate holders of addresses are loath to waste them.
> 
> I understand that many IPv6 capable MTAs exist, but I expect they do all 
> or nearly all of their external traffic via IPv4. I don't mean a general 
> condemdantion of IPv6, I am only saying that SMTP traffic from strangers 
> on IPv6 is not likely to be worthwhile.

I think this assumption has some problems, particularly in the area of
IPv6 transition.

If one assumes that RFC3974 is still generally valid, and sites use both
A and AAAA records for MXes (as we do here), then such sites may receive
email via IPv4 or IPv6, depending on the preference of the sending MTA.
And that's the important thing - that MTA if sendmail (for example)
defaults to trying IPv6 first, so you won't just receive IPv6 SMTP
connections by being IPv6 only, but also from any sender who, probably
like you, is dual-stack.

We choose to run MTAs dual-stack so we can accept mail (internally or
externally) from IPv4-only, IPv6-only or of course dual-stack nodes.

I think if you reject IPv6 SMTP, even if 'just' from strangers, you 
make transition harder - you either don't turn on v6, or if you do you
prefer v4 over v6.  Neither helps transition.

Based on our stats from June, we received an average of 158,000 messages
per day over IPv4 transport, of which 81% were deemed spam, while we 
received 438 (yes, 438!) messages via per day IPv6, of which 32% were spam.
So even for us, v6 is less than 1% of all received mail.

The spam was largely from dual-stack mail list servers, not from random
clients/hosts.   But it's interesting to look at specific connections -
non list spam tends to come from autoconfigured v6 addresses (implying
desktops) while 'good' mail comes from apparently manually configured
IPv6 addresses (because v6 admins know to not use autoconf addresses on
their servers).

One day I will convert the experience of 3+ years of running a dual-stack
MTA in production to a draft, and analyse the (at least) year's worth of 
data on v6 spam sources that we have :)

Tim

From rsk@gsp.org  Thu Aug 27 04:29:19 2009
Return-Path: <rsk@gsp.org>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B554B28C370 for <asrg@core3.amsl.com>; Thu, 27 Aug 2009 04:29:19 -0700 (PDT)
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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YhDPX6IRim8x for <asrg@core3.amsl.com>; Thu, 27 Aug 2009 04:29:19 -0700 (PDT)
Received: from taos.firemountain.net (taos.firemountain.net [207.114.3.54]) by core3.amsl.com (Postfix) with ESMTP id CEE8728C1A6 for <asrg@irtf.org>; Thu, 27 Aug 2009 04:29:18 -0700 (PDT)
Received: from squonk.gsp.org (bltmd-207.114.25.206.dsl.charm.net [207.114.25.206]) by taos.firemountain.net (8.14.1/8.14.1) with ESMTP id n7RBTNnr023836 for <asrg@irtf.org>; Thu, 27 Aug 2009 07:29:24 -0400 (EDT)
Received: from avatar.gsp.org (avatar.gsp.org [192.168.0.11]) by squonk.gsp.org (8.14.1/8.14.1) with ESMTP id n7RBLHnl017292 for <asrg@irtf.org>; Thu, 27 Aug 2009 07:21:17 -0400 (EDT)
Received: from avatar.gsp.org (localhost [127.0.0.1]) by avatar.gsp.org (8.14.3/8.14.3/Debian-4) with ESMTP id n7RBTHGO016719 for <asrg@irtf.org>; Thu, 27 Aug 2009 07:29:17 -0400
Received: (from rsk@localhost) by avatar.gsp.org (8.14.3/8.14.3/Submit) id n7RBTHVW016718 for asrg@irtf.org; Thu, 27 Aug 2009 07:29:17 -0400
Date: Thu, 27 Aug 2009 07:29:17 -0400
From: Rich Kulawiec <rsk@gsp.org>
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
Message-ID: <20090827112917.GA16635@gsp.org>
References: <45ae90370908260906t223ea020g1e964670fad7ef0d@mail.gmail.com> <20090826180601.79333.qmail@simone.iecc.com> <20090826222105.GA24507@gsp.org> <45ae90370908262017n455c0d0dg605ae81278792c80@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <45ae90370908262017n455c0d0dg605ae81278792c80@mail.gmail.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
Subject: Re: [Asrg] [ASRG] SMTP pull anyone?
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Aug 2009 11:29:19 -0000

On Wed, Aug 26, 2009 at 11:17:28PM -0400, Jeff Macdonald wrote:
> So, if one were willing to accept that there will be valid IPv6 MTA
> based connections, and the practicality of using IPv4 methods is no
> longer feasible, then your list would be composed of only SMTP
> envelope and body checks?

Hmmm.  At the moment, it sure looks that way.  Happily (at the moment)
those methods do a very good job: roughly 85% of total spam rejected
is rejected by those means before any IPv4 methods are used.  But I
have to guess that this percentage will decline and that I'm going to
need to revisit/revise this.

---Rsk

From dotis@mail-abuse.org  Thu Aug 27 20:34:14 2009
Return-Path: <dotis@mail-abuse.org>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 568913A6AFF for <asrg@core3.amsl.com>; Thu, 27 Aug 2009 20:34:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.696
X-Spam-Level: 
X-Spam-Status: No, score=-5.696 tagged_above=-999 required=5 tests=[AWL=0.859,  BAYES_00=-2.599, DATE_IN_PAST_03_06=0.044, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jsTiIUgzYI2a for <asrg@core3.amsl.com>; Thu, 27 Aug 2009 20:34:13 -0700 (PDT)
Received: from harry.mail-abuse.org (harry.mail-abuse.org [168.61.5.27]) by core3.amsl.com (Postfix) with ESMTP id 93BC93A6892 for <asrg@irtf.org>; Thu, 27 Aug 2009 20:34:13 -0700 (PDT)
Received: from SJC-Office-NAT-214.mail-abuse.org (gateway1.sjc.mail-abuse.org [168.61.5.81]) by harry.mail-abuse.org (Postfix) with ESMTP id 69C88A9443E for <asrg@irtf.org>; Thu, 27 Aug 2009 23:23:23 +0000 (UTC)
Message-ID: <4A97156B.4030302@mail-abuse.org>
Date: Thu, 27 Aug 2009 16:23:23 -0700
From: Douglas Otis <dotis@mail-abuse.org>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1.1) Gecko/20090715 Thunderbird/3.0b3
MIME-Version: 1.0
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
References: <20090826180601.79333.qmail@simone.iecc.com>	<Pine.GSO.4.64.0908261605410.13418@nber5.nber.org>	<F32F76CE-829D-4C8C-A3B8-E5C344C14292@blighty.com> <4A9601FC.1090607@nortel.com>
In-Reply-To: <4A9601FC.1090607@nortel.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [Asrg] [ASRG] SMTP pull anyone?
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Aug 2009 03:34:14 -0000

On 8/26/09 8:48 PM, Chris Lewis wrote:
> Steve Atkins wrote:
>
>> I see this asserted a lot, but I don't really see much in the way of
>> plausible arguments to back it up.
>>
>> If anything, some blacklist techniques are likely to be easier and
>> more effective on IPv6 than v4 for the obvious NAT / dynamic
>> assignment reasons.
>
> Frankly, I don't think anything that earth shattering will occur, even
> if ipv6 takes over completely.
>
> Undoubtably some techniques will work better, some about the same, and
> some won't work worth squat - they'll either evolve to work better, fade
> into meaninglessness, or just outright die.
>
> It's not as if it hasn't happened before. See much use of open relay
> DNSBLs anymore? Thought not.

Treating /64 (the network of an IPv6 addresses) as having the same 
reputation is destine for support issues when exceptions are needed for 
various legitimate services.

When establishing an IPv6 block list, once exceptions are made, 
retaining evidence for each of these exceptions removes any semblance of 
there being an upper limit on the number of IP addresses logged.  After 
all, bad actors will start wearing large snowshoes in exception ranges.

For IPv6 addresses to become first-class citizens of the email 
community, listing those that should be accepted rather those blocked 
represents perhaps the only scalable solution while using similar tools. 
  Using DKIM messages to request inclusion of a new domain can also 
assist in validating the servers.

Alternative solutions such as accessing a link returned to the domain 
might be used as well.  Nevertheless, DKIM should help reduce the 
validation steps needed, and could help prioritize and expedite 
inclusions requests.  Knowing the domain rather than just an IP address 
also allows more extensive correlations with prior abuses.

-Doug














From feenberg@nber.org  Fri Aug 28 04:46:41 2009
Return-Path: <feenberg@nber.org>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BA28628C219 for <asrg@core3.amsl.com>; Fri, 28 Aug 2009 04:46:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XQBE4r9ZMVkh for <asrg@core3.amsl.com>; Fri, 28 Aug 2009 04:46:40 -0700 (PDT)
Received: from mail2.nber.org (mail2.nber.org [66.251.72.79]) by core3.amsl.com (Postfix) with ESMTP id 4159728C20C for <asrg@irtf.org>; Fri, 28 Aug 2009 04:46:36 -0700 (PDT)
Received: from nber5.nber.org (nber5.nber.org [66.251.72.75]) by mail2.nber.org (8.14.1/8.13.8) with ESMTP id n7SBkfYx062186 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT) for <asrg@irtf.org>; Fri, 28 Aug 2009 07:46:42 -0400 (EDT) (envelope-from feenberg@nber.org)
Received: from nber5.nber.org (localhost [127.0.0.1]) by nber5.nber.org (8.13.8+Sun/8.13.8) with ESMTP id n7SBcsEV013195; Fri, 28 Aug 2009 07:38:54 -0400 (EDT)
Received: from localhost (Unknown UID 1079@localhost) by nber5.nber.org (8.13.8+Sun/8.13.8/Submit) with ESMTP id n7SBcslR013192; Fri, 28 Aug 2009 07:38:54 -0400 (EDT)
X-Authentication-Warning: nber5.nber.org: Unknown UID 1079 owned process doing -bs
Date: Fri, 28 Aug 2009 07:38:54 -0400 (EDT)
From: Daniel Feenberg <feenberg@nber.org>
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
In-Reply-To: <4A97156B.4030302@mail-abuse.org>
Message-ID: <Pine.GSO.4.64.0908280726160.10319@nber5.nber.org>
References: <20090826180601.79333.qmail@simone.iecc.com> <Pine.GSO.4.64.0908261605410.13418@nber5.nber.org> <F32F76CE-829D-4C8C-A3B8-E5C344C14292@blighty.com> <4A9601FC.1090607@nortel.com> <4A97156B.4030302@mail-abuse.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Anti-Virus: Kaspersky Anti-Virus for Sendmail with Milter API 5.6.20, bases: 20090827 #2447750, check: 20090828 clean
Subject: Re: [Asrg] [ASRG] SMTP pull anyone?
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Aug 2009 11:46:41 -0000

Tim Chown wrote:

>Based on our stats from June, we received an average of 158,000 messages
>per day over IPv4 transport, of which 81% were deemed spam, while we
>received 438 (yes, 438!) messages via per day IPv6, of which 32% were 
>spam. So even for us, v6 is less than 1% of all received mail.


The relevant percentage would be the spam percentage coming from hosts 
that have no IPv4 address. The quality of dual-stacked hosts is not 
really germane to the question of whether IPv6 only hosts will ever exist.

I don't doubt that many MTAs will accept IPv6 mail. What I dispute is the 
liklihood of anyone running a legitimate Internet MTA that accepts mail 
from an IPv6 only host. My reasoning is that such a host would have 
limited connectivity. There are two reasons for this. (1) Many MTA 
operators will lag in the adoption of IPv6 due to general lack of 
interest, ability or funds, so an IPv6 only MTA will have no access to 
many MTAs, much worse even than MTAs operating at dial-up addresses 
currently have. (2) Anyone operating an MTA on IPv6 will have to do 
without the single most effective anti-spam technique we have, the DNSBL. 
This will cause many operators with the resources to add IPv6 to hesitate 
to do so.

Given either of these two reasons, few or no MTAs will run IPv6 only, 
which obviates the need for IPv6 entirely.

Of course, some operators can do without DNSBLs, and they can 
easily operate dual-stack. There is no practical way they can drop IPv4, 
nor will they ever be able to do so.

So, how much mail came from IPv6-only hosts? And what was the percentage 
of spam?

Daniel Feenberg


From dotis@mail-abuse.org  Fri Aug 28 10:36:04 2009
Return-Path: <dotis@mail-abuse.org>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 12FE63A6821 for <asrg@core3.amsl.com>; Fri, 28 Aug 2009 10:36:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.757
X-Spam-Level: 
X-Spam-Status: No, score=-5.757 tagged_above=-999 required=5 tests=[AWL=0.842,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id t3-0pj1HEBKW for <asrg@core3.amsl.com>; Fri, 28 Aug 2009 10:36:03 -0700 (PDT)
Received: from harry.mail-abuse.org (harry.mail-abuse.org [168.61.5.27]) by core3.amsl.com (Postfix) with ESMTP id 5515A3A6963 for <asrg@irtf.org>; Fri, 28 Aug 2009 10:36:03 -0700 (PDT)
Received: from SJC-Office-NAT-214.mail-abuse.org (gateway1.sjc.mail-abuse.org [168.61.5.81]) by harry.mail-abuse.org (Postfix) with ESMTP id 72784A94452 for <asrg@irtf.org>; Fri, 28 Aug 2009 17:36:08 +0000 (UTC)
Message-ID: <4A981588.4030306@mail-abuse.org>
Date: Fri, 28 Aug 2009 10:36:08 -0700
From: Douglas Otis <dotis@mail-abuse.org>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1.1) Gecko/20090715 Thunderbird/3.0b3
MIME-Version: 1.0
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
References: <20090826180601.79333.qmail@simone.iecc.com>	<Pine.GSO.4.64.0908261605410.13418@nber5.nber.org>	<F32F76CE-829D-4C8C-A3B8-E5C344C14292@blighty.com>	<4A9601FC.1090607@nortel.com> <4A97156B.4030302@mail-abuse.org> <Pine.GSO.4.64.0908280726160.10319@nber5.nber.org>
In-Reply-To: <Pine.GSO.4.64.0908280726160.10319@nber5.nber.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [Asrg] [ASRG] SMTP pull anyone?
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Aug 2009 17:36:04 -0000

On 8/28/09 4:38 AM, Daniel Feenberg wrote:

Daniel,

> I don't doubt that many MTAs will accept IPv6 mail. What I dispute is
> the liklihood of anyone running a legitimate Internet MTA that accepts
> mail from an IPv6 only host. My reasoning is that such a host would have
> limited connectivity. There are two reasons for this. (1) Many MTA
> operators will lag in the adoption of IPv6 due to general lack of
> interest, ability or funds, so an IPv6 only MTA will have no access to
> many MTAs, much worse even than MTAs operating at dial-up addresses
> currently have. (2) Anyone operating an MTA on IPv6 will have to do
> without the single most effective anti-spam technique we have, the
> DNSBL. This will cause many operators with the resources to add IPv6 to
> hesitate to do so.
>
> Given either of these two reasons, few or no MTAs will run IPv6 only,
> which obviates the need for IPv6 entirely.

One of the significant changes we needed to make in our service when 
becoming more popular in Asia's Pacific Rim, was to provide setting that 
precluded other regions by default.  This desire might not be 
xenophobic, but based rationale interests.  When large portions of a 
country's connectivity is IPv6, having preferences for IPv6 seems 
logical.  The question you might consider would be whether those in IPv6 
predominate regions even wish to accept IPv4 connections from areas 
blighted with spam in languages foreign.

> Of course, some operators can do without DNSBLs, and they can easily
> operate dual-stack. There is no practical way they can drop IPv4, nor
> will they ever be able to do so.

Be a bit cautious about considering this a general statement.

> So, how much mail came from IPv6-only hosts? And what was the percentage
> of spam?

This type of measure will never uncover the amount of region specific 
exclusions.  You might be surprised to find IPv4 is not always king.

-Doug



