Bug 2641 - Spamd doesn't open user_prefs file in virtual-config-dir
Summary: Spamd doesn't open user_prefs file in virtual-config-dir
Status: RESOLVED FIXED
Alias: None
Product: Spamassassin
Classification: Unclassified
Component: spamc/spamd (show other bugs)
Version: 2.60
Hardware: PC Linux
: P5 normal
Target Milestone: 3.0.0
Assignee: SpamAssassin Developer Mailing List
URL:
Whiteboard:
Keywords:
: 3066 (view as bug list)
Depends on:
Blocks: 3208
  Show dependency tree
 
Reported: 2003-10-28 13:51 UTC by Richard Goode
Modified: 2004-04-28 09:39 UTC (History)
1 user (show)


Attachment Type Modified Status Actions Submitter/CLA Status
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Richard Goode 2003-10-28 13:51:11 UTC 
Spamd attempts to locate the user_prefs file in the wrong directory when
--virtual-config-dir is specified.  It looks in <virtualdir>/user_prefs rather
than <virtualdir>/.spamassassin/user_prefs.  Diff -p :

*** spamd.orig  Wed Oct 29 10:41:41 2003
--- spamd       Wed Oct 29 10:41:56 2003
*************** sub handle_virtual_user
*** 984,990 ****
        $dir =~ s/\%d/${domain}/g;

        $userdir = $dir;
!       $prefsfile = $dir.'/user_prefs';
        # Log that the default configuration is being used for a user.
        logmsg("Using default config for $username: $prefsfile");

--- 984,990 ----
        $dir =~ s/\%d/${domain}/g;

        $userdir = $dir;
!       $prefsfile = $dir.'/.spamassassin/user_prefs';
        # Log that the default configuration is being used for a user.
        logmsg("Using default config for $username: $prefsfile");
Comment 1 Justin Mason 2004-04-28 16:34:11 UTC 
thanks -- applied that
Comment 2 Justin Mason 2004-04-28 17:39:28 UTC 
*** Bug 3066 has been marked as a duplicate of this bug. ***
Comment 3 Justin Mason 2004-04-28 17:39:58 UTC 
actually, reverted it again.  I realised both of us were wrong on this!

Read the spamd doco -- that's not how virtual-config-dir works; it does *not*
use the .spamassassin subdir (because it doesn't have to).