If you have just the one backend, then its mailboxes.db is complete and
accurate. All you have to do is remove the mupdate entries from
cyrus.conf AND imapd.conf and you're good to go. I do it all the time
on my local dev setup.
On 03/22/2018 02:47 PM, Nic Bernstein wrote:
Friends,
I've got a Cyrus installation, at a client with roughly a dozen
locations around the UA, which started life about 20 years ago and was
split into a murder -- 2 frontends, 1 backend, 1 mupdate master --
several years back. At the time of the split, there were plans to
geographically distribute portions of the mailstore, via the murder.
However, before that project got very far, the client decided to make
the leap to higher bandwidth Internet feeds, and then to an MPLS
network, so the impetus for the murder has really gone away.
At this point, with an upgrade from 2.5.11 to 3.0.X imminent, it makes
sense to un-murder (resurrect?) the systems. Is this possible? I'm
assuming it would simply involve dumping the mailboxes.db, stripping
out the murder-specific bits, and then reloading it. Is that
correct? Or, given that there's only a single backend, is this even
necessary; can I just use the mailboxes.db from the single backend?
Here's what a typical user's mailboxes.db entries look like on the
murder's mupdate master:
user.onlight 1 mailbox.example.com!default onlight lrswipkxtecda
cyradmin lrswipkxtecda cyradmin lrswipkxtecda
user.onlight.Drafts 1 mailbox.example.com!default onlight
lrswipkxtecda cyradmin lrswipkxtecda
user.onlight.Junk 1 mailbox.example.com!default onlight
lrswipkxtecda cyradmin lrswipkxtecda anyone p cyradmin
lrswipkxtecda
user.onlight.Sent 1 mailbox.example.com!default onlight
lrswipkxtecda cyradmin lrswipkxtecda
user.onlight.Trash 1 mailbox.example.com!default onlight
lrswipkxtecda cyradmin lrswipkxtecda
Here is the same excerpt from the backend's mailboxes.db:
user.onlight 0 default onlight lrswipkxtecda cyradmin
lrswipkxtecda cyradmin lrswipkxtecda
user.onlight.Drafts 0 default onlight lrswipkxtecda cyradmin
lrswipkxtecda
user.onlight.Junk 0 default onlight lrswipkxtecda cyradmin
lrswipkxtecda anyone p cyradmin lrswipkxtecda
user.onlight.Sent 0 default onlight lrswipkxtecda cyradmin
lrswipkxtecda
user.onlight.Trash 0 default onlight lrswipkxtecda cyradmin
lrswipkxtecda
And here's a similarly typical user's mailboxes.db entries from a
non-murder setup of the same vintage:
user.onlight 0 default onlight lrswipcda cyradmin
lrswipcda anyone p
user.onlight.Drafts 0 default onlight lrswipcda cyradmin
lrswipcda anyone p
user.onlight.Sent 0 default onlight lrswipcda cyradmin
lrswipcda anyone p
user.onlight.Spam 0 default onlight lrswipcda cyradmin
lrswipcda anyone p
user.onlight.Trash 0 default onlight lrswipcda cyradmin
lrswipcda anyone p
So, ignoring the obvious differences in some of the ACLs, it looks to
me like the backend's mailboxes.db is just fine, and is all I would
need. Is this correct?
In other words, all I really need to do is update the backend's
cyrus.conf to reënable the various normal services, turn off the
mupdatepush service, and Bob's your uncle, right?
Please advise,
-nic
--
Nic bernstein...@onlight.com
Onlight, Inc.www.onlight.com
6525 W Bluemound Road, Suite 24 v. 414.272.4477
Milwaukee, Wisconsin 53213-4073
----
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
--
Kenneth Murchison
Cyrus Development Team
FastMail Pty Ltd
----
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
