The mailing list for listmasters using Sympa

[Nick Holden <address@concealed>]

Thanks, Olivier, but I don't think I've ever amended the scenarios in
sympa. The list in question should be a newsletter list, restricted to
moderators after confirmation.

The scenario source shows the following:

title.gettext Newsletter, restricted to moderators after confirmation

is_editor([listname],[sender])    smime           -> do_it
is_editor([listname],[sender])    smtp,md5,smime  -> editorkey
true()                          smtp,smime,md5     -> 
reject(reason='send_editor')


Is this 'buggy'? It looks the same as that on the sympa documentation.

Nick

On Mon, 2010-08-02 at 12:47 +0200, Olivier Salaün wrote:
> Hi Nick,
> 
> The first mail notice (referring to DISTRIBUTE/REJECT commands) is a 
> typical moderation message sent to a list moderator.
> The second mail notice (referring to CONFIRM command) is a confirmation 
> message. It is sent to a user whenever Sympa requires confirmation from 
> the mail sender. This is triggered by the authorization scenario engine 
> ("request_auth" action).
> 
> Therefore I suspect that your list is using a buggy send.x scenario.
> 
> Le 01/08/2010 23:10, Nick Holden a écrit :
> > Hi Olivier,
> >
> > Thanks for trying to help. I realise this may simply be that the list
> > type is one which is now supported differently in Sympa 6, but I am
> > currently stumped.
> >
> > Here is an example of the moderation problem.
> >
> > At 10:37 this morning the owner of one of the lists (called 'thought')
> > on my server sent a message to the list for distribution. As the list
> > requires moderation, sympa responded by sending back to him an email
> > which is titled "Message for list thought from email@emailaddress" - the
> > message begins "One new message for list thought from..." and includes
> > information about the message moderation queue and also a mailto link
> > for distributing or rejecting the message, using the keywords DISTRIBUTE
> > or REJECT.
> >
> > Sympa also (as expected) sends him (as the originator of the message) an
> > email saying that his message has been forwarded to moderators.
> >
> > He responds to the server that the message should be distributed.
> >
> > Sympa then sends him a message advising him to send a message back to
> > the sympa server with the instruction "CONFIRM" and then the message ID.
> >
> > The message ID is different between the sympa requests for DISTRIBUTE
> > and the one requesting CONFIRM, eg:
> >
> >
> >    
> >> To distribute the attached message in list thought:
> >> <mailto:address@concealed?subject=DISTRIBUTE%20thought%
> >>      
> > 20c5cbb26b128822235771b9e9b021e50d>
> >    
> >> Or send a message to address@concealed with the following
> >>      
> > subject:
> >    
> >> DISTRIBUTE thought c5cbb26b128822235771b9e9b021e50d
> >>
> >>      
> > ... compared to ...
> >
> >
> >    
> >> To distribute the attached message in list thought, click on the URL:
> >>
> >> mailto:address@concealed?subject=CONFIRM%
> >>      
> > 20305d07584b15e913e94d51c83c5077ff
> >    
> >> Or send a message to address@concealed@ with the following
> >>      
> > subject:
> >    
> >> CONFIRM 305d07584b15e913e94d51c83c5077ff
> >>      
> >
> > It seems as though sympa is trying to do two different things here, one
> > requiring the use of the CONFIRM keyword, and one using the DISTRIBUTE
> > keyword.
> >
> > At receipt of the second request for confirmation, the list owner
> > abandoned the email process, and logged on using the web interface and
> > approved the message, which was then sent out in the usual way.
> >
> > As you can imagine, this is confusing the list owner a lot!
> >
> > So, is this some kind of bug? Or is it simply that the list is using the
> > wrong configuration?
> >
> > Thanks,
> >
> > Nick
> >
> >    
> 
>