Developers of Sympa

[Aumont - Comite Reseaux des Universites <address@concealed>]

Adam Bernstein wrote:

> Dear Sympa crew:
>
> Problem 1: I'm unable to create a scenario that will, for instance,
> limit postings to subscribers (send.private) but forward messages
> with attachments to the moderator for approval.  Only one condition
> is checked in the scenario file, and the first one that matches is
> used.  So, if [is_subscriber] is first and it says do_it, all
> messages will be posted; if the attachment filter is first and it
> says editorkey, then all messages will be forwarded to the moderator
> for approval, even from non-subscribers.  Is there any way to require
> a message to match multiple conditions in a scenario?
You can do it starting teh scenario with :
!is_subscriber([listname],[sender]) smtp,md5,smime -> reject

At this stage any message is comming from a subscriber, you can test if 
the message must be submitted to editor because of a attachement or 
accept it

> Problem 2 (much more important): The current scenario scheme, by
> its design, becomes less and less usable with each new independent
> condition.  Adding a new condition to a system with N send scenarios
> means possibly doubling the number to 2xN -- "private with attachments
> rejected", "public with attachments rejected", etc. -- which means
> doubling the number of choices in the Send parameter for list admins.
> It's all very redundant and confusing for them.  What we need is to
> be able to select each condition independently -- "private", 
> "attachments rejected", "non-subscribers forwarded to moderator" --
> which will *greatly* simplify the WWSympa list admin interface.  
> You've indicated before that this is not in the plans, but it really
> is needed.  I will spend some time on developing it, but only if it
> will definitely be integrated into the Sympa distro.
We known various limiation of scenario

- they are not self documented so it is difficult for list owner to 
chose one
- they may be a large number of authorisation scenario all of them are 
not usefull for all kind of list : we need a way to limit the list of 
availible scenario for lists.
- there is a need for a scenari editor.
- scenario must return the reason of any reject

A large TODO...