[sam] hi there folks...

[Kendrick Vargas]

I'm new to the list, and wanted to ask a question straight away. I'm looking 
at the code to sam, specifically the amavisd-sql driver, and I was wondering 
if anyone would have and strong objections to my modifying it?

The reason I wanna modify it is cuz it seems rather destructive in it's 
current form. It doesn't pay attention to the actual policy ID a user has. 
It only looks for a policy with the same name as the user name. I'd like to 
change that to make more sense, maybe introduce the idea of "public" and 
"private" policies (with a flag in the table or something). Related to this, 
I'd like to make the driver more resistant to the user not having a personal 
profile.

Now, if I'm totally off my rocker here, let me know and I'll stop bothering 
with this now. I'm kinda new to amavisd and I want to have my users' amavis 
settings in my database, but I haven't found a whole lot of information 
regarding this. The way the policies are set up, it seems that you can 
basically tie a user to a policy, or multiple users to a single policy, for 
better management of users. I'm saying this because of the various default 
entries for the policy table that come with amavisd-sql.

The way that sam currently treats policy retrieval and storage doesn't seem 
to go well with that idea. I don't know which is right or which is wrong, 
but I'd like to alter the amavis-sql driver to work well with either.

so... am I barking up a really tall tree here for no reason?
			-peace

--
Let he who is without clue cast the first scone