RE: [webmin-devel] Webmin 1.120 pre-release now available

[Larry G. <Li...@IS...>]

Excellent!  Thanks Jamie!

--Larry


> -----Original Message-----
> From: Jamie Cameron [mailto:jca...@we...] 
> Sent: Tuesday, October 28, 2003 5:08 PM
> To: web...@li...
> Subject: RE: [webmin-devel] Webmin 1.120 pre-release now available
> 
> 
> Thanks for the information - that is pretty much how I 
> expected spamassasin to behave, and so I will have the module 
> scan all .cf files in /etc/mail/spamassassin by default in 
> the upcoming 1.120 release. You will need to adjust your 
> module configuration after upgrading from 1.119 though, as in 
> the current beta version the config path is set to 
> /etc/mail/spamassassin/local.cf
>  
>  - Jamie
> 
> On Wed, 2003-10-29 at 00:45, Larry Gilson wrote:
> > Hi Jamie,
> > 
> > I hope the following is not too verbose.  The question of what SA 
> > parses comes up quite a bit on the SA list so I thought I would at 
> > least document the answer here at the risk of overstating the 
> > answer.
> > 
> > My test machine has the following files in /etc/mail/spamassassin:
> > 
> >   90_custom.cf
> >       local.cf
> >       local.cf.rpmsave
> >       local.cf.save
> > 
> > The only files that will be parsed for rules are:
> >   90_custom.cf
> >       local.cf
> > 
> > I delete the unused files on the production machine as they are 
> > not used. So the answer is yes, only the .cf files are processed 
> > in /etc/mail/spamassassin and all others are ignored.
> > 
> > The only files, at least that I know of, that SA will use 
> > for rules or configuration are  *.cf (which includes local.cf) and 
> > user_prefs.  SA will process *.cf only in /etc/mail/spamassassin 
> > and /usr/share/spamassassin. *.cf configuration files are 
> > considered site-wide configurations. user_prefs are user 
> > configuration files and processed only when SA is invoked by the 
> > user or in a site-wide configuration when spamc is forced to use 
> > per-user config files via 'spamc -u'.  The location of user_prefs 
> > is $HOME/.spamassassin/ (which is the same location for auto-
> > whitelist and bayes files).  By default, SA will ignore rules in 
> > user_prefs.  The administrator *must* set 'allow_user_rules 1' in 
> > local.cf to override this default.  This practice is highly 
> > discouraged for security reasons as well as it places a large 
> > processing load on the system with more users.  SA must recompile
> > all tests in user_prefs on a per-message basis.
> > 
> > Not having used Usermin I might be off base here but I would think 
> > that if a site configuration were to support processing rules in 
> > user_prefs, the support would be better placed in Usermin 
> > rather than Webmin.
> > 
> > --Larry
> > 
> > 
> > 
> > > -----Original Message-----
> > > From: Jamie Cameron
> > > 
> > > So only .cf files in /etc/mail/spamassassin are processed? I
> > > noticed a few other files in that directory that are not 
> > > normal SpamAssassin configs, and thus presumably ignored ..
> > > 
> > >  - Jamie
> > > 
> > > On Tue, 2003-10-28 at 16:24, Larry Gilson wrote:
> > > > All .cf files, with respect to custom rules, are treated 
> > > > equally.I can send you a custom rule file if want an example.
> > > > 
> > > > Thanks Jamie!
> > > > 
> > > > --Larry
> > > > 
> > > > 
> > > > > -----Original Message-----
> > > > > From: Jamie Cameron
> > > > > 
> > > > > Oops, I missed that comment.
> > > > > 
> > > > > Being able to edit extra .cf files sounds like a good idea, 
> > > > > and probably not too hard to add support for. So are all 
> > > > > .cf files treated equally by spamassassin, or is local.cf 
> > > > > special in some way?
> > > > > 
> > > > >  - Jamie
> > 
> > 
> > --snip--