From: Mike Grice <incubus@ice-breaker.net>
To: mlmmj@mlmmj.org
Subject: Re: Feature Request: Subscriber Lists
Date: Wed, 13 Apr 2005 08:01:34 +0000 [thread overview]
Message-ID: <1113379294.4608.16.camel@localhost.localdomain> (raw)
In-Reply-To: <1113237126.4613.5.camel@localhost.localdomain>
On Tue, 2005-04-12 at 20:23 -0700, Christopher Mahmood wrote:
> * Jakob Hirsch (jh@plonk.de) [050412 16:15]:
> > Christian Laursen wrote:
> >
> > >So the bad guys can send the subscriber list to the owner.
> >
> > The talk was also about list management.
> > list is harmless, obviously (unless you have a really large list).
>
> The worst a bad guy can do is generate confirmation requests that
> are sent to the owner (or moderator in the case of ezmlm+idx).
> Unless they can actually read the mail that is sent and get the
> authentication cookie in the reply-to address there's nothing they
> can do.
>
> This kind of sums it up for ezmlm+idx:
> http://www.dk.ezmlm.org/faq/FAQ-4.html#ss4.17
> http://www.dk.ezmlm.org/faq/FAQ-4.html#ss4.14
In regards to the $listname+list command, this is exactly what I meant.
In summary, the list-owner has control of the destination address for
the list command, so there are no problems. Even doing it in a
spam-style way is moot as the list owner can always be contacted at the
$listname-owner (in ezmlm) way anyway.
My main reason for requesting this feature is that I'm moving an ISP
over from ezmlm to mlmmj (hopefully!). This is just pretty much the
remaining feature that if I can get, customers don't get any loss in
functionality.
I was hoping it wouldn't be a 'biggie' to implement as the functionality
is already available via the mlmmj-list command.
It's probably possible to code up some kind of wrapper, but given how
elegant mlmmj is anyway, it would be really nice to have.
Mike
--
Sticking feathers up your butt does not make you a chicken.
next prev parent reply other threads:[~2005-04-13 8:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-11 16:32 Feature Request: Subscriber Lists Mike Grice
2005-04-11 17:50 ` Vegard Svanberg
2005-04-11 18:14 ` Jakob Hirsch
2005-04-11 20:51 ` Mike Grice
2005-04-12 18:37 ` Jakob Hirsch
2005-04-12 21:27 ` Christian Laursen
2005-04-12 22:40 ` Jakob Hirsch
2005-04-12 22:55 ` Christian Laursen
2005-04-12 23:15 ` Jakob Hirsch
2005-04-13 3:23 ` Christopher Mahmood
2005-04-13 8:01 ` Mike Grice [this message]
2005-04-16 16:24 ` Mike Grice
2005-04-26 9:32 ` Mads Martin Joergensen
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=1113379294.4608.16.camel@localhost.localdomain \
--to=incubus@ice-breaker.net \
--cc=mlmmj@mlmmj.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.