Also you can rename the file and restart things to get it recreated most
likely.
On Sun, Jan 20, 2019, 06:03 Giovanni Bechis On 1/20/19 8:33 AM, Palvelin Postmaster wrote:
> > My auto-whitelist file appears corrupted. File size is about 5
> megabytes. Spamassassin says it can’t be opened. So does
On 1/20/19 8:33 AM, Palvelin Postmaster wrote:
> My auto-whitelist file appears corrupted. File size is about 5 megabytes.
> Spamassassin says it can’t be opened. So does sa-awl.
>
> Is there any other way to try to recover the file or should I just accept my
> losses and recreate it?
>
I think
T
he AWL plugin in v310.pre
was disabled!
By enabling that and give enough permission it's working
thanks
On 07/11/2013 01:01 PM, Moein Sarvi wrote:
warn: config: failed to parse line, skipping, in "/etc/spamassassin/local.cf":
auto_whitelist_path /etc/mail/spamassassin/auto-whitelist
is the AWL plugin enabled in v310.pre ?
if yes
please post the full output from
- SA version
- spamassassin --li
warn: config: failed to parse line, skipping, in "/etc/spamassassin/local.cf":
auto_whitelist_path /etc/mail/spamassassin/auto-whitelist
On 07/11/2013 12:53 PM, Moein Sarvi wrote:
hi
I can't set this command in local.cf and in --lint mode I face some error
auto_whitelist_path /etc/mail/spamassassin/auto-whitelist
"some error" is not very descriptive (helpful)
What error?
>> On Mon, Dec 01, 2008 at 03:42:05PM -0500, Dan Barker wrote:
>>
>> This issue, apparently, has been a problem for me for several
Spamassassin releases, but
>> I just now figured out what may be happening. I've been closing spamd
once per hour,
>> just to make it read new local.cf, notice sa-updat
On Mon, Dec 01, 2008 at 03:42:05PM -0500, Dan Barker wrote:
> How do I go about trapping this error in locker? (Specifically, how do I
> figure out who Called locker, to find the code that's not closing the file
> it opened?)
>
> Has anyone else run into this sort of issue?
The last time this sor
Brent Clark wrote:
Hi
I recently installed spamassasin on my freebsd test machine. For the
likes of me, I keep getting this message, and I dont know how to fix it.
Aug 6 17:06:43 spamassasin spamd[63534]: auto-whitelist: open of
auto-whitelist file failed: locker: safe_lock: cannot create t
On 26.06.08 10:06, Skip Morrow wrote:
> I see, and got it working. Next question: How would I set it up so that
> I could have a separate whitelist for each user (I only have four users)?
it's the default
> Again, I call spamassassin from procmail, and each user has its own
> procmailrc,
then
> That option wasn't removed from SA.. it was removed from the main conf
> docs, as all of the AWL is now a plugin. That option is documented in the
> docs for the AWL plugin, which is where it really belongs. (if the option
> isn't valid without the plugin, then it in theory shouldn't be in the ma
On Thu, June 26, 2008 05:56, Matt Kettler wrote:
> the docs for the AWL plugin, which is where it really belongs. (if the
> option isn't valid without the plugin, then it in theory shouldn't be in
> the main Conf manpage..)
there is still docs for bayes in conf, even bayes is a plugin now
needs
On Thu, June 26, 2008 05:16, Skip wrote:
> option with my own configuration file, and I should be able to pass it
> the -C or --siteconfigpath options to set admin settings. Any help?
AWL and BAYES will when procmail is in use be in $HOME./spamassassin/
but can be overwrited in user_prefs with
Skip wrote:
How does one set the file location for the auto-whitelist file on a
3.2.x system? I am on a shared hosting system, but call spamassassin
manually from procmail. Here's the debug output that deals with
auto-whitelist:
[25947] dbg: locker: safe_lock: created
/ramdisk/etc/spamassa
On 06.04.2008 03:26 CE(S)T, Matt Kettler wrote:
The "new fangled" way would be to use spamc for learning instead of
sa-learn.
And yes, it's a lot faster I believe.
--
Yves Goergen "LonelyPixel" <[EMAIL PROTECTED]>
Visit my web laboratory at http://beta.unclassified.de
On 06.04.2008 03:26 CE(S)T, Matt Kettler wrote:
Yves Goergen wrote:
Just remember to su to that user when running sa-learn.
This is getting a problem now! My spamd user has no access on the
mailbox directories from which I am usually learning. What's the
proposed solution for that?
The "new
Yves Goergen wrote:
Just remember to su to that user when running sa-learn.
This is getting a problem now! My spamd user has no access on the
mailbox directories from which I am usually learning. What's the
proposed solution for that?
Well, there's a couple of ways to deal with that..
The
On 05.04.2008 01:18 CE(S)T, Matt Kettler wrote:
Spamd will never be able to access anything in /root/. 3.1.8 shouldn't
have been able to do so any more than 3.2.4 could, but that might have
been a bug..
Must have been a bug, yes.
If you're always scanning mail as one user, you can create a
n
Yves Goergen wrote:
Hello,
I have upgraded SpamAssassin from 3.1.8 to 3.2.4 today. First I got
errors about a "nonexistent" path all the time. Then I added the path
to the auto_whitelist directory in local.cf. Now I get this error
message every few seconds:
Apr 4 20:01:36 mond spamd[14283]
Noah wrote:
Hi there list,
I installed the following spamassasin proggies on my FreeBSD machine
and receiving an error "auto-whitelist file failed: locker: safe_lock:
cannot create tmp lockfile"
Any clues what I am doing wrong?
# pkg_info | grep Spam
p5-Mail-SpamAssassin-3.2.3 A highly eff
On Thu, 8 Mar 2007, Matt Kettler wrote:
> Directories should have RWX permessions, not RW.
>
> In Directories, X takes on a different meaning, and refers to the
> ability to list files in the directory.. Without that, apps can only
> open files they already know the exact name of.
No the 'r' bit
Andrew Rosolino wrote:
>
>
> Here is the permissions for the folder:
> drw-rw-rw-2 root nobody 4096 Mar 8 14:35 spamassassin/
Directories should have RWX permessions, not RW.
In Directories, X takes on a different meaning, and refers to the
ability to list files in the directory.. W
On Thu, Mar 08, 2007 at 11:44:31AM -0800, Andrew Rosolino wrote:
> Mar 8 14:42:32 penguin spamd[15553]: spamd: setuid to root succeeded
> Mar 8 14:42:32 penguin spamd[15553]: spamd: still running as root: user not
> specified with -u, not found, or set to root, falling back to nobody at
> /usr/bi
On Sat, October 21, 2006 21:18, Magnus Anderson wrote:
> The Bayes are working, but the AWL are not.
is AWL plugin loaded in ?
> Is there some problem in SA 3.14 for this?
not to what i know of
--
"This message was sent using 100% recycled spam mails."
Benny Pedersen wrote:
> On Sat, October 21, 2006 11:54, Magnus Anderson wrote:
>
>> If someone knows how to solve this problem I would be very happy.
>
> give the users there own mysql db is one solution
>
> another is to define mysql db in site wide config
>
> where overwrite username is not u
On Sat, October 21, 2006 11:54, Magnus Anderson wrote:
> If someone knows how to solve this problem I would be very happy.
give the users there own mysql db is one solution
another is to define mysql db in site wide config
where overwrite username is not used, this should work for unix acoount
Mike Pepe wrote:
> I'm getting more and more spams sneaking through lately.
>
> I'm running SA 3.0.4 on Fedora Core 3.
>
> In analyzing the ones that make it through, I see that other users in my
> domain are CC, which causes the auto-whitelist to score the spam lower
> than if I run it through m
On Jun 22, 2005, at 9:36 PM, Mike Pepe wrote:
In analyzing the ones that make it through, I see that other users
in my domain are CC, which causes the auto-whitelist to score the
spam lower than if I run it through manually without that test.
I'm sure others may chime in to say that auto-whi
William R Thomas wrote:
I had some questions about how the auto whitelist score was
generated. Specifically, it seems like it is working opposite to the
way it should be in some cases.
The equation for the AWL score is:
( meanscore - currentscore) * factor
gene
You were exactly correct, I was seeing the AwlWrongWay problem (maybe
phenomena is a better term) and didn't turn up anything on google
about it, and was vastly confused.
I wish I would have checked my email again before sending the full
explanation.
On Tue, Mar 15, 2005 at 04:03:49PM -0500, M
Your message seems to be missing it's body, but I'm assuming you're
confused by how the scores for the AWL work.
I'd suggest a read of the wiki:
http://wiki.apache.org/spamassassin/AutoWhitelist
and
http://wiki.apache.org/spamassassin/AwlWrongWay
Possibly you are missing the dot in front of the SA directory name?
Usually, the SA directory will be ".spamassassin"
Just a thought.
Matt Kettler wrote:
At 11:27 AM 2/22/2005, Carinus Carelse wrote:
When I try to run the command I get the following error. Am i doing
something wrong.
bash-2.05
Yes it does exist I checked and I am running the command as root.
Carinus
At 11:27 AM 2/22/2005, Carinus Carelse wrote:
When I try to run the command I get the following error. Am i doing
something wrong.
bash-2.05# ./check_whitelist
/var/spool/MailScanner/spamassassin/bayes/auto-whitelist
Cannot open file /var/spool/MailScanner/spamassassin/bayes/auto-whitelist: No
suc
When I try to run the command I get the following error. Am i doing
something wrong.
bash-2.05# ./check_whitelist
/var/spool/MailScanner/spamassassin/bayes/auto-whitelist
Cannot open file /var/spool/MailScanner/spamassassin/bayes/auto-whitelist: No
such file or directory
At 10:31 AM 2/22/2005, Carinus Carelse wrote:
How can see what is in the Auto-Whitelist
In the tools sub-directory of the SA tarball is a tool called
"check-whitelist". This will dump your AWL contents, although you'll need
to manually tell it what AWL db to dump.
It's also got a --clean option
A small dialogue with the creator of the script "trim_whitelist":
Kris Deugau wrote:
>> Klaus Pforte wrote:
>>
>
The script make a backup of the DB-File (I changed the location in the
script), o.k.
But after this comes everytime "Cannot tie to old db."
I changed the ownership and ri
On Thu, Nov 11, 2004 at 03:58:12PM -0200, Juliano Simões wrote:
>
> Is there a way to limit the size of auto-whitelist or expire
> some of its entries?
>
There is no auto expire for AWL. It is a planned feature, sorry don't
have the bug number handy. You can manually expire entries. Assuming
- Original Message -
From: "Juliano Simões" <[EMAIL PROTECTED]>
> We started usign AWL on our site-wide setup after upgrading
> from 2.64 to 3.0.1.
>
> As I was checking system files today, I noticed that the
> auto-whitelist file size is 163MB, and growing.
>
> Is there a way to limit th
39 matches
Mail list logo
