Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
To: buildroot@busybox.net
Subject: [Buildroot] Emails being substituted when reading via Gmane NNTP
Date: Fri, 24 Jun 2016 16:57:46 +0000	[thread overview]
Message-ID: <1466787406.2872.17.camel@synopsys.com> (raw)
In-Reply-To: <87vb167ukd.fsf@dell.be.48ers.dk>

Hi Peter,

On Sat, 2016-06-18 at 10:46 +0200, Peter Korsgaard wrote:
> > 
> > > 
> > > > 
> > > > > 
> > > > > > 
> > > > > > "Alexey" == Alexey Brodkin <Alexey.Brodkin@synopsys.com> writes:
> Hi,
> 
> ?>> I believe that is an intentional feature of gmane to make it more
> ?>> difficult to harvest email addresses:
> ?>>?
> ?>> http://gmane.org/tmda.php
> ?>>?
> ?>> According to that page, this is something you as a list maintainer can
> ?>> control (but users can enforce it for their mails).
> 
> ?> So for Buildroot your guys intentionally enabled that feature?
> 
> I think it is on by default - I at least don't recall explicitly
> enabling it.
> 
> ?> Even though idea is nice still in the "original" Buildroot list
> ?> all emails are displayed as they are, see
> ?> http://lists.busybox.net/pipermail/buildroot/2016-June/164199.html:
> ?-------------------------> 8-----------------------
> ?> Romain Naour romain.naour at gmail.com?
> ?-------------------------> 8-----------------------
> 
> ?> Given that probably that's not much sense in doing email obfuscation
> ?> in Gmane? IMHO it adds more trouble for good people than adds problems
> ?> to bad guys.
> 
> Notice that the obfuscated email addresses DO work. They simply get
> forwarded through gmane's spam filter.
> 
> But yeah, it probably doesn't help much in combating spam.

So any plan to disable that for BR on Gmane if it barely adds anything meaningful :)

-Alexey

  reply	other threads:[~2016-06-24 16:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-17  7:38 [Buildroot] Emails being substituted when reading via Gmane NNTP Alexey Brodkin
2016-06-17  8:52 ` Peter Korsgaard
2016-06-17 15:41   ` Alexey Brodkin
2016-06-18  8:46     ` Peter Korsgaard
2016-06-24 16:57       ` Alexey Brodkin [this message]
2016-06-24 20:16         ` Peter Korsgaard
2016-06-27  9:01           ` Alexey Brodkin
2016-06-22 18:23     ` Waldemar Brodkorb
2016-06-22 18:28       ` Alexey Brodkin

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=1466787406.2872.17.camel@synopsys.com \
    --to=alexey.brodkin@synopsys.com \
    --cc=buildroot@busybox.net \
    /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