Hello Dominique, I thought about a SQL database, but found it's a security problem if User need to write data.
Stefan Am 25.07.2012 19:11, schrieb Dominique: > Hi Stefan, > > We don't use LDAP in most of our installations (lots of them, but > limited number of users per installations), so we keep with MySQL. > > Cheers, > > Dominique > > On 25/07/2012 18:54, Stefan Klatt wrote: >> Hi Dominique, >> >> that's the reason why I use a LDAP tree with "Sieve" objects under the >> user objects. >> This "Sieve" objects will be converted with a python script to real >> Sieve filter. >> >> The problem is only to write a web frontend for this, at the moment I >> use phpldapadmin. >> >> Stefan >> >> Am 25.07.2012 18:38, schrieb Dominique: >>> Hi Martin, >>> >>> The objective is to be consistent in environment where both TB and the >>> WebGUI are in use, and avoid confusion/conflict between both systems. >>> >>> I agree sieve scripts are not easy access to basic users, but that >>> could be organized by having the scripts prepared by more advanced >>> users and made available to all. I suppose basi users can >>> activate/deactivate scripts all alone - they do much worse in other >>> occasions. >>> >>> I'll have a look at the bug you mention and push for it. >>> >>> Cheers, >>> >>> Dominique >>> >>> On 25/07/2012 15:02, Martin Rabl wrote: >>>> A possible solution for Dominiques request could be seen in >>>> http://www.sogo.nu/bugs/view.php?id=1392, but it depends on >>>> sieve-files which are still on the server or send to the server via >>>> managesieve-command or sftp or something else - but not with SOGo. >>>> >>>> Sieve allows to store (sieve-)files on the server without activating >>>> them. >>>> >>>> So, a solution could be integrating an editor field for >>>> clean-sieve-files in a own tab (name it "Sieve" ;-) in the >>>> preferences window. This script could be stored as is on the server >>>> (and in the database) and will be enabled by integrate an include on >>>> that in the standard-sogo-sieve-script generated bei SOGo. >>>> With some changes in http://www.sogo.nu/bugs/view.php?id=1392 and in >>>> the preferences view it could be integrated, I think. >>>> >>>> Sure, Sieve scripting itself is used by the experienced user ... our >>>> "standard" users are pretty happy with the SOGo-generated sieve >>>> script. But the others ... ;-) >>>> >>>> Greetings, >>>> Martin >>>> >>>> Am 25.07.2012 14:48, schrieb Andreas Balg: >>>>> Hey Dominique: >>>>> >>>>> Log in and go to "Preferences" -> "Email" - What you see there in >>>>> the >>>>> field at the bottom named "Filter" are sieve rules nothing else >>>>> manageable by the user even with an assisant. What else would you >>>>> expect ?? Free-Style manual sieve rules probably won't be of too much >>>>> help to that many people ;-) >>>>> >>>>> Cheers >>>>> Andreas >>>>> >>>>> Am 25.07.2012 13:06, schrieb Dominique: >>>>>> Hi >>>>>> >>>>>> We run a Cyrus/Sieve Server with SOGo. However, the sieve >>>>>> integration in SOGo is less than perfect (sorry). On one end, SOGo >>>>>> offers Vacations and Forward options but on the other end no easy >>>>>> way to access/edit/maintain/create/... sieve rules - including those >>>>>> two options. >>>>>> >>>>>> Could a new admin page be created to manage sieve (when available in >>>>>> the server as per the .GNUstepDefaults file) through the SOGo webgui >>>>>> to allow users to maintain their rules by themselves ? It seems that >>>>>> Sieve is already somewhat supported by SOGo. Why not finish the >>>>>> integration and offer to use either one or the other option or both? >>>>>> >>>>>> Dominique >>>>> >>>> >> -- *CaC, Computer and Communication* Inhaber Stefan Klatt End-2-End Senior Network Consultant Triftstrasse 9 60528 Frankfurt Germany USt-IdNr.: DE260461592 Tel.: +49-(0)172-6807809 Tel.: +49-(0)69-67808-900 Fax: +49-(0)69-67808-837 Email: [email protected]
<<attachment: stefan_klatt.vcf>>
signature.asc
Description: OpenPGP digital signature
