IETF Logo Mail Archive

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

John Levine <johnl@taugh.com> Wed, 26 June 2024 03:41 UTC

Return-Path: <johnl@iecc.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 7D83CC180B41 for <tools-discuss@ietfa.amsl.com>; Tue, 25 Jun 2024 20:41:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.856
X-Spam-Level:
X-Spam-Status: No, score=-1.856 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, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=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=iecc.com header.b="Zbwke3dd"; dkim=pass (2048-bit key) header.d=taugh.com header.b="XMaDATpf"
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 V-3hF62faqyy for <tools-discuss@ietfa.amsl.com>; Tue, 25 Jun 2024 20:41:25 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 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 9DAECC14F5EA for <tools-discuss@ietf.org>; Tue, 25 Jun 2024 20:41:25 -0700 (PDT)
Received: (qmail 32966 invoked from network); 26 Jun 2024 03:41:23 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=80c3667b8de3.k2406; bh=dpx/IPHq/tvSTzV+IUtUlSSSosIG/r2GLgjJdi/KtU4=; b=Zbwke3ddySEIenC7mITO/bdh3IbUk3HltgQn3yzFWIUXyAQArK7NDR29rMjbd2QH1CyMn2dvdEA+NihkQW9SnnAR5demWe2Jp7G/c7jvHj7AbiitVCZbh5TCBy2MEUlILPAMgmL/WkZhoikw10okLUSOYy08RsuB421XX4+VYJLRagGGu9XRS9CthQUdp4bfmV/B33Q+jIH86CdUDIPv41jeDONC60xoZldz1h3Spc3ySQqDzHZHHY7NBMCfkDKB8lH/HW3upaXuyCoqEvIg+ZjL488ee6zFHPhMKEonOigwzsk9KVCC8lg6/gStt0x4dm/TMHRJH2DqvSpIxzTKvg==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=80c3667b8de3.k2406; bh=dpx/IPHq/tvSTzV+IUtUlSSSosIG/r2GLgjJdi/KtU4=; b=XMaDATpfVsynFl2Y9KFVzB9JZzbQGG06hYm8hq3sYN8f/zcnwG6WLx4bc7IMGRapimiyGQSuwbdSGpSdHBeZZs/Bu11uVa81qhiH86knfqotmgsAW8xA5y+FLZE8HVf/pkRqGEcsSx7aiXlkNvgEKE1EJBsyg8/qSny5Min4jkiCN+5jN1VVDT1qw+kVvmQPIf7YP5igUtK5HE+QeihiZtDZTPPqSig8sg3G13d7Czr4/8tUz5YI48+aMkvgbW5vhyCqKW78Iq2nYnbhWortEsPAfGz8Ko3RsgR00JEMtZsTRcoqf7oLn/pc/mMZN88z6JeaQ7EAV+SoQ+ga+Kq5eg==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.3 ECDHE-RSA CHACHA20-POLY1305 AEAD) via TCP6; 26 Jun 2024 03:41:23 -0000
Received: by ary.qy (Postfix, from userid 501) id D0F878E0F431; Tue, 25 Jun 2024 23:41:22 -0400 (EDT)
Date: Tue, 25 Jun 2024 23:41:22 -0400
Message-Id: <20240626034122.D0F878E0F431@ary.qy>
From: John Levine <johnl@taugh.com>
To: ietf@ietf.org, tools-discuss@ietf.org
In-Reply-To: <547C207F-BB93-46A7-950A-D4ABB651CB2E@rfc1035.com>
Organization: Taughannock Networks
X-Headerized: yes
Cleverness: minimal
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Message-ID-Hash: 3EO6PZLUYN6I5GWIPPSFF4NAQRH7AFMU
X-Message-ID-Hash: 3EO6PZLUYN6I5GWIPPSFF4NAQRH7AFMU
X-MailFrom: johnl@iecc.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: jim@rfc1035.com
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/AR9QGsUD9retPtb_QRJ_6Ll72N0>
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>

It appears that Jim Reid  <jim@rfc1035.com> said:
>> 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.

Due to the way AWS handles outgoing mail, it will initially come from
addresses all over their SES outgoing pool. Eventually it will be
54.240.73.154 and 54.240.73.155, but if you just allow mail from those
two addresses, you will lose a lot of mail.

There may have been a time when it wsa practical to list all of the
IPs that your correspondents use, but that time ended a long time ago.
You've been rejecting all my mail forever, and I guess now I know why.

R's,
John

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