Mark Sapiro wrote:
>In any case, the '^' was not the
>critical change to your pattern; it is changing '\s' to '\s*' (which
>will also allow '\r' at the end that is critical.
Just to be sure there's no misunderstanding, the above should have said
In any case, the '^' was not the
critical change
Peter Davis wrote:
>
>Mark Sapiro wrote:
>
>> Since by default, membership tests are done before
>> bounce_matching_headers, you could use bounce_matching_headers to hold
>> the spam and the test will be done after membership.
>>
>Possibly, but I want to hold these messages to determine whether
Thanks, Mark,
Mark Sapiro wrote:
> I assume you are using header_filter_rules, not bounce_matching_headers.
>
Correct.
> Since by default, membership tests are done before
> bounce_matching_headers, you could use bounce_matching_headers to hold
> the spam and the test will be done after member
Peter Davis wrote:
>
>I just inherited ownership of a Mailman 2.1.5 list, my first exposure to
>Mailman, though I've run lists on majordomo, Yahoo!, etc. I've checked
>the FAQ, but didn't find answers to these:
>
>1) If my list is set so that only members can post, and I have a spam
>filter set
I just inherited ownership of a Mailman 2.1.5 list, my first exposure to
Mailman, though I've run lists on majordomo, Yahoo!, etc. I've checked
the FAQ, but didn't find answers to these:
1) If my list is set so that only members can post, and I have a spam
filter set up to hold messages whose
