Bug 527 - User directory passed by spamc
Summary: User directory passed by spamc
Status: RESOLVED DUPLICATE of bug 773
Alias: None
Product: Spamassassin
Classification: Unclassified
Component: spamassassin (show other bugs)
Version: SVN Trunk (Latest Devel Version)
Hardware: Other other
: P5 enhancement
Target Milestone: 3.0.0
Assignee: SpamAssassin Developer Mailing List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-07-08 07:51 UTC by Marc Perkel
Modified: 2002-12-13 10:47 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 Marc Perkel 2002-07-08 07:51:48 UTC 
In trying to fix a problem this weekend I reinstalled Spam Assassin. My system
wide customization directory is /etc/spamassassin - but when I reinstalled it
(using make install) it created a directory /etc/mail/spamassassin. And after
creating that directory it failed to see my customizations in /etc/spamassassin.

I don't like the idea of using /etc/mail/spamassassin for myself because
/etc/mail is for sendmail and I'm using exim.

So - the make process should not create default settings in /etc/mail if they
already exist in /etc

-------------------

Additionally - I'd like to see a switch added to spamc that would allow me to
pass on the command line the directory for the presonal configuration files for
.spamassassin to be. I'm running virtual email and there are no real users. My
users have fake home directories as such.

/vhome/[domain]/home/[user]

So I want to be able to tell spamc that the .spamassassin directory is in a
custom place.
Comment 1 Duncan Findlay 2002-12-13 19:21:53 UTC 
This first bug is fixed through use of command line options to Makefile.PL.

The second one of seen requested more recently, I think; but I can't find the
bug report. Changing title to reflect that. Marking 3.0.
Comment 2 Duncan Findlay 2002-12-13 19:47:31 UTC 
There it is!

*** This bug has been marked as a duplicate of 773 ***