From: Eli Zaretskii <eliz@gnu.org>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [OT] DKIM/DomainKeys headers in messages from this list
Date: Sun, 18 Mar 2012 17:02:00 -0000 [thread overview]
Message-ID: <834ntl3kry.fsf@gnu.org> (raw)
In-Reply-To: <20120318163432.GA2576@host2.jankratochvil.net>
> Date: Sun, 18 Mar 2012 17:34:32 +0100
> From: Jan Kratochvil <jan.kratochvil@redhat.com>
> Cc: gdb-patches@sourceware.org
>
> On Sat, 17 Mar 2012 12:13:09 +0100, Eli Zaretskii wrote:
> > Does anyone else see where those 2 annoying headers, or know where do
> > they come from? Can they be removed, please?
>
> They are useful anti-spam feature, they come from:
> Ian Lance Taylor: Domain key for gcc.gnu.org
> http://sourceware.org/ml/overseers/2011-q4/msg00083.html
Thanks.
next prev parent reply other threads:[~2012-03-18 17:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-17 8:52 [PATCH] Add autoload-breakpoints [0/7] Hui Zhu
2012-03-17 11:13 ` [OT] DKIM/DomainKeys headers in messages from this list Eli Zaretskii
2012-03-17 13:42 ` Hui Zhu
2012-03-17 14:43 ` Eli Zaretskii
2012-03-18 16:34 ` Jan Kratochvil
2012-03-18 17:02 ` Eli Zaretskii [this message]
2012-03-19 4:48 ` [PATCH] Add autoload-breakpoints [0/7] Yao Qi
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=834ntl3kry.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
/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