Ken,

It works beautifully - truly poetry in motion (or maybe I'm slightly
over-reacting out of relief ;) ).

Thanks again!

Scott

>Sorry this took so long, but I've been out of town the last two days.
>Here is a patch against cyrus-imapd-2.0.9.  Consider it beta.
>
>1. Apply this patch in the imap/ directory of the distribution
>2. run config.status from the toplevel directory so that imap/Makefile
>gets rebuilt
>3. run make from either the toplevel or the imap/ directory
>
>NOTE:  I put this patch together from the 'user-rename' branch in CVS
>and tested it *very* quickly.  However I'm pretty confident that it will
>work without any problems.
>
>If you want to be really safe, use the 'user-rename' branch from CVS
>(that's what I've been using and developing on).  This branch also
>contains all of the changes from the trunk that will be in 2.0.10.
>
>As long as you're using cyrusdb_flat for seen state, subscriptions and
>quotas, you shouldn't have any problems if someone is accessing the
>folders when they are renamed.  But just to play it safe, make sure that
>the user that you are renaming is not logged into the server when you
>rename him/her.  To help prevent this, change their login name via
>whatever SASL mechanism you're using first, so they can't log in using
>their old login.
>
>When you rename the user, the seen state, quota, subscriptions and ACLs
>should all be renamed as well.  The only thing that won't happen is the
>renaming of any sieve scripts (this is outside of the scope of IMAP -- I
>might modify cyradm to handle this however).
>
>Let me know how it goes,
>Ken

Reply via email to