Re: [marf] Misuse of ARF by spam-friendly ISPs

Alessandro Vesely <vesely@tana.it> Wed, 03 August 2011 10:02 UTC

Return-Path: <vesely@tana.it>
X-Original-To: marf@ietfa.amsl.com
Delivered-To: marf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 44DCD21F8B3D for <marf@ietfa.amsl.com>; Wed, 3 Aug 2011 03:02:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.551
X-Spam-Level:
X-Spam-Status: No, score=-3.551 tagged_above=-999 required=5 tests=[AWL=-1.132, 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.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id I6Net8iXDcLp for <marf@ietfa.amsl.com>; Wed, 3 Aug 2011 03:02:03 -0700 (PDT)
Received: from wmail.tana.it (mail.tana.it [62.94.243.226]) by ietfa.amsl.com (Postfix) with ESMTP id 51F0021F8B40 for <marf@ietf.org>; Wed, 3 Aug 2011 03:02:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=test; t=1312365733; bh=1WPKX5MMwqkeZ8xMcMOVWQ+PoGy5hgCge+dcbm6zL2U=; l=1324; h=Message-ID:Date:From:MIME-Version:To:References:In-Reply-To: Content-Transfer-Encoding; b=X2hEh/cler5mJVQWqbIcUQeCJzU6zsZhIfYiiLS6rLm+R3+ZA4U47KSMZk84MPj7I 5rR5l9mZK2Be+5q9vxSJD5LNtXDBLMZ/NVybkgvcGFec8EJxYldYY2IP1K0wLHxT00 DZi3L+TOTbk/QRxRKJQxpo9mczqDAGKojKnGke20=
Received: from [172.25.197.158] (pcale.tana [172.25.197.158]) (AUTH: CRAM-MD5 515, TLS: TLS1.0,256bits,RSA_AES_256_CBC_SHA1) by wmail.tana.it with ESMTPSA; Wed, 03 Aug 2011 12:02:13 +0200 id 00000000005DC039.000000004E391CA5.00005D7A
Message-ID: <4E391CA5.6010803@tana.it>
Date: Wed, 03 Aug 2011 12:02:13 +0200
From: Alessandro Vesely <vesely@tana.it>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.18) Gecko/20110616 Lightning/1.0b2 Thunderbird/3.1.11
MIME-Version: 1.0
To: marf@ietf.org
References: <35734E6B-4579-4EF4-A139-7BFB4FA4573F@wordtothewise.com> <E41787825008234A9B8BB93D603C8B0F1707F7@bobo1.bobotek.net> <953887BF-E8AB-4246-8075-7EB50A7BF916@wordtothewise.com> <F5833273385BB34F99288B3648C4F06F13512DF4CD@EXCH-C2.corp.cloudmark.com> <A6F08584-07DB-4000-B5EB-0AD02AFD44E2@cybernothing.org>
In-Reply-To: <A6F08584-07DB-4000-B5EB-0AD02AFD44E2@cybernothing.org>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Subject: Re: [marf] Misuse of ARF by spam-friendly ISPs
X-BeenThere: marf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Message Abuse Report Format working group discussion list <marf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/marf>, <mailto:marf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/marf>
List-Post: <mailto:marf@ietf.org>
List-Help: <mailto:marf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/marf>, <mailto:marf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Aug 2011 10:02:04 -0000

On 03/Aug/11 02:42, J.D. Falk wrote:
> On Jul 30, 2011, at 9:30 PM, Murray S. Kucherawy wrote:
> 
>> I wonder if this could be mentioned in the BCP effort we're doing (JD?).
> 
> I suppose it could be added to the growing list of use cases that
> draft-jdfalk-marf-as specifically does not address, along with
> individual user submissions, virus/malware reports, churning monkey
> butter, et cetera.

What is the meaning of a list of non-addressed use cases?  Possibly
suggest that they are not worth being addressed in general?  Hmm...
that's quite strange, especially considering that everyone likes the
monkey butter.

> Sounds to me like what's actually needed is a BCP on accepting
> abuse reports from the general public -- maybe a task for the
> ASRG?

I agree such a BCP is needed, and I take this chance to propose it
again.  The ASRG has already done research on this topic, and John
summarized it in

  http://wiki.asrg.sp.am/wiki/Adding_a_junk_button_to_MUAs

That still looks current.  It allows MUAs to report in a variety of
ways.  For SMTP, it is obviously better to wrap the offending mail in
an ARF message, but not mandatory.

For homogeneity, I'd put this extra BCP in MARF rather than ASRG.
There are related issues, like manual vs. auto submission, and privacy
considerations.