[Tools-discuss] Mail "subject" handling - has it changed?

Brian E Carpenter <brian.e.carpenter@gmail.com> Wed, 15 May 2024 22:53 UTC

Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: tools-discuss@ietfa.amsl.com
Delivered-To: tools-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 762AEC1D4A6E for <tools-discuss@ietfa.amsl.com>; Wed, 15 May 2024 15:53:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.098
X-Spam-Level:
X-Spam-Status: No, score=-7.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 efnkSmdsgvUs for <tools-discuss@ietfa.amsl.com>; Wed, 15 May 2024 15:53:54 -0700 (PDT)
Received: from mail-pj1-x1031.google.com (mail-pj1-x1031.google.com [IPv6:2607:f8b0:4864:20::1031]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 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 193E8C1CAF46 for <tools-discuss@ietf.org>; Wed, 15 May 2024 15:53:54 -0700 (PDT)
Received: by mail-pj1-x1031.google.com with SMTP id 98e67ed59e1d1-2b9702e05easo2216167a91.1 for <tools-discuss@ietf.org>; Wed, 15 May 2024 15:53:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1715813633; x=1716418433; darn=ietf.org; h=content-transfer-encoding:in-reply-to:from:to:content-language :references:subject:user-agent:mime-version:date:message-id:from:to :cc:subject:date:message-id:reply-to; bh=vTIoUfPsZ9tQU1kUwVOfj84ewqHDxKAcLxzPHZbqsRE=; b=F2GYjkA0yse6gQYqnhtn4ccMZtQFxQ4xAfpQE1JmsrwCbnP/gxQxf1rS+/WRoumCDV K4n9Q+B+HeENmGodoodni9wiauA4JK+klq6+lECo8apYdi7BMDYGeLcEjbacERD1P2U9 OZ3rMaDqkMtVJFhR+fd9HNC/kdgqrkVl/31jF3iONvJf6IN5UoLBDUgQHw7B2QP3c/ob jI3tv7bPrVjBMbZn/oeLBnMIwoTOjnqWvGbHxhXYBhKdz0oTbc22QDpxpWUBrBpLWfit tEkhRpH1r1yv2Te7zjo+1iJlKn2WN6uHeUPbWOLzsspcm+r4xsXLwPvHafH0qadEKQG0 Extw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1715813633; x=1716418433; h=content-transfer-encoding:in-reply-to:from:to:content-language :references:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=vTIoUfPsZ9tQU1kUwVOfj84ewqHDxKAcLxzPHZbqsRE=; b=ndGlf0dtbCZ9zAUFsSbSfUA8fv7w4JlpKJKJz2HI8J/smP0qBLAAdQO69OADf708cX TSHgIsTrpLtyonrIMNW7Gl+RmZ+P7BryQZdbWCdMZQngFUIATqpdXxMFKAik8HsOtSXG +6Pug0lv+fcgXHgNIJc271S8a+w65xDkfC1IUFpzt1csaEuNcj62HTdzTfqx8AjXFrYk z0e+UnNEkeF4eXqY+7DUdkEGlki8s0v0fWdX7PFOsLv4hqRuO/GZuH15RvidJQgX6tra W5NkzRmC5Qjli1fv8mls3FfpmtjbjwrwVmfG7bH1ELGjAAi7pFQ+gci/8huvvmWl8Xcl QXvA==
X-Gm-Message-State: AOJu0YwGPNKbABfRae/nFBj2ii8KmTVHOqBFtqNJsgt4DeXImeQDPgnJ g+AMhAafNfTygWZR55PYIAKut6i5rQ4s7VVXOoIsvv/ZlbOk4dGyTU1GHmCB
X-Google-Smtp-Source: AGHT+IFiTa0TlO4G9iJcNcbAVTDncos7KlUNviYB9jLaAJ5TIpiDPd3Aoe8WBV4qV7MZrmnEGxUbuQ==
X-Received: by 2002:a17:90a:de03:b0:2ac:23ec:6a57 with SMTP id 98e67ed59e1d1-2b6ccd7d47bmr14166037a91.39.1715813633476; Wed, 15 May 2024 15:53:53 -0700 (PDT)
Received: from ?IPV6:2404:4400:541d:a600:44b7:2c2e:2bc6:8707? ([2404:4400:541d:a600:44b7:2c2e:2bc6:8707]) by smtp.gmail.com with ESMTPSA id 98e67ed59e1d1-2b69b2f0305sm11246162a91.42.2024.05.15.15.53.51 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 15 May 2024 15:53:53 -0700 (PDT)
Message-ID: <71a8773c-79a2-47c6-97a7-f8670102c9b8@gmail.com>
Date: Thu, 16 May 2024 10:53:49 +1200
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
References: <CAN-Dau0VhxrLzMDnEwO-hYP2MJO00BrsbkK-3XRwm6X=hWaFZQ@mail.gmail.com>
Content-Language: en-US
To: Tools Team Discussion <tools-discuss@ietf.org>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
In-Reply-To: <CAN-Dau0VhxrLzMDnEwO-hYP2MJO00BrsbkK-3XRwm6X=hWaFZQ@mail.gmail.com>
X-Forwarded-Message-Id: <CAN-Dau0VhxrLzMDnEwO-hYP2MJO00BrsbkK-3XRwm6X=hWaFZQ@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: base64
Message-ID-Hash: EWB32A45N6GXYETV7RIQYV2PEC7D47PS
X-Message-ID-Hash: EWB32A45N6GXYETV7RIQYV2PEC7D47PS
X-MailFrom: brian.e.carpenter@gmail.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-tools-discuss.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [Tools-discuss] Mail "subject" handling - has it changed?
List-Id: IETF Tools Discussion <tools-discuss.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/FlYD3J93X3f5h4F8Jobvm3P4H5I>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tools-discuss>
List-Help: <mailto:tools-discuss-request@ietf.org?subject=help>
List-Owner: <mailto:tools-discuss-owner@ietf.org>
List-Post: <mailto:tools-discuss@ietf.org>
List-Subscribe: <mailto:tools-discuss-join@ietf.org>
List-Unsubscribe: <mailto:tools-discuss-leave@ietf.org>

Hi,

We've had a bit of a plague of absurd subject headers over on 6man, due to people whose corporate email system prepends "External:" to the subject. It's suddenly become recursive, so we got up to

>>> Re: [IPv6]Re: External: Re: External: Re: Re: External: Re: External: Re: Re: External: Re: External: Re: External: Re: RIOs First...

Has the mailman upgrade changed something, as David suggests below?

    Brian

-------- Forwarded Message --------
Subject: 	Re: [IPv6]Externality
Date: 	Wed, 15 May 2024 17:25:29 -0500
From: 	David Farmer <farmer@umn.edu>
To: 	Brian E Carpenter <brian.e.carpenter@gmail.com>
CC: 	ipv6@ietf.org



I think there could be some interaction with the new mailing list behavior for IETF lists, which I've noticed lately. For me, Gmail is not associating my local copy or the direct copy of an email with the one from the list like it used to. So, I see two copies of emails sent through IETF Lists that I send or for which I am also a direct recipient.

Thanks for the reminder, though.

On Wed, May 15, 2024 at 5:00 PM Brian E Carpenter <brian.e.carpenter@gmail.com <mailto:brian.e.carpenter@gmail.com>> wrote:

      >>> Re: [IPv6]Re: External: Re: External: Re: Re: External: Re: External: Re: Re: External: Re: External: Re: External: Re: RIOs First...
     OK, we get it, it's external email...

     Please could people trim such garbage out of the subject field when replying? It makes obvious techniques for managing email threads painful or impossible.

     Regards
          Brian Carpenter

     --------------------------------------------------------------------
     IETF IPv6 working group mailing list
     ipv6@ietf.org <mailto:ipv6@ietf.org>
     Administrative Requests:
     --------------------------------------------------------------------



-- 
===============================================
David Farmer Email:farmer@umn.edu <mailto:Email%3Afarmer@umn.edu>
Networking & Telecommunication Services
Office of Information Technology
University of Minnesota
2218 University Ave SE        Phone: 612-626-0815
Minneapolis, MN 55414-3029   Cell: 612-812-9952
===============================================