Re: [dispatch] FYI draft-levine-mailbomb-header-00

Cullen Jennings <fluffy@iii.ca> Tue, 20 June 2017 18:22 UTC

Return-Path: <fluffy@iii.ca>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 38CB51315CE for <dispatch@ietfa.amsl.com>; Tue, 20 Jun 2017 11:22:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.701
X-Spam-Level:
X-Spam-Status: No, score=-4.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.8, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8wpcGrMy04oI for <dispatch@ietfa.amsl.com>; Tue, 20 Jun 2017 11:22:00 -0700 (PDT)
Received: from smtp80.iad3a.emailsrvr.com (smtp80.iad3a.emailsrvr.com [173.203.187.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0B4591315C6 for <dispatch@ietf.org>; Tue, 20 Jun 2017 11:22:00 -0700 (PDT)
Received: from smtp19.relay.iad3a.emailsrvr.com (localhost [127.0.0.1]) by smtp19.relay.iad3a.emailsrvr.com (SMTP Server) with ESMTP id 3C6CF515F; Tue, 20 Jun 2017 14:21:59 -0400 (EDT)
X-Auth-ID: fluffy@iii.ca
Received: by smtp19.relay.iad3a.emailsrvr.com (Authenticated sender: fluffy-AT-iii.ca) with ESMTPSA id D665550B9; Tue, 20 Jun 2017 14:21:58 -0400 (EDT)
X-Sender-Id: fluffy@iii.ca
Received: from [10.1.3.55] (d172-219-247-164.abhsia.telus.net [172.219.247.164]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384) by 0.0.0.0:587 (trex/5.7.12); Tue, 20 Jun 2017 14:21:59 -0400
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
From: Cullen Jennings <fluffy@iii.ca>
In-Reply-To: <20170619174225.10412.qmail@ary.lan>
Date: Tue, 20 Jun 2017 12:21:57 -0600
Cc: dispatch@ietf.org
Content-Transfer-Encoding: 7bit
Message-Id: <33E62B35-8048-4EBA-A5D8-409564D5B667@iii.ca>
References: <20170619174225.10412.qmail@ary.lan>
To: John Levine <johnl@taugh.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/kyguiEy_d8v6wrEvU7X7bLfITlw>
Subject: Re: [dispatch] FYI draft-levine-mailbomb-header-00
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Jun 2017 18:22:03 -0000

For v6, how much would typically be redacted ?



> On Jun 19, 2017, at 11:42 AM, John Levine <johnl@taugh.com> wrote:
> 
> This draft came out of a discussion last week at M3AAWG.  The issue is
> that bad guys (or more likely bad bots) fill out web forms and include
> fake mail addresses, the forms provoke confirmation mail which then
> mailbombs the address(es).
> 
> This draft adds a new header to indicate that a message is in response
> to a form submission:
> 
> Form-Sub: v=1; ip4=198.51.x.x
> 
> The IP address is that of the web client, which may be partly redacted
> with "x" for privacy reasons.  If a recipient mail system sees too
> many of them, it may block the system that's sending them.  The draft
> also asks for an enhanced status code which means we rejected this
> message because it's part of a flood with Form-Sub headers.
> 
> When we had the discussion there were people from at least two large
> consumer mail systems and a dozen hosters and (sending) mail service
> providers in the room, so it is likely this will be implemented
> enough to see if it's useful.
> 
> At this point the main point of writing the draft was to have a
> reference so I could ask IANA to register the header and status code.
> If it does turn out to be useful I'll come back and ask for it to be
> dispatched into a standards track document.
> 
> R's,
> John
> 
> _______________________________________________
> dispatch mailing list
> dispatch@ietf.org
> https://www.ietf.org/mailman/listinfo/dispatch