Re: [SM-PLUGINS] amavisnewsql and postfixadmin

[Paul L. <pa...@sq...>]

On Sat, Oct 4, 2008 at 6:52 PM, Jared Watkins <ja...@ja...> wrote:
> Frank wrote:
>> Firstly, thanks for a great plugin!
>>
>> I am setting up amavisnewsql on the following setup
>> and am wondering whether it is possible to use the same database for the
>> amavisnewsql settings as for postfixadmin
>> This would get around the problem of patching postfixadmin to create
>> new usernames in the amavis database.
>>
>> Also, I have set up my server mostly from this guide:
>> http://codepoets.co.uk/postfixadmin-postgresql-courier-squirrelmail-debian-etch-howto-tutorial
>>
>> but I am having some trouble with the best settings for amavis to
>> access the sql database, do you have an example amavis.conf that is
>> set up for this, the INSTALL file assumes that this is already set up,
>> which is not the case for me.
>>
>>
>>
> As for using db tables from another project with this plugin... anything
> is possible.. as they say it's a simple matter of software.   Really
> though.. short of rewriting one of the two packages to support the db of
> the other I don't see this working. If all you need is an extra table
> insertion to work with postfixadmin I'd say that's your best way to go.

I have a new plugin in testing that allows you to define any set of
options you'd like that can be saved into whatever database table you
want.  I don't know what amavis-specific functionality you need, but
if all you're trying to do is get some user settings into a database,
then something like this new plugin, without hard-coded database
tables/schemas, is going to be more suited to your needs (and does not
require any hacks of other packages).  You'd have to ask me offlist
for a beta copy.

> The sql queries for amavis to work with with amavisnewsql are indeed in
> the README file that comes with the plugin.  Keep in mind.. even when it
> was current.. my plugin didn't use the default amavis-new database
> schema.  If you setup the various bits as described in the plugin readme
> it should still work though.. I know there are others out there still
> using it with current versions of everything.
>
> I've said this before on the list.. and I'll repeat it again for the
> archive.  I'm glad there are a few people out there still finding this
> code useful.. but I've not touched it in quite a while and won't be in
> the foreseeable future. Also.. probably best to cc me directly to the
> address listed in the readme as I may miss stuff posted here.