Bug 737 - user_prefs not being read using spamc
Summary: user_prefs not being read using spamc
Status: RESOLVED FIXED
Alias: None
Product: Spamassassin
Classification: Unclassified
Component: spamc/spamd (show other bugs)
Version: 2.31
Hardware: Sun SunOS
: P4 normal
Target Milestone: ---
Assignee: SpamAssassin Developer Mailing List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-08-26 10:10 UTC by Samantha Lacy
Modified: 2002-09-03 22:29 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 Samantha Lacy 2002-08-26 10:10:44 UTC 
We have implemented spamassassin globally on our mail server with a system wide
/etc/procmailrc using spamc.  I am running spamd with these flags:

/pkg/gnu2k1/bin/spamd -dcL

When I first began testing this package simply using spamasssassin in the
/etc/procmailrc, it created the .spamassassin/user_prefs per user, and worked
just fine.  The problem was that the amount of mail we recieve was bogging down
the server using spamassassin, so we switched over to spamc.  This part works
great, and everyone loves it, except now it doesn't read the user_prefs that
were already there, nor does it create it for the users that didn't have it.  

Is there something else that needs to be done to make this work.  I have stopped
and started spamd numerous times after making changes as well.

Thanks in advance,

Samantha
Comment 1 Justin Mason 2002-09-04 06:29:16 UTC 
recommend retesting in a few days with 2.41 when it comes out.
please reopen if not fixed.

Note also that spamd will not read user's custom rules, as this
is a security problem in that setup.