[ postfixadmin-Feature Requests-1807305 ] sieve db column
Brought to you by:
christian_boltz,
gingerdog
From: SourceForge.net <no...@so...> - 2007-11-09 13:37:43
|
Feature Requests item #1807305, was opened at 2007-10-03 22:25 Message generated for change (Comment added) made by nobody You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937967&aid=1807305&group_id=191583 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Database Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: ondras (ondras) Assigned to: Nobody/Anonymous (nobody) Summary: sieve db column Initial Comment: It would be nice to add a column 'sieve' to 'mailbox' table; this would be used to store a path to user sieve script. I am using dovecot+cmusieve for virtual delivery and the filter needs to know, where is the relevant script located. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2007-11-09 05:37 Message: Logged In: NO I use Sieve as Dovecot plugin. Sieve is applied when mail is locally delivered (via Dovecot), so Sieve script path should be stored next to list of virtual mailboxes and domains. Now when I have these data in MySQL database, it is pretty straightforward to store sieve path in DB as well. And the DB is managed via postfixadmin, so it is logical to have this setting also available in this webinterface. Sieve script is an attribute of a mailbox, similarly to password and redirect path. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2007-11-07 05:24 Message: Logged In: NO can you give a practical example that sieve is needed in postfixadmin ? ---------------------------------------------------------------------- Comment By: ondras (ondras) Date: 2007-11-07 05:02 Message: Logged In: YES user_id=1038215 Originator: YES This is not possible. Imagine shell user A taking care of mailboxes B & C, editing sieve scripts for B & C located in his home directory. A needs to explicitely state that B's and C's sieve scripts are located somewhere in /home/A/... and not in say /home/%username%/ . ---------------------------------------------------------------------- Comment By: GingerDog (gingerdog) Date: 2007-10-07 06:32 Message: Logged In: YES user_id=1761957 Originator: NO Could you not solve this through convention - e.g. the sieve script always has the same name as the username? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937967&aid=1807305&group_id=191583 |