>Ok, awesome. What about the /usr/bin/spamassasin? I saw that there was a
>"dont_copy_prefs" option in Mail::SpamAssassin, but it doesn't look like I
>can set that via a command line or config file anywhere. I'd rather not
>modify the SpamAssassin.pm file to set this to 1, instead of 0, but if
>that's the only way, then I'll do it.
Here's a patch that will do the job:
#################
84d83
< -x turn off per-user config files.
96c95
< $opt_d $opt_L $opt_e $opt_W $opt_M $opt_R $opt_F $opt_a $opt_S $opt_x
---
> $opt_d $opt_L $opt_e $opt_W $opt_M $opt_R $opt_F $opt_a $opt_S
103c102
< getopts ('atc:p:ehVDxrPw:l:dLSWRM:F:') or usage();
---
> getopts ('atc:p:ehVDrPw:l:dLSWRM:F:') or usage();
154,155c153
< 'debug' => $opt_D,
< 'dont_copy_prefs' => $opt_x
---
> 'debug' => $opt_D
#################
However, this does cause complaints. If I ran it like this:
spamassassin -P -x 1
Then, I'll get a complaint each and every mail message:
Failed to create default prefs file
/path/to/user/.spamassassin/user_prefs:
No such file or directory
This seems to come about as part of the init() portion of Mail::SpamAssassin:
if (defined $fname) {
if (!-f $fname && !$self->create_default_prefs($fname)) {
warn "Failed to create default prefs file $fname: $!\n";
}
}
In this case, create_default_prefs ALWAYS returns
a 0, which ALWAYS causes this error message to display.
--
Kevin Hemenway
_______________________________________________________________
Have big pipes? SourceForge.net is looking for download mirrors. We supply
the hardware. You get the recognition. Email Us: [EMAIL PROTECTED]
_______________________________________________
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
