Re: [spfbis] New issue: 8.4. Fail: rejection is not described explicitly

"Murray S. Kucherawy" <superuser@gmail.com> Sat, 20 April 2013 17:20 UTC

Return-Path: <superuser@gmail.com>
X-Original-To: spfbis@ietfa.amsl.com
Delivered-To: spfbis@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7D4BC21F87B7 for <spfbis@ietfa.amsl.com>; Sat, 20 Apr 2013 10:20:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.099
X-Spam-Level:
X-Spam-Status: No, score=-3.099 tagged_above=-999 required=5 tests=[AWL=-0.500, BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KV2u35UG2BNA for <spfbis@ietfa.amsl.com>; Sat, 20 Apr 2013 10:20:00 -0700 (PDT)
Received: from mail-wi0-x22d.google.com (mail-wi0-x22d.google.com [IPv6:2a00:1450:400c:c05::22d]) by ietfa.amsl.com (Postfix) with ESMTP id A57F721F8771 for <spfbis@ietf.org>; Sat, 20 Apr 2013 10:19:59 -0700 (PDT)
Received: by mail-wi0-f173.google.com with SMTP id c10so2330638wiw.0 for <spfbis@ietf.org>; Sat, 20 Apr 2013 10:19:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=HgnF0TvsF8HWWRSLA/G1dyCQxsncEvF0ho1Yqt33468=; b=qWh0PkzyeCJUWQ344+9emFby/wjUX9oN8WazYJGVt1EuxUwr3hNPWl/3zldsAyV8+F Wwz0zppeocCGH9SlJ80dwxbmhN1TTKP9RpeUXQi3HcNxKcXTLak5evgOyJ02W2zzh0zy DsUna/EaMujdwjZMyADPMOP+fGPfLAZNaMbglxrG3unQ3NCTwdRIBSIswgLAYVkr22To qEpuEdNcqIHoWwbMMkj8NJC4w7LSkDnfD5lZjMJ/vFcFg4dd59O+LB4NqM4xktZxjemr w8eSPb6trqW3FX/2F9oaD0tnbm2LjccK+H0R3juIBEA/fMgjkrWpUu40WfkBi+02T1mv vucA==
MIME-Version: 1.0
X-Received: by 10.180.84.162 with SMTP id a2mr35366183wiz.14.1366478398843; Sat, 20 Apr 2013 10:19:58 -0700 (PDT)
Received: by 10.180.36.176 with HTTP; Sat, 20 Apr 2013 10:19:58 -0700 (PDT)
In-Reply-To: <51726641.7070606@tana.it>
References: <51726641.7070606@tana.it>
Date: Sat, 20 Apr 2013 10:19:58 -0700
Message-ID: <CAL0qLwb0KzATJ5p3Ca1+0sj5bvYi7wJx-MppnBfyX_UUg_JPzw@mail.gmail.com>
From: "Murray S. Kucherawy" <superuser@gmail.com>
To: Alessandro Vesely <vesely@tana.it>
Content-Type: multipart/alternative; boundary="f46d044271948e710104dace0bfd"
Cc: "spfbis@ietf.org" <spfbis@ietf.org>
Subject: Re: [spfbis] New issue: 8.4. Fail: rejection is not described explicitly
X-BeenThere: spfbis@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: SPFbis discussion list <spfbis.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spfbis>, <mailto:spfbis-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/spfbis>
List-Post: <mailto:spfbis@ietf.org>
List-Help: <mailto:spfbis-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spfbis>, <mailto:spfbis-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 20 Apr 2013 17:20:00 -0000

On Sat, Apr 20, 2013 at 2:56 AM, Alessandro Vesely <vesely@tana.it> wrote:

> Appendix H.2 should be merged into Section 8.4, as the reason to keep
> them separate was beaten out by Murray's reorganization.  I mentioned
> that in my review.
>

I don't agree.  What's in H.2 discusses local policy development which
cannot be normative.  It's strictly pedagogical.  Section 8 contains purely
definitions and normative material.  I don't support mixing them.

I also agree with what John said about this.

In addition, the combined text is not explicit in describing how
> reject-on-fail works when enabled.  H.2 says "rejection can be done
> before the SMTP content is transferred."  Explicit would be to to say
> that the negative response can be given to either the MAIL or the RCPT
> commands.
>

I would be fine with changing H.2 to make that very explicit, although I
think we can rely on people understanding SMTP already since it's a
normative reference, so I'm also fine with leaving it as-is, and at this
late stage that is also my preference.


>
> Of course, it is also possible to reject after receiving the content.
> It is not typical of SPF implementations to do so.  Early rejection may
> conflict with DMARC and similar policies, and the point of this issue is
> that an explicit note can save readers the time to puzzle it out
> themselves, and possibly avoid some misunderstanding.
>

We should absolutely not discuss DMARC or other layers here.

-MSK