Re: Syntax for mailbox_default_options

[ellie timoney]

I believe it's an integer bitmask of the OPT_* values that are defined in 
imap/mailbox.h in the source.

The sparse documentation suggests it's for developer, rather than normal 
administrator use, maybe for rigging up tests?  It's included in the imapd.conf 
man page because that man page is autogenerated from the code that processes 
the options.

Unless you've got something in particular you're trying to do, I'd probably 
just leave it alone. :)

Cheers,

ellie

On Fri, Apr 13, 2018, at 1:21 AM, Nels Lindquist wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
> 
> The man page for imapd.conf has this to say regarding
> "mailbox_default_options":
> 
> > Default “options” field for the mailbox on create. You’ll want to 
> > know what you’re doing before setting this, but it can apply some 
> > default annotations like duplicate supression
> Well, I don't know what I'm doing and I'm not finding anything in the
> documentation (or Google) to help.
> 
> What's the syntax for this directive?
> 
> Thanks,
> 
> Nels Lindquist 
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v2
> 
> iEYEARECAAYFAlrPeXUACgkQh6z5POoOLgSseQCeMf84dZYsch4TEgyh1yp/nFxK
> jNkAnjkmipQpX840srzkAUhxOd0vYW2z
> =q9eN
> -END PGP SIGNATURE-
> 
> 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

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

Syntax for mailbox_default_options

[Nels Lindquist]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

The man page for imapd.conf has this to say regarding
"mailbox_default_options":

> Default “options” field for the mailbox on create. You’ll want to 
> know what you’re doing before setting this, but it can apply some 
> default annotations like duplicate supression
Well, I don't know what I'm doing and I'm not finding anything in the
documentation (or Google) to help.

What's the syntax for this directive?

Thanks,

Nels Lindquist 
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iEYEARECAAYFAlrPeXUACgkQh6z5POoOLgSseQCeMf84dZYsch4TEgyh1yp/nFxK
jNkAnjkmipQpX840srzkAUhxOd0vYW2z
=q9eN
-END PGP SIGNATURE-

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

Re: backends with different altnamespace in a murder configuration

[Ken Murchison]

Since the proxy is where the mailbox LIST is normally generated for the 
client, those clients that want to have altnamespace presented to them 
need to be talking to proxys with altnamespace enabled.  So, essentially 
you need to have one set of frontends/backends configured for 
altnamespace and another set for standard namespace.  They all can talk 
to the same mupdate server(s).


This is all theoretical, as I have never tested such a configuration.


On 04/12/2018 06:07 AM, Jean-Christophe Delaye wrote:

On 04/11/2018 06:52 PM, Ken Murchison wrote:

Do you have any frontend proxys?  They would also have to be using
altnamespace.

Yes, respectively 2 frontend proxys which are also the murder master and
slave. So how can I managed from these proxys that I have backend
servers with different altnamespace settings ? ... if it's possible ?




On 04/11/2018 12:20 PM, Jean-Christophe Delaye wrote:

Hello,

We are currently running cyrus 2.4 in a murder configuration: 2 murder
servers (master and slave) and 5 backend servers.
As in 2.x version, the altnamespace value is set to its legacy value
:off on all the server's imapd.conf.

We would like to change the altnamespace value to on BUT only for some
backend servers. The idea is to have a better integration for specific
users depending of their mail clients.

My question is: Is it possible in a murder cluster configuration to have
backend servers with different altnamespace settings. If so, what is the
impact of the murder servers altnamespace value ?

Greetings.

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




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



--
Ken Murchison
Cyrus Development Team
FastMail US LLC

<>
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

Re: backends with different altnamespace in a murder configuration

[Jean-Christophe Delaye]

On 04/11/2018 06:52 PM, Ken Murchison wrote:
> Do you have any frontend proxys?  They would also have to be using
> altnamespace.

Yes, respectively 2 frontend proxys which are also the murder master and
slave. So how can I managed from these proxys that I have backend
servers with different altnamespace settings ? ... if it's possible ?

> 
> 
> 
> On 04/11/2018 12:20 PM, Jean-Christophe Delaye wrote:
>> Hello,
>>
>> We are currently running cyrus 2.4 in a murder configuration: 2 murder
>> servers (master and slave) and 5 backend servers.
>> As in 2.x version, the altnamespace value is set to its legacy value
>> :off on all the server's imapd.conf.
>>
>> We would like to change the altnamespace value to on BUT only for some
>> backend servers. The idea is to have a better integration for specific
>> users depending of their mail clients.
>>
>> My question is: Is it possible in a murder cluster configuration to have
>> backend servers with different altnamespace settings. If so, what is the
>> impact of the murder servers altnamespace value ?
>>
>> Greetings.
>> 
>> 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
> 
> 
> 
> 
> 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
> 


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