IETF Logo Mail Archive

Re: [dmarc-ietf] Review of draft-kucherawy-dmarc-base-00 (was:Fwd: Eliot's review of the DMARC spec)

Franck Martin <fmartin@linkedin.com> Sat, 06 July 2013 19:15 UTC

Return-Path: <prvs=892313021=fmartin@linkedin.com>
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 06F0C21F9B94 for <dmarc@ietfa.amsl.com>; Sat, 6 Jul 2013 12:15:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.19
X-Spam-Level:
X-Spam-Status: No, score=-6.19 tagged_above=-999 required=5 tests=[AWL=0.075, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_MED=-4]
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 Vy3TmH7GPdFM for <dmarc@ietfa.amsl.com>; Sat, 6 Jul 2013 12:15:33 -0700 (PDT)
Received: from esv4-mav05.corp.linkedin.com (esv4-mav05.corp.linkedin.com [69.28.149.81]) by ietfa.amsl.com (Postfix) with ESMTP id 7394521F9C4E for <dmarc@ietf.org>; Sat, 6 Jul 2013 12:15:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linkedin.com; i=@linkedin.com; q=dns/txt; s=proddkim1024; t=1373138131; x=1404674131; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=vjlJDNLFsHw718OrNrA+kJiYBLi2UFymqHpVc77tTR0=; b=pNM7+FQ/Q7RmzrIWVkUa1KLoM6iOWqWrDGvZLrjLmrYDAIV5uazpTCkZ iCoUkCDMmj4neHBFKBXnnKHJ2arI+ylGq97GUsLSBz69IxGoNLx/oEKQv /gn6LX+cyb9tGQes6cI8YeZPq5Sj0lj6/phoEloGjm8lkYc7pVsmjiJdl E=;
X-IronPort-AV: E=Sophos;i="4.87,1010,1363158000"; d="scan'208";a="54887137"
Received: from esv4-exctest.linkedin.biz (172.18.46.60) by esv4-cas01.linkedin.biz (172.18.46.140) with Microsoft SMTP Server (TLS) id 14.2.328.11; Sat, 6 Jul 2013 12:15:14 -0700
Received: from ESV4-MBX02.linkedin.biz ([fe80::20f1:6264:6880:7fc7]) by esv4-exctest.linkedin.biz ([::1]) with mapi id 14.02.0328.009; Sat, 6 Jul 2013 12:15:14 -0700
From: Franck Martin <fmartin@linkedin.com>
To: SM <sm@resistor.net>
Thread-Topic: [dmarc-ietf] Review of draft-kucherawy-dmarc-base-00 (was:Fwd: Eliot's review of the DMARC spec)
Thread-Index: AQHOenNZRnhBwLurRkCph9DVdvyg+JlYesqA
Date: Sat, 06 Jul 2013 19:15:14 +0000
Message-ID: <77426B543150464AA3F30DF1A91365DE53A7FE84@ESV4-MBX02.linkedin.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> <6.2.5.6.2.20130706105143.0d56b5f8@resistor.net>
In-Reply-To: <6.2.5.6.2.20130706105143.0d56b5f8@resistor.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [172.18.46.253]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <6F0F947CB6144A4D8AC650428EF5142F@linkedin.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<dmarc@ietf.org>" <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 19:15:37 -0000

On Jul 6, 2013, at 11:01 AM, SM <sm@resistor.net> wrote:

> 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.
> 
Sure, but if you don't provide guidance in this document for implementors, where will you give it?

v2.23.0 | Report a Bug | By Email