public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Jim Blandy <jimb@redhat.com>
To: overseers@sources.redhat.com
Subject: GMANE archive and E-mail address encryption
Date: Thu, 13 Nov 2003 21:34:00 -0000	[thread overview]
Message-ID: <vt2vfpolzty.fsf@zenia.home> (raw)


The gdb@ and gdb-patches@ are both archived on gmane.org.  Since that
site makes messages available via both HTTP and NNTP, spam harvesters
could gather addresses from there.  It tries to obscure the addresses
when it presents them via HTTP, but it can't really do that with NNTP.

GMANE does, however, have an option that list administrators can
request that will encrypt E-mail addresses when they appear in the
archives --- and provide forwarding so that the encrypted addresses
actually work.  For details, see:

    http://gmane.org/tmda.php

I don't know a reliable way to check this, but it seems to me that
address encryption is not enabled for gdb@ and gdb-patches@.  Could we
turn that on?  The FAQ says how to go about that:

    http://gmane.org/faq.php

             reply	other threads:[~2003-11-13 21:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-13 21:34 Jim Blandy [this message]
2003-11-13 22:01 ` Ian Lance Taylor
2003-11-13 22:14   ` Christopher Faylor

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=vt2vfpolzty.fsf@zenia.home \
    --to=jimb@redhat.com \
    --cc=overseers@sources.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).