Christoph, thanks for the reply! Christoph Martin <[EMAIL PROTECTED]> wrote: > > Hi Jonathan, > > Jonathan Hankins schrieb: > > Package: mimedefang > > Version: 2.48-1 > > Severity: normal > > > > I am a bit confused about which rules files spamassassin uses when run from > > mimedefang anyway. Doesn't SpamAssassin find /etc/spamassassin/local.cf > > anyway? If so, why does mimedefang.pl also specify it as userprefs_filename > > (in the case where sa-mimedefang.cf is not present above)? > > spamc and mimedefang are both perl programs which use the spamassassin > perl packages. Every program specifies which preferences file to use. > spamc uses local.cf, mimedefang.pl uses normaly sa-mimedefang.pl.
>From reading the man page and looking through SpamAssassin.pm, I got the impression that SpamAssassin.pm loads *.cf from the first directory it finds, from its list of "default" and "site" rules paths (the latter of which includes /etc/spamassassin), thus the local.cf file is hit during this process. It looks like mimedefang.pl will, when sa-mimedefang.cf is not present, also pass local.cf to Mail::SpamAssassin->new() as "userprefs_filename". This seems incorrect to me. > > Also, the man page for Mail::SpamAssassin::Conf mentions that some items are > > privileged and cannot appear in the user prefs file. I am assuming that > > when > > mimedefang.pl calls Mail::SpamAssassin->new() with userprefs_filename = > > "/etc/mail/sa-mimedefang.cf" (or whatever) that this file cannot contain > > "privileged" items? Is this a problem? > > I think, this is correct. What "privileged" items do you want to use here? Well, several important items like "use_auto_whitelist", "auto_whitelist_path", "bayes_path", etc. are listed under "ADMINISTRATOR SETTINGS" in the man page for Mail::SpamAssassin::Conf. It says: These settings differ from the ones above, in that they are considered 'more privileged' -- even more than the ones in the PRIVILEGED SETTINGS section. No matter what "allow_user_rules" is set to, these can never be set from a user's "user_prefs" file. So, it looks like, with mimedefang.pl passing sa-mimedefang.cf to SpamAssassin as "userprefs_filename" that you could never control bayes and whitelist options, among others, from this config file. It seems kind of weird that you can pass a "userprefs_filename" parameter to Mail::SpamAssassin->new(), but you have to rely on its hard-coded path list to find "site wide" and "administrator" rule sets / config files. Maybe I am just misunderstanding something. I am not using SpamAssassin outside of mimedefang, so my /etc/spamassassin/local.cf is empty. Right now, it looks like that, if I want to specify whitelist or bayes parameters (or other "privileged" parameters) to SpamAssassin running under mimedefang, I would have to put them in /etc/spamassassin/*.cf, but then those options would be in effect for anyone using SpamAssassin through spamc, etc. Thanks, -Jonathan Hankins -- -------------------------------------------------------------------------- Jonathan Hankins Homewood City Schools [EMAIL PROTECTED] -------------------------------------------------------------------------- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
