Mercurial > hg > mlmmj
changeset 387:76232e610354
1.1.0-RC3 prep
| author | mmj |
|---|---|
| date | Fri, 26 Nov 2004 07:01:02 +1100 |
| parents | 7a484c4b7925 |
| children | b58c5059749e |
| files | ChangeLog README README.access VERSION |
| diffstat | 4 files changed, 32 insertions(+), 20 deletions(-) [+] |
line wrap: on
line diff
--- a/ChangeLog Fri Nov 26 07:00:53 2004 +1100 +++ b/ChangeLog Fri Nov 26 07:01:02 2004 +1100 @@ -1,3 +1,6 @@ +1.1.0-RC3 + o Add 'moderate' tag for usage in control/access when one wants to have the + moderators moderate posts hitting this regexp. See README.access o Add a To: header with the recipient's address when sending digests 1.1.0-RC2 o Strip envelope from before resending to +owner
--- a/README Fri Nov 26 07:00:53 2004 +1100 +++ b/README Fri Nov 26 07:01:02 2004 +1100 @@ -1,4 +1,4 @@ -README mlmmj-1.1.0-RC2 November 22th 2004 +README mlmmj-1.1.0-RC3 November 25th 2004 This is an attempt at implementing a mailing list manager with the same functionality as the brilliant ezmlm, but with a decent license and mail server @@ -17,6 +17,7 @@ · Functionality to retrieve old posts · Web-interface · Digests + · No mail delivery subscription To use mlmmj, do the following:
--- a/README.access Fri Nov 26 07:00:53 2004 +1100 +++ b/README.access Fri Nov 26 07:01:02 2004 +1100 @@ -1,5 +1,5 @@ README.access present in mlmmj versions >= 0.8.0 - + (moderate tag since 1.1.0-RC3) Access control in mlmmj ======================= @@ -13,16 +13,18 @@ all headers are first tested against the first rule, then all headers are tested against the second rule, and so on. -The first rule to match a header decides which action to take - allow or -deny the post. +The first rule to match a header decides which action to take - allow, deny +or moderate the post. The syntax is quite simple: action[ [!]regexp] -- "Action" can be "allow" or "deny". +- "Action" can be "allow", "deny" or "moderate". - The optional "!" makes the rule a match, if NO header matches the regular expression. - "Regexp" is a POSIX.2 extended regular expression. Matching is done case insensitive. +IMPORTANT: if "moderate" is used then don't forget to add people who should + function as moderators in listdir/control/moderators First a simple example. This rule set will reject any mail that is NOT plain text, or has a subject that contains "BayStar", and allow anything else: @@ -31,6 +33,12 @@ deny ^Subject:.*BayStar allow +To allow only text mails, but have the moderators moderate every html mail one +would use this: + + allow ^Content-Type: text/plain + moderate ^Content-Type: text/html + deny Now on to a more advanced example. Morten can post anything, Mads Martin can post if the subject does not contain "SCO". Everything else is denied: @@ -42,7 +50,6 @@ The last rule (deny) can be left out, as deny is the default action. - A third example. Deny any mails with "discount", "weightloss", or "bonus" in the subject. Allow PGP signed and plain text mails. Anything else is denied: @@ -51,3 +58,4 @@ deny ^Subject:.*bonus allow ^Content-Type: multipart/signed allow ^Content-Type: text/plain +