Bug 3215 - Per-User Bayes database should only track existing accounts
Summary: Per-User Bayes database should only track existing accounts
Status: RESOLVED FIXED
Alias: None
Product: Spamassassin
Classification: Unclassified
Component: spamc/spamd (show other bugs)
Version: SVN Trunk (Latest Devel Version)
Hardware: Other Linux
: P5 enhancement
Target Milestone: Undefined
Assignee: SpamAssassin Developer Mailing List
URL:
Whiteboard:
Keywords:
Depends on: 3380
Blocks:
  Show dependency tree
 
Reported: 2004-03-25 14:57 UTC by Jay Eno
Modified: 2004-12-20 05:14 UTC (History)
1 user (show)


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 Jay Eno 2004-03-25 14:57:09 UTC 
Using spamassassin system wide using spamd/spamc will allow for per-user bayes
in a Mysql/PG database. There is currently no verification process for spamd to
check if a user is valid before processing the bayes learning stuff. This can
lead to a database full of invalid mail (user) accounts listed in the bayes
database. There should be some sort of "verify_user" function to verify users
with whatever configuration system is in use (vpopmail, passwd, ldap...)
Comment 1 Michael Parker 2004-12-20 14:14:55 UTC 
Added a services_authorized_for_username hook and then support in BayesSQL for this.

For a sample plugin that uses this functionality you can see:
http://wiki.apache.org/spamassassin/AuthzUserPlugin