unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Gregory Heytings <gregory@heytings.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Richard Stallman <rms@gnu.org>, emacs-devel@gnu.org
Subject: Re: master 42596bd 2/6: Little improvements in rmail.el. Recognize encryped override headers.
Date: Wed, 12 May 2021 14:17:59 +0000	[thread overview]
Message-ID: <ef56467bdfd9d44c656c@heytings.org> (raw)
In-Reply-To: <ef56467bdfe07ebd91e5@heytings.org>


>>> +    ;; Debbugs sometimes adds `[External] :'; if that happened,
>>> +    ;; delete everything up thru there.  Empirically, that deletion makes
>>> +    ;; the Subject match the other messages in the thread.
>> 
>> This is not accurate -- it's just Drew that insists on adding that 
>> string to his subjects.  I find it pretty odd to add general code to 
>> Emacs to handle a single person's Subject mangling.
>
> I don't think Drew does this himself.  It's probably something that the 
> MTA (mail transport argent) from Oracle adds.  I've seen similar 
> behavior from other people on other mailing lists, most often with 
> [External] or [EXTERNAL], so I would make the comparison 
> case-insensitive.
>

See https://its.uiowa.edu/support/article/114496 for a possible 
explanation.  This is typically something big corporations or government 
agencies do; for another example on this mailing list, see the posts from 
Stephan Mueller (microsoft.com), which use [EXTERNAL].



  reply	other threads:[~2021-05-12 14:17 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20210512030946.27770.7288@vcs0.savannah.gnu.org>
     [not found] ` <20210512030949.65CD421128@vcs0.savannah.gnu.org>
2021-05-12  8:16   ` master 47070ed 6/6: Merge branch 'master' of git.sv.gnu.org:/srv/git/emacs Robert Pluim
2021-05-12 12:50     ` Eli Zaretskii
2021-05-13  4:53       ` Richard Stallman
2021-05-13  6:38         ` Eli Zaretskii
2021-05-14  5:23           ` Richard Stallman
2021-05-14  7:00             ` Eli Zaretskii
2021-05-14 13:45               ` Stefan Monnier
2021-05-14 14:49                 ` Andreas Schwab
2021-05-16  4:37               ` Richard Stallman
     [not found] ` <20210512030948.6448F21128@vcs0.savannah.gnu.org>
2021-05-12 12:17   ` master 42596bd 2/6: Little improvements in rmail.el. Recognize encryped override headers Lars Ingebrigtsen
2021-05-12 13:12     ` Eli Zaretskii
2021-05-12 13:16       ` Lars Ingebrigtsen
2021-05-12 13:20       ` Eli Zaretskii
2021-05-12 15:14       ` Stefan Monnier
2021-05-12 15:45         ` Eli Zaretskii
2021-05-12 15:47         ` Lars Ingebrigtsen
2021-05-12 15:59           ` Eli Zaretskii
2021-05-12 15:54         ` Robert Pluim
2021-05-12 14:03     ` Gregory Heytings
2021-05-12 14:17       ` Gregory Heytings [this message]
2021-05-13  4:52     ` Richard Stallman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ef56467bdfd9d44c656c@heytings.org \
    --to=gregory@heytings.org \
    --cc=emacs-devel@gnu.org \
    --cc=larsi@gnus.org \
    --cc=rms@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).