You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@spamassassin.apache.org by bu...@bugzilla.spamassassin.org on 2004/09/20 17:06:34 UTC
[Bug 3793] New: virtual-config & virtual-config-dir bug/feature
http://bugzilla.spamassassin.org/show_bug.cgi?id=3793
Summary: virtual-config & virtual-config-dir bug/feature
Product: Spamassassin
Version: 2.64
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Documentation
AssignedTo: dev@spamassassin.apache.org
ReportedBy: pipene-sa@pu.kielce.pl
According to documentation:
(part of --virtual-config-dir)
"So for example, if "/vhome/users/%u/spamassassin" is specified, and spamc sends
a virtual username of "jm@example.com", the directory "/vhome/users/jm@example.
com/spamassassin" will be used."
[...]
"This path must be a writable directory. It will be created if it does not
alrady exist. If a file called user_prefs exists in this directory, it will be
loaded as the user's preferences. The auto-whitelist and/or Bayes databases for
that user will be stored in this directory."
So if I set --virtual-config-dir=/foo/bar/%u/ user prefs file should be /foo/
bar/user/user_prefs. Not true. SpamAssassin appends '.spamassassin' and the real
path is /foo/bar/user/.spamassassin/user_prefs. This also apply to auto-
whitelist and bayes db files.
Is there a way to set custom value of @default_userprefs_path (besides messing
in soures)? If any of these vitual-config options are set, '.spamassassin'
should be imho ommited.
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.