Re: [Bimi] Proposal to Clarify Role of MUA in BIMI Evaluation
Todd Herr <todd.herr@valimail.com> Wed, 20 July 2022 13:16 UTC
Return-Path: <todd.herr@valimail.com>
X-Original-To: bimi@ietfa.amsl.com
Delivered-To: bimi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 41827C13C515 for <bimi@ietfa.amsl.com>; Wed, 20 Jul 2022 06:16:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.105
X-Spam-Level:
X-Spam-Status: No, score=-2.105 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, HTML_MESSAGE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=valimail.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HsIPHd8mGmSJ for <bimi@ietfa.amsl.com>; Wed, 20 Jul 2022 06:16:29 -0700 (PDT)
Received: from mail-yb1-xb2d.google.com (mail-yb1-xb2d.google.com [IPv6:2607:f8b0:4864:20::b2d]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 50789C14F74F for <bimi@ietf.org>; Wed, 20 Jul 2022 06:16:29 -0700 (PDT)
Received: by mail-yb1-xb2d.google.com with SMTP id i14so32048261yba.1 for <bimi@ietf.org>; Wed, 20 Jul 2022 06:16:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=valimail.com; s=google2048; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=4c/9513Q/TRz3YJa4yTxFkq9jq96XAGHdifisuvEK6M=; b=UnCGNX7jnQKiFrPUBx915nyyb4+nN3GZBVtbbHgiqgXZmI44OPTjfbgfXHQ4BpFrHs bknS5xJO17mydlVgg5UxRhTWjD5ITSIPggCzL7mEcTIRzOJuuVn2VyEvMfXS/uMIW9qx 9OCco2H+d8zezQeJFOlKZJnALZMNrKgG1DaMvfuc94iAY5u2koaFHNhU+pPH9pIc6IAf gRkK7HFVptKNGbPGkTKSqouH7xHY83RcGUKWB57j+CVXrkYC2c8gfVZmGNC0CtNiTyuv je8HIqV5ikvooVdT2BzQVegQDZfZjMYeCnb1kl1TG0+5IEgdo8HP9XoHDsVfv00cZ1Wy r/PA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=4c/9513Q/TRz3YJa4yTxFkq9jq96XAGHdifisuvEK6M=; b=ZK8NiXzDJwwQ0UdtMdg8gGSEGxJsZnZMGR55j/Xm9L6FzUrb6k6udS7oDwfXICEYRC uESEJrOgvPnn/Z1X/yYweupz/AQOavRT9NANEa+8Uu0vhg6oimfB1/pZWccyWSmFIkdY CP8yAOJC+WlxqU1XlEqlLBdx8YHXOTlC1DV1tfEYxwB/HBZng1+GthW7Ce9tBEyGxURq Rs+V/PJEq9WHqW1GNbVO0aFMs8k0XNKXO1H427m4ntbzXMYQ//lt9Vw55NFuifO/0NmN pWkslqQKBB8xTivPYrIIFJiMFvAtxLjeSa1lYlg/MMBx3P4nCtQJqDrwQNEQ/pZodefX M2sA==
X-Gm-Message-State: AJIora8B0Z7l64jzV79XoR07G9tKA4cY8x0WjQpWKJD54TL+K6aucOUV aum/dhhmK5pQ5YeQwBMr1hzp+pXFQF2k9FX1dEDh7tmIFFk=
X-Google-Smtp-Source: AGRyM1t5RNyNJzlqaYhqy0y/88ofmeTtN4bA7LiteskbJNuyxwz4xEI/FIF2G3tyMPsXSHooFmOunnE+vtNIQkHKAcs=
X-Received: by 2002:a05:6902:211:b0:670:852c:4f44 with SMTP id j17-20020a056902021100b00670852c4f44mr6550496ybs.551.1658322987246; Wed, 20 Jul 2022 06:16:27 -0700 (PDT)
MIME-Version: 1.0
References: <DE61AC51-4BC3-44FF-862D-7D8ADFB3BC29@proofpoint.com> <20CBD506-7E50-4161-ADE6-64614630B1B2@proofpoint.com> <CAHej_8kridbc322MDRpxfgd+8Y2yNacxTAtvr+HF=+wevdRQhw@mail.gmail.com> <VI1PR01MB70538965904FD08A49F75C37C78C9@VI1PR01MB7053.eurprd01.prod.exchangelabs.com> <11A2B052-A26C-4A9C-9D88-72B594DA1C59@proofpoint.com> <VI1PR01MB70537BA29DA1F456B858C17FC78C9@VI1PR01MB7053.eurprd01.prod.exchangelabs.com> <6993E8B6-11A0-4AF3-A94E-044F880E56BC@proofpoint.com> <CAHej_8kjwtGE4rDrXfTpgThOD-jh7t0GK9EUnVjVZT_OJzzsvg@mail.gmail.com> <VI1PR01MB705353E36328899609DE2471C78C9@VI1PR01MB7053.eurprd01.prod.exchangelabs.com> <12a85dfe-664f-d757-0fa2-81f17c8088c2@dcrocker.net> <4e9ab94e-8675-df70-3e4b-00edcedb266e@dcrocker.net> <5DE65D46-853F-4F61-ADA7-20CB5E7E6840@kitterman.com> <7f030278-3f9b-c8ea-f9eb-644f006cded9@dcrocker.net> <CC11EF68-1E27-41CD-AE2D-AC26DA261EAD@kitterman.com> <CAHej_8mNCTw0LpnWTBCpqZJhHQcDgrsC4truK1dD_-HbyVgsWA@mail.gmail.com> <DM8PR14MB5237459AC795AE826FDDA198838F9@DM8PR14MB5237.namprd14.prod.outlook.com> <qnuJf0TDr11iFAcB@highwayman.com> <CAHej_8kySKk4_F3eVDRQU4ABjs3JUg4Z9UipTwGJE2nSJQ5SJA@mail.gmail.com> <U4H2IKEmq$1iFAbY@highwayman.com>
In-Reply-To: <U4H2IKEmq$1iFAbY@highwayman.com>
From: Todd Herr <todd.herr@valimail.com>
Date: Wed, 20 Jul 2022 09:16:11 -0400
Message-ID: <CAHej_8khwuig8ykrgUWbWErGRZKL1+sz3RtYFs73OtEcMMwVdQ@mail.gmail.com>
To: "bimi@ietf.org" <bimi@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000093fc8f05e43c6857"
Archived-At: <https://mailarchive.ietf.org/arch/msg/bimi/XUF86xrxnPf8yKGjlsbLR_yj7c0>
Subject: Re: [Bimi] Proposal to Clarify Role of MUA in BIMI Evaluation
X-BeenThere: bimi@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Brand Indicators for Message Identification <bimi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bimi>, <mailto:bimi-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bimi/>
List-Post: <mailto:bimi@ietf.org>
List-Help: <mailto:bimi-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bimi>, <mailto:bimi-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Jul 2022 13:16:33 -0000
On Wed, Jul 20, 2022 at 8:54 AM Richard Clayton <richard@highwayman.com> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > In message <CAHej_8kySKk4_F3eVDRQU4ABjs3JUg4Z9UipTwGJE2nSJQ5SJA@mail.gma > il.com>, Todd Herr <todd.herr=40valimail.com@dmarc.ietf.org> writes > > > I'm not clear on what you mean by the phrase "magically available > > for fetching" here. > > > > The current draft of the BIMI specification describes a "BIMI > > Assertion Record" ( > > > https://datatracker.ietf.org/doc/html/draft-brand-indicators-for-message-identification#section-4.2 > > ) as a relatively straightforward DNS TXT record, one making use of > > a tag-value syntax, not unlike a DMARC policy record. > > Exactly ... it requires the DNS record to still exist and short of magic > I know of no way to achieve that for ancient email. At this point in time, even magic wouldn't help, because there'd have been no BIMI record in existence at the time the ancient mail was sent/delivered, for some values of ancient, because BIMI didn't exist at the time. Even going forward, there will be cases where a domain owner sent messages before they chose to publish a BIMI record, and I don't believe that those messages that are older than the domain's BIMI record should have a logo displayed, but DNS doesn't have a wayback machine of which I'm aware. > > Recall that just two days ago you were discussing a "real-world > scenario" involving changing phone and your mail client being faced with > 9GB of stored email > > How many messages should the Mail client try to do BIMI validation > on before the battery on my phone is exhausted and/or the iPhone > becomes a smoldering pile of melted plastic and silicon? > > the answer to the question BTW would be "as many as were about to be > displayed" (since the only value of BIMI is to provide images and if an > email falls into the forest of the far reaches of your inbox it won't > just make no sound, but it won't display an image either!) > The answer to "as many as were about to be displayed" is implementation-dependent. There are currently BIMI implementations where the mailbox provider displays logos only when the message is opened, and others where the logo is displayed in the folder list view as well as when the message is opened. An MUA choosing to display logos in the folder list view and caring not a whit for when the sender's messages qualified for BIMI would potentially be about to display a great number of logos, although I confess I am no longer a coder and I have no idea what kind of resource consumption that might entail. -- *Todd Herr * | Technical Director, Standards and Ecosystem *e:* todd.herr@valimail.com *m:* 703.220.4153 This email and all data transmitted with it contains confidential and/or proprietary information intended solely for the use of individual(s) authorized to receive it. If you are not an intended and authorized recipient you are hereby notified of any use, disclosure, copying or distribution of the information included in this transmission is prohibited and may be unlawful. Please immediately notify the sender by replying to this email and then delete it from your system.
- [Bimi] Proposal to Clarify Role of MUA in BIMI Ev… Trent Adams
- Re: [Bimi] Proposal to Clarify Role of MUA in BIM… Marc Bradshaw
- Re: [Bimi] Proposal to Clarify Role of MUA in BIM… Ken O'Driscoll
- Re: [Bimi] Proposal to Clarify Role of MUA in BIM… Trent Adams
- Re: [Bimi] Proposal to Clarify Role of MUA in BIM… Ken O'Driscoll
- Re: [Bimi] Proposal to Clarify Role of MUA in BIM… Brotman, Alex
- Re: [Bimi] Proposal to Clarify Role of MUA in BIM… John C Klensin
- Re: [Bimi] Proposal to Clarify Role of MUA in BIM… Trent Adams
- Re: [Bimi] Proposal to Clarify Role of MUA in BIM… Todd Herr
- Re: [Bimi] Proposal to Clarify Role of MUA in BIM… Ken O'Driscoll
- Re: [Bimi] Proposal to Clarify Role of MUA in BIM… Trent Adams
- Re: [Bimi] Proposal to Clarify Role of MUA in BIM… Ken O'Driscoll
- Re: [Bimi] Proposal to Clarify Role of MUA in BIM… Trent Adams
- Re: [Bimi] Proposal to Clarify Role of MUA in BIM… Todd Herr
- Re: [Bimi] Proposal to Clarify Role of MUA in BIM… Ken O'Driscoll
- Re: [Bimi] Proposal to Clarify Role of MUA in BIM… Brotman, Alex
- Re: [Bimi] Proposal to Clarify Role of MUA in BIM… Dave Crocker
- Re: [Bimi] Proposal to Clarify Role of MUA in BIM… Dave Crocker
- Re: [Bimi] Proposal to Clarify Role of MUA in BIM… Scott Kitterman
- Re: [Bimi] Proposal to Clarify Role of MUA in BIM… Dave Crocker
- Re: [Bimi] Proposal to Clarify Role of MUA in BIM… Scott Kitterman
- Re: [Bimi] Proposal to Clarify Role of MUA in BIM… Dave Crocker
- Re: [Bimi] Proposal to Clarify Role of MUA in BIM… Dave Crocker
- Re: [Bimi] Proposal to Clarify Role of MUA in BIM… John C Klensin
- Re: [Bimi] Proposal to Clarify Role of MUA in BIM… Dave Crocker
- Re: [Bimi] Proposal to Clarify Role of MUA in BIM… Scott Kitterman
- Re: [Bimi] Proposal to Clarify Role of MUA in BIM… Todd Herr
- Re: [Bimi] Proposal to Clarify Role of MUA in BIM… Dave Crocker
- Re: [Bimi] Proposal to Clarify Role of MUA in BIM… Todd Herr
- Re: [Bimi] Proposal to Clarify Role of MUA in BIM… Dave Crocker
- Re: [Bimi] Proposal to Clarify Role of MUA in BIM… Todd Herr
- Re: [Bimi] Proposal to Clarify Role of MUA in BIM… Tim Hollebeek
- Re: [Bimi] Proposal to Clarify Role of MUA in BIM… Richard Clayton
- Re: [Bimi] Proposal to Clarify Role of MUA in BIM… Todd Herr
- Re: [Bimi] Proposal to Clarify Role of MUA in BIM… Richard Clayton
- Re: [Bimi] Proposal to Clarify Role of MUA in BIM… Todd Herr
- Re: [Bimi] Proposal to Clarify Role of MUA in BIM… Dave Crocker