From: Christoph Loesch <wireguard-mail@chil.at>
To: <wireguard@lists.zx2c4.com>
Subject: Re: User on mailinglist that collects addresses to send spam?
Date: Sat, 28 Jan 2023 00:34:53 +0100 [thread overview]
Message-ID: <373d9237-1b23-93cd-fa4e-b5fc14e6007b@chil.at> (raw)
In-Reply-To: <f982e6d1-902f-d698-892d-54c5bb041844@chil.at>
Hi,
wouldn't it be a consideration worth to hide or at least obfuscate mail addresses a bit more in mailman on this list here?
Mailman is able to obfuscate this better, see for example on lists.funkfeuer.at
Since I wrote the first time here about the "offer" I got, I'm getting more and more "spam" in the last weeks on the address I registered here on this list.
How do you work with this situation? Update/add rules in Mailfilter until the next mail comes through? Cat and mouse game? ;)
Kind regards,
Am 17.01.2023 um 19:42 schrieb Christoph Loesch:
> Hi,
>
> thank you for the for explanation.
>
> Interesting, some months ago I wanted to lookup something in the archive and couldn't access it, so I assumed since then that the archive is not publicly available.
> Was maybe some hickup or temporary issue...
>
> Well, that explains it then..
>
> Thanks and kind regards!
>
> Am 17.01.2023 um 10:35 schrieb Jaron Kent-Dobias:
>> 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-27 23:35 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
2023-01-17 18:42 ` Christoph Loesch
2023-01-27 23:34 ` Christoph Loesch [this message]
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=373d9237-1b23-93cd-fa4e-b5fc14e6007b@chil.at \
--to=wireguard-mail@chil.at \
--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).