At 03:31 PM 8/18/2003 -0700, Matthew Cline wrote:
If you're using spamd, and this is in user_prefs file, you'll have to set
"allow_user_rules" to 1 in the local.cf file.
He's using local.cf for his rules, not user_prefs.. but the above is
definitely true.
--
On Monday 18 August 2003 08:11 am, Danita Zanre wrote:
> and feeling pretty dumb about it.
>
> I receive two types of emails that cannot be "whitelisted" by sender,
> because the sender is always different. So, I'm trying to create rules
> that will give a negative value to a subject line. Here's
At 8/18/03 01:28 PM , Matt Kettler wrote:
At 12:08 PM 8/18/2003 -0700, Kai MacTane wrote:
In other places, such as in Ms. Zanre's rule, it means "beginning of line
or string", just as $ means "end of line or string".
True, his rule should work, provided that the GOREALTIME is actually at
the star
At 12:08 PM 8/18/2003 -0700, Kai MacTane wrote:
In other places, such as in Ms. Zanre's rule, it means "beginning of line
or string", just as $ means "end of line or string".
True, his rule should work, provided that the GOREALTIME is actually at the
start of the subject line, and not anywhere el
At 8/18/03 10:48 AM , Fred I-IS.COM wrote:
Hello,
Try this:
header GOREALTIME Subject =~ /GOREALTIME\b/i
I am thinking the problem was the ^ before the text.
I think that means to not match anything following.
No, it only means that when it's the first character in a [^bracketgroup].
In other pl
AIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, August 18, 2003 11:11 AM
Subject: [SAtalk] Trying to create rule . . .
> and feeling pretty dumb about it.
>
> I receive two types of emails that cannot be "whitelisted" by sender,
> because the sender is alway
and feeling pretty dumb about it.
I receive two types of emails that cannot be "whitelisted" by sender,
because the sender is always different. So, I'm trying to create rules
that will give a negative value to a subject line. Here's one:
In the header I have:
Subject: GOREALTIME Transaction
S
