From: Matti Aarnio <matti.aarnio@zmailer.org>
To: linux-kernel@vger.kernel.org
Subject: New List Manager experiment at vger.kernel.org
Date: Mon, 13 Jul 2009 13:00:35 +0300 [thread overview]
Message-ID: <20090713100035.GI10130@mea-ext.zmailer.org> (raw)
I am doing some experimenting of a new list manager concept for vger.
If things go well, it will replace Majordomo, and the command interface
will be similar to Majordomo -- including eventual address where it
responds: majordomo@vger ...
Right now the thing is available for the curious at:
listmanager@vger.kernel.org
The main difference in here against the Majordomo, and even Mailman is
that this system uses SQL database to keep track of lists, subscribers,
and subscriptions. Not individual text (or horrors - object serialization
binary streams!) files.
Supported commands:
lists
which
subscribe listname
unsubscribe listname
unsubscribe *
auth ...
They are similar, and yet slightly different from Majordomo's commands.
For example the authentication token is unique random blob, which has
meaning only for given user trying to subscribe OR UNSUBSCRIBE, and one
can not predict its value, thus malicious removal on somebodys subscriptions
is at least difficult.
The "help" command will be replaced with a web-page describing the commands.
At present the system is in development mode, and no email traffic goes
thru it. However it has utility to import all existing VGER's Majordomo
list configurations, and subscribers, which utility I do run quite often
to prime databases - especially after altering database schemas.
The 'lists' command shows all public list email addresses, and how many
'direct delivery' subscribers there are.
The 'subscribe' command adds email address, and subscription data in state
'unconfirmed', and calls for confirmation.
Doing then 'auth' commands in shown way will change state to
value 'direct'. Somewhere in deep plans is to add also 'digest',
but we shall see...
The 'unsubscribe *' will send a list of "please send these
'auth ... unsubscribe NNN' commands back to me, if you approve."
The 'which' is best explained by an example:
# << which
# List of subscriptions for this address:
# linux-kernel@vger.kernel.org (direct)
# netdev@vger.kernel.org (unconfirmed)
# netfilter@vger.kernel.org (unconfirmed)
Doing a set of 'subscribe' commands followed by 'which' command will
show you something like this above example has. The 'linux-kernel'
subscription has been confirmed with 'auth' command, thus its state
is 'direct', others are still pending.
Somebody will want to know if the sources will be available.
Yes, but it is only my 3rd day of hacking at it yet...
/Matti Aarnio -- one of <postmaster@vger.kernel.org>
reply other threads:[~2009-07-13 10:09 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20090713100035.GI10130@mea-ext.zmailer.org \
--to=matti.aarnio@zmailer.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®