Re: [dmarc-ietf] Review of draft-kucherawy-dmarc-base-00 (was:Fwd: Eliot's review of the DMARC spec)
SM <sm@resistor.net> Sat, 06 July 2013 18:05 UTC
Return-Path: <sm@resistor.net>
X-Original-To: dmarc@ietfa.amsl.com
Delivered-To: dmarc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8E52221F9CC4 for <dmarc@ietfa.amsl.com>; Sat, 6 Jul 2013 11:05:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hllbWPFmUIyf for <dmarc@ietfa.amsl.com>; Sat, 6 Jul 2013 11:05:18 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 7D00D21F9AF0 for <dmarc@ietf.org>; Sat, 6 Jul 2013 11:05:12 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r66I51lb013870; Sat, 6 Jul 2013 11:05:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1373133908; bh=Ouvz9RTM8nPVEQmVIcNBKpbuAKpewzuqZ4NmRe4a5H0=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=gC+nit0430bx5fZfoaNhMJ9TWnDCzoPdiTj1aiP5IjpnpHQHQzoCdVDUao1DH03a0 vWyUz/NPSD3Afgqza0imxlFT0Pt4Lr+qsFodQLFxGJJQXLeOIoxjTrib8GRyVqyS3l iiMnhu/+fWAbGfhzgyGjWTIW/grx3jNQrQDsKLHE=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1373133908; i=@resistor.net; bh=Ouvz9RTM8nPVEQmVIcNBKpbuAKpewzuqZ4NmRe4a5H0=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=ZxyejxzT9uUmmf0oXYBY7/FjAbWG1NApoNNLBn9zQ1pqmW/8LjD07ofS1OEGYka+L 1uIamMhRhh0h8gL5u3MP7XH49/bSDhhhCQ8Y387sfFU/NYDNbikYDTZrLkvzCCSNAF GJJhkbZf/Kz7HKA0TOaSN4xEbA8kAlTbYRX3Jme4=
Message-Id: <6.2.5.6.2.20130706105143.0d56b5f8@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sat, 06 Jul 2013 11:01:40 -0700
To: Franck Martin <fmartin@linkedin.com>
From: SM <sm@resistor.net>
In-Reply-To: <77426B543150464AA3F30DF1A91365DE53A77D0C@ESV4-MBX02.linked in.biz>
References: <519B47DC.20008@cisco.com> <CAL0qLwYZOp1FNVSAmzXYkZG_O3Yv+EQrAKKLpRiE5svcOMamTA@mail.gmail.com> <6.2.5.6.2.20130523002139.0da7ac58@resistor.net> <CAL0qLwYT6BS=HGLX1-u80aqaJWefipT5tcg5Ut_549y4rOej9g@mail.gmail.com> <6.2.5.6.2.20130705091238.0be05400@resistor.net> <77426B543150464AA3F30DF1A91365DE53A77D0C@ESV4-MBX02.linkedin.biz>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Cc: dmarc@ietf.org, "Murray S. Kucherawy" <superuser@gmail.com>
Subject: Re: [dmarc-ietf] Review of draft-kucherawy-dmarc-base-00 (was:Fwd: Eliot's review of the DMARC spec)
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dmarc>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dmarc>, <mailto:dmarc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 06 Jul 2013 18:05:19 -0000
Hi Frank, At 01:14 06-07-2013, Franck Martin wrote: >There is not much standardization of response codes from MTAs. There >are extended response codes, but then you cannot deduct from them, >if the problem is due to DMARC or other security policies. If I'm >not mistaken, take the case of Facebook, refusing an email because >you are not a friend of the recipient... Or the same error code >could indicate SPF or DKIM or other protocol failure... Having the >word DMARC in the text of the error message gives a lot of >information for debugging a specific email. Consider also the error >could be generated after a forwarder is trying to send an email... >Without a proper hint of what is the reason of the reject it is very >hard to know what really happened for a specific email. That is usually know as a local policy decision. If I recall correctly the question of the sender knowing the reason for a mail delivery failure was discussed in another working group. I understand the use case mentioned above. I would look at the draft in terms of a standard for the Internet, if that is the intended purpose, instead of a document about how to know why a message is considered as spam. Regards, -sm
- [dmarc-ietf] Fwd: Eliot's review of the DMARC spec Murray S. Kucherawy
- Re: [dmarc-ietf] Fwd: Eliot's review of the DMARC… SM
- Re: [dmarc-ietf] Fwd: Eliot's review of the DMARC… John Levine
- Re: [dmarc-ietf] Eliot's review of the DMARC spec Tim Draegen
- Re: [dmarc-ietf] Fwd: Eliot's review of the DMARC… Matt Simerson
- Re: [dmarc-ietf] Fwd: Eliot's review of the DMARC… John R Levine
- Re: [dmarc-ietf] Eliot's review of the DMARC spec Murray S. Kucherawy
- Re: [dmarc-ietf] Fwd: Eliot's review of the DMARC… Murray S. Kucherawy
- Re: [dmarc-ietf] Eliot's review of the DMARC spec Eliot Lear
- Re: [dmarc-ietf] Eliot's review of the DMARC spec John Levine
- Re: [dmarc-ietf] Eliot's review of the DMARC spec Murray S. Kucherawy
- [dmarc-ietf] Review of draft-kucherawy-dmarc-base… SM
- Re: [dmarc-ietf] Eliot's review of the DMARC spec John R Levine
- Re: [dmarc-ietf] Review of draft-kucherawy-dmarc-… Franck Martin
- [dmarc-ietf] cousin domain definition (was Re: Fw… Dave Crocker
- Re: [dmarc-ietf] Review of draft-kucherawy-dmarc-… SM
- Re: [dmarc-ietf] cousin domain definition (was Re… Matt Simerson
- Re: [dmarc-ietf] cousin domain definition (was Re… Dave Crocker
- Re: [dmarc-ietf] cousin domain definition (was Re… Elizabeth Zwicky
- Re: [dmarc-ietf] cousin domain definition (was Re… Matt Simerson
- Re: [dmarc-ietf] Review of draft-kucherawy-dmarc-… Franck Martin
- Re: [dmarc-ietf] cousin domain definition (was Re… Franck Martin
- Re: [dmarc-ietf] cousin domain definition (was Re… Dave Crocker
- Re: [dmarc-ietf] cousin domain definition (was Re… John Levine
- Re: [dmarc-ietf] cousin domain definition (was Re… Murray S. Kucherawy
- Re: [dmarc-ietf] Review of draft-kucherawy-dmarc-… SM
- Re: [dmarc-ietf] Review of draft-kucherawy-dmarc-… Murray S. Kucherawy
- Re: [dmarc-ietf] cousin domain definition (was Re… Murray S. Kucherawy
- Re: [dmarc-ietf] cousin domain definition (was Re… Matt Simerson
- Re: [dmarc-ietf] cousin domain definition (was Re… Matt Simerson
- Re: [dmarc-ietf] cousin domain definition (was Re… Dave Crocker
- Re: [dmarc-ietf] cousin domain definition (was Re… MH Michael Hammer (5304)
- Re: [dmarc-ietf] cousin domain definition (was Re… Steve Jones
- Re: [dmarc-ietf] cousin domain definition (was Re… Barry Leiba
- Re: [dmarc-ietf] cousin domain definition (was Re… Scott Kitterman
- Re: [dmarc-ietf] cousin domain definition (was Re… Steve Jones
- Re: [dmarc-ietf] cousin domain definition (was Re… Matt Simerson