From: Ben Schmidt <mail_ben_schmidt@yahoo.com.au>
To: mlmmj@mlmmj.org
Subject: Re: [mlmmj] mlmmj wishlist request
Date: Tue, 03 Feb 2015 23:57:21 +0000 [thread overview]
Message-ID: <54D16061.1000702@yahoo.com.au> (raw)
In-Reply-To: <54D14B2F.3010003@vlsc.org>
Hi, Philip!
Mlmmj can do what you want already, I believe. Just add a subscriber of the
'nomail' type using the -n option to mlmmj-sub or by sending mail to
listname+subscribe-nomail@domain.tld. Nomail users can post to the list, but posts
are not distributed to them.
See the third paragraph of the description here:
http://mlmmj.org/docs/mlmmj-sub/
And the help list text (which you get by sending mail to listname+help@domain.tld)
also contains information on this (though in source form, not the most readable):
http://mlmmj.org/hg/listtexts/file/904ef6171308/en/help
Best regards,
Ben.
On 4/02/15 9:26 AM, webmaster@vlsc.org wrote:
> I've been successfully running a handful of small mlmmj lists for several months
> now, on an eApps centOS cloud server, running sendmail. I have a question/request
> related to a feature that I used to exploit when working with the old majordomo
> mailing list tool:
>
> When using majordomo it was possible to configure a "closed" list, in terms of
> senders and receivers of posts (functionally similar to how mlmmj works using the
> "subonlypost" control file), while at the same time it was also possible to
> configure a secondary file (containing addresses) that could only submit posts,
> but not receive any posts.
>
> Perhaps a simple example can illustrate how this might be used:
> Acme Services is run by a board of directors, and the board has their own closed
> mlmmj list. There are also several dept managers that work for Acme Services, and
> the board would like these managers to be able to communicate directly with all
> the members of the board by simply sending an email to the board list. On the
> other hand, the board doesn't want the managers receiving any of the board list posts.
>
> There are several other scenarios that might benefit from this ability - in fact
> I'd say it might find many uses, and the varied possibilities are likely the
> reason majordomo had this feature.
>
> I haven't seen anything that indicates this is somehow currently possible with
> mlmmj, so I apologize in advance for missing the notes on how to do this
> currently, if its already available.
>
> With mlmmj, I could envision having another directory similar to the existing
> "subscribers.d", that would contain file(s) of addresses that only had permission
> to "submit" posts.
>
> Or perhaps there could be some way to flag or code files contained in the existing
> "subscribers.d" directory that would indicate if the addresses it contains are
> only "submitters" or only " receivers" or both "submitters and receivers".
>
> I haven't looked under the hood far enough to know how simple or complicated this
> might be to implement with mlmmj (assuming its not there now) so I'm just sharing
> the thought, in the hope that someone might be intrigued by the idea of adding
> this feature, and hoping it would not be difficult to implement.
>
> Philip Parshley
>
next prev parent reply other threads:[~2015-02-03 23:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-03 22:26 [mlmmj] mlmmj wishlist request webmaster
2015-02-03 23:57 ` Ben Schmidt [this message]
2015-02-05 20:15 ` webmaster
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=54D16061.1000702@yahoo.com.au \
--to=mail_ben_schmidt@yahoo.com.au \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox