Re: [spfbis] RFC7208 4.6.4 Interpretation - MX Lookup Count Inconsistencies
Tim Wicinski <tjw.ietf@gmail.com> Mon, 23 January 2023 03:52 UTC
Return-Path: <tjw.ietf@gmail.com>
X-Original-To: spfbis@ietfa.amsl.com
Delivered-To: spfbis@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CD115C14CEFC for <spfbis@ietfa.amsl.com>; Sun, 22 Jan 2023 19:52:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.094
X-Spam-Level:
X-Spam-Status: No, score=-2.094 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, 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=gmail.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 nbjRhTbdWnkP for <spfbis@ietfa.amsl.com>; Sun, 22 Jan 2023 19:51:57 -0800 (PST)
Received: from mail-ej1-x62a.google.com (mail-ej1-x62a.google.com [IPv6:2a00:1450:4864:20::62a]) (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 BFB13C14F72D for <spfbis@ietf.org>; Sun, 22 Jan 2023 19:51:57 -0800 (PST)
Received: by mail-ej1-x62a.google.com with SMTP id hw16so27189224ejc.10 for <spfbis@ietf.org>; Sun, 22 Jan 2023 19:51:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=Ey7W08gFWavWUKcInFXGbf2+gQAutbifK0o8FbNKdGQ=; b=pM+nmSZRjruh9y/tLEVdgnNKips+HF/Is8f+8/g/7Q448L/1ySu/shkUHddo5Tnflh KP+dbefDYWmg6yApx9EyahGkn1va195za2LdKS2FtmPnRSmNnKKXOSNfVukGqEvjYFuo 9CmUNrcITAz11ZQeNN674gvhRW5YExeH2lLZnNi+p5VwkID0ScKVPEEFaQznX9oYqPVh ITznMojitKhRfUDsihOYmmkn1vZgq4KeqPUvpnDyFhXdEJtfvjVSSV96YLS4in2A6tIl wtOF45zVQDBWierDkZyrYtAlzEhozxjj2aAeaar6sIr9Q5l278oPNHrETC0cDEpwwk1W xozQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=Ey7W08gFWavWUKcInFXGbf2+gQAutbifK0o8FbNKdGQ=; b=FzoaokGmJK48Um6CZluFc86FImTj1d11GQ0VWgeJUMRUTgtObCiURMH6PhHg4oLe19 xu6rbjxIVX4Rv7Lr6ud9Z934KWs1o2+wpDA/rOYn0GPOE4XVGRgOP8bKCvRz5CqYBFZG XWsZ7yZhOFeRdOWkGChZ5hwrqbLuv/Q5U++EBTiHq2T1SBpFFj40j/7TCZuk+NvwY/wg DMlwjaL9b5y1k6iZuyrI+Q7gkSPXe+c9v/PXeeUyLNGPZy+ThlootoolMzeIXwL9LonN auoaYaKaS1x4B3dzhi8GoYqFO51NC7vxZzXbwxL8eftJV0eyMWqiIttzCZXB06OO5EXW MEZQ==
X-Gm-Message-State: AFqh2krt8o+VjW0KqEFlsD4DcF+DWfwlJLgon3tmW78yRnM8pRpeaVy6 wFo8BDar151AUDCw+eaKGEy3qSBpGbw0KMR+yVhFJq9+
X-Google-Smtp-Source: AMrXdXuIIbfcRPjhvnuXnosAL5DlUNeytaZulFHkWw5jXe/RnB7XtFgWUOnsxg35NcRjkyBHPgRGCUpDw6bgGxpxVBM=
X-Received: by 2002:a17:906:670b:b0:86f:a21d:62c9 with SMTP id a11-20020a170906670b00b0086fa21d62c9mr2073941ejp.248.1674445915834; Sun, 22 Jan 2023 19:51:55 -0800 (PST)
MIME-Version: 1.0
References: <CADyWQ+FRgUPOC3OiMZ74kbD9Mn+r=Z51meY7uTZutfAJDr6ssQ@mail.gmail.com> <20230123031354.527A67D6DA86@ary.qy>
In-Reply-To: <20230123031354.527A67D6DA86@ary.qy>
From: Tim Wicinski <tjw.ietf@gmail.com>
Date: Sun, 22 Jan 2023 22:51:44 -0500
Message-ID: <CADyWQ+EExQj2H4eL-VW39GM7zdF3CiCrgDJP7PSjzh0oddJpbw@mail.gmail.com>
To: John Levine <johnl@taugh.com>
Cc: spfbis@ietf.org
Content-Type: multipart/alternative; boundary="0000000000000253bb05f2e6526c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/spfbis/Tj5jPuuqrL3awbmhzKpEMDQC7rA>
Subject: Re: [spfbis] RFC7208 4.6.4 Interpretation - MX Lookup Count Inconsistencies
X-BeenThere: spfbis@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: SPFbis discussion list <spfbis.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spfbis>, <mailto:spfbis-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spfbis/>
List-Post: <mailto:spfbis@ietf.org>
List-Help: <mailto:spfbis-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spfbis>, <mailto:spfbis-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Jan 2023 03:52:01 -0000
I am always happy when I'm proven wrong. Thanks Mr. John. tim On Sun, Jan 22, 2023 at 10:13 PM John Levine <johnl@taugh.com> wrote: > It appears that Tim Wicinski <tjw.ietf@gmail.com> said: > >I also feel that technology stacks have matured over time. Jan, do you > see > >real world examples of a domain with 11 MX servers? > > Well, there's Comcast: > > $ host -t mx comcast.net > comcast.net mail is handled by 50 mx1a1.comcast.net. > comcast.net mail is handled by 5 mx2.mxge.comcast.net. > comcast.net mail is handled by 50 mx2a1.comcast.net. > comcast.net mail is handled by 50 mx1c1.comcast.net. > comcast.net mail is handled by 5 mx1.mxge.comcast.net. > comcast.net mail is handled by 50 mx2c1.comcast.net. > comcast.net mail is handled by 50 mx1h1.comcast.net. > comcast.net mail is handled by 50 mx2h1.comcast.net. > > And there's Yahoo, but its MX is only four lookups: > > $ host -t mx yahoo.com > yahoo.com mail is handled by 1 mta6.am0.yahoodns.net. > yahoo.com mail is handled by 1 mta7.am0.yahoodns.net. > yahoo.com mail is handled by 1 mta5.am0.yahoodns.net. > > $ host mta5.am0.yahoodns.net. > mta5.am0.yahoodns.net has address 67.195.228.109 > mta5.am0.yahoodns.net has address 98.136.96.76 > mta5.am0.yahoodns.net has address 67.195.204.72 > mta5.am0.yahoodns.net has address 67.195.204.79 > mta5.am0.yahoodns.net has address 67.195.228.111 > mta5.am0.yahoodns.net has address 98.136.96.77 > mta5.am0.yahoodns.net has address 67.195.228.110 > mta5.am0.yahoodns.net has address 98.136.96.91 > $ host mta6.am0.yahoodns.net. > mta6.am0.yahoodns.net has address 67.195.204.74 > mta6.am0.yahoodns.net has address 98.136.96.76 > mta6.am0.yahoodns.net has address 67.195.228.110 > mta6.am0.yahoodns.net has address 67.195.204.79 > mta6.am0.yahoodns.net has address 67.195.204.77 > mta6.am0.yahoodns.net has address 67.195.228.111 > mta6.am0.yahoodns.net has address 67.195.228.94 > mta6.am0.yahoodns.net has address 98.136.96.77 > $ host mta7.am0.yahoodns.net. > mta7.am0.yahoodns.net has address 67.195.204.79 > mta7.am0.yahoodns.net has address 67.195.204.77 > mta7.am0.yahoodns.net has address 98.136.96.91 > mta7.am0.yahoodns.net has address 67.195.228.111 > mta7.am0.yahoodns.net has address 67.195.228.106 > mta7.am0.yahoodns.net has address 67.195.228.94 > mta7.am0.yahoodns.net has address 67.195.204.72 > mta7.am0.yahoodns.net has address 98.136.96.77 > > And Charter: > > $ host -t mx charter.com > charter.com mail is handled by 10 nce.mail.chartercom.com. > charter.com mail is handled by 10 ncw.mail.chartercom.com. > > $ host nce.mail.chartercom.com. > nce.mail.chartercom.com has address 142.136.234.134 > nce.mail.chartercom.com has address 142.136.234.135 > nce.mail.chartercom.com has address 142.136.234.136 > nce.mail.chartercom.com has address 142.136.234.137 > nce.mail.chartercom.com has address 142.136.234.138 > nce.mail.chartercom.com has address 142.136.234.139 > nce.mail.chartercom.com has address 142.136.234.142 > nce.mail.chartercom.com has address 142.136.234.143 > nce.mail.chartercom.com has address 142.136.234.144 > > $ host ncw.mail.chartercom.com. > ncw.mail.chartercom.com has address 142.136.235.134 > ncw.mail.chartercom.com has address 142.136.235.135 > ncw.mail.chartercom.com has address 142.136.235.136 > ncw.mail.chartercom.com has address 142.136.235.137 > ncw.mail.chartercom.com has address 142.136.235.138 > ncw.mail.chartercom.com has address 142.136.235.139 > ncw.mail.chartercom.com has address 142.136.235.142 > ncw.mail.chartercom.com has address 142.136.235.143 > ncw.mail.chartercom.com has address 142.136.235.144 > > I occasionally see spammy looking hosts with a lot > of MX'es but if their SPF checks fail, who cares. > > R's, > John >
- [spfbis] RFC7208 4.6.4 Interpretation - MX Lookup… Mark Alley
- Re: [spfbis] RFC7208 4.6.4 Interpretation - MX Lo… Mark Alley
- Re: [spfbis] RFC7208 4.6.4 Interpretation - MX Lo… Mark Alley
- Re: [spfbis] RFC7208 4.6.4 Interpretation - MX Lo… Scott Kitterman
- Re: [spfbis] RFC7208 4.6.4 Interpretation - MX Lo… Mark Alley
- Re: [spfbis] RFC7208 4.6.4 Interpretation - MX Lo… Jan Schaumann
- Re: [spfbis] RFC7208 4.6.4 Interpretation - MX Lo… Jan Schaumann
- Re: [spfbis] RFC7208 4.6.4 Interpretation - MX Lo… Scott Kitterman
- Re: [spfbis] RFC7208 4.6.4 Interpretation - MX Lo… Jan Schaumann
- Re: [spfbis] RFC7208 4.6.4 Interpretation - MX Lo… Scott Kitterman
- Re: [spfbis] RFC7208 4.6.4 Interpretation - MX Lo… Tim Wicinski
- Re: [spfbis] RFC7208 4.6.4 Interpretation - MX Lo… John Levine
- Re: [spfbis] RFC7208 4.6.4 Interpretation - MX Lo… Tim Wicinski
- Re: [spfbis] RFC7208 4.6.4 Interpretation - MX Lo… Jan Schaumann
- Re: [spfbis] RFC7208 4.6.4 Interpretation - MX Lo… william
- Re: [spfbis] RFC7208 4.6.4 Interpretation - MX Lo… John R Levine
- Re: [spfbis] RFC7208 4.6.4 Interpretation - MX Lo… Klaus Frank