nb - I typoed the score rule. Should be:
rewrite_header subject * Rated SPAM: _SCORE(00)_ *
^ I left that off.
sorry.
And, of course, the rule did not fire. You are testing for "spam"
and you sent "SPAM". If you want a case insensitive test then you
need:
body LOCAL_DEMONSTRATION_RULE /spam/i
^ makes it case insensitive
And you tested case insensitive for "test" and sent "TEST".
That should have fired and probably did.
{^_^}
----- Original Message -----
From: "DuBois, Joseph" <[EMAIL PROTECTED]>
To: <users@spamassassin.apache.org>
Sent: Thursday, August 24, 2006 06:35
Subject: RE: Filtering Aliases/Forwarders
Joanne,
Thanks for info, yeah saw the variables I could make substitutions on
and will probably do that once I get it up and running so I can make
better rules, but I am just trying to get it running right now.
For my tests, I am just trying to get it to work. I was sending emails
to myself from work to home accounts with the proper stuff to set off
the rules, but for some reason it doesn't seem to be catching it(and
rewritting the subjects).
For example I sent an email with a subject TEST and in the body SPAM. I
would expect to receive the email at my home email account with the
subject line rewritten, but it's not happening. The hosting provider
won't give me any help, thus turning to the list. Once I get it working
I will starting writing more unique rules to try and filter out all the
truly junk mail I get. Verizon has already shut off my emails once,
because I have about 23 public emails accounts forward to a single
account, thus really need to try and start cleaning it up.
On the CPANEL, it says it's enabled and that's about he only status I
seem to be able to check. It does have a "configuration" button which
brings up a form, where I can see that my local rules are set (from my
user_prefs file). So it seems to be at least reading that. Not sure
which version we are running, but I sent a request into the Hosting
provider to get that information along with any other configuration
information he can give me since he will not help me.
So I can only think, that one it is not parsing Alias/forward emails? Or
something else is wrong.
Again any help in getting this running is greatly appreciated!
Thanks all.
-----Original Message-----
From: jdow [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 23, 2006 6:49 PM
To: users@spamassassin.apache.org
Subject: Re: Filtering Aliases/Forwarders
Joseph, may I make a slight suggestion for you?
For the rewrite try something about the same size that makes eyeball
filtering ham out of the spam folder much easier:
rewrite_header subject * Rated SPAM: _SCORE(00) *
Then the header subject will start with something like this:
"* Rated SPAM: 019.8 *". It'll be followed by the original subject, of
course. You filter to spam if "* Rated SPAM:" is seen. And you can sort
by subject to bring the low scores to the top.
And for demonstration or test rules I'd use low scores unless you
specifically wanted to see a hit. Then I'd search for something
gibberish in the text. Hm, actually I wonder if "gibberish" itself would
be a safe rule for testing. It almost never appears in normal mail and
spammers USUALLY are averse to calling their mail gibberish.
So.... {^_-} The scores I use run for rule testing are in the 0.001 to
0.1 range. Once the look good I give them real scores.
{^_^} Joanne
----- Original Message -----
From: "DuBois, Joseph" <[EMAIL PROTECTED]>
Well met,
Just activated SpamAssassin on my website (by my web hosting provider)
and wanted to do some simple tests which I read from the Wiki site and
FAQ. When it didn't run I opened a ticket with my provider and he said
he didn't support it and I needed to find help else where. So here I am.
Right now, I'm just trying some simple tests to get my
Aliases/Forwarders (which get sent through my site) and forwarded onto
my ISP providers email account.
i.e. a public email [EMAIL PROTECTED] would get forwarded onto my
local isp provider at verizon, or comcast depending on who I have for a
particular month, so that way I don't have to change my email every
month.
So for my test, I set up the following basic local rules in
~/.spamassassin/user_prefs file.
I assume this would take any email with the word spam in the BODY or
test in SUBJECT and rewrite the SUBJECT with the new HEADER. But for
some reason it does not appear to be working.
body LOCAL_DEMONSTRATION_RULE /spam/
score LOCAL_DEMONSTRATION_RULE 6.0
describe LOCAL_DEMONSTRATION_RULE This is a simple test rule
header LOCAL_DEMONSTRATION_SUBJECT Subject =~ /\btest\b/i
score LOCAL_DEMONSTRATION_SUBJECT 2
required_score 5
rewrite_header subject * Rated SPAM: Junk This! *
Does it not work for Aliases/Forwarders? Do you have to have a special
Client? I am using BAT by RitLABs, and/or Webbrowser.
Thanks!
Joseph DuBois, Lead Application Specialist
Application Standards & Specialty Projects
Children's Hospital Boston
[EMAIL PROTECTED]
