You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@spamassassin.apache.org by bu...@bugzilla.spamassassin.org on 2004/11/17 01:29:28 UTC

[Bug 3971] New: GRANTing appropriate privileges for bayes Pg DB

http://bugzilla.spamassassin.org/show_bug.cgi?id=3971

           Summary: GRANTing appropriate privileges for bayes Pg DB
           Product: Spamassassin
           Version: 3.0.1
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: enhancement
          Priority: P5
         Component: Documentation
        AssignedTo: dev@spamassassin.apache.org
        ReportedBy: kjetil@kjernsmo.net


I haven't found any details on how to GRANT the appropriate privileges to the
database user when using a Pg database for the bayesian classification. So, I
went through the source of the *Store::SQL, and made the appropriate grants
according to what I could see that code do to the different tables. I have
tested by learning a few hundred messages and sending a few messages through
spamassassin. It seems to be correct. However, since I can't exhaustively test
it, do not know the SA code in detail, it is a bit scary, if suddenly it could
be insufficient privileges when the DB syncs some time in the future for
example.... 

Michael Parker encouraged me to submit this bug, and I will attach a patch to
README.bayes shortly. 

I'm not completely certain this approach makes sense however. The main README
seems to advocate creating a db, then create a user and assign ownership of the
db to this user. I have too little experiences with databases, but I think the
approach should be that the db superuser creates the db, then creates the
tables, then creates the user and grants the privileges to that user, without
assigning full ownership. Does that make sense? In that case, I think a separate
bayes_grant_pg.sql may be a better approach, and then document how to use that.

Thanks a lot for all the work you've laid down in 3.0!



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.