IETF Logo Mail Archive

[Tools-discuss] Re: IETF mail service outage planned for 1200 UTC on 27 June 2024

Michael Richardson <mcr+ietf@sandelman.ca> Tue, 25 June 2024 21:18 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: tools-discuss@ietfa.amsl.com
Delivered-To: tools-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C64CCC1840FC for <tools-discuss@ietfa.amsl.com>; Tue, 25 Jun 2024 14:18:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.106
X-Spam-Level:
X-Spam-Status: No, score=-7.106 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_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=sandelman.ca
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 lNu_NK2GrMaT for <tools-discuss@ietfa.amsl.com>; Tue, 25 Jun 2024 14:18:23 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D66E9C14F5EE for <tools-discuss@ietf.org>; Tue, 25 Jun 2024 14:18:23 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 63E013898F; Tue, 25 Jun 2024 17:18:22 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 2Ohn36vh3t3v; Tue, 25 Jun 2024 17:18:19 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id D60D53898E; Tue, 25 Jun 2024 17:18:18 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sandelman.ca; s=mail; t=1719350298; bh=quEc2P9Iu8yBF0V/JCwhE6ZuxYVXFHtkZwzwX3VZUjw=; h=From:To:cc:Subject:In-Reply-To:References:Date:From; b=iad1QhZvcKi586MxGqef8pv1qeAIQ3p9MxbrH7AKigPrxQRFjHB5kyU3g0RQq/ZJD iajQig5JXAl4DuKHvfZK+23Hs/RBdOQ2dGQukg63pikEHPFwWUcaMfXvxirAphuOD3 DNWQVZou32bq5EKAHgQ5rtD9ynjjXhioH83DDf/RZ8ND7qxhs7maYESCtNyVzy2UXW sIPmZ09LQDCuLCsO9b/Eslfbmb9Qa6nUJj0rcXBVh1NtzkSywYlGT7xc1rJaE719Av FF8lqOVDUD3opAJIPQyaNBwoMimW3EktTO8+HBZqTKHFmID+NyMajyAtAuI82LDKBe ZcoQLfyHSUDPg==
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id CBFC1238; Tue, 25 Jun 2024 17:18:18 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: S Moonesamy <sm+ietf@elandsys.com>
In-Reply-To: <6.2.5.6.2.20240625132230.194bcfa8@elandnews.com>
References: <f6857f95-f096-4f45-9fbd-c8c51efd0c7e@nostrum.com> <6.2.5.6.2.20240625132230.194bcfa8@elandnews.com>
X-Mailer: MH-E 8.6+git; nmh 1.8+dev; GNU Emacs 28.2
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0;<'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Tue, 25 Jun 2024 17:18:18 -0400
Message-ID: <22675.1719350298@obiwan.sandelman.ca>
Message-ID-Hash: AQJ34SV6Q2O4BBOZTV574RJYI7ANB6AU
X-Message-ID-Hash: AQJ34SV6Q2O4BBOZTV574RJYI7ANB6AU
X-MailFrom: mcr+ietf@sandelman.ca
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-tools-discuss.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: tools-discuss@ietf.org
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [Tools-discuss] Re: IETF mail service outage planned for 1200 UTC on 27 June 2024
List-Id: IETF Tools Discussion <tools-discuss.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/ePXfH1cHw8PnaqK2oyCBXe25Mr4>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tools-discuss>
List-Help: <mailto:tools-discuss-request@ietf.org?subject=help>
List-Owner: <mailto:tools-discuss-owner@ietf.org>
List-Post: <mailto:tools-discuss@ietf.org>
List-Subscribe: <mailto:tools-discuss-join@ietf.org>
List-Unsubscribe: <mailto:tools-discuss-leave@ietf.org>

S Moonesamy <sm+ietf@elandsys.com> wrote:
    > There is a SPF include for amazonses.com.  Does the above mean that the
    > mail traffic for ietf.org mailing lists will be sent through the
    > following IP addresses:

>   3.161.94.70 3.161.94.112 3.161.94.102 3.161.94.51

I get different answers for amazonses.com.
A bunch of 108.138.106.x IPv4, and no IPv6!
But that's not the included SPF list, which is different again, and also no IPv6.
This concerns me if ietf will no longer deliver over IPv6.

    > Are those IP addresses also used by other AWS customers?

Are you concerned that you will be unable to block other AWS customers
without also blocking ietf.org?

--
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide

v2.39.1 | Report a Bug | By Email | System Status