public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Drake Wyrm <wyrm@haell.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] reply-to munging
Date: Thu, 14 Apr 2005 10:25:31 -0700	[thread overview]
Message-ID: <20050414172531.GA27204@phaenix.haell.com> (raw)
In-Reply-To: <425E9B3B.3030607@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 1181 bytes --]

At 2005-04-14T09:32:59-0700, Donnie Berkholz <spyderous@gentoo.org>
wrote:
> Reply to List hasn't even worked properly for me since switching to
> the new server or whatever. It duplicates to @gentoo.org and
> @lists.gentoo.org. I'd guess this has something to do with people
> sending to @gentoo.org when the list thinks it's @lists.gentoo.org,
> and it never gets things figured out.

I noticed that. It took me a couple of double-postings before I fixed it
on my end with a procmail recipe. Pardon the strangely-wrapped line. I
figure most of you can figure it out.

      39 :0
      40 * ^list-id:.*gentoo
      41 {
      42 
      43 # fix the problem where mailing list emails
      44 # get sent to several equivalent addresses
      45 # requires GNU sed
      46 :0hf
      47 |sed -re '/^((mail-followup-|reply-)?to|from|cc|list-post): /I s/@(li
         sts|robin)\.gentoo\.org/@gentoo.org/g'
      48 
      49 INCLUDERC=$HOME/.procmail.d/gentoo-lists.procmailrc
      50 
      51 }

-- 
Batou: Hey, Major... You ever hear of "human rights"?
Kusanagi: I understand the concept, but I've never seen it in action.
  --Ghost in the Shell

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2005-04-14 17:25 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-14  8:54 [gentoo-dev] reply-to munging Paul de Vrieze
2005-04-14  9:01 ` Andrea Barisani
2005-04-14  9:06   ` Georgi Georgiev
2005-04-14  9:11     ` Andrea Barisani
2005-04-14 11:18       ` Chris Gianelloni
2005-04-14 13:49         ` Ming Zhao
2005-04-14 14:15           ` Stuart Longland
2005-04-14 15:23             ` Chris Gianelloni
2005-04-14 15:42               ` Ciaran McCreesh
2005-04-14 18:59                 ` Chris Gianelloni
2005-04-14 16:32               ` Donnie Berkholz
2005-04-14 17:25                 ` Drake Wyrm [this message]
2005-04-14 18:11                 ` Paul de Vrieze
2005-04-14 19:01                   ` Chris Gianelloni
2005-04-15  6:02                   ` [gentoo-dev] " Duncan
2005-04-15  6:35                 ` [gentoo-dev] " Andrea Barisani
2005-04-15 19:52                   ` Donnie Berkholz
2005-04-16  8:59                     ` Andrea Barisani
2005-04-16  9:09                       ` Donnie Berkholz
2005-04-14 20:10               ` Jason Wever
2005-04-15  0:37                 ` Georgi Georgiev
2005-04-17 18:02                 ` D. Wokan
2005-04-14 23:20               ` Stuart Longland
2005-04-15  8:50                 ` [gentoo-dev] " Torsten Veller
2005-04-15 11:32                 ` [gentoo-dev] " Chris Gianelloni
2005-04-14 12:12       ` Graham Murray
2005-04-14 12:40       ` Ciaran McCreesh
2005-04-14  9:16     ` Spider
2005-04-14  9:11   ` Paul de Vrieze
  -- strict thread matches above, loose matches on Subject: below --
2002-05-25 16:31 [gentoo-dev] Reply-To Munging Chad M. Huneycutt
2001-01-08  5:26 [gentoo-dev] reply-to munging drobbins

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=20050414172531.GA27204@phaenix.haell.com \
    --to=wyrm@haell.com \
    --cc=gentoo-dev@lists.gentoo.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