OMLDAPSYNC ignoring search filter in sync.cfg?

[patrickmcshane]

Rachel,

I tried the "omdelent -e" and the rerun of "omldapsync -u" but to no avail.

When I ran omdelent it deleted the entry from the Scalix directory as expected.

When I then reran "omldapsync -u dslx01p" the entries that omldapsync sees in our OpenLDAP are not modified or updated in any way.

Are we at the point where we call this a bug either in "omldapsync" and related objects?

We REALLY need this to work as it was one of the requirements we had when the purchase was made and we ARE using a vanilla (and I do mean vanilla) Redhat EL 4 ES x86_64 installation.

Please advise or escalate as you see fit.

Thanks,
Pat

[patrickmcshane]

Rachel,

I ended up having to completely delete the two test Scalix users and then bring them back in with

Code: Select all

omldapsync -i dslx01p

in order to do what you wanted.

The command:

Code: Select all

omdelent -e "cn=Patrick Mcshane"

processed normally and the entry was deleted.

The command:

Code: Select all

omldapsync -u dslx01p

Showed the following output:

Code: Select all

2006-03-30 10:59:02 STATUS: Interactive for dslx01p started ########
Common tasks menu for syncid dslx01p
0. Display this menu
1. Configure the LDAP dir sync settings
2. Force a complete (re)load of the directory
3. Update the directory after some changes
4. Accept previous error and update directory
5. Skip previous error and update directory
6. Update the directory and prompt for error
7. Modify all sync records from the directory
8. Delete all sync records in the directory
d. Toggle debug mode from current setting <0>
n. Toggle test mode from current setting <>
q. Quit
INPUT: Please enter an option (0):2
2006-03-30 10:59:04 STATUS: LDAP dir sync import dslx01p started ###############
2006-03-30 10:59:04 STATUS: load all records from dslx01p.be.sddc1.luthresearch.com ...
2006-03-30 10:59:05 INFO: work dir is /var/opt/scalix/ldapsync/dslx01p/import
2006-03-30 10:59:05 STATUS: search source directory on dslx01p.be.sddc1.luthresearch.com ...
2006-03-30 10:59:05 INFO: search base is dc=luthresearch,dc=com
2006-03-30 10:59:05 INFO: ... 2 entries to check
2006-03-30 10:59:05 STATUS: find delta and perform mapping ...
2006-03-30 10:59:05 INFO: ... 0 entries to delete
2006-03-30 10:59:05 INFO: ... 2 entries to add
2006-03-30 10:59:05 INFO: ... 0 entries to modify
2006-03-30 10:59:05 STATUS: apply membdelete data against Scalix ...
2006-03-30 10:59:05 INFO: ... 0 entries passed for member.curr
2006-03-30 10:59:05 INFO: ... 0 entries failed for member.curr
2006-03-30 10:59:05 INFO: ... 0 entries warned for member.curr
2006-03-30 10:59:05 STATUS: apply delete data against Scalix ...
2006-03-30 10:59:05 INFO: ... 0 entries passed for delete.curr
2006-03-30 10:59:05 INFO: ... 0 entries failed for delete.curr
2006-03-30 10:59:05 INFO: ... 0 entries warned for delete.curr
2006-03-30 10:59:05 STATUS: apply add data against Scalix ...
2006-03-30 10:59:07 INFO: ... 2 entries passed for add.curr
2006-03-30 10:59:07 INFO: ... 0 entries failed for add.curr
2006-03-30 10:59:07 INFO: ... 0 entries warned for add.curr
2006-03-30 10:59:07 STATUS: apply limit data against Scalix ...
2006-03-30 10:59:07 INFO: ... 0 entries passed for add.curr
2006-03-30 10:59:07 INFO: ... 0 entries failed for add.curr
2006-03-30 10:59:08 INFO: ... 0 entries warned for add.curr
2006-03-30 10:59:08 STATUS: apply modify data against Scalix ...
2006-03-30 10:59:08 INFO: ... 0 entries passed for modify.curr
2006-03-30 10:59:08 INFO: ... 0 entries failed for modify.curr
2006-03-30 10:59:08 INFO: ... 0 entries warned for modify.curr
2006-03-30 10:59:08 STATUS: apply limit data against Scalix ...
2006-03-30 10:59:08 INFO: ... 0 entries passed for modify.curr
2006-03-30 10:59:08 INFO: ... 0 entries failed for modify.curr
2006-03-30 10:59:08 INFO: ... 0 entries warned for modify.curr
2006-03-30 10:59:08 STATUS: apply membadd data against Scalix ...
2006-03-30 10:59:08 INFO: ... 0 entries passed for member.curr
2006-03-30 10:59:08 INFO: ... 0 entries failed for member.curr
2006-03-30 10:59:08 INFO: ... 0 entries warned for member.curr
2006-03-30 10:59:08 STATUS: apply membmodify data against Scalix ...
2006-03-30 10:59:08 INFO: ... 0 entries passed for member.curr
2006-03-30 10:59:08 INFO: ... 0 entries failed for member.curr
2006-03-30 10:59:08 INFO: ... 0 entries warned for member.curr
2006-03-30 10:59:08 STATUS: LDAP dir sync import dslx01p completed #############
2006-03-30 10:59:08 STATUS: LDAP dir sync export dslx01p started ###############
2006-03-30 10:59:08 STATUS: load all records from mxlx01p.fe.sddc1.luthresearch.com ...
2006-03-30 10:59:08 INFO: agreement type 13 only supports import operation
2006-03-30 10:59:08 STATUS: LDAP dir sync export dslx01p completed #############
Common tasks menu for syncid dslx01p
0. Display this menu
1. Configure the LDAP dir sync settings
2. Force a complete (re)load of the directory
3. Update the directory after some changes
4. Accept previous error and update directory
5. Skip previous error and update directory
6. Update the directory and prompt for error
7. Modify all sync records from the directory
8. Delete all sync records in the directory
d. Toggle debug mode from current setting <0>
n. Toggle test mode from current setting <>
q. Quit
INPUT: Please enter an option (0):3
2006-03-30 11:05:01 STATUS: LDAP dir sync import dslx01p started ###############
2006-03-30 11:05:02 INFO: work dir is /var/opt/scalix/ldapsync/dslx01p/import
2006-03-30 11:05:02 STATUS: search source directory on dslx01p.be.sddc1.luthresearch.com ...
2006-03-30 11:05:02 INFO: search base is dc=luthresearch,dc=com
2006-03-30 11:05:02 INFO: ... 2 entries to check
2006-03-30 11:05:02 STATUS: find delta and perform mapping ...
2006-03-30 11:05:02 INFO: ... 0 entries to delete
2006-03-30 11:05:02 INFO: ... 0 entries to add
2006-03-30 11:05:02 INFO: ... 0 entries to modify
2006-03-30 11:05:02 STATUS: apply membdelete data against Scalix ...
2006-03-30 11:05:02 INFO: ... 0 entries passed for member.curr
2006-03-30 11:05:02 INFO: ... 0 entries failed for member.curr
2006-03-30 11:05:02 INFO: ... 0 entries warned for member.curr
2006-03-30 11:05:02 STATUS: apply delete data against Scalix ...
2006-03-30 11:05:02 INFO: ... 0 entries passed for delete.curr
2006-03-30 11:05:02 INFO: ... 0 entries failed for delete.curr
2006-03-30 11:05:02 INFO: ... 0 entries warned for delete.curr
2006-03-30 11:05:02 STATUS: apply add data against Scalix ...
2006-03-30 11:05:03 INFO: ... 0 entries passed for add.curr
2006-03-30 11:05:03 INFO: ... 0 entries failed for add.curr
2006-03-30 11:05:03 INFO: ... 0 entries warned for add.curr
2006-03-30 11:05:03 STATUS: apply limit data against Scalix ...
2006-03-30 11:05:03 INFO: ... 0 entries passed for add.curr
2006-03-30 11:05:03 INFO: ... 0 entries failed for add.curr
2006-03-30 11:05:03 INFO: ... 0 entries warned for add.curr
2006-03-30 11:05:03 STATUS: apply modify data against Scalix ...
2006-03-30 11:05:03 INFO: ... 0 entries passed for modify.curr
2006-03-30 11:05:03 INFO: ... 0 entries failed for modify.curr
2006-03-30 11:05:03 INFO: ... 0 entries warned for modify.curr
2006-03-30 11:05:03 STATUS: apply limit data against Scalix ...
2006-03-30 11:05:03 INFO: ... 0 entries passed for modify.curr
2006-03-30 11:05:03 INFO: ... 0 entries failed for modify.curr
2006-03-30 11:05:03 INFO: ... 0 entries warned for modify.curr
2006-03-30 11:05:03 STATUS: apply membadd data against Scalix ...
2006-03-30 11:05:03 INFO: ... 0 entries passed for member.curr
2006-03-30 11:05:03 INFO: ... 0 entries failed for member.curr
2006-03-30 11:05:03 INFO: ... 0 entries warned for member.curr
2006-03-30 11:05:03 STATUS: apply membmodify data against Scalix ...
2006-03-30 11:05:03 INFO: ... 0 entries passed for member.curr
2006-03-30 11:05:03 INFO: ... 0 entries failed for member.curr
2006-03-30 11:05:03 INFO: ... 0 entries warned for member.curr
2006-03-30 11:05:03 STATUS: LDAP dir sync import dslx01p completed #############
2006-03-30 11:05:03 STATUS: LDAP dir sync export dslx01p started ###############
2006-03-30 11:05:03 INFO: agreement type 13 only supports import operation
2006-03-30 11:05:03 STATUS: LDAP dir sync export dslx01p completed #############
Common tasks menu for syncid dslx01p
0. Display this menu
1. Configure the LDAP dir sync settings
2. Force a complete (re)load of the directory
3. Update the directory after some changes
4. Accept previous error and update directory
5. Skip previous error and update directory
6. Update the directory and prompt for error
7. Modify all sync records from the directory
8. Delete all sync records in the directory
d. Toggle debug mode from current setting <0>
n. Toggle test mode from current setting <>
q. Quit
INPUT: Please enter an option (0):


