Skip to Content.
Sympa Menu

en - Re: [sympa-users] Moderating e-mails containing special header?

Subject: The mailing list for listmasters using Sympa

List archive

Chronological Thread  
  • From: Patrick von der Hagen <address@concealed>
  • To: address@concealed
  • Subject: Re: [sympa-users] Moderating e-mails containing special header?
  • Date: Tue, 16 Aug 2005 14:23:55 +0200

Am Dienstag, den 16.08.2005, 13:36 +0200 schrieb Olivier Salaün - CRU:
> In Sympa we consider this feature as relevant to the site policy, not
> to a specific mailing list policy. Therefore such a feature is not
> provided through the list admin pages.
Hmmm, it's a pity. My current policy is to require all lists to have
such a filter, but the decision, whether to act on 5 points or on 10
points, is left to the owner. Well, I'll just have to provide lots of
scenari...

> Sympa has a scalable and extensible authentication and authorization
> architecture that is well described in the reference manual :
> http://www.sympa.org/doc/html/node12.html
> http://www.sympa.org/doc/html/node13.html
>
> You can also read this article :
> http://www.sympa.org/documentation/AA-in-Sympa/
I had a look at both sources, but still don't understand all the
details. http://www.sympa.org/doc/html/node13.html gives no information,
if there is a special ordering in which the rules are evaluated.
For example, I might have
is_owner([listname],[sender]) smtp -> request_auth
is_listmaster([sender]) smtp -> do_it
true() md5,smime -> do_it

Well, it would certainly be a stupid configuration, no doubt about it...

But what will happen, if the listmaster happens to be the listowner?
Which rule would trigger? Given
http://www.sympa.org/documentation/AA-in-Sympa/ I'd suppose the first
rule would win, but I'm not quite sure about it.

Is there a way to combine several rules? For example, the listowner
might be allowed to send attachments, but no one else?
"is_owner([sender]) && match([header->Content-type],/multipart/) md5
do_it"?

Without "and" or "or" I wouldn't know how to create such a condition.
"all()" might offer a soulution, but all() is just mentioned as a
possible, valid rule without explaining what it really does. IMHO those
rules are "described", but not necessarily "well described".

--
CU,
Patrick.





Archive powered by MHonArc 2.6.19+.

Top of Page