On Sat, 3 Feb 2018, Alex wrote:
Hi,
The only "solution" I've ever come up with is to create a meta rule group to
account for the Subject hit:
body __FOO /foo/
header __SUBJ_FOO Subject =~ /foo/
meta FOO __FOO && !__SUBJ_FOO
I have to admit it's annoyed me on occasion that I can't create
On 3 Feb 2018, at 16:37 (-0500), Bill Cole wrote:
On 2 Feb 2018, at 16:59 (-0500), Kevin A. McGrail wrote:
There is no solution at the moment. The subject is appended to the
body of the text for rule parsing.
The 2nd sentence is wrong: the subject is *prepended* to the body.
Also: the
On 2 Feb 2018, at 16:59 (-0500), Kevin A. McGrail wrote:
There is no solution at the moment. The subject is appended to the
body of the text for rule parsing.
The 2nd sentence is wrong: the subject is *prepended* to the body. Also:
the 1st sentence is wrong, there's no *PRETTY* solution.
On 2/3/2018 2:28 PM, Alex wrote:
I've also had a problem when trying to write rules that rely on or
otherwise measure the length of the body. A more complicated set of
rules are needed for that, if it's even possible/reliable.
Take a look at these rules for an example:
72_active.cf:
On 2/2/2018 6:09 PM, John Hardin wrote:
There is no solution at the moment. The subject is appended to the
body of the text for rule parsing. I've added a task I plan to
submit for GSOC consideration to add a tflag to disable this behavior.
Globally, or per-rule?
A tflag affect just
Hi,
>> The only "solution" I've ever come up with is to create a meta rule group to
>> account for the Subject hit:
>>
>> body __FOO /foo/
>> header __SUBJ_FOO Subject =~ /foo/
>> meta FOO __FOO && !__SUBJ_FOO
>>
>> I have to admit it's annoyed me on occasion that I can't create a single
>>
On 2 Feb 2018, at 14:27, Kris Deugau wrote:
> The only "solution" I've ever come up with is to create a meta rule group to
> account for the Subject hit:
>
> body __FOO /foo/
> header __SUBJ_FOO Subject =~ /foo/
> meta FOO __FOO && !__SUBJ_FOO
>
> I have to admit it's