specification of wordlist directory

[Matthias Andree]

David Relson writes: 

> Matthias, 
> 
> I've been thinking about directory names and here's what I remember: 
> 
> 1. If BOGOFILTER_DIR is defined, remember its value.
> 2. If not defined, check for HOME and remember its value.
> 3. When parsing the command line, "-d directory" can supercede any prior 
> value. 
> 
> So, neither environment variable is required and bogofilter shouldn't 
> complain if neither is defined.  Bogofilter _should_ complain if there's 
> no directory specified when it's time to open the wordlists. 
> 
> Lastly, I've now made it possible to specify the directory name in the 
> config file.  I'm thinking that config file takes precedence over 
> environment variable and that command line takes precedence over config 
> file.

I'd think that the ordering goes (from weakest to strongest): 

1. configuration file
2. environment $HOME
3. environment $BOGOFILTER_DIR
4. command line 

> Assuming that the above is right, we need to change the code to make it 
> work in this manner. 
> 
> There's an additional, older idea still around.  Bogofilter has code to 
> work with a list of wordlists, i.e. more than just the two normally used.  
> At one time, using multiple "-d directory" switches on the command line 
> would add pairs of good/spam wordlists for use in calculating a word's 
> spamicity score.  We could allow multiple config file lines to name 
> directories.  Doing this would allow an admin to configure a system 
> wordlist plus allowing users to have their own wordlists.  Do we want to 
> disable this or to fully enable it?

Anticipating side-wide deployment with user-specific configuration, we 
should consider enabling it. 

-- 
Matthias Andree