From: Markus Krainz <ldm@gmx.at>
To: Marc MERLIN <marc@merlins.org>
Cc: dm-crypt@saout.de
Subject: Re: [dm-crypt] Fwd: saout.de mailing list memberships reminder
Date: Thu, 20 Dec 2012 18:25:08 +0100 [thread overview]
Message-ID: <50D349F4.9030004@gmx.at> (raw)
In-Reply-To: <20121220170358.GA9233@merlins.org>
Am 20.12.2012 18:03, schrieb Marc MERLIN:
> On Thu, Dec 20, 2012 at 04:55:09PM +0100, Markus Krainz wrote:
>> Hi,
>>
>> I think the forwarded message speeks for itself :)
> I used to be mailman admin for sourceforge, a few million folks just like
> you.
> I got so tired of answering mails like this one that I wrote an FAQ :)
>
> http://marc.merlins.org/netrants/mailman-password.txt
>
> Note, if you disagree, you are welcome to change your password further or
> unsubscribe.
>
> Marc
That's a nice FAQ.
However most points are moot imho. The users that don't read
instructions are the most vulnerable for this kind of practice because
they tend to use same passwords every time and you'd rather not send
their passwords if in doubt they read instructions. In any case I don't
care too much from someone changing the subscription settings but it
violates trust that users are used to when they put in a password. Maybe
you do it for legal reasons but there's nothing about in the faq. So
again it just seems odd.
However you are of course free to do what you want with the lists and it
seems it has been discussed extensively alrady.
Best, Markus
next prev parent reply other threads:[~2012-12-20 17:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.140.1351742424.23588.mailman@saout.de>
2012-12-20 15:55 ` [dm-crypt] Fwd: saout.de mailing list memberships reminder Markus Krainz
2012-12-20 16:05 ` [dm-crypt] [Off topic] " Alasdair G Kergon
2012-12-20 17:08 ` Markus Krainz
2012-12-20 17:03 ` [dm-crypt] " Marc MERLIN
2012-12-20 17:25 ` Markus Krainz [this message]
2012-12-25 1:14 ` Karol Babioch
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=50D349F4.9030004@gmx.at \
--to=ldm@gmx.at \
--cc=dm-crypt@saout.de \
--cc=marc@merlins.org \
/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