From: Jaron Kent-Dobias <jaron-wg@kent-dobias.com>
To: wireguard@lists.zx2c4.com
Subject: Re: User on mailinglist that collects addresses to send spam?
Date: Tue, 17 Jan 2023 10:35:54 +0100 [thread overview]
Message-ID: <Y8Zr+l4j2oqjLqLP@mail.kent-dobias.com> (raw)
In-Reply-To: <5d0d60df-ee8c-87ab-379b-31ed33675668@chil.at>
Hello,
On Tuesday, 17 January 2023 at 00:45 (+0100), Christoph Loesch wrote:
>I use a separate mail-address for every site/contact who wants my
>mail-address. Just checked my spam-folder and what do I see? a mail
>from janisa@onertronics.com to my wireguard mail-address which I use
>only for this mailinglist. So I guess janisa@onertronics.com is
>collecting mail-addresses here and then sending unwanted spam-mails.
It's nothing so complicated: the wireguard list is publicly archived
online, addresses included (with minor obfuscation).
An example:
https://lists.zx2c4.com/pipermail/wireguard/2019-July/004276.html
Jaron
next prev parent reply other threads:[~2023-01-17 9:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-16 23:45 Christoph Loesch
2023-01-17 9:35 ` Jaron Kent-Dobias [this message]
2023-01-17 18:42 ` Christoph Loesch
2023-01-27 23:34 ` Christoph Loesch
2023-02-07 22:10 ` Jason A. Donenfeld
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=Y8Zr+l4j2oqjLqLP@mail.kent-dobias.com \
--to=jaron-wg@kent-dobias.com \
--cc=wireguard@lists.zx2c4.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 NNTP newsgroup(s).