Quote:
Originally Posted by adeelarifbhatti THX,
Did you automate the script, if yes then how did you manage the usernames and password of old mail server and for the new mail server in the script. |
It was fairly automated. A few perl scripts were used to create the zimbra accounts, added aliases, transfer the personal address book entries (PAB) and imapsync their email.
We are using an external ldap server for authentication so we did not need to transfer their password into zimbra and created the account like:
Code:
zmprov ca someuser@mydomain.com "" givenname "firstName" sn "lastName" cn "firstName lastName" displayName "firstName lastName"
If you are importing the passwords into zimbra's openldap server, then maybe run ldapsearch on sun's directory server and retrieve the 'userpassword' value for the user and include the result in the zmprov command. You should also be able to grab the cn, sn, mail, mailalternateaddress, etc values from sun's directory server and use it to build the appropriate zmprov command.
Code:
zmprov ca someuser@mydomain.com {ssha}sdkfgjksdfjksajfdskaf givenname "firstName" sn "lastName" cn "firstName lastName" displayName "firstName lastName"
zmprov aaa someuser@mydomain.com theiralias@mydomain.com On the sun side, a "message store administrator" was established. Store admins can have imap proxy rights to individual accounts. You will not need to know the user's password to transfer their email into zimbra. Same is true on the zimbra side.
We did something similar to this:
Code:
foreach $user (@listofusers){
$user1 = $user2 = $user;
$cmd = "/usr/bin/imapsync --buffersize 8192000 --nosyncacls " .
"--subscribe --syncinternaldates --host1 $oldserver " .
"--user1 $user1 --authuser1 $sunproxyauthuser1 --authmech1 PLAIN " .
"--passfile1 $passfile1 --port1 143 --host2 $newserver " .
"--user2 $user2 --authuser2 $zimbraproxyauthuser2 --authmech2 PLAIN " .
"--passfile2 $passfile2 --port2 143 --noauthmd5";
system ($cmd);
}