Return-Path: X-Original-To: spring@ietfa.amsl.com Delivered-To: spring@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 747E7C180B59; Thu, 9 May 2024 13:00:19 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.794 X-Spam-Level: X-Spam-Status: No, score=-2.794 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=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 (1024-bit key) header.d=joelhalpern.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 9Z24Op5Cicic; Thu, 9 May 2024 13:00:15 -0700 (PDT) Received: from maila1.tigertech.net (maila1.tigertech.net [208.80.4.151]) (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 993CDC180B41; Thu, 9 May 2024 13:00:15 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by maila1.tigertech.net (Postfix) with ESMTP id 4Vb2tR2wP6z4TDS2; Thu, 9 May 2024 13:00:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1715284815; bh=u/4c8fpbzcqfwWoszunK5g1cHBdacC8L//dnDQOcsEc=; h=Date:Subject:References:To:From:In-Reply-To:From; b=FEa9UYgThbQVbO0COWk48HBDD82iG34/LyoVQf+JMPk+Tth+TaJ/GC7emEQ77PlBt bmRAaVqueMbd4VMxmLVAmaUZ81hmfQi5JeiPnXqxeGOUGBK+lynjmo4vdVsmHx9kAW MaVL7loXSNbjBgZ/4EECz3M2sgbOkZAZuEIejK2Y= X-Quarantine-ID: <2fKY8kZaw9hG> X-Virus-Scanned: Debian amavisd-new at a1.tigertech.net Received: from [192.168.23.1] (unknown [50.233.136.230]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by maila1.tigertech.net (Postfix) with ESMTPSA id 4Vb2tQ6PFGz4TDly; Thu, 9 May 2024 13:00:14 -0700 (PDT) Content-Type: multipart/alternative; boundary="------------nfjDra1SIP40Y5UgQRxMzWAr" Message-ID: Date: Thu, 9 May 2024 16:00:12 -0400 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Content-Language: en-US References: To: "savnet@ietf.org" , SPRING WG List From: Joel Halpern In-Reply-To: X-Forwarded-Message-Id: Message-ID-Hash: 5UETGABHNOIAWSH5LK5YV6IBGOBY4MJX X-Message-ID-Hash: 5UETGABHNOIAWSH5LK5YV6IBGOBY4MJX X-MailFrom: jmh@joelhalpern.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-spring.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.9rc4 Precedence: list Subject: =?utf-8?q?=5Bspring=5D_Fwd=3A_Update_on_ongoing_mail_delivery_issues_and_req?= =?utf-8?q?uest_to_resend_failed_messages?= List-Id: "Source Packet Routing in NetworkinG (SPRING)" Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: This is a multi-part message in MIME format. --------------nfjDra1SIP40Y5UgQRxMzWAr Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit If you sent email today and did not see a copy on the list, this may be why... Yours, Joel -------- Forwarded Message -------- Subject: Update on ongoing mail delivery issues and request to resend failed messages Date: Thu, 9 May 2024 14:29:06 -0500 From: Robert Sparks Reply-To: tools-discuss To: tools-discuss , Working Chairs , irsg@irtf.org If you have had a message fail to deliver to a list since the mailman3 transition, please resend it at this time. If it fails to deliver again, please let us know by sending the message-id to tools-help@ietf.org. There was a period today (roughly 1600-1900 UTC) where no messages made it through to the lists. The issue that led to that, and many earlier failures has been addressed. Several other improvements were made yesterday and this morning that further reduced the number of messages that were not delivered to lists, even though they appeared to have been accepted.  We are hopeful, but not yet confident, that all delivery issues have now been addressed. The system continues to be monitored by several people for signs of ongoing issues. Work on delivering the messages that were accepted but not yet delivered has started. It is expected to take several days to complete. This turns out to be surprisingly complex. It is possible that they won't be recoverable. RjS --------------nfjDra1SIP40Y5UgQRxMzWAr Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit

If you sent email today and did not see a copy on the list, this may be why...

Yours,

Joel



-------- Forwarded Message --------
Subject: Update on ongoing mail delivery issues and request to resend failed messages
Date: Thu, 9 May 2024 14:29:06 -0500
From: Robert Sparks <rjsparks@nostrum.com>
Reply-To: tools-discuss <tools-discuss@ietf.org>
To: tools-discuss <tools-discuss@ietf.org>, Working Chairs <wgchairs@ietf.org>, irsg@irtf.org


If you have had a message fail to deliver to a list since the mailman3 transition, please resend it at this time. If it fails to deliver again, please let us know by sending the message-id to tools-help@ietf.org.

There was a period today (roughly 1600-1900 UTC) where no messages made it through to the lists. The issue that led to that, and many earlier failures has been addressed. Several other improvements were made yesterday and this morning that further reduced the number of messages that were not delivered to lists, even though they appeared to have been accepted.  We are hopeful, but not yet confident, that all delivery issues have now been addressed. The system continues to be monitored by several people for signs of ongoing issues.

Work on delivering the messages that were accepted but not yet delivered has started. It is expected to take several days to complete. This turns out to be surprisingly complex. It is possible that they won't be recoverable.

RjS

--------------nfjDra1SIP40Y5UgQRxMzWAr--