Developers of Sympa

[Olivier Salaün - CRU <address@concealed>]

Hi Adam,

I've fixed this to apply scenario conditions on all occurences of 
multi-valued header fields. Here is the patch :
http://sourcesup.cru.fr/cgi/viewcvs.cgi/sympa/src/List.pm?r1=1.648&r2=1.649&makepatch=1&diff_format=u

We think your extention to provide the message as a parameter to the 
scenario engines makes sense. Please submit your patch in our tracking 
system : https://sourcesup.cru.fr/tracker/?group_id=23

Adam Bernstein wrote:

> > I see no obvious reason why you wouldn't want to make that function 
> > available for command messages (as opposed to distributed list 
> > messages), and looking in the code, I think the cause is simply that 
> > the full message is not retained in the sequence of function calls 
> > involved in processing a command.  
>
> Well, I have succeeded in passing the message through all the 
> necessary calls so that subscribe (and all other) scenarios can all 
> use SMTP header matching for rule conditions.  However, I've hit 
> another problem: If you're trying to match Received: headers, the code 
> only checks the first (ie. most recent) Received: header for a match, 
> and then it stops looking.  So if you're looking for a match somewhere 
> further back in the SMTP chain, it always fails.