> According to my notes, MUPDATEPUSH is used through an admin user's IMAP
> connection (via imtest) not through mupdatetest.
>
> If the mailbox doesn't actually exist, you might need to use LOCALCREATE via
> IMAP to the backend prior to MUPDATEPUSH.
>
> LC1 LOCALCREATE user.foo
Thank you Simon
On 9 Jul 2013, at 22:20, Shawn Winnington-Ball wrote:
>
>> You can force a backend to push all of its mailboxes to the mupdate master
>> by running "ctl_mboxlist -m" on the backend. If you're not 100% sure
>> whether you want to push every mailbox before you know what state things
>> are in, you
Hi Dave,
Thanks for the quick, helpful response.
> If you log in to mailbox-03-internal and run:
>
> # ctl_mboxlist -d | grep "^user\.foo"
>
> is anything returned? For that matter, run this on each of your backend
> servers and see if it exists anywhere.
None of the mailbox servers have any
On 7/9/13 3:04 PM, "Shawn Winnington-Ball" wrote:
>Hi all,
>
>I'm having an issue with a Cyrus murder wherein the mupdate server
>believes that a set of mailboxes are in mid-transfer, when in fact
>they don't exist on any of the downstream mailbox servers. Here's
>an example of a lone entry glea
Hi all,
I'm having an issue with a Cyrus murder wherein the mupdate server
believes that a set of mailboxes are in mid-transfer, when in fact
they don't exist on any of the downstream mailbox servers. Here's
an example of a lone entry gleaned from the output of `ctl_mboxlist
-d' run on the mupdat
