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 wrote:
>
> Sorry for confuse. I was little confused myself :)
>
> Yes, my user an
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 re
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 conn
Hi, thanks for quick answer,
Yes, I know about shared folder sieves, but I have aniother case:
Eg I have some users:
user/us...@example.org
user/us...@example.org
user/us...@example.org
and shared folder
shared/t...@example.org
This folder connected to all users and have no shared see
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 script
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 workin
