Re: [ietf-smtp] CC'ing ticket systems

Valdis Kl ē tnieks <> Thu, 09 July 2020 21:57 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 5BC2D3A08F6 for <>; Thu, 9 Jul 2020 14:57:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id xpUtBfkIZBre for <>; Thu, 9 Jul 2020 14:57:25 -0700 (PDT)
Received: from ( [IPv6:2607:b400:92:8300:0:c6:2117:b0e]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id DF3AF3A08F0 for <>; Thu, 9 Jul 2020 14:57:24 -0700 (PDT)
Received: from ( [IPv6:2607:b400:92:8500:0:af:2d00:4488]) by (8.14.4/8.14.4) with ESMTP id 069LvNcA009657 for <>; Thu, 9 Jul 2020 17:57:23 -0400
Received: from ( []) by (8.14.7/8.14.7) with ESMTP id 069LvIcg000931 for <>; Thu, 9 Jul 2020 17:57:23 -0400
Received: by with SMTP id d45so2684483qte.12 for <>; Thu, 09 Jul 2020 14:57:23 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:sender:from:to:cc:subject:in-reply-to:references :mime-version:content-transfer-encoding:date:message-id; bh=FzhMWCDX7s8YH+0Vl50M5YJFkxZSuJXgR9mrieTTTAY=; b=i0cLk94xATxxtyh8aKl27EuutxRlgT9v2jNJWAmff0Q2uFIva6u7WQogzNKfV6LgYK SH6C9m9NlYSe37bxoa//sOvaId0wGUSRtFHwHARK+c6uTEwZFEwdjQIpokt5FTQt6CfJ hAyF6A3+wxzXS2AkHDK2RMVTVINft+lWAUNJz+Dh0UQjRLx5vcpl5fKRDrKGu883MT1f 55rGqoMiskn7JQH+cvRvLvWoG6I5WspO68jNF+QRsskhiaBLra7CPrGwtuU3iNnsc4Eo yV1u6WnyrQtvQdmGcta5UIJO0nxdR9o1q8pt0wDGa/4F/Ry2BW84gv3bHldUZGxWsHs8 XZzA==
X-Gm-Message-State: AOAM533moLBk8q12kTXEt87nxOw5JY9CLAu1qMrmaLRvJbS9+aUFviiU 1h7LYE5GXMEzLLFG5LnKoFcQrVjR5XajDcs0RYBqc5R6YXEI4Y2eCKoil8SCUmHylcfPCGVtkMA G9HoEOrR6DgjpZ3C962IQyQ==
X-Received: by 2002:a05:6214:72c:: with SMTP id c12mr61668800qvz.76.1594331838178; Thu, 09 Jul 2020 14:57:18 -0700 (PDT)
X-Google-Smtp-Source: ABdhPJz3sugZ/6+K8T/gtMh4KAjDG1d0zikyJUTLFA50MQ8rs5iN+1UxbawYsb9XbM2vwi6OujxHYQ==
X-Received: by 2002:a05:6214:72c:: with SMTP id c12mr61668772qvz.76.1594331837784; Thu, 09 Jul 2020 14:57:17 -0700 (PDT)
Received: from turing-police ([2601:5c0:c001:c9e1::359]) by with ESMTPSA id a185sm5023750qkg.3.2020. (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 09 Jul 2020 14:57:16 -0700 (PDT)
Sender: Valdis Kletnieks <>
From: "Valdis Kl=?utf-8?Q?=c4=93?=tnieks" <>
X-Google-Original-From: "Valdis Kl=?utf-8?Q?=c4=93?=tnieks" <>
X-Mailer: exmh version 2.9.0 11/07/2018 with nmh-1.7+dev
To: Michael Richardson <>
In-Reply-To: <16746.1594119340@localhost>
References: <16746.1594119340@localhost>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_1594331835_102792P"; micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Thu, 09 Jul 2020 17:57:15 -0400
Message-ID: <108085.1594331835@turing-police>
Archived-At: <>
Subject: Re: [ietf-smtp] CC'ing ticket systems
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discussion of issues related to Simple Mail Transfer Protocol \(SMTP\) \[RFC 821, RFC 2821, RFC 5321\]" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 09 Jul 2020 21:57:27 -0000

On Tue, 07 Jul 2020 06:55:40 -0400, Michael Richardson said:

> Hi, have you had the experience of starting an email thread where one of the
> participants is a ticket system?  As the initiator you get a ticket open,
> and then each person who was in the To/CC, as they reply, get their own
> ticket open.

The vast majority of the time, it's the result of somebody subscribing to a
fairly active list like NANOG, and then leaving their organization, at which
point some low-lumen bulb forwards the departed's mail to the trouble ticket

Hilarity and hijinks ensue.

Surprisingly enough, if the mails carry some chaining indication, such as a
'TICKET AG7342'  in the Subject: header, usually the ticketing system *does*
aggregate all the replies into one ticket - and still sends out another
notification for each addition to the ticket.  I don't know of any that use
the References: or In-Reply-To: headers to determine if a mail is related, but
that would also be a sane behavior, except the chances of a MUA breaking
the threading by nuking those headers is pretty high.  In fact, one of the
replies in this thread is lacking a References: header.

And if the ticket system is being fed multiple mails that *don't* look like
they're part of a thread (by whatever method the system uses), it's hard to
argue that starting a new ticket is always a bad idea (and sometimes it
may even be required for regulatory compliance purposes)...

So I suspect there's two orthogonal issues here, and you're looking at the
less problematic one.