[v6ops] Re: SMTP IPv4 outage 1 July 2026

S Moonesamy <sm+ietf@elandsys.com> Fri, 03 July 2026 11:20 UTC

Return-Path: <sm@elandsys.com>
X-Original-To: v6ops@mail2.ietf.org
Delivered-To: v6ops@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id D264F10D907DE for <v6ops@mail2.ietf.org>; Fri, 3 Jul 2026 04:20:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1783077650; bh=UfYdop+KDo2ztkf6vPPF5v/Wi8awV6fccUkwuJCRzUc=; h=Date:To:From:Subject:In-Reply-To:References; b=i94KAswwJqKkw0HG+7yWJUfVI6I3EsTzjQjtSmtAby/G9Dg/llXg9K8Grdk/lR+71 3VJau0stMXdIpwshyO/PbkHN5WNoFZEJa4CQI5umfpCDXDfWMZ/DO1W1Zl0BZBimRt gUmN9sEB5kW5UCfjQnSKcV9nzecfuOQ6Rm5Bwgu4=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -1.7
X-Spam-Level:
X-Spam-Status: No, score=-1.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.com
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EcrARjXICXdH for <v6ops@mail2.ietf.org>; Fri, 3 Jul 2026 04:20:49 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by mail2.ietf.org (Postfix) with ESMTP id 5BF7410D907D7 for <v6ops@ietf.org>; Fri, 3 Jul 2026 04:20:49 -0700 (PDT)
Received: from DESKTOP-K6V9C2L.elandsys.com ([102.117.33.87]) (authenticated bits=0) by mx.elandsys.com (8.15.2/8.14.5) with ESMTPSA id 663BKQTM028150 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 3 Jul 2026 04:20:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=elandsys.com; s=mail; t=1783077639; x=1783164039; i=@elandsys.com; bh=UfYdop+KDo2ztkf6vPPF5v/Wi8awV6fccUkwuJCRzUc=; h=Date:To:From:Subject:In-Reply-To:References; b=3fvJiV6wC9B73FSHLHusJ3rOrhRryMslq9Ib651lx2hGqAndk/N3OowkS5CqPD0ac XbM3/flVHVjvQIXsd8+ckn+1inD+0MHo8EaNf2/dYV8KQcEy4wHXmfa+4tjLIh/l2u A+JT/yC99dOh9buZktIGLP8SZL0kU0fIKIYgxvRs=
Message-Id: <6.2.5.6.2.20260703032400.10555a50@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 03 Jul 2026 04:18:05 -0700
To: Nick Hilliard <nick@foobar.org>, v6ops@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
In-Reply-To: <7a6fa20d-be1b-dc16-4465-10681112306e@foobar.org>
References: <50D08FD0-51D4-437D-8240-CF72B957EF01@newmachinefutures.nz> <7a6fa20d-be1b-dc16-4465-10681112306e@foobar.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Message-ID-Hash: U5D62C5RFJO4TJFV3TFHBRABIMMIYZN4
X-Message-ID-Hash: U5D62C5RFJO4TJFV3TFHBRABIMMIYZN4
X-MailFrom: sm@elandsys.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-v6ops.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
Subject: [v6ops] Re: SMTP IPv4 outage 1 July 2026
List-Id: v6ops discussion list <v6ops.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/QCngpOeK8ouKSXZR-8SoB22_UjA>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Owner: <mailto:v6ops-owner@ietf.org>
List-Post: <mailto:v6ops@ietf.org>
List-Subscribe: <mailto:v6ops-join@ietf.org>
List-Unsubscribe: <mailto:v6ops-leave@ietf.org>

Hi Nick,
At 03:00 AM 03-07-2026, Nick Hilliard wrote:
>Sam Sargeant wrote on 02/07/2026 23:50:
>>On1 July 2026,  from 04:55Z to 20:10Z, IETF SMTP servers (25/tcp)
>>were unreachable over IPv4. For these 15 hours, messages addressed to
>>lists or aliases at ietf.org, irtf.org, iab.org, and rfc-editor.org
>>over IPv4 were not accepted.
>the internal wasp in me wonders how or why this would have been 
>service-affecting for anyone.

The duration of the outage was 15 hours and 15 minutes.  The 
timeframe of the outage intersects with standard working day in North 
America or Europe.  There wasn't any publicly-accessible 
complaints.  Either nobody cared about the outage or nobody noticed it.

SMTP is not an interactive service, i.e. it's not like HTTPS where 
the user would see a an error message in the web browser stating that 
the site cannot be reached.  That might explain why nobody noticed the outage.

There wasn't any traffic from my side, to 2602:f977:800:f7f6::1 
(tcp/25) while the SMTP service was not reachable over IPv4.

Regards,
S. Moonesamy