Are we at the point where we escalate this and call it a bug in somewhere in Scalix?

Thanks,
Pat

[ScalixSupport]

Hi Patrick,

Okay, I believe I've found the problem. I guess you've been working with one of our other engineers here as well and he had a copy of your sync.cfg file. I found a couple of problems with your file. After correcting those, everything works fine. First, it looks like you correctly replaced these values:

Code: Select all

#${EX_SCALIX_MAILBOX}|omMailbox|*|*
#${EX_SCALIX_MAILNODE}|omMailnode|*|*
#${EX_SCALIX_MSGLANG}|UL-IL|*|*
#${EX_SCALIX_ADMIN}|ADMIN|*|*
#${EX_SCALIX_MBOXADMIN}|MBOXADMIN|*|*


with these values:

Code: Select all

exScalixObject|omMailbox|*|*
exScalixMailnode|omMailnode|*|*
exScalixMsglang|UL-IL|*|*
exScalixAdmin|ADMIN|*|*
exScalixMboxadmin|MBOXADMIN|*|*

However, you didn't replace:

Code: Select all

EX_ATTR=${EX_SCALIX_MAILBOX} ${EX_SCALIX_MAILNODE} ${EX_SCALIX_MSGLANG} ${EX_SCALIX_ADMIN} ${EX_SCALIX_MBOXADMIN} member dn uid objectClass displayName sn givenname initials mail EmailAliases entryUUID cn facsimileTelephoneNumber homephone street st telephoneNumber title co company departmentNumber description l mobile pager physicalDeliveryOfficeName postalCode


