Greetings- I've got spamd running fairly well in a virtual mail environment with postfix, where I have many domains and hundreds of mailboxes on the linux filesystem owned by one system account (we'll call it 'vmail').
I invoke spamd with something that looks like this: /usr/bin/spamd -p 784 -d -a -x -m5 -u vmail -r /var/run/vmail-spamd.pid --virtual-config-dir=/home/vmail/mail/%d/%l The actual virtual mail system is laid out according to the following schema: /home/vmail/mail/domain.tld/user/ - the 'home' directory of the user /home/vmail/mail/domain.tld/user/Maildir - self explanatory /home/vmail/mail/domain.tld/user/.spamassassin - this directory is created by spamc when the above config is used Now, this seems all good to me, but when I'm actually processing the mail, I get this: May 25 13:12:29 xxxxx spamd[29600]: Using default config for [EMAIL PROTECTED]: /home/vmail/mail/domain.tld/user/user_prefs This is not where the user_prefs would be located in a default SA environment; the user_prefs would be located in a .spamassassin directory. Why is this happening? It stores the AWL and the bayes in the created .spamassassin directory, so why does it look for the user_prefs file somewhere else? If I changed the --virtual-config-dir to something like /home/vmail/mail/%d/%l/.spamassassin, the user prefs would be where I would assume, but spamc then creates _another_ .spamassassin directory and operates in the fashion explained above. While this is more or less workable, it is not as clean as default SA behavior in a normal environment, and not what I expected (I was writing out user_prefs configs to the .spamassassin directory). I'd like to declare the --virtual-config-dir and have it contain the config, the bayes files, and the AWL, as any sane person would expect. Advice? Thanks, -Matt --------------------- Matthew Anderson Executor Internet Distributed Data Exchange - IDDX.NET
