From: Kyle Meyer <kyle@kyleam.com>
To: Guillaume MULLER <guillaume.muller@univ-st-etienne.fr>
Cc: emacs-orgmode@gnu.org
Subject: Re: On the protection of emails in the archives
Date: Fri, 09 Apr 2021 02:14:04 -0400 [thread overview]
Message-ID: <8735w0ouhf.fsf@kyleam.com> (raw)
In-Reply-To: <edc5ab20-5c8a-d9f5-7028-e71e433e20b7@univ-st-etienne.fr>
Guillaume MULLER writes:
> Hi all,
>
> I recently sent an email on this mailing list (see
> https://orgmode.org/list/b1e778c5-acbf-8a17-c9bf-dcb6693e9845@univ-st-etienne.fr/
> )
>
> Since then, I'm receiving spams on the email address I used to send
> the message.
>
> After some research, it seems that this email address only appears on
> 2 websites, notably this orgmode.org mailing list archive.
Your email address can also be harvested from the lists.gnu.org
archives. Inspect the output of
$ curl -fSsL https://lists.gnu.org/archive/html/emacs-orgmode/2020-07/msg00125.html
$ curl -fSsL https://lists.gnu.org/archive/mbox/emacs-orgmode/2020-07
> Would it be possible to configure the archive to obfuscate / hide the
> email addresses inorder to protect its users?
<https://orgmode.org/list> and its upstream source
<https://yhetil.org/orgmode> are public-inbox
(<https://public-inbox.org/>) archives. There's an option (disabled by
default) to configure address obfuscation. However, in my view email
obfuscation is giving you a false sense of security. Ignoring other
ways spammers get your address, you're posting to a public space, and
your address can be harvested (and, as shown above, not just from these
public-inbox archives).
And this isn't something specific to Org mode's archives. Just as some
examples, take a look at <https://lore.kernel.org/git/>,
<https://issues.guix.gnu.org/>,
<https://lists.sr.ht/~sircmpwn/sr.ht-discuss/>, or
<https://lists.gnu.org/archive/html/emacs-devel/2021-04/msg00285.html>.
Anyway, that being said and despite my opinion on this, I'm considering
turning on obfuscation at <https://orgmode.org/list> and
<https://yhetil.org/orgmode>. There's at least one issue that'd need to
be fixed before doing so though:
<https://public-inbox.org/meta/87a6q8p5qa.fsf@kyleam.com/>.
next prev parent reply other threads:[~2021-04-09 6:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-08 8:29 On the protection of emails in the archives Guillaume MULLER
2021-04-08 9:13 ` Russell Adams
2021-04-08 19:12 ` Daniele Nicolodi
2021-04-09 6:14 ` Kyle Meyer [this message]
2021-04-09 6:58 ` Tim Cross
2021-04-09 16:01 ` Jean Louis
2021-04-09 22:32 ` Tim Cross
2021-04-10 0:43 ` Jean Louis
2021-04-10 1:27 ` Tim Cross
2021-04-09 15:58 ` Jean Louis
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8735w0ouhf.fsf@kyleam.com \
--to=kyle@kyleam.com \
--cc=emacs-orgmode@gnu.org \
--cc=guillaume.muller@univ-st-etienne.fr \
/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/org-mode.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).