http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5611
------- Additional Comments From [EMAIL PROTECTED] 2007-08-20 04:17 ------- (In reply to comment #2) > Justin, is that something you thought about when doing the patch for bug 5522, > or were you just cleaning up wording of the comment in the patch that someone > else had submitted? Yes. I think we have two use cases, the bug-5522 one, and this one. They are diametrically opposed :( What about using the "--user-config" switch to differentiate? "spamd --nouser-config -u spamduser": the bug 5522 case. turns off reading ~/.spamassassin/user_prefs from the remote username's home dir "spamd --user-config -u spamduser": this case. turns ON reading ~/.spamassassin/user_prefs from the remote username's home dir does that make sense? for reference, here's the POD docs for those 2 options: =item B<-x>, B<--nouser-config>, B<--user-config> Turn off(on) reading of per-user configuration files (user_prefs) from the user's home directory. The default behaviour is to read per-user configuration from the user's home directory. This option does not disable or otherwise influence the SQL, LDAP or Virtual Config Dir settings. =item B<-u> I<username>, B<--username>=I<username> Run as the named user. If this option is not set, the default behaviour is to setuid() to the user running C<spamc>, if C<spamd> is running as root. Note: "--username=root" is not a valid option. If specified, C<spamd> will exit with a fatal error on startup. > What is the right thing to do here? > > Is this related to what I saw in bug 5606 that spamd is now reading the user > prefs of the userid it is running at at initialization time (which I think is > a > bug)? no, I don't think it's related. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
