> Am Mittwoch, den 04.08.2010, 11:08 +0100 schrieb Simon Beale: > >> While that would work, and it's something that I could do for myself, >> it >> doesn't help when I roll out shared folders to all our users, and they >> start using the Outlook/Thunderbird normal delete mechanism, which is >> why >> I need RENAME to work. > > You might try checking http://cyrusimap.web.cmu.edu/ag.html > > <quote> > [RENAME] > RENAME is only interesting in the cross-server case. In this case it > issues a (non-standard) XFER command to the backend that currently hosts > the mailbox, which performs a binary transfer of the mailbox (and in the > case of a user's inbox, their associated seen state and subscription > list) to the new backend. During this time the mailbox is marked as > RESERVED in mupdate, and when it is complete it is activated on the new > server in MUPDATE. The deactivation prevents clients from accessing the > mailbox, and causes mail delivery to temporarily fail. > </quote> Hmm; with that in mind, I've hooked up gdb, and turned on the imap protocol logging on the backends, and run through what it's doing when I send a RENAME to the frontend. It appears that the backend is receiving the RENAME command intact and unchanged, and not any sort of XFER command. And therefore the reason it's returning IMAP_PERMISSION_DENIED is because it's trying to rename to a subfolder of a usermbox that doesn't exist on that backend. Err... anyone any suggestions as to what I need to look at in my configuration? Cheers Simon ---- 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