kick_mupdate?

[Wesley Craig]

On 29 Oct 2010, at 15:29, Michael D. Sofka wrote:
> When moving files from a 2.2.12 back-end server to a 2.3.16 back-end 
> server using xfer, the 2.3.16 server logs:
> 
> Oct 29 15:23:23 imap-be4 imap[5933]: kick_mupdate: can't connect to 
> target: No such file or directory
> 
> The xfer was initialized from the 2.2.12 server, and completes without 
> any other errors.
> 
> What causes this, and is it anything to worry about?

It's a nuisance bug.  There is no mupdate to kick on the backend, unless it's a unified config.

:wes