LDAP settings

Discuss the Scalix Server software

Moderators: ScalixSupport, admin

bluemike
Posts: 202
Joined: Fri Oct 28, 2005 1:30 pm
Location: Everett,WA
Contact:

LDAP settings

Postby bluemike » Wed Apr 26, 2006 1:26 am

I am attempting to access my valid email addresses via an outside application. In order to do this, it asks for a bunch of LDAP info. Some of the basic stuff (like the server name) I know, but some of this is WAY over my head. Could someone help me out?

LDAP Server: (my server IP, duh!)
LDAP Port: (389, right?)
LDAP/Exchange Username: (I assume just a valid user@domain.com?)
LDAP/Exchange Password: (valid pw for above account)
LDAP Filter: (no idea at all)
LDAP Search Base: (again, not a clue)
LDAP UID: (user ID maybe? Not sure)
LDAP Primary Email Alias: (unknown)
Canary Email: (any valid email address, right?)
Valid Email (for testing): (I know this one!)

Thanks in advance!

ScalixSupport
Scalix
Scalix
Posts: 5503
Joined: Thu Mar 25, 2004 8:15 pm

Postby ScalixSupport » Wed Apr 26, 2006 6:06 pm

Hi Mike,

The documentation for the "outside application" should provide some information for exactly what they want in each field. I'm assuming the LDAP username/password is for authenticated binds. I don't know if the application has to do authenticated binds, but if so you can use the sxadmin accout or some other user that you've created. The syntax would be: "cn=sxadmin, o=Scalix" and the password would be the password.

The LDAP filter shouldn't be needed, the Search Base is o=Scalix, The LDAP UID could be omLocalUniqueId, the omGlobalUniqueId or the omUlAuthid (the latter requires an authenticated bind to extract). I don't know about the others, what does the application docs say?

Thanks,
Rachel

bluemike
Posts: 202
Joined: Fri Oct 28, 2005 1:30 pm
Location: Everett,WA
Contact:

Postby bluemike » Thu Apr 27, 2006 2:23 am

First of all, let me clarify... I meant to write appliance, not application. It's one of those Barracude spam firewalls.

Regarding LDAP authentication, and what they call 'Exchange Accelerator', the documentation simply says to 'refer to the mail server documentation' when filling in these fields.

This may just be a non-issue, as I don't really know what the benefit of LDAP auth would be.....



Anyway, for what it's worth, I contacted their tech support for more information, and here was their response (most of this stuff is way beyond my skillset):

Code: Select all

My apologies for not getting back to you in a timely fashion.  From our efforts yesterday, it appears an LDAP configuration was difficult w/ your organisations' IMail server.  Attached below are the mix-and-match options available for an LDAP configuration.  Feel free to try these while you continue in-house tests:

"Communigate / Linux                            username@domain.com

Exchange 2000/2000                            username@internaldomain.com

Exchange 2003/2003                            required full definition of the name listing containers,path,etc. barracuda@bec.bandera-ec.com (fully qualified)

Exchange 5.5/NT 4                              cn=username

Lotus Notes     username@domain.com  *may need to add this filter:

                                                            '(|(mail=${recipient_email})(cn=${recipient_local_part})(shortname=${recipient_local_part})(fullname=${recipient_local_part}))'



Exchange 5.5/2000                               cn=username@domain.com or cn=username(worked with simple account)



Imail/2000                                            cn=username,o=domain.com



Domino 6.5                                          Filter: (|(Shortname=${recipient_email})(shortname=${recipient_local_part}))

                                                            UID: Shortname



Novell Groupwise                                 username = cn=username.o=gsy

                                                            search base = o=gsyhosted

                                                            filter = (|(cn=${recipient_email}))

                                                            plus you might  have to change the mta_ldap_unique_attr to cn also please add a referrence next to the 10024 and 10025 telnet lines about clam being on 3310

                                                            http://www.novell.com/coolsolutions/tip/11837.html



Change default Filter:                            emacs recipient_verify.cf

                                                            default_filter = (|(proxyaddresses=smtp\$__RECIPIENT__)(proxyaddresses=smtp:__RECIPIENT__))
"

ScalixSupport
Scalix
Scalix
Posts: 5503
Joined: Thu Mar 25, 2004 8:15 pm

Postby ScalixSupport » Fri Apr 28, 2006 3:49 pm

Hi Mike,

Based on you've posted, you should be able to use the values I provided in my previous posting.

Thanks,
Rachel


Return to “Scalix Server”



Who is online

Users browsing this forum: No registered users and 11 guests