> I think I may downgrade the milter as far back as I can and see if that
> fixes it. If it does, then we know that this specific version ignores the
> SA
> local.cf commands to change subject and report safe.
Looks like I may have a different answer. Am testing it now.
> Your maillog paste doesn't show the Subject: header being modified, it
> only shows the X-Spam headers being added. This may be a symptom of the
> '-m' option being present in the call to whatever the spamass-milter
> executable is.
Yes exactly. I see the milter doing *some* work, i.e. adding
> For those of us who use mail clients that understand what headers like
> Thread-Index: AcVAiG7iyfb2TrlzT+CYcsBsxEhNiAAYn8GA
> In-Reply-To: <[EMAIL PROTECTED]>
> mean, replying to a message in a thread to ask a different question means
> that
> we may or may not see your question (as it may be n
> The problem with your setup is with spamass-milter, not SpamAssassin.
And people exclusively ask questions about SA on here? Never ever one on the
milter?
> The problem with your lack of responses is that you started your thread
> by replying to a message in the thread titled "--username flag"
One month FREE spam and fraud protection at
http://www.cloudmark.com/safetybarsig/?
> -Original Message-----
> From: Chris Harvey [mailto:[EMAIL PROTECTED]
> Sent: Monday, April 11, 2005 9:21 PM
> To: 'SpamAssassin list'
> Subject: RE: report_safe doesn't seem
Anyone else seeing similar behavior!? I cannot find out what is wrong.
If I edit my sensitivity (require_hits) it's reflected in my logs, yet none
of these settings appear to be working:
report_safe 1
rewrite_header Subject **NEW_SPAM(_SCORE_)**
If I put the old settings back of:
rewrite_subjec
> I upgraded to FC3 this last weekend and I just noticed today that the mail
> in my junk folder are not encapsulated/wrapped like they were before.
>
> I checked my config file and have:
>
> required_hits 4.5
> rewrite_header Subject **SPAM(_SCORE_)**
> report_safe 1
> use_bayes 1
>
> So it see
I upgraded to FC3 this last weekend and I just noticed today that the mail
in my junk folder are not encapsulated/wrapped like they were before.
I checked my config file and have:
required_hits 4.5
rewrite_header Subject **SPAM(_SCORE_)**
report_safe 1
use_bayes 1
So it seems ok, but it's defin
> Why aren't more tests being triggered?
I was having similar problems recently where SA didn't seem to be picking up
much spam. Running spamd in debug mode showed me a number of things were
going wrong that must have happened over time with various other binary
updates (i.e. DNS wasn't working)
Ok, now I'm noticing this
Creating default_prefs [/root/.spamassassin/user_prefs]
Creating default_prefs [/root/.spamassassin/user_prefs]
Is there a file path I can set so that the new working directory is my new
.spamassasin directory I created?
I specifically set the bayes and the autowhitelis
>
> First, I assume you're using a bayes_path statement to force the bayes DB
> for all users to be in roots homedir.
Yep!
>
> If so, DO NOT proceed..
> In order for your bayes DB to be wide open, ALL users must have r_x access
> to /root... that's a bad thing that you don't want to give them.
I'm seeing in my maillog file (SA 3.x running in Debug mode) the following:
cannot write to /root/.spamassassin/bayes_journal, Bayes db update ignored:
Permission denied
This is right after all the bayes token statements. It suggests it's a
problem, but I don't seem to be able to fix it.
My defa
12 matches
Mail list logo
