Re: IETF email service transition planned for 24 February
Robert Sparks <rjsparks@nostrum.com> Fri, 21 February 2025 18:14 UTC
Return-Path: <rjsparks@nostrum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E1E52C14F71D; Fri, 21 Feb 2025 10:14:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.513
X-Spam-Level:
X-Spam-Status: No, score=0.513 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_DISCARD=1.8, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, HTML_MESSAGE=0.001, KHOP_HELO_FCRDNS=0.399, T_SCC_BODY_TEXT_LINE=-0.01, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=nostrum.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 UUE63peyJ1At; Fri, 21 Feb 2025 10:14:21 -0800 (PST)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4C0EEC14CE5E; Fri, 21 Feb 2025 10:14:21 -0800 (PST)
Received: from [192.168.1.103] ([47.186.49.96]) (authenticated bits=0) by nostrum.com (8.18.1/8.18.1) with ESMTPSA id 51LIEIsH063874 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Fri, 21 Feb 2025 12:14:18 -0600 (CST) (envelope-from rjsparks@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1740161659; bh=/ORxqzIm5KhFBeJ3A0Mbl3wxuvT9NQNiGMyiUyzrO3c=; h=Date:Subject:From:To:Reply-To:References:In-Reply-To; b=mLzZC+CYJ0plZu4LAcLwhqiOhlgnb2ck7XzzEc07fGN9ZMcywefUCBf07nbKmE4Ye H65WROs5J9HaqwVBSjJMBVh8Za/BwkBX2bDq6NSoxpz+xdKv0bOQmS+lSVk8XGtV/m RWr7WfuBV7vGRMWwJPd1Db+A6zUSAWlBke77QsY0=
X-Authentication-Warning: raven.nostrum.com: Host [47.186.49.96] claimed to be [192.168.1.103]
Content-Type: multipart/alternative; boundary="------------VZnUQr7SGmRvT1GPk1dEqpvB"
Message-ID: <34a5ded2-1610-4650-86e0-e80f93ad0f09@nostrum.com>
Date: Fri, 21 Feb 2025 12:14:13 -0600
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: IETF email service transition planned for 24 February
From: Robert Sparks <rjsparks@nostrum.com>
To: Tools Team Discussion <tools-discuss@ietf.org>, IETF discussion list <ietf@ietf.org>, admin-discuss@ietf.org, "wgchairs@ietf.org" <wgchairs@ietf.org>, irsg@irtf.org
References: <1889c11d-4b3a-42ca-9cd8-7ce4ff12c35e@nostrum.com>
Content-Language: en-US
In-Reply-To: <1889c11d-4b3a-42ca-9cd8-7ce4ff12c35e@nostrum.com>
Message-ID-Hash: 6SUIU7NNN44XT6MSFKLYMV6XMGITGXTT
X-Message-ID-Hash: 6SUIU7NNN44XT6MSFKLYMV6XMGITGXTT
X-MailFrom: rjsparks@nostrum.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-ietf.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc6
Precedence: list
Reply-To: Tools Team Discussion <tools-discuss@ietf.org>
List-Id: "IETF-Discussion. This is the most general IETF mailing list, intended for discussion of technical, procedural, operational, and other topics for which no dedicated mailing lists exist." <ietf.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/9zV92fGgNxrD7jg0R0HNYBM6YXg>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Owner: <mailto:ietf-owner@ietf.org>
List-Post: <mailto:ietf@ietf.org>
List-Subscribe: <mailto:ietf-join@ietf.org>
List-Unsubscribe: <mailto:ietf-leave@ietf.org>
Resending this message as reminder of this Monday's transition: On 2/14/25 3:10 PM, Robert Sparks wrote: > > Please be aware > ofhttps://www.ietf.org/blog/email-service-transition-2025-02/ > <https://www.ietf.org/blog/email-service-transition-2025-02/>. > > Repeating from that post: > >> The IETF email processing infrastructure transition planned for >> 0900-1100 UTC on 24 February may result in some delivery delays. >> >> During the transition, delivery of messages to addresses at ietf.org, >> iab.org, irtf.org, iesg.org, and rfc-editor.org, including email >> lists, will be paused. The goal is to deliver all mail sent to our >> addresses during the transition, once the transition is complete. >> > > Note that there will also be changes that are not expected to > delay/disrupt services that will be taking place between now and the > 24th. There is some discussion of these in the notes from this week’s > Tools call if you are curious > (https://notes.ietf.org/tools-team-20250211 > <https://notes.ietf.org/tools-team-20250211>). > > Please direct any responses to tools-discuss@ietf.org. > > RjS >
- IETF email service transition planned for 24 Febr… Robert Sparks
- Re: IETF email service transition planned for 24 … Robert Sparks
- Mail service transition complete Robert Sparks