From: Jakob Hirsch <jh@plonk.de>
To: mlmmj@mlmmj.org
Subject: Re: Feature Request: Subscriber Lists
Date: Tue, 12 Apr 2005 18:37:48 +0000 [thread overview]
Message-ID: <425C157C.5080708@plonk.de> (raw)
In-Reply-To: <1113237126.4613.5.camel@localhost.localdomain>
Mike Grice wrote:
>>should be not too hard to implement, but it has to be password- or
>>challange/response-protected.
> The thing is, (IIRC) ezmlm lets you do this. You don't need to password
> it because it's only allowed to be requested by the owner, and the reply
> goes back to the configured owner address.
And how is the owner identified?
I like the idea, as long as it's protected properly.
next prev parent reply other threads:[~2005-04-12 18:37 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 [this message]
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
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=425C157C.5080708@plonk.de \
--to=jh@plonk.de \
--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.