On Tue, Oct 02, 2001 at 11:01:46AM -0400, djinn wrote: > Obviously, three things need to happen: > 1) saslpasswd username/password
saslpasswd has some support for being called from other programs. So that shouldn't be too bad. You might want to write a little setuid script to protect the database from getting entries whose username/passwords can not be verified with the old username/password. That way, if there is a weakness in one of your CGI scripts, someone can't take over your customer's accounts and start spamming or doing other nasty things. It shouldnt require setuid root, just some user who has access to write to the back end database for saslpasswd. > 2) cyradm cm user.username > 3) transfer of mail/mailboxes from old server to new According to the imail web page, it supports imap. There are a bunch of imap access libraries for perl. Mail::IMAPClient has an example program copy_folder.pl which will copy imap mailboxes between servers, including creating the mailbox. It could probably be modified pretty quickly to do what you want. -- Andrew Eason System Administrator [EMAIL PROTECTED]
