just a quick note of good news. It seems something
is changing in the behavior of procmail/spamassassin
on the server for me.. Here is what I did over the
last 5 days as a user, no admin privs...
in $HOME/.spamassassin
-rm'd a lock file on the autowhitelist from 30 days
ago
-cleared
Hello All-
My primary mail acct is hosted on a legacy Soalis
5.8 sun box, with SA 2.6 installed. I have been
getting a ton of mail - 8k msgs per day, to my desktop
client. It killed a hard drive!
So I am attempting to look into the config myself.
No one else has time to do this for this
with this...
How to proceed ? thanks in advance
-brian
--- Brian Hamlin [EMAIL PROTECTED] wrote:
Date: Sun, 25 Jun 2006 00:46:29 -0700 (PDT)
From: Brian Hamlin [EMAIL PROTECTED]
Subject: Detecting active config as a user
To: users@spamassassin.apache.org
Hello All-
My primary mail acct
all- i read the theory of operation on the wiki for
spamd. Still wondering...
Since I am not installing a new SA as a user, the
existing SA is there, but for whatever reason is not
active for my acct, yet is reachable and basically
functioning...
There must be a magic line in the original
I am putting along with Perl. I just wrote a script
that loops through my mail, reads a msgs, sends it to
SA, then writes it out to a nw mbox. When it is done,
it copies the new mbox into the system one.
* horribly slow
* will miss mails
* mayeb I made more mistakes
but it is better than the
