IETF Logo Mail Archive

Re: [Ietf-dkim] Adding an aim= tag to DKIM Signature Tag Specifications

Alessandro Vesely <vesely@tana.it> Tue, 12 May 2020 16:30 UTC

Return-Path: <vesely@tana.it>
X-Original-To: ietf-dkim@ietfa.amsl.com
Delivered-To: ietf-dkim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4EBE33A0363 for <ietf-dkim@ietfa.amsl.com>; Tue, 12 May 2020 09:30:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1152-bit key) header.d=tana.it
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 LzO_9qi6H-kv for <ietf-dkim@ietfa.amsl.com>; Tue, 12 May 2020 09:30:26 -0700 (PDT)
Received: from wmail.tana.it (wmail.tana.it [62.94.243.226]) (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 DD4FF3A02BE for <ietf-dkim@ietf.org>; Tue, 12 May 2020 09:30:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1589301023; bh=uFwX/y7a1YBBd0cCkudMTS/1lWGLXM/W7U+c2UL3I5Y=; l=727; h=To:Cc:References:From:Date:In-Reply-To; b=BdUeOIw9KvFg9wsaXXlk8MSR/MuTrvz2KsBWsgXc8DO8YJSHxzkQy7lS+VagcMonA W8JGhFOgon4/2KdMTTCDtVQh9lhPs5KwIsBRlGMSIT8awgkd/snpsY8c1mQKRqrfnF PFVfaSUeRfmQBEjHXnbWrIielODUu2udLjDed5tEIaj7q2hbEVsUpxxZDRoKv
Authentication-Results: tana.it; auth=pass (details omitted)
Received: from [172.25.197.111] (pcale.tana [172.25.197.111]) (AUTH: CRAM-MD5 uXDGrn@SYT0/k, TLS: TLS1.2, 128bits, ECDHE_RSA_AES_128_GCM_SHA256) by wmail.tana.it with ESMTPSA id 00000000005DC09F.000000005EBACF1F.00002AFF; Tue, 12 May 2020 18:30:23 +0200
To: "Murray S. Kucherawy" <superuser@gmail.com>
Cc: ietf-dkim@ietf.org
References: <80533fb3-75a2-1d60-801d-c54d735d4094@tana.it> <7ac84ebf-e30b-6288-81c2-4a6631471d74@dcrocker.net> <5d9709d4-fd1e-9275-6a36-dfc6e7fca97b@bluepopcorn.net> <486245c5-d261-c6df-560b-f022c1ebabd5@dcrocker.net> <551162f8-6c95-071c-3b2e-6a265b1c9783@tana.it> <CAL0qLwYDxA7uyLp6h19P5iSVH0eVen0aEGKRic9BrV=C7gC68Q@mail.gmail.com>
From: Alessandro Vesely <vesely@tana.it>
Message-ID: <c975c01e-c3a5-a0d6-dba6-f4a1c245ab56@tana.it>
Date: Tue, 12 May 2020 18:30:23 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.7.0
MIME-Version: 1.0
In-Reply-To: <CAL0qLwYDxA7uyLp6h19P5iSVH0eVen0aEGKRic9BrV=C7gC68Q@mail.gmail.com>
Content-Type: text/plain; charset="us-ascii"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-dkim/9sizpbqgpkyBJC90k0res4gXpXw>
Subject: Re: [Ietf-dkim] Adding an aim= tag to DKIM Signature Tag Specifications
X-BeenThere: ietf-dkim@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF DKIM List <ietf-dkim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-dkim>, <mailto:ietf-dkim-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-dkim/>
List-Post: <mailto:ietf-dkim@ietf.org>
List-Help: <mailto:ietf-dkim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-dkim>, <mailto:ietf-dkim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 May 2020 16:30:27 -0000

On Tue 12/May/2020 17:48:38 +0200 Murray S. Kucherawy wrote:
> On Tue, May 12, 2020 at 1:20 AM Alessandro Vesely <vesely@tana.it> wrote:
>> On Mon 11/May/2020 20:23:12 +0200 Murray S. Kucherawy wrote:
>>> Indeed; why would I believe what any given domain claims in this tag?
>>
>> If you trust the domain, you can as well trust their tagging.
>>
> 
> If you trust the domain, you don't need their tagging.


Why not?  I may trust gmail, say.  Yet, in order to learn what restrictions
they apply to the From: I have to create an account and try.  There is no
standard location where they declare their policy in a machine-readable manner,
and policies written in legalese are even less readable...


Best
Ale
--

v2.23.0 | Report a Bug | By Email