Cyrus IMAP 2.5 Discrete Murder

2013-06-14 Thread Jeroen van Meeuwen (Kolab Systems)
Hi there,

I've attempted to deploy a discrete murder topology setup using git master @ 
534066.

I run in to a particular issue attempting to create a mailbox, for which I 
have attempted two scenarios:

  a) have the frontends configured with no partition-default setting,

  b) have the frontends configured with a partition-default of 
/var/spool/imap/

The configuration is working fine for cyrus-imapd-2.4.17.

In case a), a . CREATE user/someu...@domain.tld results in a 
Unknown/invalid partition error,

In case b), the mailbox does get created, but on the frontend, which of course 
is not the intention, and while I would be able to reproduce the error message 
I subsequently get, it's going to take me a while to move forward and then 
backwards again.

Attached are the configuration files, for reference.

Kind regards,

Jeroen van Meeuwen

-- 
Systems Architect, Kolab Systems AG

e: vanmeeuwen at kolabsys.com
m: +44 74 2516 3817
w: http://www.kolabsys.com

pgp: 9342 BF08# standard standalone server implementation

START {
# do not delete this entry!
recover cmd=ctl_cyrusdb -r

# this is only necessary if using idled for IMAP IDLE
idled   cmd=idled

# Push out my current list of mailboxes to the mupdate server
mupdate cmd=ctl_mboxlist -m
}

# UNIX sockets start with a slash and are put into /var/lib/imap/sockets
SERVICES {
# add or remove based on preferences
imapcmd=imapd listen=imap prefork=5
imaps   cmd=imapd -s listen=imaps prefork=1
pop3cmd=pop3d listen=pop3 prefork=3
pop3s   cmd=pop3d -s listen=pop3s prefork=1
sieve   cmd=timsieved listen=sieve prefork=0

lmtpunixcmd=lmtpd listen=/srv/imap/config/socket/lmtp prefork=1

# this is only necessary if using notifications
notify  cmd=notifyd listen=/srv/imap/config/socket/notify 
proto=udp prefork=1
}

EVENTS {
# this is required
checkpoint  cmd=ctl_cyrusdb -c period=30

# this is only necessary if using duplicate delivery suppression,
# Sieve or NNTP
duplicateprune cmd=cyr_expire -E 3 at=0400

# Expire data older then 69 days. Two full months of 31 days
# each includes two full backup cycles, plus 1 week margin
# because we run our full backups on the first sat/sun night
# of each month.
deleteprune cmd=cyr_expire -E 4 -D 69 at=0430
expungeprune cmd=cyr_expire -E 4 -X 69 at=0445

# this is only necessary if caching TLS sessions
tlsprunecmd=tls_prune at=0400

## Create search indexes regularly
#squattercmd=squatter -s -i at=0530
}
# standard standalone server implementation

START {
# do not delete this entry!
recover cmd=ctl_cyrusdb -r

# this is only necessary if using idled for IMAP IDLE
idled   cmd=idled
}

# UNIX sockets start with a slash and are put into /var/lib/imap/sockets
SERVICES {
# add or remove based on preferences
imapcmd=proxyd listen=imap prefork=5
imaps   cmd=proxyd -s listen=imaps prefork=1
pop3cmd=proxyd listen=pop3 prefork=3
pop3s   cmd=proxyd -s listen=pop3s prefork=1
sieve   cmd=timsieved listen=sieve prefork=0

mupdate cmd=mupdate listen=3905 prefork=1
}

EVENTS {
# this is required
checkpoint  cmd=ctl_cyrusdb -c period=30

# this is only necessary if caching TLS sessions
tlsprunecmd=tls_prune at=0400
}
# standard standalone server implementation

START {
# do not delete this entry!
recover cmd=ctl_cyrusdb -r
}

# UNIX sockets start with a slash and are put into /var/lib/imap/sockets
SERVICES {
mupdate cmd=mupdate -mlisten=3905 prefork=1
}

EVENTS {
# this is required
checkpoint  cmd=ctl_cyrusdb -c period=30

# this is only necessary if caching TLS sessions
tlsprunecmd=tls_prune at=0400
}
/vendor/horde/share-params,mailbox,string,backend,value.shared value.priv,a
/vendor/kolab/color,mailbox,string,backend,value.shared value.priv,a
/vendor/kolab/folder-test,mailbox,string,backend,value.shared value.priv,a
/vendor/kolab/folder-type,mailbox,string,backend,value.shared value.priv,a
/vendor/kolab/incidences-for,mailbox,string,backend,value.shared value.priv,a
/vendor/kolab/pxfb-readable-for,mailbox,string,backend,value.shared value.priv,a
/vendor/kolab/h-share-attr-desc,mailbox,string,backend,value.shared value.priv,a
/vendor/kolab/activesync,mailbox,string,backend,value.priv,r
/vendor/x-toltec/test,mailbox,string,backend,value.shared value.priv,aconfigdirectory: /var/lib/imap
admins: cyrus-admin
sievedir: /var/lib/imap/sieve
sendmail: /usr/sbin/sendmail
sasl_pwcheck_method: saslauthd
sasl_mech_list: PLAIN LOGIN
allowplaintext: no
tls_cert_file: /etc/pki/cyrus-imapd/cyrus-imapd.pem
tls_key_file: /etc/pki/cyrus-imapd/cyrus-imapd.pem
tls_ca_file: /etc/pki/tls/certs/ca-bundle.crt
# uncomment this if you're operating in a 

Re: cyrus-imapd-2.4.17-caldav-beta5 released

2013-06-14 Thread Bron Gondwana
On Fri, Jun 14, 2013, at 01:16 AM, Dave McMurtrie wrote:

The data is replicated, but right now the associated metadata is not.
I think brong and/or Ken are working on this, but they can correct me
if I'm wrong.



For now, you'd need to reconstruct the dav database on the replica if
you failed over.





Ooh, if that's all there is to it - I can probably just fix the
sync_server process to build the dav database on the fly!  Nice.



(yes, I am working on it... though not 100%, got other things going on)



--
Bron Gondwana
br...@fastmail.fm