> > > btw one of last updates had to fix this problem. When did you
> > > sa-update last time?
> On Tue, Oct 28, 2008 at 8:55 PM, Nelson Serafica <[EMAIL PROTECTED]>wrote:
> > It's been a week. I'll be putting this on my crontab today probably every
> > 12am
On 28.10.08 21:05, Nelson Serafica wro
On Tue, 2008-10-28 at 21:05 +0800, Nelson Serafica wrote:
>
>
> On Tue, Oct 28, 2008 at 8:55 PM, Nelson Serafica
> <[EMAIL PROTECTED]> wrote:
>
> > btw one of last updates had to fix this problem.
> When did you sa-update last
> > time?
>
On Tue, Oct 28, 2008 at 8:55 PM, Nelson Serafica <[EMAIL PROTECTED]>wrote:
>
> > btw one of last updates had to fix this problem. When did you sa-update
>> last
>> > time?
>>
>
> It's been a week. I'll be putting this on my crontab today probably every
> 12am
>
I already put this on my crontab
> > btw one of last updates had to fix this problem. When did you sa-update
> last
> > time?
>
It's been a week. I'll be putting this on my crontab today probably every
12am
On 28.10.08 11:01, Nelson Serafica wrote:
> I have setup qmail-scanner to quarantine and notify admin for any spam
> receive. I just notice that it tagged an email which was legitimate (false
> positive).
>
> As I check spamd.log, I saw
>
> AWL,FAKE_REPLY_C,FORGED_MUA_OUTLOOK
> FORGED_MUA_OUTLOOK
> My spamassassin version is 3.2.5. I go to
> /var/lib/spamassassin/3.002005/updates_spamassassin_org
> and edit 50_scores.cf and edit FORGED_MUA_OUTLOOK and set
> it to 0.
>
> Is this the correct way to edit default rules or I have
> to put it on local.cf?
You should do the score in local.c
I have setup qmail-scanner to quarantine and notify admin for any spam
receive. I just notice that it tagged an email which was legitimate (false
positive).
As I check spamd.log, I saw
AWL,FAKE_REPLY_C,FORGED_MUA_OUTLOOK
FORGED_MUA_OUTLOOK,HS_FORGED_OE_FW
AWL,FORGED_MUA_OUTLOOK,HS_FORGED_OE_FW
AW
