Migrando Exchange 2010 a Zarafa, parte 4

Ahora, editamos la parte de Ldap, haciendo:

root@zeus:/etc/zarafa# cp ldap.openldap.cfg ldap.cfg

Cambiamos :
nano ldap.cfg

##############################################################
# LDAP/ACTIVE DIRECTORY USER PLUGIN SETTINGS
#
# Any of these directives that are required, are only required if the
# userplugin parameter is set to ldap.
# LDAP host name/IP address
# Optional, default = localhost
ldap_host = la.ip.de.mi.ldap
# LDAP port
# Optional, default = 389
# Use 636 for ldaps
ldap_port = 389
# LDAP protocol
# Optional, default = ldap
# use ‘ldaps’ for SSL encryption. Make sure /etc/ldap/ldap.conf is
# configured correctly with TLS_CACERT
ldap_protocol = ldap
# The DN of the user to bind as for normal operations (not used for
# authentication if ldap_authentication_method is set to «bind»
# Optional, default = empty (anonymous bind)
# The userPassword attribute must be readable for this user if the
# ldap_authentication_method option is set to password.
ldap_bind_user = cn=admin,dc=craem,dc=net
# LDAP bind password
# Optional, default = empty (no password)
ldap_bind_passwd = password_ldap_user
# The timeout for network operations in seconds
ldap_network_timeout = 30
# When an object (user/group/company) is changed, this attribute will also change:
# Active directory: uSNChanged
# LDAP: modifyTimestamp
ldap_last_modification_attribute = modifyTimestamp
#########
# Object settings
# Top level search base, every object should be available under this tree
ldap_search_base = dc=craem,dc=net
# attribute name which is/(should: was) used in ldap_user_search_filter
ldap_object_type_attribute = objectClass
ldap_user_type_attribute_value = posixAccount
ldap_group_type_attribute_value = posixGroup
ldap_contact_type_attribute_value = zarafa-contact
ldap_company_type_attribute_value = organizationalUnit
ldap_addresslist_type_attribute_value = zarafa-addresslist
ldap_dynamicgroup_type_attribute_value = zarafa-dynamicgroup

y para manejar las quotas de almacenamiento:
should also receive a warning mail when a user exceeds his quota.
ldap_quota_userwarning_recipients_attribute = zarafaQuotaUserWarningRecipients
# Optional, default = text
# Active directory: dn
# LDAP: text
ldap_quota_userwarning_recipients_attribute_type = text
# Optional, default empty
ldap_quota_userwarning_recipients_relation_attribute =
# Optional
# The attribute which indicates which users should receive a warning mail
# when a company exceeds his quota.
ldap_quota_companywarning_recipients_attribute = zarafaQuotaCompanyWarningRecipients
# Optional, default = text
# Active directory: dn
# LDAP: text
ldap_quota_companywarning_recipients_attribute_type = text
# Optional, default empty
ldap_quota_companywarning_recipients_relation_attribute =
# Whether to override the system wide quota settings
ldap_quotaoverride_attribute = zarafaQuotaOverride
ldap_warnquota_attribute = zarafaQuotaWarn
ldap_softquota_attribute = zarafaQuotaSoft
ldap_hardquota_attribute = zarafaQuotaHard


# Whether to override the system wide quota settings for all users within the company
ldap_userdefault_quotaoverride_attribute = zarafaUserDefaultQuotaOverride
ldap_userdefault_warnquota_attribute = zarafaUserDefaultQuotaWarn
ldap_userdefault_softquota_attribute = zarafaUserDefaultQuotaSoft
ldap_userdefault_hardquota_attribute = zarafaUserDefaultQuotaHard
# Mapping from the quota attributes to a number of bytes. Qmail-LDAP
# schema uses bytes (1), ADS uses kilobytes (1024*1024).
ldap_quota_multiplier = 1

Aplicamos los cambios y iniciamos zarafa
root@zeus#/etc/init.d/zarafa-server start
Ahora modificamos los usuarios de ldap para que sean usuarios de zarafa, añadiendo los siguientes atributos:
object-Class: zarafa-user
Y modificando:

zarafaAccount = 1
zarafaAdmin = 1

ZarafaAdmin=1 será el usuario con derecho de acceso a todos los buzones, importante para la migración. zarafaAccount=1, indica que este usuario es de zarafa.
Añadimos las direcciones de email, en el campo email, que pueden ser, de 1 a N.
Una vez modificados todos los usuario implicados, consultamos desde la lí­nea de comandos los usuarios de zarafa:

root@zeus:/etc/zarafa# zarafa-admin -l
User list for Default(9):
Username Fullname Homeserver
—————————————————-
SYSTEM SYSTEM Zarafa
pepito Pepito
manolito Manolito
poseidon Poseidon
zeus Zeus
andromeda Andromeda
openfire openfire
cepheus Cepheus
info info

Si no nos sale la lista de usuarios, algo hemos hecho mal y toca revisar la configuración.
Antes de crear los buzones, configuramos correctamente el idioma, para evitar sorpresas y cambios posteriores en el idioma de los buzones. Nos vamos al directorio:
/etc/zarafa/userscripts/createuser.d
y editamos el fichero 00createstore y lo dejamos tal que:

#! /bin/sh
# Create a Zarafa user for an already existing external user. Create
# and initialize the user’s stores.
PATH=$PATH:/sbin:/usr/local/sbin:/usr/sbin
# The ZARAFA_USER variable from the server will always be in UTF-8
# format. The –utf8 option must be set before this value is used,
# since the current locale isn’t necessarily UTF-8.
zarafa-admin –create-store username –lang es_ES.UTF-8
#zarafa-admin –utf8 –create-store «${ZARAFA_USER}» –lang «${ZARAFA_LANG}»

Ahora creamos los buzones:

root@zeus#zarafa-admin –create-store pepito
…..

Y así­ con todos los buzones