The mailing list for listmasters using Sympa

[Chris Hastie <address@concealed>]

On Mon, 17 Oct 2005, address@concealed wrote
>   Edward Rynes <address@concealed> recently wrote (in part):
>
> > I too have had complaints from our users about this
> > feature/problem.
>
>   Looking for list robot commands in the body of a posting is a
>   hold over from the old days of mailing lists.  We have been
>   running ListProc for a very long time, and even for that
>   system which does *not* have a web interface for managing a
>   list or subscription, this feature seems to trap more
>   legitimate postings then it does misdirected ones.
>
>   Command detection should probably be left as an option for the
>   individual list owner who can turn it on if such postings have
>   historically been a problem for their own particular list.

I currently have an include.send.header scenario to trap anything that 
looks like it might be a vacation response and send it to the list's 
editor. I wonder if this might be a better, or at least more 
configurable and flexible approach to trapping commands?

This is what I use now:
match ([header->precedence], /list|bulk/)               smtp,smime,md5   -> 
reject,quiet
match ([header->subject], /auto( |-)+respon(se|der)/)   smtp,smime,md5   -> 
editorkey,quiet
match ([header->subject], /out of (the )+office/)       smtp,smime,md5   -> 
editorkey,quiet
match ([header->subject], /auto( |-)+reply/)            smtp,smime,md5   -> 
editorkey,quiet
match ([header->subject], /(vacation|holiday)/)         smtp,smime,md5   -> 
editorkey,quiet

I had a message to this list trapped by this mechanism yesterday, but 
reading through this thread I think I've found the answer to my question 
- wait for 5.2 (I was wondering if the subscriber confirmation request 
was customisable yet in 5.1 - I hacked 4.1 to make it so and don't 
really want to have to hack again when I upgrade).
--
Chris Hastie