IETF Logo Mail Archive

Re: Service outages planned for April 25

Keith Moore <moore@network-heretics.com> Thu, 28 April 2022 10:51 UTC

Return-Path: <moore@network-heretics.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 A8272C157902 for <ietf@ietfa.amsl.com>; Thu, 28 Apr 2022 03:51:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.741
X-Spam-Level:
X-Spam-Status: No, score=-3.741 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, NICE_REPLY_A=-1.857, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, T_SPF_TEMPERROR=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=messagingengine.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 rrspt8muPPk0 for <ietf@ietfa.amsl.com>; Thu, 28 Apr 2022 03:51:17 -0700 (PDT)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (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 3B4F0C14F73A for <ietf@ietf.org>; Thu, 28 Apr 2022 03:51:12 -0700 (PDT)
Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id 3056F5C016C for <ietf@ietf.org>; Thu, 28 Apr 2022 06:51:12 -0400 (EDT)
Received: from mailfrontend2 ([10.202.2.163]) by compute5.internal (MEProxy); Thu, 28 Apr 2022 06:51:12 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:date:from:from:in-reply-to:in-reply-to:message-id :mime-version:references:reply-to:sender:subject:subject:to:to :x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm1; t=1651143072; x=1651229472; bh=89ppUcuGcV30cAKOm3/JIFswjujX /LEi6O+diO/9Wxg=; b=qqvlMXYqLpstnIOVVw+/6zd7yHYOCZ6h+Z3QlMIcigif ml17hlotGI5Hgzh7h7nsYo129bbftCi80OGDRMg0tXcuvM0NQSSaD9IvSae5djev 3yzQXpV/9ZHehUc6MEKYto9qoU9AsuWLy0L619MOUmg3mx2JByEbAD/CFY3GDQPA kgGiUEVU5pYci0CTnBH5txKZI5Rw6szypXQr0rLFEO6/xYnardps+L6ihzfU28lJ 4qsqQpDpJb+8Tkrp+Bp+KNB456KJsLc1KmQ8fVN+udDxByreiIMhuy7wlM9etZXF VY5UVkyEO/BTL6ue62j4noMNcx9nJe3hQtzwl5nzPQ==
X-ME-Sender: <xms:n3FqYsoOlEWFJZOjaW1gW84TpS6ldiNrD4vmCkkdXdAwFptYkPNVzA> <xme:n3FqYirkgbv9gxmUjHGH-n5J2XWbxe_6QyDqfaR601AZJo0TR4XKCj9h475RV4Fop Hg4eeXtUFZYPw>
X-ME-Received: <xmr:n3FqYhM6ZEM7qQuXgrzCBYyx2iLcCTYEyphjglT5rYBCvEccXmRR91ghDRYfXd5TqWgUP8ArSFs8igKI8Lb0QUPlP6IVrXDplPQgVlGTqfBp9FpOZvX42g>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvfedrudejgdefvdcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepkfffgggfuffvfhfhjggtgfesthekre dttdefjeenucfhrhhomhepmfgvihhthhcuofhoohhrvgcuoehmohhorhgvsehnvghtfiho rhhkqdhhvghrvghtihgtshdrtghomheqnecuggftrfgrthhtvghrnhepfedtvdelieejve ekjefhueduheeviefhjeefvdfgudfhfffhudduudefgefgteevnecuvehluhhsthgvrhfu ihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepmhhoohhrvgesnhgvthifohhrkh dqhhgvrhgvthhitghsrdgtohhm
X-ME-Proxy: <xmx:n3FqYj44QQbUnOERVKCtMzzW3lCOqfiudozV7y90AeNqMDvYoCtqNQ> <xmx:n3FqYr5quBsx2JHUJ4fiGfk5RVlcWTP1p9JLvrs_WFWo_k-JhvT4NA> <xmx:n3FqYjjDeiny--Y20XY3GFGlWhUNQb4_kNoxpk9eZ-kyxxuMgNPBbw> <xmx:oHFqYtHIxxLERXmnjpqwTrZqebAZcSCkN8_RfwT4fPx3GVi6Fluv3A>
Received: by mail.messagingengine.com (Postfix) with ESMTPA for <ietf@ietf.org>; Thu, 28 Apr 2022 06:51:11 -0400 (EDT)
Message-ID: <664edff3-3690-995f-1c1e-ce3e6c5c1eae@network-heretics.com>
Date: Thu, 28 Apr 2022 06:51:09 -0400
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.7.0
Subject: Re: Service outages planned for April 25
Content-Language: en-US
To: ietf@ietf.org
References: <dcc27c29-51f8-c2a4-8ce4-ee1a3c6cb017@nostrum.com> <66aebf8b-2835-d572-ad00-eb2df514a157@nostrum.com> <626A610B.9050508@btconnect.com> <A449287A-CDA4-4173-8691-7049488FD130@ietf.org>
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <A449287A-CDA4-4173-8691-7049488FD130@ietf.org>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/NNyLEU5ShZvkecAPNJ_54RZY31A>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.34
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Apr 2022 10:51:23 -0000

On 4/28/22 06:22, Jay Daley wrote:

> One of the changes made in this transition was to the IP address range 
> of our mail servers.  As the IETF is a very high volume mail sender 
> our address ranges often need whitelisting or other special treatment 
> by large mail receivers.  Having that special treatment restored with 
> one large receiver took a couple of days (and much thanks to the 
> IETF’r who helped with that).

I'm glad this was taken care of expeditiously.    But I can't help but 
notice that the fact that it was necessary at all is a sign that email 
interoperates poorly in practice, and a sign that IETF has failed to 
maintain the email protocols to keep them interoperable.

Keith

v2.23.0 | Report a Bug | By Email