[This reply is also CC'd to mj2-dev]
>>>>> "HG" == Hansel, Glen <ghansel@ti.com> writes:
HG> How close is the functionality and the implementation on the restrict
HG> post logic in Majordomo 1.94.4 and Majordomo 2?
That depends on what you're asking. Mj2 supports the restrict_post
variable for backwards compatibility, but instead of keeping the addresses
in a special file that you can't remotely edit, Mj2 supports an arbitrary
number of "auxiliary lists" per list that you can manipulate remotely. You
can restrict posting to these. You can also do restriction based on
pattern matching or a host of other things.
HG> We are currently running Majordomo 1.94.4 and we need more flexibility
HG> with restrict post than the "mungedomain" option appears to provide.
mungedomain is Mj1's method of handling "fuzzy matching" on addresses. Mj2
extends this concept greatly, but it sounds as if that's not what you're
looking for.
HG> In particular, we would like to have some way to easily include
HG> everybody within a specific domain, like "*@ti.com". The idea here is
HG> to allow all internal users to post to the mailing list but restrict
HG> all external users.
What you want is "access_rules", the generalized access control mechanism.
To consult the list owner on posts not coming from ti.com, use a stanza
like:
# Consult the owner if the user's host doesn't end in "ti.com"
post
consult
$host !~ /ti\.com$/
You can do a rather large number of things using this mechanism. You can
restrict subscriptions (and indeed any command) this way as well.
HG> If Mj2 already has that capability, that's great and I would like to
HG> receive the details so that I can backfit the same concept into our
HG> Majordomo 1.94.4.
I'm not sure how you would backfit this into Mj1. Mj2 is a complete
rewrite.
- J<
References:
|
|
