The mailing list for listmasters using Sympa

[Xavier Beaudouin <address@concealed>]

Hi David,

Le 17 janv. 08 à 06:08, David Verdin a écrit :

> Something's wrong with your scenario interpretation: the message  
> shouldn't be rejected. Your scenario states that, should all the  
> accepting rules fail, the message would be kept for moderation, not  
> rejected.
> I think that the scenario you showed us is not the one actually used  
> by Sympa.
>
> From the path you showed in your precedent message, I conclude that  
> you use an install-specific scenario (it is located directly in /usr/ 
> local/etc/sympa/scenari).
> As you're talking about 5.2 and 5.3.4, I guess you just upgraded,  
> didn't you?
> Then this is some things you could try:
> 1- check the pathes. Are your sure the pathes you sepcified at  
> install time correspond to your precedent install? For example, the  
> default install directory is /home/sympa/.
> 2- check the rights. Is Sympa able to read in the directory  
> containing the scenario?
> 3- check that there is list or robot specific scenario. If the list  
> directory contains a scenario, it will be used instead of the  
> install specif one.
> 4- check the list config. No offense, but that kind of things can  
> happen after all: are you sure your list is configured to use this  
> scenario?

In fact seems that my sympa has forgotten something. I had to reload  
using wwsympa the scenario and this works now.... Very strange...

Thanks for your help !

/Xavier

> Hope this helps.
>
> Regads,
>
> Xavier Beaudouin a écrit :
> > Hi there,
> >
> > Le 14 janv. 08 à 11:20, Xavier Beaudouin a écrit :
> >
> > > Hello,
> > >
> > > Le 14 janv. 08 à 03:51, David Verdin a écrit :
> > >
> > > > Hi,
> > > >
> > > > It is impossible to know why this message is sent to bad from the  
> > > > informations you provide.
> > > > Are you sure this email is the one the user is subscribed with ?
> > > > What scenario send do you use?
> > >
> > > A custom one :
> > >
> > > [kiwi@lists /usr/local/etc/sympa/scenari]$ more  
> > > send.privateoreditorkeycvs
> > > title.us Private, for caudiumforge users and moderated for non  
> > > subcribers
> > >
> > > match([sender], /@cvs.caudiumforge.net$/)       smtp,smime,md5  ->  
> > > do_it
> > > match([sender], /@users.sourceforge.net$/)      smtp,smime,md5  ->  
> > > do_it
> > > is_subscriber([listname],[sender])      smtp,smime,md5  -> do_it
> > > is_editor([listname],[sender])          smtp,smime,md5  -> do_it
> > > is_owner([listname],[sender])           smtp,smime,md5  -> do_it
> > > true()                                  smtp,smime,md5  -> editorkey
> > >
> > > This scenario vas working on sympa 5.2..
> >
> > Seems that I found why :
> >
> > Jan 15 17:14:48 lists sympa[18667]: main::DoFile() Processing /address@concealed 
> >  ; sender: Xavier Beaudouin <address@concealed>  ; message- 
> > id: <address@concealed>
> > Jan 15 17:14:48 lists sympa[18667]: main::DoMessage() Processing  
> > message for openvisp-commits with priority 5, <address@concealed 
> > >
> > Jan 15 17:14:48 lists sympa[18667]: main::DoMessage() Message for  
> > openvisp-commits from address@concealed rejected() because  
> > sender not allowed
> > Jan 15 17:14:49 lists sympa[18667]: Moving bad file address@concealed 
> >  to bad/
> >
> > Does match([sender], ...) has changed since sympa 5.2 ?
> >
> > /Xavier
>
> --
> David Verdin
> Comité réseau des universités

Attachment: smime.p7s
Description: S/MIME cryptographic signature