upgrade problem [was: simplicity vs safety with complexity]

David Relson relson at osagesoftware.com
Thu Jan 27 00:59:11 CET 2005


On Wed, 26 Jan 2005 12:05:39 -0800
Greg McCann wrote:

> On 1/26/2005 at 1:50 PM Clint Adams <schizo at debian.org> wrote:
> 
> >I don't know why you would want to share a database; having one db per
> >user would mesh much more easily with your current setup.
> 
> That (and Tom Anderson's suggestion of crosslinked wordlists) might be a step toward solving the technical problems I am having with the new db.  But until now the shared wordlist has not been much of a problem, and there are good reasons (I think) for having a shared wordlist in my environment.
> 
> First, my users have no desire to be responsible for maintaining their own databases.
> 
> Also, having a shared wordlist allows all users to get the benefit of my wordlist maintenance.  The shared wordlist is automatically kept current by being continuously updated with spam received by several spamtrap addresses.  That allows it to automatically keep up with the latest trends in spam which may be the V-word this week and something else next week.  I also do occasional manual tweaks for optimal performance.
> 
> I may be mistaken afer retreating in panic from the new version, but with the new db I had the impression that new db__ and .log files were being created under individual UIDs even when they should have only needed read-only access to the database with "bogofilter -epl".
> 
> Maybe the new db will force me to rethink the way I am doing things, but my current configuration has been a good solution until now.
> 
> Best regards,
> 
> 
> Greg McCann

Greg,

It sounds like you do all the wordlist maintenance and your users are
strictly readers.  Is that correct?  Let me know so I can try some
experiments to learn more about the trouble you ran into.

Regards,

David




More information about the Bogofilter mailing list