After some more testing, I found Luma fails to use the attributes that Mozilla Thunderbird’s AB feature expects. So, stuff like a person’s address, which is visible to Luma when I browse my LDAP tree, is not visible to me under Thunderbird or SquirrelMail’s ldapquery plugin.
Not satisified with this, I looked for a few other ways of managing my LDAP based address book. I came across phpldapadmin, which is truly an awesome Web based application. It rocks my world as much as Gallery2 did when I first started using it.
One of the schema layouts it supports is apparently MozillaOrgPerson, which is uniquely suited to work with, yep, Mozilla Thunderbird. Now my address book is nearly guaranteed to have entries added that will be visible in Thunderbird the way I’d expect them, with each person’s primary address listed. I haven’t verified if the SquirrelMail plugin will do the right thing, or be confused by my using this extended schema.
Here’s what MozillaOrgPerson has to say about the matter:
# # mozillaOrgPerson schema v. 0.6.3 # ... objectclass ( 1.3.6.1.4.1.13769.2.2.1 NAME 'mozillaOrgPerson' SUP top AUXILIARY MAY ( sn $ givenName $ cn $ displayName $ mozillaNickname $ title $ telephoneNumber $ facsimileTelephoneNumber $ mobile $ pager $ homePhone $ street $ postalCode $ mozillaPostalAddress2 $ mozillaHomeStreet $ mozillaHomePostalAddress2 $ l $ mozillaHomeLocalityName $ st $ mozillaHomeState $ mozillaHomePostalCode $ c $ mozillaHomeCountryName $ co $ mozillaHomeFriendlyCountryName $ ou $ o $ mail $ mozillaSecondEmail $ mozillaUseHtmlMail $ nsAIMid $ mozillaHomeUrl $ mozillaWorkUrl $ description $ mozillaCustom1 $ mozillaCustom2 $ mozillaCustom3 $ mozillaCustom4 ) ) # not part of the official Mozilla schema but # read by Mozilla: 'departmentNumber' and 'postOfficeBox' #
I finally found an article on Linux.com that briefly describes the process I just completed, including the challenges I encountered.