What flags should I supply to cyr_expire in a replication configuration when I
have expire annotations in use?
I have a replication relationship from a 2.5.12 machine (in the process of
being replaced, but currently the master) to a 3.0.8-6+deb10u4 (as replica).
I have had problems with old
Hi Nic,
On 11/01/2016 11:43 AM, Nic Bernstein via Info-cyrus wrote:
Friends,
Further questions for our effort to abandon our aging DaviCal server.
How does one set the Display Name for a collection in Cyrus? Is this
handled via annotations? We can see from the sources (annotate.h,
line 57
Friends,
Further questions for our effort to abandon our aging DaviCal server.
How does one set the Display Name for a collection in Cyrus? Is this
handled via annotations? We can see from the sources (annotate.h, line
57) that there's a new /vendor/cmu/cyrus-httpd branch defined, b
Hi. Using perl IMAP::Admin library, annotations for the given mailbox survive
mailbox deletion. Is there a way do delete all annotations for the given
mailbox or do I have to set all the available annotations to "none" before I
delete a mailbox?
Also what other things survive mailbo
On Mon, 2009-07-20 at 18:24 +0200, Carsten Hoeger wrote:
> On Mon, Jul 20, Reinaldo de Carvalho wrote:
> > >> > I'm currently trying to find out how to use cyr_expire in combination
> > >> > with
> > >> > annotations exluding one single subfo
On Mon, Jul 20, Reinaldo de Carvalho wrote:
> >> > I'm currently trying to find out how to use cyr_expire in combination
> >> > with
> >> > annotations exluding one single subfolder per mailbox.
> >
> > [...]
> >
> >> D
On Mon, Jul 20, 2009 at 9:54 AM, Carsten Hoeger wrote:
> On Mon, Jul 20, Reinaldo de Carvalho wrote:
>
>> > I'm currently trying to find out how to use cyr_expire in combination with
>> > annotations exluding one single subfolder per mailbox.
>
> [...]
>
>&
On Mon, Jul 20, Reinaldo de Carvalho wrote:
> > I'm currently trying to find out how to use cyr_expire in combination with
> > annotations exluding one single subfolder per mailbox.
[...]
> Don't set expire for user (root) mailbox, only to "user/test1001/Sent Ite
> I'm currently trying to find out how to use cyr_expire in combination with
> annotations exluding one single subfolder per mailbox.
> I'm running RHEL5 with v2.3.7-Invoca-RPM-2.3.7-2.el5_3.2.
> What I did:
> . setannotation "user/test1001" "/vendor/cmu/c
On Mon, Jul 20, 2009 at 5:33 AM, Carsten Hoeger wrote:
> Hi,
>
>
> I'm currently trying to find out how to use cyr_expire in combination with
> annotations exluding one single subfolder per mailbox.
>
> I'm running RHEL5 with v2.3.7-Invoca-RPM-2.3.7-2.el5_3.2.
>
Hi,
I'm currently trying to find out how to use cyr_expire in combination with
annotations exluding one single subfolder per mailbox.
I'm running RHEL5 with v2.3.7-Invoca-RPM-2.3.7-2.el5_3.2.
What I did:
. setannotation "user/test1001" "/vendor/cmu/cyrus-imapd/ex
> To get a tiny statistic we are going through all mailboxes and use
> GETANNOTATION to retrieve possible annotations, which is a time consuming
> progress. GETANNOTATION does not like wildcards like LIST.
Yes it does.
Bah, seems the draft is up to -13 now, and they've actually ch
Is there a way to get all annotations with one imap or cyrus command?
We are using annotations here to be able to set an expiration time for spam
mailboxes (messages older then x days are deleted automatically at night
with cyr_expire).
To get a tiny statistic we are going through all
Ah, you're talking about message flags (keywords actually). All flags
other than \Seen are shared flags in Cyrus. If/when we implement
message annotations, we could make keywords private. There is currently
no way to change the behavior that you're seeing.
Btw: The share folders ar
ot under some users INBOX but on the same
level as the users INBOXes.
Thanks for your help!
Ken Murchison schrieb:
Michael Karrer wrote:
Hello List,
Is there a way to make the annotations (like important, to do...) "per
user" and not "per folder" - just like the seen un
Michael Karrer wrote:
Hello List,
Is there a way to make the annotations (like important, to do...) "per
user" and not "per folder" - just like the seen unseen database?
Per folder just doesnt make sense in a large company with a lot of people.
Cyrus supports both sha
Hello List,
Is there a way to make the annotations (like important, to do...) "per
user" and not "per folder" - just like the seen unseen database?
Per folder just doesnt make sense in a large company with a lot of people.
Thanks for ANY! help.
Cyrus Home Page: ht
[EMAIL PROTECTED] wrote:
On Sun, 11 Jan 2004, Ken Murchison wrote:
The 3 vendor-specific annotations used by Cyrus are all documented in
the appropriate locations:
squat: squatter(8)
expire: cyr_expire(8), install-netnews.html
news2mail: install-netnews.html
What about these?
https
On Sun, 11 Jan 2004, Ken Murchison wrote:
> The 3 vendor-specific annotations used by Cyrus are all documented in
> the appropriate locations:
>
> squat: squatter(8)
> expire: cyr_expire(8), install-netnews.html
> news2mail: install-netnews.html
What about these?
https://bugzi
o a small quest of the other possibilities of annotations,
such as EXPIRY
Unfortunately, I have not yet found a list online of all annotations
Cyrus supports, and what each annotation does and takes as arguments.
Did I stop looking too early, or is this really a big mystery ? ;-)
The 3
Hi all,
Looking around on various archives and testing out the squatter
function, I have found that this function only works if I set the
'squat' annotation on a mailbox.
This led me to a small quest of the other possibilities of annotations,
such as EXPIRY
Unfortunately, I have not
21 matches
Mail list logo