with these values:

Code: Select all

EX_ATTR=exScalixObject exScalixMailnode exScalixMsglang exScalixAdmin exScalixMboxadmin member dn uid objectClass displayName sn givenname initials mail entryUUID cn facsimileTelephoneNumber homephone street st telephoneNumber title co company departmentNumber description l mobile pager physicalDeliveryOfficeName postalCode


Second, you've changed:

Code: Select all

IM_OMADDRESS=/internet

to be:

Code: Select all

IM_OMADDRESS=mxlx01p,luthresearch

Please change that back. There are few other things which I don't believe are causing you a problem such as uncommenting:

Code: Select all

IM_LOGON=Import Admin
IM_PASS=xxxxxxx


which should be commented out for agreement 13. And lastly, you have:

Code: Select all

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

which I didn't test, so I can't confirm that works. You may want to clean up the entries from your directory again, then move the sync.cfg into another subdirectory under ldapsync (let's say dslx01p-2), edit the file, then do:

Code: Select all

omldapsync -u dslx01p-2

Regarding which LDAP Front-End to use, we don't really have any recommended products on that end. Generally customers have some product that they want to use for directory management and that's why they use LDAP Sync in first place. Otherwise, they just use the Scalix directory management tools.

Regarding some of the other LDAP questions you have, I'll let the Deployment Engineer work with you on that because some of it depends on how frequently you make directory changes.

Thanks,
Rachel

[patrickmcshane]

Rachel,

I must now take you out to dinner!!!! That worked. I guess I took for granted that the variable substitution would be work when omldapsync processed the file. NOT a good assuption apparently.

The literal values worked.

Do you happen to have the code snippet available for the Redhat Linux EL 4 ES /etc/mail/sendmail.cf file available and if so could you reply with it?

Best regards and thanks again!!!
Pat

[ScalixSupport]

Hi Pat,

I'm glad it's working. I'm not sure what you mean by the code snippet for the sendmail.cf file. Do you mean some type of milter code? Let me know.

Thanks,
Rachel

[patrickmcshane]

Rachel,

Greg Orr of Scalix mentioned that a small modification was needed in our Redhat EL 4 ES /etc/mail/sendmail.cf file in order for Scalix to be able to benefit from Spamassassin and ClamAV. I am I barking up the wrong tree? He indicated that we should refrain from using the make file with sendmail.mc and that we should manually edit sendmail.cf.

Thanks,
Pat

[ScalixSupport]

Hi Pat,

Ah yes, the Spamassassin and ClamAV technotes. You can find both of those in the Scalix Knowledgebase - http://www.scalix.com/support/knowledgebase.html . Included in the Spamassassin technote is the milter info for hooking the spamass-milter to sendmail. ClamAV does not specifically interface with sendmail, but rather hooks into the Scalix Service Router (you'll see that in the tech note).

Thanks,
Rachel