Quote:
Originally Posted by adeelarifbhatti  Well, Thanks but any explanation of the following.
--authuser1 $sunproxyauthuser1 |
It is described here.
Specifying Administrator Access to the Message Store - Sun Java Communications Suite - wikis.sun.com
1. from the sun messaging server command line, run:
Code:
configutil -o store.admins
2. Add to the list of admins, preserving any values from step 1:
Code:
configutil -o store.admins -v "admin,jnorton,frankf,ted"
3. Run an ldap search to locate service admins. This is sun's directory server, not zimbras, openldap server.
Code:
ldapsearch -D 'cn=directory manager' ... -b 'dc=host,dc=com' 'cn=Service Administrators' dn
4. Ldapmodify the dn from step three, to include the dn of the admin from step 2.
Code:
ldapmodify ....
dn: cn=Service Administrators, ou=Groups, dc=host,dc=com
changetype: modify
add: uniqueMember
uniqueMember: uid=ted, ou=accounting, dc=host,dc=com
5. ldapmodify the dn of the new admin to include the service admin of value from step 3
Code:
ldapmodify ....
dn: uid=ted, ou=accounting, dc=host,dc=com
changetype: modify
add: memberOf
memberOf: cn=Service Administrators, ou=Groups, dc=host,dc=com
6. restart sun's messaging server imapd process.
The zimbra side is more simple.
Quote:
|
--authuser2 $zimbraproxyauthuser2
|
From the command line on your zimbra server, run:
That is the list of users that can auth on behalf of others to perform tasks like imapsync. One might be "admin".
Using the examples above, I would use "ted" on the sun side and maybe "admin" from the zimbra side to perform the syncs, like:
Code:
$cmd = "/usr/bin/imapsync --buffersize 8192000 --nosyncacls " .
"--subscribe --syncinternaldates --host1 $oldserver " .
"--user1 $user1 --authuser1 ted --authmech1 PLAIN " .
"--passfile1 $passfile1 --port1 143 --host2 $newserver " .
"--user2 $user2 --authuser2 admin --authmech2 PLAIN " .
"--passfile2 $passfile2 --port2 143 --noauthmd5"; The $passfile1 and $passfile2 should point to a file containing the password for authuser1 and authuser2.