Bug 501827 - Spamassassin default user "nobody" raises problem with bayes, autolearn, etc
Summary: Spamassassin default user "nobody" raises problem with bayes, autolearn, etc
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: spamassassin
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Warren Togami
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-05-20 21:59 UTC by Javier Alejandro Castro
Modified: 2009-05-21 16:08 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2009-05-21 16:08:56 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Javier Alejandro Castro 2009-05-20 21:59:17 UTC
Description of problem:

 There is no "untouched package way" to use spamassassin with autolearn auto-whitelist feature just fine.

Version-Release number of selected component (if applicable):

 spamassassin-3.2.5-5.fc11.x86_64

How reproducible:

 always

Steps to Reproduce:
1. Install spamassassin
2. Enable spamd service with default config
3. Look at syslog for spamd process. Lots of errors trying to access/create /.spamassassin/ directory, etc
  
Actual results:

 Errors. Spamassassin not being able to autolearn spam messages.

Expected results:

 Out of the box option for enabling spamd for in-site configuration, and being able to build the bayes database and auto-whitelist thing

Additional info:

 It seems spamd runs as user nobody, and user nobody home is ... /? so spamd tries to use/create /.spamassassin/user_prefs, etc...

 May be the best is to create a spamd user on the RPM scripts, etc and run spamc/spamd with that user? may be home must be set to /var/lib/spamassassin ?

Comment 1 Warren Togami 2009-05-21 16:08:56 UTC
I can't reproduce this issue.  spamd reads and writes .spamassassin in the home directory of the user running spamc.

As you said, probably an issue with cyrus-imapd.  Talk to that project.


Note You need to log in before you can comment on or make changes to this bug.