On 01 March 2002, Craig R Hughes said:
> Just changed it in CVS to:
>
> header SUBJ_ALL_CAPS Subject =~ /^[^a-z]*$/
But that'll match an empty subject. (No comments on whether that's a
spam discriminator, but it probably happens more often in non-spam than
an "ALL CAPS" subject does
Just changed it in CVS to:
header SUBJ_ALL_CAPS Subject =~ /^[^a-z]*$/
C
Greg Ward wrote:
> Date: Fri, 1 Mar 2002 08:49:34 -0500
> From: Greg Ward <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject: Re: [SAtalk] rule SUBJ_ALL_CAPS not working right
>
>
The key to this rule is it triggers if there's no lower case in the subject.
It's somewhat misnamed. If you're seeing legitimate subject lines with no lower
case letters in them, please forward the subject lines so we can analyze and
adapt the rule. Thanks.
C
Evert Jan van Ramselaar wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> -Original Message-
> From: Craig R Hughes [mailto:[EMAIL PROTECTED]]
> Sent: Friday, March 01, 2002 8:07 PM
> Subject: Re: [SAtalk] rule SUBJ_ALL_CAPS not working right
>
>
> The key to this rule is it triggers if
Date: Fri, 1 Mar 2002 12:06:29 +0100
> From: Gunter Ohrner <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject: Re: [SAtalk] rule SUBJ_ALL_CAPS not working right
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Am Friday, 1. March 2002 11:23 schrieb Evert
On 01 March 2002, Evert Jan van Ramselaar said:
> I get the idea the rule SUBJ_ALL_CAPS is not working right in all
> situations.
> I have seen it getting triggered on a subject without any capital,
> and on subjects with just one word in capitals.
If you're using SA 2.1 with Perl 5.005, this rul
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Friday, 1. March 2002 11:23 schrieb Evert Jan van Ramselaar:
> I have seen it getting triggered on a subject without any capital,
> and on subjects with just one word in capitals.
It's definitely not working with subjects using an asian charset, t