[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re[2]: [vps-mail] VPS2, Bayes problem



SW> It sounds like you want the following behavior:

SW>   * scan mail with spamassassin with the recipient's UID (for Bayes
SW>     training)

NO. I want to use Bayes & Autowhitelisting server wide, with
ONE Bayes database shared by all.  (Believe me, we all get
the same spam).

SW>   * deliver the mail to their mailbox if it's not spam

Yes.


SW>   * deliver the mail to /var/mail/spam if it is spam

Yes.

I appear to have fixed it now, but here is what I had to do.
I was mistaken in thinking that it
would write to Bayes with Dropprivs=yes. With that setting,
it was creating the Bayes journal, but not writing to it.

Here is the configuration I now have that works (just in
case anyone else needs it).

/etc/mail/local.cf:

use_bayes        1
bayes_path      /var/spool/spamassassin/bayes
bayes_file_mode  0777
bayes_auto_expire  1
bayes_auto_learn   1


Directory /var/spool/spamassassin -
chmod: 777

Also, I need to note that the path to bayes was not changed
merely by restart_sendmail -- I needed to also reboot.

-Abigail

======================================================================
This is <vps-mail@xxxxxxxxxxxx>       <http://www.perlcode.org/lists/>
Before posting a question, please search the archives (see above URL).


Main Index | Thread Index
Match: Format: Sort by:
Search: