Sven Riedel wrote:
> Hi,
>
> a while back someone kindly posted a rule here that matches on
> empty mails:
>
> header __X Content-Type =~ /^(message|multipart)/i
> rawbody __Y /\S/
> meta Z ( !X && !Y )
>
> Now I find that Z matches on all mails - investigation shows
> that Y matches on all non
Don't know. This meta rule seems to work fine for me.
Perhaps one of __X, __Y or Z is defined another rule. SA wouldn't
warn you on it.
Try changing their names to something longer and unique.
> On 8/3/05, Sven Riedel <[EMAIL PROTECTED]> wrote:
> >
> >
> > Hi,
> >
> > > On Wed, Aug 03, 2005 at
Title: RE: Question regarding meta rule handling
Hi,
> On Wed, Aug 03, 2005 at 08:18:16AM +0200, Sven Riedel wrote:
> > header __X Content-Type =~ /^(message|multipart)/i
> > rawbody __Y /\S/
> > meta Z ( !X && !Y )
> >
> > and yet the rule trigger
On Wed, Aug 03, 2005 at 08:18:16AM +0200, Sven Riedel wrote:
> header __X Content-Type =~ /^(message|multipart)/i
> rawbody __Y /\S/
> meta Z ( !X && !Y )
>
> and yet the rule triggers for me. Doing a
Of course. __X != X ... :)
--
Randomly Generated Tagline:
"The question is to what extent par
Hi,
a while back someone kindly posted a rule here that matches on
empty mails:
header __X Content-Type =~ /^(message|multipart)/i
rawbody __Y /\S/
meta Z ( !X && !Y )
Now I find that Z matches on all mails - investigation shows
that Y matches on all non-whitespaces as it should, and X
doesn't
