From: Mads Martin Joergensen <mmj@mmj.dk>
To: mlmmj@mlmmj.org
Subject: Re: feature requests
Date: Mon, 20 Sep 2004 20:04:31 +0000 [thread overview]
Message-ID: <20040920200431.GS76919@mmj.dk> (raw)
In-Reply-To: <20040920191944.GA5112@cirrus.madduck.net>
* martin f krafft <madduck@madduck.net> [Sep 20. 2004 21:56]:
> > High on the TODO is the ability when posting to a subscribers only
> > posting list to get a reply whether one wants to be able to post from
> > this address in the future. A simple reply to that mail will subscribe
> > the address to the nomail list which is already implemented, just not
> > released yet.
>
> Yeah, that would be nice.
>
> However, please take care with automatic replies and the like.
> Challenge Response systems (of which this is one) are very painful
> if not done right; and I know not aof a single one done right.
>
> http://kmself.home.netcom.com/Rants/challenge-response.html
We send mails to the envelope from (Return-Path:) for confirmation of
subscription. I'm sure you want that?
> > This way one can have one address subscribed getting the mail, and
> > a bunch of addresses subscribed without getting any mail.
>
> Please allow for manual setting of such aliases as well. The nice
> thing about majordomo2's approach is that the addresses lose their
> right to post when someone unsubscribes. I don't think you can do
> that with the challenge system.
With mlmmj there's a seperate 'version' of the list, just like the
way digests are done in ezmlm.
If you send a mail to listname+subscribe-nomail@domain.tld you subscribe
to the list without getting any email from it ever. Handy if you read
your lists via the web, or through a news gateway.
So what could be done simply treat postings to a subscribers only
list from emails not subscribed, as if they were trying to subscribe to
the nomail version of it.
This way they only need one reply, and they are allowed to post from
this address.
To do it right, the mail that was originally sent, will of course be
posted to the list, if the person subscribes to the nomail version--a
little bit like moderation.
--
Mads Martin Joergensen, http://mmj.dk
"Why make things difficult, when it is possible to make them cryptic
and totally illogical, with just a little bit more effort?"
-- A. P. J.
next prev parent reply other threads:[~2004-09-20 20:04 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-20 19:19 feature requests martin f krafft
2004-09-20 19:33 ` Mads Martin Joergensen
2004-09-20 19:56 ` martin f krafft
2004-09-20 20:04 ` Mads Martin Joergensen [this message]
2004-09-20 20:10 ` martin f krafft
2004-09-20 20:24 ` Mads Martin Joergensen
2004-09-20 20:28 ` Mads Martin Joergensen
2004-09-20 20:38 ` martin f krafft
2004-09-20 20:54 ` Mads Martin Joergensen
2004-09-20 20:59 ` martin f krafft
2004-09-20 21:00 ` Mads Martin Joergensen
2004-09-20 21:04 ` martin f krafft
2004-09-20 21:05 ` Mads Martin Joergensen
2004-09-20 21:15 ` martin f krafft
2004-09-20 21:17 ` Mads Martin Joergensen
2004-09-20 21:21 ` martin f krafft
2004-09-20 21:25 ` Mads Martin Joergensen
2004-09-21 10:42 ` Morten K. Poulsen
2004-09-21 14:22 ` martin f krafft
2004-09-21 14:54 ` Morten K. Poulsen
2004-09-21 14:59 ` martin f krafft
-- strict thread matches above, loose matches on Subject: below --
2022-12-06 22:07 b4 prep HEAD fails when specifying branch point Mark Brown
2022-12-06 22:15 ` Konstantin Ryabitsev
2022-12-06 23:52 ` Feature requests Mark Brown
2022-12-09 21:09 ` Konstantin Ryabitsev
2022-12-12 12:22 ` Mark Brown
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=20040920200431.GS76919@mmj.dk \
--to=mmj@mmj.dk \
--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.