Bug 4375 - spamd not creating .spamassassin-per-user-directory
Summary: spamd not creating .spamassassin-per-user-directory
Status: RESOLVED INVALID
Alias: None
Product: Spamassassin
Classification: Unclassified
Component: spamc/spamd (show other bugs)
Version: 3.0.3
Hardware: Other Linux
: P5 normal
Target Milestone: Undefined
Assignee: SpamAssassin Developer Mailing List
URL:
Whiteboard:
Keywords: triage
Depends on:
Blocks:
 
Reported: 2005-05-31 13:08 UTC by jas
Modified: 2005-06-02 22:37 UTC (History)
0 users


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 jas 2005-05-31 13:08:42 UTC 
I run spamd with the "-c" option, but it does not create the .spamassassin
directory in the users home directory when it does not exist.  Instead, it tries
to write the user_prefs file to the non-existing directory, and produces an
error that it can't do it. It appears that the only functions in spamd that
contain the "mkdir $spam_conf_dir" are handle_user_setuid_with_sql and 
handle_user_setuid_with_ldap.  What about when there is no sql/ldap and you're
just using standard user home directories?
Comment 1 Bob Menschel 2005-06-02 19:19:55 UTC 
This seems very strange to me, since SA spamd has done exactly what it should
"when there is no sql/ldap and you're just using standard user home directories"
for years. I find it hard to believe that such activity broke in version 3.0.3. 

Can you attach a full copy of the log, showing the error stream?  If you could
recreate this with debugging on as well, and provide that log, that'd probably
be even better.
Comment 2 jas 2005-06-03 06:37:30 UTC 
Turning on debug revealed the real problem.  The problem was that these users
were over disk quota.  I'm still not sure why the error in the log was:

The errors were like this:

2005-06-02 08:50:47 [8877] i: Creating default_prefs
[/cs/home/user/.spamassassin/user_prefs]
2005-06-02 08:50:47 [8877] i: Cannot write to
/cs/home/user/.spamassassin/user_prefs: No such file or directory
2005-06-02 08:50:47 [8877] i: Couldn't create readable default_prefs for
[/cs/home/user/.spamassassin/user_prefs]

It might make sense for the standard log file to say that the directory is being
created, and when it can't be created to show the reason why.