Sieve scripts execution for connected folders

kvaps kvapss at gmail.com
Tue Oct 9 15:17:45 EDT 2018


Yes, my version is 2.5.11-10.11.el7.kolab_16, and seems there is this
bug, so shared folder sieves not working there
https://github.com/cyrusimap/cyrus-imapd/issues/1453


- kvaps
On Tue, Oct 9, 2018 at 9:13 PM kvaps <kvapss at gmail.com> wrote:
>
> Sorry for confuse. I was little confused myself :)
>
> Yes, my user and few other users subscribed to this shared folder.
> Each user have own seen status for this folder - this is ok.
> But folder is big and have new mails quite often.
>
> Each user should react different mails in this mailbox.
> For now I receive notifications for all new mails, this is really annoying.
> I need notifications only for few of them, eg "mails with specific
> word in subject", the rest should be marked as seen.
> Usually this behavior can be configured via sieve script, but in case
> with shared folders it is not working.
> Global sieve script for shared folder will not work too, because it
> changes global seen state, but state for each user.
>
> Probably no way, as you said before.
>
> - kvaps
> On Tue, Oct 9, 2018 at 5:10 PM Nic Bernstein <nic at onlight.com> wrote:
> >
> > Your use of the phrase "connected to all users" and, earlier, "connected and subscribed", is confusing.  Am I correct to assume you mean the folder is "subscribed" by all users?  There is no such thing asa mailbox/folder being "connected" as a state.  It may be subscribed or not, it may be connected to, by a client, but "connected" is not a static condition.
> >
> > Cyrus can support shared seen state, but it's also not clear, from your messages, if you want shared seen state, or don't want it?  Just what are you trying to achieve?
> >
> > Also, which version of Cyrus are you using?  Current is 3.0.8, historic is 2.5.12, development is 3.1.X.
> >
> > The rule with user sieve scripts is that they may only act on that user's mailboxes, not on shared mailboxes which one is subscribed to.  If you want to have new messages in a shared mailbox show as new for each user, separately, then you need to disable shared seen.  This may be done on the mailbox level, using the cyradm(8) command, with the mboxcfg subcommand:
> >
> > localhost> info office
> > {office}:
> >   private:
> >     check: NIL
> >     checkperiod: NIL
> >     comment: NIL
> >     sort: NIL
> >     specialuse: NIL
> >     thread: NIL
> >     expire: NIL
> >     news2mail: NIL
> >     sieve: NIL
> >     squat: NIL
> >   shared:
> >     check: NIL
> >     checkperiod: NIL
> >     comment: NIL
> >     sort: NIL
> >     specialuse: NIL
> >     thread: NIL
> >     annotsize: 0
> >     duplicatedeliver: false
> >     expire: NIL
> >     lastpop: NIL
> >     lastupdate: 31-Jul-2018 09:59:20 -0500
> >     news2mail: NIL
> >     partition: default
> >     pop3newuidl: true
> >     pop3showafter: NIL
> >     sharedseen: false
> >     sieve: NIL
> >     size: 4101
> >     squat: NIL
> >     synccrcs: 1118531081 0
> >     uniqueid: 4c8f66f0-9f6a-4fa1-b8bf-547afa1ec5e8
> > localhost> mboxcfg office sharedseen true
> > localhost> info office
> > {office}:
> >   private:
> >     check: NIL
> >     checkperiod: NIL
> >     comment: NIL
> >     sort: NIL
> >     specialuse: NIL
> >     thread: NIL
> >     expire: NIL
> >     news2mail: NIL
> >     sieve: NIL
> >     squat: NIL
> >   shared:
> >     check: NIL
> >     checkperiod: NIL
> >     comment: NIL
> >     sort: NIL
> >     specialuse: NIL
> >     thread: NIL
> >     annotsize: 0
> >     duplicatedeliver: false
> >     expire: NIL
> >     lastpop: NIL
> >     lastupdate:  9-Oct-2018 10:09:19 -0500
> >     news2mail: NIL
> >     partition: default
> >     pop3newuidl: true
> >     pop3showafter: NIL
> >     sharedseen: true
> >     sieve: NIL
> >     size: 4101
> >     squat: NIL
> >     synccrcs: 1118531081 0
> >     uniqueid: 4c8f66f0-9f6a-4fa1-b8bf-547afa1ec5e8
> >
> > Is that what you're trying to achieve, changing the setting of Shared \Seen?
> >
> > Cheers,
> >     -nic
> >
> > On 10/09/2018 12:16 PM, kvaps wrote:
> >
> > Hi, thanks for quick answer,
> >
> > Yes, I know about shared folder sieves, but I have aniother case:
> >
> > Eg I have some users:
> >
> >   user/user1 at example.org
> >   user/user2 at example.org
> >   user/user3 at example.org
> >
> > and shared folder
> >
> >   shared/test at example.org
> >
> > This folder connected to all users and have no shared seen state.
> > I need to set seen flag automatically for user1, and keep second as unseen.
> >
> > - kvaps
> > On Tue, Oct 9, 2018 at 1:08 PM Nic Bernstein <nic at onlight.com> wrote:
> >
> > Kvaps,
> > It is unclear from your message just where this "shared folder" is
> > rooted and where your sieve scripts are.  Do you mean a folder which is
> > outside of the "user" name space?  If so, you cannot manage message
> > delivery to this folder via user sieve scripts, but must use global
> > sieve scripts instead.
> >
> > Please see the documentation here:
> > https://www.cyrusimap.org/imap/reference/admin/sieve.html#sieve-scripts-in-shared-folders
> >
> > I hope this is helpful information,
> >      -nic
> >
> > On 10/09/2018 11:57 AM, kvaps wrote:
> >
> > Hello,
> >
> > I have shared folder which connected and subscribed in my mailbox, it
> > is looks like normal subfolder., but my sieve scripts not handle mail
> > inside it.
> >
> > I want to set seen flag for new messages inside this folder
> > automatically by sieve script.
> > Is it possible for configure sieve-script working for connected folders too?
> >
> > - kvaps
> > ----
> > 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
> >
> > --
> > Nic Bernstein                             nic at onlight.com
> > Onlight Inc.                              www.onlight.com
> > 6525 W Bluemound Rd., Ste 24              v. 414.272.4477
> > Milwaukee, Wisconsin  53213-4073          f. 414.290.0335
> >
> >
> > --
> > Nic Bernstein                             nic at onlight.com
> > Onlight Inc.                              www.onlight.com
> > 6525 W Bluemound Rd., Ste 24          v. 414.272.4477
> > Milwaukee, Wisconsin  53213-4073  f. 414.290.0335


More information about the Info-cyrus mailing list