spamassassin-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Karsten Br├Ąckelmann <>
Subject Re: Change .spamassassin directory
Date Thu, 22 Jul 2010 17:26:51 GMT
Please keep list-posts on list.

On Thu, 2010-07-22 at 10:03 -0700, Neil Hodge wrote:
> 2010/7/22 Karsten Br├Ąckelmann <>:
> >
> > man spamassassin-run
> >
> > That would be --prefspath. Only used for per-user preferences, usually
> > does *not* contain any rules. The --configpath points to the stock rules
> > dir by default, and should *not* be changed.
> >
> > Begs the question, why you want to change the default ~/.spamassassin
> > anyway?
> So, when I read the man page, it says:
> -p prefs, --prefspath=file, --prefs-file=file   Set user preferences file
> When I saw this, I thought it was maybe for changing the preferences
> file _name_, but not necessarily its location.  Maybe the description
> of this option in the man page should be something like "Set user
> preferences file.  All user-local files (whitelist, bayes, etc) will
> be read from the same base directory.", or something similar.

See bayes_path, auto_whitelist_path and the bunch of related options in
the M::SA::Conf and AWL plugin documentation respectively.

Do note, that you'll need to use these with spamd anyway, and they do
work with 'spamassassin' as well.

Anyway, I still do not see why you want to change these to begin with.
If you want site-wide databases, check out the wiki and its information
how to do that. If the reason is anything else -- you probably should
not do it. ;)

> > Well, since installing SA 3.3.1, did you actually run sa-update?
> >
> > You do realize that this is now mandatory since 3.3 to grab the latest
> > stock rule-set, do you? (Alternatively, a separate rules tarball is
> > available.) SA doesn't ship with all rules bundled any longer.
> Basically, I was getting this error because I was using the wrong
> command line option.
> No, I have not run sa-update, nor did I realize it was required.
> While I probably would have figured it out after SA did nothing at
> all, thanks for the heads up . . . :)

If you installed SA from distro provided packages, odds are stock rules
have been installed. You will find the particular dirs and the order
they are checked by SA in 'man spamassassin'.

> > spamc / spamd rather than the plain and costly 'spamassassin' script, I
> > hope. Any chance the spamd daemon is started with the -c create user
> > prefs option?
> Not yet.  I figured that until I could get the standalong exec
> working, no need to complicate the situation.  I will probably use the
> standalone for a week or two, until I am convinced it is working as
> desired, then I will switch to the client/server mode.

I would switch as soon as possible, since using the plain spamassassin
script comes with a quite severe overhead of starting a Perl process and
compiling all rules -- per message.

Also, I would avoid *any* usage of 'spamassassin' command line options,
unless for debugging. See the note above regarding such options and
later use of spamd.

> Thanks for the clarification.
> Cheers,
> Neil
char *t="\10pse\0r\0dtu\0.@ghno\x4e\xc8\x79\xf4\xab\x51\x8a\x10\xf4\xf4\xc4";
main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;i<l;i++){ i%8? c<<=1:
(c=*++x); c&128 && (s+=h); if (!(h>>=1)||!t[s+h]){ putchar(t[s]);h=m;s=0;

View raw message