IETF Logo Mail Archive

Re: [Bimi] Bimi logo hosting

Mark Alley <mark.alley@tekmarc.com> Mon, 25 September 2023 19:50 UTC

Return-Path: <mark.alley@tekmarc.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 4B43CC16B5A0 for <bimi@ietfa.amsl.com>; Mon, 25 Sep 2023 12:50:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.196
X-Spam-Level:
X-Spam-Status: No, score=-7.196 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, NICE_REPLY_A=-0.091, RCVD_IN_DNSWL_HI=-5, 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=tekmarc.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 lAGj9ohyi0be for <bimi@ietfa.amsl.com>; Mon, 25 Sep 2023 12:50:13 -0700 (PDT)
Received: from mail-yb1-xb2f.google.com (mail-yb1-xb2f.google.com [IPv6:2607:f8b0:4864:20::b2f]) (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 0A094C16B5A8 for <bimi@ietf.org>; Mon, 25 Sep 2023 12:50:12 -0700 (PDT)
Received: by mail-yb1-xb2f.google.com with SMTP id 3f1490d57ef6-d894b8b9b7cso1628558276.1 for <bimi@ietf.org>; Mon, 25 Sep 2023 12:50:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tekmarc.com; s=google; t=1695671411; x=1696276211; darn=ietf.org; h=in-reply-to:from:references:to:content-language:subject:user-agent :mime-version:date:message-id:from:to:cc:subject:date:message-id :reply-to; bh=GZVLZit26lh8mjBqC3Anft8KtsPhB5lMMFq383CIYG0=; b=ZhKjMK5nZkiyCmh64nOvbKNbFfaMa/F+3QZOsUP/Eo8IJBxnb42b1ib7KzbC5wxGqE zw8Ytnsm0CDwB1kLLqngdPQGzFHBu9JLN/24ddLNS2rbGvFCIKlXxcOz3vQWrJLE/O2v 7rF7o9uZb5Z8DIC7BBd+1al3tTtL6FX9AkKRbOr8X9r38YaZgvpkAnf5Agejr336uJEg M1EccKTqryi7X8oY6LIdsNmfdNxlG7Ru+U47qgRRIiDna1FoC7QDm02CzF8NhkmLJMZ4 3pc19eirut1C14Hjt4KtqJiTDNZN6Fzdf/CYET1F4kmlnTO4CJQIiOCT8d/Moq9K15Ww Ui2w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1695671411; x=1696276211; h=in-reply-to:from:references:to:content-language:subject:user-agent :mime-version:date:message-id:x-gm-message-state:from:to:cc:subject :date:message-id:reply-to; bh=GZVLZit26lh8mjBqC3Anft8KtsPhB5lMMFq383CIYG0=; b=o6dAxmMHkN6AhS5/MW+Zl0GzUZtrlnB1oFY1yEzBD4+MUug6Lhz6crP459XGbn/FO7 6Yj+k+TUJWpOpxggySOZkhznuELUAbncW0bQOOUgPaEDZFo/BzvN+vdtoQ6Spoz6CP+I ITR8rJ+8kI1BYpBIpkO80vW0ztD6ys8AWaLfMOEmKo+EQaxgAS6mYFEe8S6jN0LUh6dB nH1u6jrjt/nh+KOvr2LVCNxmCfCKPF7jDaRtOnLNtnudM5uwC7L504vIRsxR8IADQwVn MLefJgQuaqu7DU0eKuoc41dhp69QxlYG3WebjJqBxRCjb+Tb7SCJeLnEdGYEG8mV3x2h mkwg==
X-Gm-Message-State: AOJu0YwMC9cPl7MT5U+GQEw0uue848FGCNmsfAPvxFt1IQl91h7Ofnnx mMK3jkpNY0cd1iYTkpVwFf9OwZeL9Ypv3kdHxeuG1w==
X-Google-Smtp-Source: AGHT+IFGfRbnHppOQJZiXy13JjgFvWq0GjLCEaxDTGidD7lKGs9biqW4lFQOkygQNg/GDHQuahNrAQ==
X-Received: by 2002:a25:abf3:0:b0:d81:67c4:181c with SMTP id v106-20020a25abf3000000b00d8167c4181cmr478377ybi.16.1695671411091; Mon, 25 Sep 2023 12:50:11 -0700 (PDT)
Received: from [192.168.2.20] (162-238-103-217.lightspeed.brhmal.sbcglobal.net. [162.238.103.217]) by smtp.gmail.com with ESMTPSA id x8-20020a259a08000000b00d7b8a1074d4sm2245784ybn.57.2023.09.25.12.50.10 for <bimi@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 25 Sep 2023 12:50:10 -0700 (PDT)
Content-Type: multipart/alternative; boundary="------------Vl0c4HajHn0Q6BT4dklhfxQ8"
Message-ID: <47719179-cf86-7a48-7624-4c3e0f9a1019@tekmarc.com>
Date: Mon, 25 Sep 2023 14:50:10 -0500
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.15.1
Content-Language: en-US
To: bimi@ietf.org
References: <f2cf5e6c-d177-8eac-bfea-54fd15703b6a@iovo.me> <MN2PR11MB43516B9DFDAE5B4CF1798D14F7FCA@MN2PR11MB4351.namprd11.prod.outlook.com>
From: Mark Alley <mark.alley@tekmarc.com>
In-Reply-To: <MN2PR11MB43516B9DFDAE5B4CF1798D14F7FCA@MN2PR11MB4351.namprd11.prod.outlook.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/bimi/B-i5mntUS_LJbCxyK865VLP6ySM>
Subject: Re: [Bimi] Bimi logo hosting
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: Mon, 25 Sep 2023 19:50:17 -0000

I know of several organizations hosting their logos and certificates 
through Entrust (i.e. the cert and logo hosting domain are Entrust's), 
and as far as I'm aware they have not had any issues with Google 
displaying their logos, although if Google's policy on that changed 
recently, take that with a grain of salt.

- Mark Alley


On 9/25/2023 1:52 PM, Brotman, Alex wrote:
>
> As far as the spec is concerned, you can definitely host on a separate 
> domain/server.  I suppose it’s possible that some MBP may decide that 
> could be a risk, I’m not aware of any that have done this yet.
>
> See:
>
> default._bimi.emails.xfinity.com. 10800 IN TXT 
> "v=BIMI1;a=https://postmaster.comcast.net/bimi_logos/emails.xfinity.com.pem;l=https://postmaster.comcast.net/bimi_logos/xfinity.svg"
>
> I’m not aware we’ve had issues because they weren’t on the same domain.
>
> -- 
>
> Alex Brotman
>
> Sr. Engineer, Anti-Abuse & Messaging Policy
>
> Comcast
>
> *From:* bimi <bimi-bounces@ietf.org> *On Behalf Of * Ivan Hadzhiev
> *Sent:* Monday, September 25, 2023 10:15 AM
> *To:* bimi@ietf.org
> *Subject:* [Bimi] Bimi logo hosting
>
> Hello,
>
> I've a simple question.
>
> I read the FAQ questions on bimigroup.org.
>
> *Is it a problem if I want to have BIMI on myemaildomain.com but the 
> images (the image path) is myimagehost.com?*
> The logo referenced by the “l=” value in the BIMI record can resolve 
> to any domain and directory path. It does not need to match the domain 
> where the BIMI logo is published.
>
> Then i read the google Troubleshoot BIMI issues:
>
> BIMI image issues
>
>   * Verify the SVG file for your brand logo meets the requirements and
>     recommendations for BIMI image files.
>   * Verify the SVG file is accessible on your public web server.
>   * *Verify the public web server is in the same domain as the domain
>     where you added the DNS TXT record for BIMI.*
>   * Verify the URL for the SVG file is correct in your BIMI record.
>
> Which one is correct?
>
> If i host my logo on 3rd party server could that be a problem?
>
> Thank you.
>
> P.S.
>
> I've dmarc p=reject, and VMC, so there is no other reason to not show 
> my logo instead of hosting.
>
> Also the bimi record passed all available checks.
>
>

v2.23.0 | Report a Bug | By Email