Now THAT is a good idea! What are you going to do for delivery if there’s more than one folder with the flag (or is that already impossible some other way)?
-- Stephen > On Oct 2, 2015, at 5:43 PM, Bron Gondwana <br...@fastmail.fm> wrote: > > I'm planning to create an option to reject delete or move into a sub folder > for any folder with a special-use flag. We would allow rename. Of course with > this would be a sieve extension to do delivery to a special-use flag instead > of folder name... > > Bron. > > On Sat, Oct 3, 2015, at 05:41, Stephen Ulmer wrote: >> A user deleting her spam folder won’t be prevented by a sieve script. >> >> I hope that most of your spam identification rules are run in your MTA (not >> in sieve) and then sieve is used to sort messages based on a a few simple >> flags. >> >> There may be a perfectly good use case for confusing users by having >> something that they can’t see or edit change their mailbox behavior, but I >> don’t think that spam defense is it. That being said, implementing global >> identifiers for an “include” directive would be nice… Then the user could >> include features from a catalog using a name from a registry of includes, >> rather than a path. >> >> >> -- >> Stephen >> >> >> >>> On Oct 2, 2015, at 3:22 PM, Mai Ling <mailinglist...@gmail.com >>> <mailto:mailinglist...@gmail.com>> wrote: >>> >>> Even if you create once & forget, there are still cases where site-enforced >>> rules are useful: >>> On the previous setup I've managed I've encountered lots of cases where >>> people accidentally deleted their spam folders or their spam rules; >>> Having an user rule automagically imported/enforced from a site template >>> would always prevent these. >>> >>> On Vin, oct. 2, 2015 at 10:13 p.m., Stephen Ulmer <ul...@ufl.edu >>> <mailto:ul...@ufl.edu>> wrote: >>> I would not imagine that you’d need (or want) to change all of the users’ >>> rules to make an update for spam filtering. Just filter on an X- header >>> that’s added by your MTA. Change the way the header gets calculated, but >>> not what it means to the sieve script. >>> >>> This is presuming that you make the modification just once (to turn it on). >>> >>> >>> -- >>> Stephen >>> >>> >>> >>> On Oct 2, 2015, at 3:08 PM, Mai Ling <mailinglist...@gmail.com >>> <mailto:mailinglist...@gmail.com>> wrote: >>> >>> Oh awesome! >>> >>> I wish they add support for editable site-default sieve rules that override >>> user sieve rules. >>> >>> This way you won't have to update all users rules when you want to make >>> modification to everyones' rules (usecase: spam filtering) >>> >>> On Sâm, sept. 26, 2015 at 1:30 a.m., Artyom Aleksandrov >>> <mailing.l...@tem4uk.ru <mailto:mailing.l...@tem4uk.ru>> wrote: >>> Hello,I want to create default sieve scipt for all my users but I stuck >>> with strange problem that looks like the bug. Unfortunately I've never >>> wrote on C so it's difficult for me to find it. >>> When Cyrus (2.5.3 or 2.5.6) create default sieve script it doesn't put file >>> in sieve_dir/?/user folder. It jist creates tmp files in configdirectory >>> with names like this >>> -rw------- 1 cyrus mail 124 Sep 26 00:41 ?&?P??default.script.bc >>> -rw------- 1 cyrus mail 231 Sep 26 00:41 ?&?P??default.script.script >>> lrwxrwxrwx 1 cyrus mail 17 Sep 26 00:41 ?&?P??defaultbc -> default.script.bc >>> >>> There are not checks in this stage so my syslog is clean of error. >>> Everything seems fine. >>> >>> Sep 26 00:41:34 imapsync cyrus/imap[26117]: autocreate_sieve: Problem >>> opening compiled script file: default.script.bc. Compiling it >>> Sep 26 00:41:34 imapsync cyrus/imap[26117]: autocreate_sieve: Compiled >>> sieve script was successfully saved in default.script.bc >>> Sep 26 00:41:34 imapsync cyrus/imap[26117]: autocreate_sieve: User XXXX, >>> default sieve script creation succeeded >>> >>> >>> My setting: >>> autocreate_sieve_script: /var/spool/sieve/global/default.script >>> autocreate_sieve_script_compile: yes >>> autocreate_sieve_script_compiled: default.script.bc >>> sievedir: /var/spool/sieve/ >>> Distributive: Ubuntu 14.04.3 >>> >>> I'll be glad for any help. ) >>> >>> Best regards, Artyom >>> ---- >>> Cyrus Home Page: <http://www.cyrusimap.org/>http://www.cyrusimap.org/ >>> <http://www.cyrusimap.org/> >>> List Archives/Info: >>> <http://lists.andrew.cmu.edu/pipermail/info-cyrus/>http://lists.andrew.cmu.edu/pipermail/info-cyrus/ >>> <http://lists.andrew.cmu.edu/pipermail/info-cyrus/> >>> To Unsubscribe: >>> >>> <https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus>https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus >>> <https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus> >> >> ---- >> Cyrus Home Page: http://www.cyrusimap.org/ <http://www.cyrusimap.org/> >> List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ >> <http://lists.andrew.cmu.edu/pipermail/info-cyrus/> >> To Unsubscribe: >> https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus >> <https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus> > > -- > Bron Gondwana > br...@fastmail.fm > >
---- Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ To Unsubscribe: https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
