On Thu, 2002-11-21 at 19:13, Dick Roth wrote:
Chris--
I don't know what kind of server, except that it is not Exchange (the
server is unix-based).
hm, I'm going to see about crafting some checks to determine server
types (if it's possible in all cases, I'm only sure it's possible for
Hi All--
With hope in my heart, I tried this edit to the .xml file but with no
joy. What to do!! I use LDAP lookups often during the day and now have
to use gq to look up addresses and type them into my outgoing message.
This function worked perfectly in 1.0.8. But now, frustration.
Dick
On Thu, 2002-11-21 at 15:33, Dick Roth wrote:
Hi All--
With hope in my heart, I tried this edit to the .xml file but with no
joy. What to do!! I use LDAP lookups often during the day and now have
to use gq to look up addresses and type them into my outgoing message.
This function worked
Chris--
I don't know what kind of server, except that it is not Exchange (the
server is unix-based). Here is the .xml:
?xml version=1.0?
addressbooks
contactserver
nameLincoln Directory/name
description/
port389/port
hostllph/host
rootdno=mit_lincoln_laboratory/rootdn
On Tue, 2002-11-19 at 22:34, Dieter Kluenter wrote:
Hello,
Cormac Long [EMAIL PROTECTED] writes:
Does anyone have evo 1.2 working with MS Exchange LDAP server?.. if so can you
provide details of the configuration.. bind, scope etc
I've monitored evo and gq using Ethereal..
Results
Got it working,
edited evolution/addressbook-sources.xml which shows the config for the LDAP server
I changed the
scopebase/scope
to scopesub/scope
and all worked OK.
Of course if you edit this in the GUI, the drop down combo shows only one and base and if you change it, you lose your
On Wed, 2002-11-20 at 06:59, Cormac Long wrote:
Got it working,
edited evolution/addressbook-sources.xml which shows the config for
the LDAP server
I changed the
scopebase/scope
to scopesub/scope
and all worked OK.
Of course if you edit this in the GUI, the drop down
i'm connecting to an older exchange 5.5 server for ldap contacts, and it
no longer works with evo 1.2. it worked perfect with 1.0.8. i think it
has something to do with the fact that its an ldap v2 server, and not a
v3. i have no problems connecting to our newer iplanet directory.
On Wed,
On Wed, 2002-11-20 at 13:55, steve j. kondik wrote:
i'm connecting to an older exchange 5.5 server for ldap contacts, and it
no longer works with evo 1.2. it worked perfect with 1.0.8. i think it
has something to do with the fact that its an ldap v2 server, and not a
v3. i have no problems
Does anyone have evo 1.2 working with MS Exchange LDAP server?.. if so can you provide details of the configuration.. bind, scope etc
I've monitored evo and gq using Ethereal..
Results from using gq (which works)
firstly, it binds but with simple authentication and dn and password set to
ldapsearch -h 10.1.1.30 -x -s sub
'(|(displayName=dlewis*)(name=dlewis*)(mail=dlewis*))'
returns the CORRECT info for user whose info begins with
dlew*
With 1.2 evolution trying to authenticate with dn set to cn=MY-NT-DOMAIN
USERNAME and give my password, no query comes back, all I get s
On Tue, 2002-11-19 at 14:12, Cormac Long wrote:
Does anyone have evo 1.2 working with MS Exchange LDAP server?.. if so
can you provide details of the configuration.. bind, scope etc
I've monitored evo and gq using Ethereal..
Results from using gq (which works)
firstly, it binds but with
Hello,
Cormac Long [EMAIL PROTECTED] writes:
Does anyone have evo 1.2 working with MS Exchange LDAP server?.. if so can you
provide details of the configuration.. bind, scope etc
I've monitored evo and gq using Ethereal..
Results from using gq (which works)
firstly, it binds but with simple
13 matches
Mail list logo
