IETF Logo Mail Archive

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

Jim Reid <jim@rfc1035.com> Tue, 25 June 2024 20:02 UTC

Return-Path: <jim@rfc1035.com>
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 7FE23C151556; Tue, 25 Jun 2024 13:02:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level:
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
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 tnJ46AZIujV8; Tue, 25 Jun 2024 13:02:35 -0700 (PDT)
Received: from shaun.rfc1035.com (smtp.v6.rfc1035.com [IPv6:2001:4b10:100:7::25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D1398C15154F; Tue, 25 Jun 2024 13:02:33 -0700 (PDT)
Received: from smtpclient.apple (gromit.rfc1035.com [195.54.233.69]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by shaun.rfc1035.com (Postfix) with ESMTPSA id E0EBA2420E4A; Tue, 25 Jun 2024 20:02:27 +0000 (UTC)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.600.62\))
From: Jim Reid <jim@rfc1035.com>
In-Reply-To: <a4b9e0a3-1aea-4c7a-9c2a-7064d3696394@nostrum.com>
Date: Tue, 25 Jun 2024 21:02:27 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <547C207F-BB93-46A7-950A-D4ABB651CB2E@rfc1035.com>
References: <a4b9e0a3-1aea-4c7a-9c2a-7064d3696394@nostrum.com>
To: tools-discuss <tools-discuss@ietf.org>
X-Mailer: Apple Mail (2.3774.600.62)
Message-ID-Hash: SWXTJXKRFWZXYNKEDOD5STYGLBGZDUMB
X-Message-ID-Hash: SWXTJXKRFWZXYNKEDOD5STYGLBGZDUMB
X-MailFrom: jim@rfc1035.com
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: IETF discussion list <ietf@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/V3wTA3GXC3q6R06FyQN5vtYqOHk>
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>


> On 25 Jun 2024, at 20:52, Robert Sparks <rjsparks@nostrum.com> wrote:
> 
> This transition moves our primary mail sending to be through AWS. The relevant SPF records have already been updated.

Robert, what IP addresses (blocks) are AWS going to use for this? I can’t be the only IETFer who will need to put these in an allowlist.

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