Has anyone looked at modifying the sieve implementation to allow the use of MySQl to store the rules? david
Maybe you can write a daemon to read rules from mysql and then build sieve scripts. :) On Tue, 07 Apr 2009 11:36:15 +0100 David Reid <david at jetnet.co.uk> wrote:> Has anyone looked at modifying the sieve implementation to allow the use > of MySQl to store the rules? > > david-- Xueron Nee http://www.xueron.com
On Tue, 2009-04-07 at 11:36 +0100, David Reid wrote:> Has anyone looked at modifying the sieve implementation to allow the use > of MySQl to store the rules?Maybe instead of MySQL directly it could use lib-dict, which then could be configured to use MySQL or whatever. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part URL: <http://dovecot.org/pipermail/dovecot/attachments/20090408/f79cbd04/attachment-0002.bin>
David Reid schreef:> Has anyone looked at modifying the sieve implementation to allow the use > of MySQl to store the rules? >This is a two-sided problem: - The ManageSieve server needs to store, retrieve and activate the scripts in the SQL database. - The Sieve plugin needs access to the SQL database to retrieve scripts. There are future plans to provide an alternative to the filesystem storage method that ManageSieve currently uses. However, the Sieve plugin then also needs to use this storage method. To obtain a unified implementation, I intend to integrate the Sieve plugin and ManageSieve packages into one monolithic package for Sieve support. This is for the more distant future however. Regards, -- Stephan Bosch stephan at rename-it.nl