On 03 Jun 2010, at 09:24, Gavin Gray wrote: > imap[29289]: [ID 886451 local6.error] Could not trigger remote push to > mupdate serverduring move of user... During the xfer, the local backend sets some information in the mupdate master WRT the new mailbox location. However, this information may be a bit of a guess. The MUPDATEPUSH instructs the remote backend to set whatever the correct information is in the mupdate master. Stupidly, the above log doesn't report what the problem was, and neither does the remote backend. That should be fixed (can you open a bug report?). However, the error is not fatal. > imap[22505]: [ID 772019 local6.error] Could not set remote acl on > user.... This error is fatal. In fact, you ought to not execute the following MUPDATEPUSH, because not being able to set the ACL is not permissible. Perhaps you're seeing this problem: https://bugzilla.andrew.cmu.edu/show_bug.cgi?id=3218 Of course, the logging again fails to tell us *why* we aren't able to set the remote ACL (another good opportunity to report a bug). > The error on the new backend receiving the error is: > kick_mupdate: can't connect to target: No such file or directory Is this a unified murder? Skimming imapd.c, I see a mix of calls to kick_mupdate(), some protected by checks for the type of murder, some not. Perhaps that's the problem. In any case, kick_mupdate() is void, so errors relating to it are probably cascades from some other failed step in the process. :wes ---- Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
