Not all GAL entries in Outlook!

[Lionel]

Hi,

I'm currently testing Outlook connector. It works really great!!

But, I'm here because I have a little problem with GAL access from Outlook.
In fact, the Zimbra GAL from Outlook is incomplete, only the x first entries are displayed (I don't know how many).
This is a little bit annoying because I can't add a shared calendar from a person that isn't is this list. Also, I can't find a GAL contact not in the list.

The problem is that Outlook doesn't search directly into Zimbra GAL on Zimbra server (maybe for offline access), but in a truncated GAL copy. I can't find where to configure the limit!

Am I the only person with this problem?
Is it possible to correct it?

Thanks!
Lionel

Zimbra Network Edition 4.5.6 on CentOS 5
Outlook connector 4.5.6

[Klug]

Bonjour & bienvenue.

You can force a GAL sync within Outlook : go in the "Envoyer/Recevoir" menu and select "Mettre à jour la liste d'adresse globale".

Once you've synced, can you try a search ?

[Lionel]

Originally Posted by Klug

Bonjour & bienvenue.

You can force a GAL sync within Outlook : go in the "Envoyer/Recevoir" menu and select "Mettre à jour la liste d'adresse globale".

Once you've synced, can you try a search ?

Bonjour!!

Thank you for your answer!

I've already tried this action with no success... I did it again, same problem.
A search only works if a contact is in the truncated list.

Lionel

[Klug]

Bon...

My own GAL is short (2 users and a couple aliases), I can not do some extended testing.

Are you using an internal or external GAL ?

Did you try to search for "." (that should list all users in GAL) ?

Did you try the same tests from the WebUI (just to be sure the "bug" is in the ZCO) ?

[sam]

We have customers using ZCO with GALs containing 30K+ entries synchronizing properly. We fully expect all items be be downloaded and available.

What version of the connector/server are you using?
How is the GAL configured on the server side?

To diagnose:
Enable ZCO logging, restart outlook, refresh the gal, shutdown outlook and attach the logs.

[Lionel]

Hi,

My GAL is more important!
I'm using an external GAL (linked to an external LDAP server).

From WebUI, it works very well, I can see all the GAL...

Are you sure for "."? In outlook??

Thanks!
Lionel

[Lionel]

Originally Posted by sam

We have customers using ZCO with GALs containing 30K+ entries synchronizing properly. We fully expect all items be be downloaded and available.

What version of the connector/server are you using?
How is the GAL configured on the server side?

To diagnose:
Enable ZCO logging, restart outlook, refresh the gal, shutdown outlook and attach the logs.

I've tested with version 4.5.288 et 4.5.301 (found in Pre-download section on Zimbra portal). Same problem with both versions.

On server side, the GAL is connected to an external LDAP server.
- LAG mode : external
- Max results : I've just tried to change this value to 10000, and I don't have more entries in Outlook GAL...

You can find ZCO log in attachment...

Thanks
Lionel

[Klug]

The issue relies in the "external GAL", I've seen it elsewhere yesterday.

Here for example, someone with the same problem (with Zimbra 4.5.3) : gal search issue

Lionel, what external GAL are you using (LDAP, AD, stg else) ?
What are the search/filter parameters you've used while setting up the external GAL ?

[Lionel]

Originally Posted by Klug

The issue relies in the "external GAL", I've seen it elsewhere yesterday.

Here for example, someone with the same problem (with Zimbra 4.5.3) : gal search issue

Lionel, what external GAL are you using (LDAP, AD, stg else) ?
What are the search/filter parameters you've used while setting up the external GAL ?

I'm using LDAP external GAL.

Here my GAL config :
LAG mode: Externe
Max results : 10000 (an unsuccessful test )
Server type : LDAP
LDAP filter:
(&(|(cn=*%s*)(sn=*%s*)(givenName=*%s*)(mail=*%s* )) (objectclass=inetOrgPerson)))
Autocomplete :
(|(cn=%s*)(sn=%s*)(givenName=%s*)(mail=%s*))

[sam]

Just looked at your ZCO log and I don't see the SyncGalResponse. You must enable http tracing in the log, then run through the steps and post a new log.