Scalix Forums

Setting up an omldapsync of an OpenLDAP directory and this directory includes all email addresses assigned to a user.

Can omldapsync be configured to import those addresses into scalix?

If not, how can I script the addition and update of these.

Just to clarify, the OpenLDAP 'mail' attribute holds a users Primary address and the 'EmailAliases' attribute holds all additional addresses, upto 100 in some cases.

anyone?

abnormaliti wrote:anyone?

Running

man omldapsync

will give you some good information to start with. OpenLDAP is supported and yes, you can sync with this. Use agreement # 13 to import meta directory information from OpenLDAP directory to Scalix. This is used to maintain Scalix users from the remote system, including common tasks such as creating mailboxes and maintaining groups. A set of Scalix specific attributes will need to be defined and reserved on the remote system (e.g. mailbox, mailnode, authentication, admin). They should be new remote directory attributes created by extending the schema as detailed in the schema file ~scalix/sys/ldapsync13.schema. Note that read only access of the remote system will be via LDAP, while write only access of the local system will be via Scalix web services. Hope this helps.

Sascha.

I have added the Scalix schema to OpenLDAP and i have the accounts syncing but what i am wanting to do is to also import all of the users additional email addresses from the 'EmailAliases' attribute in OpenLDAP to Scalix.

I have read through the 'man omldapsync' and the ldapsync13.cfg but cannot see how this can be done.

abnormaliti wrote:I have added the Scalix schema to OpenLDAP and i have the accounts syncing but what i am wanting to do is to also import all of the users additional email addresses from the 'EmailAliases' attribute in OpenLDAP to Scalix.

I have read through the 'man omldapsync' and the ldapsync13.cfg but cannot see how this can be done.

Hello,

importing up to 100 aliases will be a challenge as the IA field in our directory is limited to 512 bytes. So whatever fits in that field will define the maximum alias you can get.

That said, is EmailAliases the field that contains the users primary mail address or does that still exists? If it is an additional field and the primary mail address is in the mail attribute, you need to add a mapping in sync.cfg:

mail|INTERNET-ADDR|*,1,512|*
EmailAliases|INTERNET-ADDR|*,1,512|*

If all your mail addresses are stored in EmailAliases, you can simply search and replace the mail attribute with the EmailAliases attribute.

Also, you need to extend the attribute list for the ldap lookup. This is done by adding the attribute EmailAliases to EX_ATTR.

Hope this helps,

Cheers,

Sascha.

The later is correct, by adding;

mail|INTERNET-ADDR|*,1,512|*
EmailAliases|INTERNET-ADDR|*,1,512|*

i was able to import additional addresses, not all due to 512 bytes limit, but now the problem is the order, the 'mail' does not remain as the primary address. so an address from 'EmailAliases' now becomes the primary address and the one visible to the world. anything i can do about that?

also, anyway to increase the 512bytes limit?

abnormaliti wrote:The later is correct, by adding;

mail|INTERNET-ADDR|*,1,512|*
EmailAliases|INTERNET-ADDR|*,1,512|*

i was able to import additional addresses, not all due to 512 bytes limit, but now the problem is the order, the 'mail' does not remain as the primary address. so an address from 'EmailAliases' now becomes the primary address and the one visible to the world. anything i can do about that?

also, anyway to increase the 512bytes limit?

There is no way to overcome the 512 byte limit, sorry.

If you are sufficient in scripting, I would suggest having a look at the omldapsync script and modify in function fn_extract_data the line

omldapsearch \
`if [ "$MY_PAGESIZE" ]; then echo "-P $MY_PAGESIZE"; fi` \
-h "$MY_HOST" \
-p "$MY_PORT" \
-D "$MY_LOGON" \
-w "$MY_PASS" \
-S "$MY_GUID" \
-b "$MY_BASE" \
-L "$LDFORMAT" \
$MY_FILTER \
$MY_ATTR \
>search.curr 2>search.log

and insert some sort of a filter that you can pipe the output thru that changes the order of attributes. Make sure mail is the first one. This is beyond what we can support on the free support forum, our deployment services would be happy to assist you with this.

Cheers,

Sascha.