For security reasons I am running spamd under a seperate username
'spamd -d -a -u foo'
This creates a system wide AWL under the user 'foo' home directory
(/var/spool/spamassassin).
Problem is that the command 'spamassassin --add-addr-to-blacklist' doesn't
know anything about the user 'foo' and I can't add a command line option '-u
foo' for this one either.
Any suggestions on how I can configure this so that I have either a system
wide AWL that is accessable from the command spamassassin or be able to runs
spamd under another username and have it know about the different AWL lists
for each real user (~/.spamassassin/..)
As near as I can tell, there isn't any really good way to get the spamd and
spamassassin AWL's to work together. But I am assuming that I'm missing
something "obvious"
(Version 2.43)
--
My idea of roughing it is when room service is late.
-------------------------------------------------------
This SF.net email is sponsored by: Get the new Palm Tungsten T
handheld. Power & Color in a compact size!
http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0002en
_______________________________________________
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
- [SAtalk] Bayesian hybrid Tom Allison
- [SAtalk] Bayesian hybrid Christopher Eykamp
- Re: [SAtalk] Bayesian hybrid Matt Sergeant
- Re: [SAtalk] Bayesian hybrid Vivek Khera