From: Segher Boessenkool <segher@kernel.crashing.org>
To: gcc-patches@gcc.gnu.org
Cc: Segher Boessenkool <segher@kernel.crashing.org>
Subject: [wwwdocs] lists: Correct procmail recipe
Date: Tue, 1 Jun 2021 16:01:58 +0000 [thread overview]
Message-ID: <8beab8102fd97e0bc745a285e619c08c52d74b6f.1622563227.git.segher@kernel.crashing.org> (raw)
We haven't had Sender: for a while now. Use the standard List-Id:
header in its place.
Committed.
Segher
---
htdocs/lists.html | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/htdocs/lists.html b/htdocs/lists.html
index 42a44ab83d9b..4ac5d5a84cd1 100644
--- a/htdocs/lists.html
+++ b/htdocs/lists.html
@@ -217,8 +217,8 @@ with enough prodding, that sending mail to the address listed in
<h2>Filtering</h2>
<p>If you want to use procmail or similar tools to process the GCC
-mailing lists, you can filter using the Sender: header, as well as all
-of the RFC2369 headers (List-Subscribe, List-Unsubscribe, List-Post,
+mailing lists, you can filter using the List-Id: header from RFC2919, as well
+as all of the RFC2369 headers (List-Subscribe, List-Unsubscribe, List-Post,
List-Archive, etc.).</p>
<p>For example, the following procmail rule will sort all mail from
@@ -226,7 +226,7 @@ our lists into a single folder named INLIST.gcc:</p>
<blockquote><p><code>
:0<br />
-* ^Sender: .*-owner@gcc.gnu.org<br />
+* ^List-Id: .*<.*@gcc.gnu.org>$<br />
INLIST.gcc<br />
</code></p></blockquote>
@@ -235,7 +235,7 @@ can use the following recipe (Use at your own risk!):</p>
<blockquote><p><code>
:0 Wh: msgid.lock<br />
-* ^Sender: .*-owner@gcc.gnu.org<br />
+* ^List-Id: .*<.*@gcc.gnu.org>$<br />
| formail -D 8192 msgid.cache
</code></p></blockquote>
--
1.8.3.1
next reply other threads:[~2021-06-01 16:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-01 16:01 Segher Boessenkool [this message]
2021-06-01 16:28 ` Andreas Schwab
2021-06-02 8:44 ` Gerald Pfeifer
2021-06-02 14:26 ` Segher Boessenkool
2021-06-03 23:10 ` Hans-Peter Nilsson
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8beab8102fd97e0bc745a285e619c08c52d74b6f.1622563227.git.segher@kernel.crashing.org \
--to=segher@kernel.crashing.org \
--cc=gcc-patches@gcc.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.
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).