IETF RT System Problem

Glen <> Tue, 24 January 2017 22:52 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 7E90F1294DA for <>; Tue, 24 Jan 2017 14:52:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_SORBS_SPAM=0.5, RP_MATCHES_RCVD=-3.199, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id Y56gLIeRJcTS for <>; Tue, 24 Jan 2017 14:52:03 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 9FCFE1294CD for <>; Tue, 24 Jan 2017 14:51:59 -0800 (PST)
Received: from (localhost []) by (Postfix) with ESMTPS id 69F431E5663 for <>; Tue, 24 Jan 2017 14:51:18 -0800 (PST)
Received: from ( []) by (Postfix) with ESMTPSA id 41DB01E5664 for <>; Tue, 24 Jan 2017 14:51:18 -0800 (PST)
Received: by with SMTP id l66so676702ioi.1 for <>; Tue, 24 Jan 2017 14:51:59 -0800 (PST)
X-Gm-Message-State: AIkVDXJdExW1HPIaqciIyxrxZPged3nJmBGWy69KL8WJYze+uugXQNO5aWzJmZYiUeXoiC0RIg6mjvWQYFrUnw==
X-Received: by with SMTP id 99mr29754403ios.45.1485298318616; Tue, 24 Jan 2017 14:51:58 -0800 (PST)
MIME-Version: 1.0
Received: by with HTTP; Tue, 24 Jan 2017 14:51:38 -0800 (PST)
From: Glen <>
Date: Tue, 24 Jan 2017 14:51:38 -0800
X-Gmail-Original-Message-ID: <>
Message-ID: <>
Subject: IETF RT System Problem
Content-Type: text/plain; charset="UTF-8"
Archived-At: <>
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IETF announcement list. No discussions." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 24 Jan 2017 22:52:04 -0000

Dear IETF Community -

As many of you know, the IETF uses the "RT" ticketing system to record
and manage help requests sent by the community to public help
addresses such as, and other similar addresses.

We have detected and corrected a problem with the RT system which,
over the past 24 hours, prevented *some* (but not all) requests from
processing in to the system correctly.

As a result, the secretariat might not have all of the requests sent
to them within the past day.

If you sent a request to an IETF address, and you received an
auto-reply message with a ticket number, then we have your request,
and no further action is needed.

If, however, you have sent any requests in the past day to an IETF
address, and you did NOT receive a ticket number, we request that you
please re-send your original message again at this time.  You should
receive a ticket number confirmation message within just a few

And of course, if you have any problems sending to RT, or any problems
getting your requests resolved, you are welcome to reach out to me
directly, and I will follow up.

Thank you for your patience.

Glen Barney
IT Director
AMS (IETF Secretariat)