The QUIC list is not broken

Glen <> Mon, 08 January 2018 19:20 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id DF87A124B18; Mon, 8 Jan 2018 11:20:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id RQhFAaK9X3yM; Mon, 8 Jan 2018 11:20:24 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id BB3FE126D46; Mon, 8 Jan 2018 11:20:24 -0800 (PST)
Received: from (localhost []) by (Postfix) with ESMTPS id 3A2571CAE41; Mon, 8 Jan 2018 11:19:49 -0800 (PST)
Received: from ( []) by (Postfix) with ESMTPSA id 188011CAE31; Mon, 8 Jan 2018 11:19:49 -0800 (PST)
Received: by with SMTP id c16so8720082itc.5; Mon, 08 Jan 2018 11:20:24 -0800 (PST)
X-Gm-Message-State: AKGB3mLXDdlyVNUkXHLzouNeUgjG3tL0fmFdMzGK9u/Jy7+vmiLc89QE x1O351Ql87YYuHPVZrjdDuN6Edi9Swe+cTS1msY=
X-Google-Smtp-Source: ACJfBovKDudIQNyR3pc6czZ6Do+PrVSFJEzRbHmr4nqb/slUpnbL3yoqR4SK/bKdpIEdFSOVUG12LIc8bnn1gc5VjKw=
X-Received: by with SMTP id m12mr12421849iti.110.1515439224089; Mon, 08 Jan 2018 11:20:24 -0800 (PST)
MIME-Version: 1.0
Received: by with HTTP; Mon, 8 Jan 2018 11:20:03 -0800 (PST)
From: Glen <>
Date: Mon, 8 Jan 2018 11:20:03 -0800
X-Gmail-Original-Message-ID: <>
Message-ID: <>
Subject: The QUIC list is not broken
Content-Type: multipart/alternative; boundary="94eb2c1fcb40a1735c056248b05e"
Archived-At: <>
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 08 Jan 2018 19:20:26 -0000

Dear QUIC subscribers -

The tools team and I are working on some improvements to the mail systems
on the IETF servers.  During the course of testing some improvements, an
old email message accidentally got replayed through the list, and was sent
to many of you.

We apologize for the noise, the list is not broken, mail is not delayed,
this was simply something working much more quickly than we expected it to.

Thank you for your patience as we continue to work on improvements to the
system.  We hope no more messages will go out... but if another does, there
is no need to panic!

As always, any questions, let me know.

Glen Barney
IT Director
AMS (IETF Secretariat)